Mirror

In plain words: Persona keeper and attribution

Designed 2 min read 6 glossary terms 13 connected pages
The short version written for the Snayu team

The planned identity area (Persona Keeper, or Mirror) that records which exact persona version, caller, authority and contributors stand behind each act, and how agents are prepared with that identity.

Why read it: Read this before adding personas, agent identity prompts, or attribution of who produced an artifact.
  1. 1Every Job Request records an exact persona revision or an explicit no-persona choice.
  2. 2Caller (Principal), producer, agent step, persona and run are distinct names; attribution is not authorization.
  3. 3Today only a fixed 'The First One' agent and static identity text exist.

Designed No revisioned personas or reproducible identity preparation yet.

Words on this page, decoded click one for its card

Plug-in AreaPersona Keeper
Where it sits in LychD

Persona Keeper Mirror

Keeps track of the assistant's personality profiles and who did what.

It's like: An HR file with version history.

Click a dot to open that part's card.

Glossary page In the network
The original text Underlined words open their plain-English card.

A temporary Agent finishes its step; the act outlasts it. MirrorPersona Keeper keeps the act and its contributors bound to an operative identity, so a later reader can ask who spoke, under whose authority, and through which revision. Every admitted InvocationJob Request records an exact Persona revision or an explicit no-Persona choice under Identity.

MirrorPersona Keeper remains Designed. The fixed The First One AgentSpec, static identity instruction, and loopback magus:* SigilID Badge demonstrate current Agent and authority plumbing. They do not yet supply revisioned Personas or reproducible hydration; State keeps that delivery boundary.

The mirror and the Mirror

The lowercase mirror is the contemplative image of mind. Capitalized MirrorPersona Keeper keeps Persona lineage and attribution in their technical home.

I. The Answer / Ahaṃkāra

Answer binds the focal “I.” Answer and The EGO develop identity, attachment, and Corruption. MirrorPersona Keeper records the exact identity binding through which an act becomes attributable.

II. The Names in the Glass

Begin with the request: the Principal initiated or approved it, and the active SigilID Badge records the bounded authority. The principal may differ from the human or machine producer that contributed the result. Asking for work does not make every contribution one's own.

Then identify the performance. The Agent is one typed cognitive step; AgentSpec defines its executable contract, and Posture constrains the particular act. Pattern and InvocationJob Request identify the admitted workflow performance; RunJob Record supplies its durable execution identity. Agents owns Agent and Posture semantics; Spellweaver owns PatternWorkflow and InvocationJob Request law. The identity distinctions keep these bindings exact.

An act may also be shaped by a Persona: a durable, revisioned voice, commitments, boundaries and orientation. It is neither the caller nor the producer nor the temporary step. Here voice means discourse and manner; acoustic voice, music, timed-language editions and presentation assets retain their separate owners. Eligible identity-scoped memory may enter hydration.

III. Attribution Without Laundering

Follow an artifact through two applications. Its first attribution envelope distinguishes the initiating and approving principals from delegate or actor, Persona, AgentSpec, Posture, SigilID Badge, exact workflow revisions, human and machine producers, sources, tools, and handoffs. When a second application consumes it, the original producer remains on the artifact. The consumer opens its own separately admitted InvocationJob Request and binding. Selection cannot rewrite origin: human edits and rejected branches retain their authorship as well.

A spotless MirrorPersona Keeper keeps provenance clear enough to show the stain: exact origins and revisions, ruptures, contradictions, corrections, and rejected branches remain visible. Clarity never requires erasing a difficult part of the lineage.

Attribution alone establishes no authorization, truth, quality, credit, or fault. Ward owns authentication and authorization; Drift supplies evaluated findings. Identity continuity rests on exact revision lineage and reproducible binding. An enduring process, generic workflow continuity, memory, resemblance, or a reputation for trust cannot substitute for them.

IV. Summoning and Hydration

To prepare an Agent, hydration takes the Persona revision pinned by the admitted PatternWorkflow—or its explicit no-Persona choice—and combines it with PatternWorkflow and AgentSpec requirements, active Principal and SigilID Badge, and eligible identity-scoped memory. It produces ordered identity ContextBriefing Pack within bounds and a receipt recording that construction. Fresh and resumed Agents keep the pinned revision. Resemblance to yesterday's voice cannot supply the missing binding.