Synthesizer

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.

The output groups evidence into tentative claims, relations, contradictions, and proposed uses. Each proposal names its subject and receiving owner, exact proposed content or change, supporting and opposing source references, uncertainty, dependencies, and required review. A Persona-change proposal names its exact parent revision. A summary retains its derivation rather than becoming a substitute source.

The stage keeps three subjects distinct: the operator's preferences and history, the Lich'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

Settled Smith outputs may also enter Transmuter as attributed material for interpretation. Their authorship establishes no promotion or truth. Forge constructs packages and images; Soulforge 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.

Retries preserve fixed inputs and revision pins. Source changes or corrections create revised candidates and invalidates affected pending proposals. Past acceptances remain recorded; needed repairs are proposed to the responsible owner rather than silently rewriting its 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.