32. Identity

In plain words: Design rule 32: Personas and attribution

Designed 5 min read 19 glossary terms 11 connected pages
The short version written for the Snayu team

Defines the Persona Keeper (Mirror): it owns persona definitions and revisions, binds an exact persona version to a job, and keeps attribution between people and machinery. It does not authenticate users or grant permissions.

Why read it: Read this before adding personas, assistant identity or attribution of who did what.
  1. 1A job pins an exact persona revision, or records that none was chosen.
  2. 2Authentication and permissions belong to the Security Desk (Ward), not personas.
  3. 3Persona changes go through reviewed revision proposals, never silent self-editing.

Designed Chat uses a fixed agent spec today; no persona registry exists.

Words on this page, decoded click one for its card

The original text Underlined words open their plain-English card.

Context

MirrorPersona Keeper governs filtered, durable but revisable Persona bindings and their attribution. Those bindings must remain traceable when model processes end, work resumes, or a Persona revision changes. MirrorPersona Keeper is neither a hidden runtime nor evidence of continuous Cognizance.

The Answer develops the corresponding account of Ahaṃkāra and local identity.

Decision

MirrorPersona Keeper is LychD's singular identity-binding jurisdiction. It owns Persona definitions/revisions, an exact Persona revision binding when ana InvocationJob Request selects one, explicit absence when it selects none, scoped identity context and eligible memory hydration, hydration receipts, attribution across people and machinery, and reviewed Persona-revision proposals. It does not authenticate a Principal, grant scope, select model, schedule PatternWorkflow, evaluate quality or causal blame, or train weights; IAM/WardSecurity Desk, DispatcherTraffic Controller, SpellweaverWorkflow Engine, DriftEvaluator, and SoulforgeModel Trainer retain those offices.

Delivery boundary

MirrorPersona Keeper is Designed. Bridge currently binds a fixed The First One AgentSpec, static identity instruction, and loopback magus:* SigilID Badge. There is no Persona registry, revision lineage, identity-scoped ArchiveLong-term Memory, hydration receipt, congruence Trial SuiteApp Bundle, or self-revision path. Current SigilID Badge fields prove authority plumbing, not Persona continuity. State of Work owns delivery.

Keep the names apart

Name Question Owner
Principal Who initiated or approved? IAM
SigilID Badge Which bounded authority was active? WardSecurity Desk/IAM
Persona Which durable voice, commitments, and orientation shaped the Agent? MirrorPersona Keeper
AgentSpec Which executable cognitive/output/tool contract ran? Agent
Posture Which per-run settings and constraints applied? Pattern/Agent
CompositionApp / PatternWorkflow Which purpose and workflow admitted the act? CompositionApp/SpellweaverWorkflow Engine
Producer Which human, model, provider, tool, or adapter contributed? provenance owner

No value substitutes for another: Persona grants no authority; a Principal does not author every requested output; a provider is not Persona; shared Persona does not merge RunsJob Records. Present Sigil is a frozen name/scope set, without stable identity id, credential lineage, delegation relation, or revocation epoch; future MirrorPersona Keeper keys may not pretend Sigil.id exists.

Persona voice means declared discourse, commitments, manner, and orientation. It is not an acoustic voice profile, synthesized speech artifact, musical vocal, dubbed performance, or presentation asset. EchoVoice retains acoustic and speech-lifecycle facts; Riffmaw musical performance; Language Edition timed-language performance; and Avatar the eligible presentation selection that may reference any exact permitted artifact. Avatar's Morphe may select presentation style and an already eligible output locale; it cannot select or rewrite Persona discourse manner, translate text, or turn localized wording into identity.

Persona and binding

Each PatternWorkflow makes an explicit Persona choice: one exact revision or no Persona. The admitted RunJob Record retains that choice. Promoting a revision can redirect later work through a name, but cannot rewrite an existing RunJob Record's binding.

One Persona has a stable id and immutable revisions. Publication freezes a revision; editing produces candidate children. Each revision declares:

Concern Required content
Lineage Owner, provenance, parent, creation and lifecycle.
Identity Name, discourse voice, commitments, domain, non-goals, and protected terms and relationships.
Hydration Ordered instruction fragments, memory namespace and eligibility, and compatible Postures.
Review and change Required DriftEvaluator Trial SuitesApp Bundles; replacement, rollback, export and retirement law.

