Synthesizer
In plain words: Transmuter: Synthesizer stage
The stage that relates extracted units to dates, purposes and existing knowledge, groups them into claims and contradictions, and prepares reviewable proposals for memory, persona or training.
- 1Keeps three subjects apart: the operator's preferences, the Assistant's persona, and dated facts.
- 2Repetition cannot turn a model's interpretation into an endorsed preference.
- 3Each proposal names its receiving owner: Long-term Memory, Persona Keeper, Model Trainer or Smith.
Designed Proposed responsibility only.
Words on this page, decoded click one for its card
An old conversation asks for brief answers; a later project calls for detailed explanations. Synthesizer would relate those statements to their dates and purposes, preserving both until evidence or review supports a scoped preference. It is the interpretation and synthesis stage of the Transmuter candidate, working from Extractor outputs.
Compare and propose
Each synthesis attempt pins the selected extracted units, explicitly authorized comparison material, purpose, target namespaces, synthesis implementation and configuration revisions, and resource limits. Missing authorization excludes the comparison source or destination. Similarity does not grant access to another person's or Persona's records.
Group the selected evidence into tentative claims, relations, contradictions, and proposed uses. A reviewer must be able to assess each proposal on its own: name its subject and receiving owner, exact proposed content or change, supporting and opposing source references, uncertainty, dependencies, and required review. A Persona-change proposal also names its exact parent revision. Keep a summary's derivation available so the summary never substitutes for the source.
The stage keeps three subjects distinct: the operator's preferences and history, the LichAssistant's Persona and commitments, and dated facts about devices or software. A model-generated description of the operator remains that model's interpretation. Repetition cannot turn it into an endorsed preference. Material may remain a source-linked knowledge candidate without any request to change memory or identity.
Receiving owners
| Proposed use | Receiving decision |
|---|---|
| Retain or correct a memory | Archive owns Memory admission, curation, and recall eligibility. |
| Revise the LichAssistant's Persona | Mirror owns the reviewed revision and its publication. |
| Nominate material for training | Soulforge independently admits a corpus and any later training. |
| Request a missing parser, tool, or code candidate | Smith supplies candidate authorship through a separately admitted exact application contract. |
Settled Smith outputs may also enter Transmuter as attributed material for interpretation. Their authorship establishes no promotion or truth. Forge constructs packages and images; SoulforgeModel Trainer owns training. Neither code activation nor weight promotion follows automatically from synthesis. This study specifies these proposed handoffs without publishing executable contracts for them.
Account for the result
The dossier links each fixed proposal to its handoff and the receiving owner's outcome. Local synthesis may finish while memory is accepted, a Persona change is refused, and training was never requested. An unknown downstream effect remains unknown until reconciled with that owner; a missing receipt is not permission to repeat the effect.
Retry an attempt against its fixed inputs and revision pins. If a source changed or was corrected, prepare a revised candidate and invalidate the affected pending proposals instead. Earlier acceptances remain in the record. Any repair they need must be proposed to the responsible owner, which retains authority over its own history.
Budget exhaustion retains completed proposals and identifies unfinished work. Cancellation stops new synthesis and handoffs while preserving committed effects. Resumption must reconcile recorded uncertainty and recheck authority before further work. The exact executable recovery contract remains acceptance work under Workflow.