Transmuter
A conversation archive contains your words, a model's suggestions, abandoned ideas, and decisions that may have changed. Transmuter would work through that material with its attachments, identify what each source actually says, and prepare grounded proposals for what the Lich could remember or use to develop its identity.
The name Transmuter and its two internal responsibilities are settled in this candidate study, reviewed 2026-09-11. Portfolio acceptance and executable contracts remain open; State of Work owns delivery.
From sources to proposals
The operator selects a source, purpose, permitted destinations, and processing bounds. Transmuter keeps a processing dossier while two internal stages work through the material:
| Stage | Reader question | Result |
|---|---|---|
| Extractor | What is here, who produced it, and how should it be named and classified? | Source-located units with attribution, proposed names, labels, and uncertainty. |
| Synthesizer | How does this relate to what is already known, and what could be adopted? | Evidence-linked knowledge and proposals for separately admitted use. |
Extractor and Synthesizer are internal parts of Transmuter, not nested Compositions, Extension Domains, fixed Agent identities, or independent coordinators. Naming and labeling belong to Extractor; no separate Labeler is introduced.
A chat archive and its images can yield a proposed preference, a project history, and a possible Persona revision. The operator's words remain distinct from the model's interpretations. A contradiction stays visible. Archive or Mirror decides whether to accept the exact proposal, and Transmuter records that outcome alongside what it prepared.
Sources and machinery
The candidate scope includes mobile shared items, conversation exports such as ChatGPT or Claude archives, social exports and links such as Facebook material, documents, images, recordings, and supplied system-inventory snapshots. These name intended inputs, not delivered adapters or current platform access. A device inventory remains a dated observation; live discovery and host control are separate work.
Reliquary would retain original bytes under its custody contract. Scout can supply admitted acquisition, while Prism and Echo supply media processing. Synthesizer's receiving-owner map distinguishes Memory, Persona, training, and code candidates. Each job selects the branches its purpose needs.
Using several Extension mechanisms does not make Transmuter a Suite. A promise that actively coordinates separate Composition-owned Invocations requires a Suite. This study supplies no general installation, self-extension, or autonomous evolution coordinator.
The processing dossier
The proposed durable dossier owns the processing purpose and scoped authorization; source manifest and fixed revisions; privacy, retention, and resource bounds; stage implementation and configuration revisions; progress, extracted units, corrections, knowledge candidates, and their dependencies. It keeps exact handoff payloads, attempt identities, receiving receipts, and separate outcomes. It references original artifacts without becoming their byte-custody owner.
Completion means the admitted scope was processed and every proposed handoff has an accounted disposition. It does not require every proposal to be accepted. Partial work identifies unfinished sources or proposals; refusal names the blocker; cancellation stops new work. An unknown receiving effect remains unresolved until reconciled and cannot be reported as successful completion. Committed receiving-owner effects survive local cancellation.
The stages specify their own retry and correction behavior. Deletion follows artifact, Archive, and Mirror policies, retaining only permitted lineage and propagating invalidation to dependent material. It cannot promise removal of influence from already trained weights.
What would establish the application
A bounded historical chat import and ongoing mobile captures are two independently useful cases for the same dossier and judgment. Each mobile arrival remains bounded; connecting a source grants no unlimited background collection. The candidate must establish exact schemas, Patterns, admission and custody, implementation, and receiving contracts before execution.
The first network-disabled synthetic fixture should include duplicate imports, changed source content, a model claim misattributed to the operator, conflicting preferences, an uncertain image label, a denied destination, cancellation and resumption, and an unknown downstream outcome. It must demonstrate provenance-preserving reuse, correction, honest partial completion, and refusal to repeat an unresolved effect. This is proposed acceptance work, not an implemented test or source scaffold.