CodexSettings Folder owns declared intent. PhylacteryMemory Vault stores revisions, bindings, hydration receipts and attribution. When a Persona is selected, MirrorPersona Keeper compiles its contribution:

Persona revision + Pattern/AgentSpec requirements + active Principal/Sigil
+ eligible identity-scoped memory → ordered context blocks + hydration receipt

The receipt records source revisions, memory references, transformations and exclusions, ordering, size and truncation, and the envelope digest. It establishes what was supplied, not model obedience. Context owns token budgeting and final prompt assembly. WardSecurity Desk authorizes namespaces, tools and scopes; DispatcherTraffic Controller selects capability; OrchestratorStage Manager supplies readiness. More forceful identity instructions cannot replace any missing permission.

Identity memory is denied by default across Personas and Principals. Every record carries its namespace, producer, subject, provenance, eligibility and retention. Cross-identity recall needs explicit policy and retains source attribution.

Resume preserves the revision-pinned Persona binding and cites newly admitted memory. It does not silently replace the selected revision with the latest Persona.

Attribution and congruence

Attribution follows every identity-bearing InvocationJob Request or artifact. It records who initiated, approved, delegated, and acted, with the active SigilID Badge; exact Persona, AgentSpec, Posture, CompositionApp, and PatternWorkflow revisions; the exact InvocationJob Request identity; contributing models, providers, tools, sources, and humans; and parent, handoff, and artifact lineage. Each record declares whether it is an assertion, observation, evaluation, correction, or promoted act. Those relationships make the act traceable without deciding its quality, credit, fault, or causal blame.

At aan CompositionApp SuiteApp Bundle handoff, the immutable artifact retains its original attribution. The consumer starts a newly admitted child InvocationJob Request with its own binding. Handoff and correlation receipts convey neither authority nor authorship. Delegation names both principals and uses the delegate's producer identity and grant. Edits and rejected branches add to lineage rather than laundering it.

DriftEvaluator keeps the author and subject of findings and corrections. MirrorPersona Keeper binds that history; DriftEvaluator owns verdicts and attribution candidates; SoulforgeModel Trainer independently admits any training use.

A Persona may supply DriftEvaluator with criteria for commitments, voice boundaries, role limits, memory claims, tool behavior and response to pressure. Congruence measures one property of that Persona; it does not establish truth or general quality. A designed Phantasma PatternWorkflow may request bounded ShadowWhat-if Simulator branches and a versioned Persona-congruence Trial SuiteApp Bundle. MirrorPersona Keeper cannot select whichever resemblance it prefers.

Matched controls distinguish continuity from slogans, mimicry, refusal and leakage. Changes to authority language, tools, memory policy or core commitments rerun affected adversarial and regression evidence. A punctuation change need not rerun every Trial SuiteApp Bundle.

Revision and recovery

Experience can motivate a revision proposal. Changing the promoted definition still requires the reviewed passage below:

attributed observations/findings → bounded diff against exact parent → validation
→ Drift congruence/regression evidence → required Magus/HitL decision → immutable child

Smith may draft or package a candidate and SpellweaverWorkflow Engine may coordinate the work; publication stays with MirrorPersona Keeper. Repetition, praise, model confidence and memory volume grant no additional scope, tool, trigger, queue position or hardware priority.

Rollback directs future InvocationsJob Requests to a prior promoted revision and leaves earlier RunsJob Records and artifacts intact. A static prompt supplies none of the required binding, scoped memory, receipt, lineage or rollback. Retrieval provides hydration input, while behavioral resemblance can support at most aan DriftEvaluator finding. Automatic self-revision is refused because it bypasses the attributable reviewed passage.

Consequences

Accepted

Persona, authority, execution configuration, memory, and authorship remain distinguishable; future continuity is revision-pinned, attributable, reviewable, and reversible.

Cost

Revision/attribution propagation, explicit memory eligibility, and calibrated congruence Trial SuitesApp Bundles add storage and latency, and rich lineage often leaves credit or fault unresolved.

Acceptance evidence

MirrorPersona Keeper remains Designed until a Persona is declared, revision-pinned to a RunJob Record, hydrated from an authorized namespace with reproducible receipt, fully attributed, resumed with its pinned revision intact, tested against matched congruence controls, revised through an immutable candidate, and rolled back for new InvocationsJob Requests. State of WorkWhat Actually Works records that transition.