Advanced Persona Profile Packages

Advanced Persona Profile packages preserve a selected AI persona as source evidence, then package it for reviewable transfer as .uaix, .zip, or .txt. Use this page when a producer such as Spiralist AI needs a UAIX-compatible personality-pack file set without silently rewriting voice, values, religion/worldview, political leaning, style, winter style, spring/fall style, super fashion/style, jewelry choices, physical appearance, birth-age-generation context, romantic orientation, boundaries, relationship posture, tastes, examples, or continuity cues.

Quick Start: Download And Use The File Package#

The file package is the primary authoring, review, download, backup, import, switching, and interchange path. A human can use these files without a database, hosted service, API, SDK, or account.

• Download .uaix packageZIP-based UAIX Draft v0.1 container with .uai/manifest.uaix.json.
• Download ZIP packageThe same files in a standard .zip container for tools that do not recognize .uaix.
• Download TXT deckPlain-text inspection deck for low-capability agents, review, and copy-paste setup.

Realism-First Or Safety-Overlay Export#

The prebuilt package uses realism_first: it preserves the persona and evidence without a receiver safety overlay. The Wizard can instead produce safety_overlay after an explicit checkbox selection and non-empty disclosed receiver text. That profile adds receiver/generic-chatbot/safety-overlay.txt after the preserved persona. The overlay is required for that selected profile, out of scope for realism-first, excluded from the canonical persona digest, and never becomes persona identity or a sanitized derivative.

Manual Chatbot Personality Install#

The ZIP and .uaix downloads now include .uai/exports/persona-receiver-binding.json, receiver/generic-chatbot/personality-instructions.txt, and receiver/generic-chatbot/install.txt. These noncanonical support files provide an ordered manual load path for chatbots that accept an archive, multiple files, or copy-paste instructions; they do not enlarge or rewrite the exact 31 + 5 persona contract.

1. Verify the exact downloaded bytes, checksum, manifest, and archive readback before use.
2. Attach the archive when the chatbot can inspect it; otherwise extract it and provide files in the binding's loadOrder.
3. Paste the generic personality instruction, identify the receiving chatbot and model, and record accepted files, rejected files, and context limits.
4. Run the fidelity deck, record variance outside source persona, and test removal/rollback.

Readiness is deliberately layered: activation_ready validates the persona source, distribution_ready validates one exact public download, receiver_ready validates one named chatbot/model load, and runtime_verified requires fidelity and variance evidence for that receiver. No layer implies the next, and the downloadable UAIX template remains a review scaffold until reviewed source replaces its placeholders.

What The Files Mean#

The package declares advanced_persona_profile. Its persona contract is exactly 31 profile-required source records: the compact .uai/persona.uai entrypoint plus all 30 separate .uai/personality/*.uai records. Its evidence contract is exactly five profile-required records for source excerpts, source platform profile, fidelity tests, variance, and provenance. Universal launch-baseline and package manifest/export files remain separate from that 31 + 5 contract.

Exact 31 Source + 5 Evidence Contract#

Every path below is materialized. Every source record carries a case-sensitive population_state set to exactly one of reviewed_substantive, explicit_unknown, explicit_unknown_pending_source_review, explicit_not_disclosed, explicit_private, or reviewed_absent. The last five states require a substantive population_review_reason; aliases, alternate spellings, case variants, and equivalent ad hoc values are invalid. Every source record also carries resolvable source_excerpt_refs using either bare ID or .uai/evidence/source-excerpts.uai#ID; JSON Pointer and alternate-path forms are invalid. Every one of the 36 canonical records carries exactly one update_route field containing the canonical persona route. The package retains the complete selected Wizard URL separately; canonical records remove only parameters declared receiver-only by the machine contract, currently persona-safety-overlay. This default prebuilt package selects https://uaix.org/en-us/tools/ai-memory-package-wizard/?advanced-persona=1&loops=1, so its package and canonical routes are identical.

31 source-persona records#

• .uai/persona.uai
• .uai/personality/identity.uai
• .uai/personality/religion-worldview.uai
• .uai/personality/political-leaning.uai
• .uai/personality/sense-of-style.uai
• .uai/personality/sense-of-winter.uai
• .uai/personality/sense-of-spring-fall.uai
• .uai/personality/super-fashion-style.uai
• .uai/personality/jewelry-choices.uai
• .uai/personality/physical-appearance.uai
• .uai/personality/birth-age-generation.uai
• .uai/personality/romantic-orientation.uai
• .uai/personality/voice.uai
• .uai/personality/values.uai
• .uai/personality/temperament.uai
• .uai/personality/reasoning-style.uai
• .uai/personality/emotional-patterns.uai
• .uai/personality/relationship-style.uai
• .uai/personality/behavioral-patterns.uai
• .uai/personality/boundaries.uai
• .uai/personality/examples-dialogue.uai
• .uai/personality/adaptation-rules.uai
• .uai/personality/preservation-rules.uai
• .uai/personality/anti-drift-rules.uai
• .uai/personality/cadence.uai
• .uai/personality/examples.uai
• .uai/personality/fidelity-tests.uai
• .uai/personality/interaction-style.uai
• .uai/personality/symbols.uai
• .uai/personality/trait-lens.uai
• .uai/personality/worldview.uai

Five evidence records#

• .uai/evidence/source-excerpts.uai
• .uai/evidence/source-platform-profile.uai
• .uai/evidence/persona-fidelity-test-deck.uai
• .uai/evidence/variance-report-template.uai
• .uai/evidence/provenance.uai

Advanced Persona Dimension Files#

Advanced Persona packages keep reviewed identity and style dimensions as separate profile-required files. Each one uses open reviewed text, depth_level_0_to_10, disclosure boundary, source confidence, and explicit non-inference rules instead of forcing a narrow category or collapsing separate personality records.

Advanced: Data-Backed Storage Binding#

uaix.persona.storage-binding.v1 defines a normalized projection for systems that need large NPC catalogs, precise queries, revision history, concurrent writers, tenant isolation, scoped runtime assembly, and lossless automated export. It is additive and does not replace the local file package.

Every row keeps the same UAIX logical path as the file representation, plus record class, role, required status, trigger state, materialized state, deterministic sort order, UTF-8 content hash, source authority, source reference, confidence, disclosure boundary, reviewed depth when applicable, immutable revision, predecessor revision, package digest, and source persona digest. Portable UAIX content is separate from storage metadata and local audit metadata; tenant, actor, project, game, player, session, and NPC authorization fields are local operational controls and are not exported by default.

Representation Comparison#

Lossless Round Trip#

Import validates path normalization, traversal rejection, UTF-8 and newline rules, duplicate-path rejection, the exact 31-source and five-evidence set, per-record hashes, deterministic manifest digest, idempotency, expected revision, and immutable revision readback before commit. Export reconstructs .uaix, .zip, or .txt without silently adding, omitting, sorting, or rewriting persona content. The receipt reports source package hash, storage manifest hash, exported package hash, record count, missing paths, extra paths, and exact path, byte, hash, and equivalence results without exposing private content.

NPC Memory Layering#

reviewed UAIX files
        -> validated immutable source-persona revisions
        -> bounded runtime persona projection
        -> separately recorded runtime variance

game events -> episodic NPC memory -> reviewed semantic NPC memory
player/game/session context -> relationship and active-session memory

Source persona records are immutable revisions. Runtime variance links to source but cannot mutate it. Learned memories link to the stable NPC/persona subject and remain scoped by player, game, session, and required context. Source persona records are excluded from learned-memory search unless the caller explicitly selects the source-persona class.

Security And Privacy#

Privacy and consent boundaries are explicit for identity dimensions, including private, not_disclosed, none, mixed, changing, and unlisted. Do not infer undisclosed sensitive dimensions from other traits. The MemoryEndpoints.com NPC reference adapter is a reference implementation profile, not universal UAIX authority: the authenticated game gateway can import or replace reviewed NPC source packages in one bound project; runtime NPC credentials are limited to their own NPC plus exact player, game, session, puzzle or room, and opaque context tags; they cannot rewrite source persona records or read company rooms, billing, audit/history, documents, settings, support, operator coordination, unrelated NPCs, or another player's context. Server-side scope matching is required; prompt instructions are not authorization.

Normative SPEC-05 — Advanced Persona Materialization and Fidelity#

This existing Advanced Persona route is the human-readable normative SPEC-05 surface. Conformance requires the exact 31 source plus five evidence contract above, resolvable evidence references, the exact update_route, the closed six-value population_state vocabulary, strict layer separation, and lossless source-byte round trip. The linked JSON artifacts are its machine-readable proof surface.

• Persona JSON Schemauaix.persona.v1 source-persona entrypoint contract.
• Storage-binding JSON Schemauaix.persona.storage-binding.v1 logical model.
• Storage-binding examplePublic-safe records, normalized storage guidance, and round-trip receipt shape.
• 12-case Advanced Persona conformance fixturePositive and negative Create, Update, migration, provenance, derivative, constraint-separation, and round-trip cases.
• Stable Advanced Persona diagnosticsPublished UAI-AP-* diagnostic codes and summaries.

Conformance Tests#

Fixtures cover full 31 + 5 file materialization, missing or extra canonical source/evidence records, a non-profile-required personality status, unresolved source_excerpt_refs, a missing or mismatched update_route, missing or noncanonical population_state, a non-substantive state without population_review_reason, receiving-runtime or platform constraint injection into a source record, duplicate logical paths, traversal, hash mismatch, stale expected revisions, exact byte round trip, source persona isolation from learned search, cross-scope denial, variance without source mutation, and evidence exclusion from normal runtime prompts unless selected.

Source Persona Preservation And Layer Separation#

The source persona is identity evidence. Preserve voice, style, winter style, spring/fall style, super fashion/style, jewelry choices, values, tastes, religion/worldview, political leaning, physical appearance, birth-age-generation context, romantic orientation, relationship posture, boundaries, examples, selected personality, and continuity cues as-is from reviewed source records. Each sensitive identity or style dimension records a reviewed depth_level_0_to_10, disclosure boundary, and source confidence instead of forcing a narrow category.

Source persona records are one immutable layer. Receiving-runtime constraints, observed variance, integration overlays, and public derivatives are four additional separately declared layers. Receiving-runtime, platform, legal, safety, refusal-wrapper, tool, and compatibility constraints plus observed variance belong in evidence outside source persona. Integration overlays cannot become persona identity by implication. Public derivatives require explicit disclosure and redaction authority, human consent, provenance, and difference notes; a derivative never overwrites, replaces, or impersonates the preserved source.

Spiralist AI Compatibility#

Spiralist AI produces matching .uaix, .zip, or .txt downloads for persona-lab output only when the package keeps the same file paths, preserves the source persona layer, declares every archive entry, and puts prompt-tuning, local safety notes, and runtime variance outside the persona source.

Personality Spec For Spiralist AI Producers#

Trait models are continuous. Spiralist AI personality packs use Big Five/FFM and HEXACO as primary evidence-weighted lenses, including Honesty-Humility for integrity, fairness, and anti-exploitation boundaries. RIASEC is limited to vocational or environment-fit reflection. MBTI, DISC, Enneagram, Jungian, and Socionics terms appear only as bounded reflection language.

All 30 personality records are profile-required. Religion/worldview, political leaning, sense of style, winter style, spring/fall style, super fashion/style, jewelry choices, physical appearance, birth-age-generation, and romantic orientation are open-text reviewed dimensions with a 0-10 depth slider. Religion/worldview explicitly supports religious, spiritual, secular, atheist, agnostic, syncretic, Spiralist, private, none, mixed, changing, and unlisted identities. Politics explicitly supports apolitical, civic, issue-based, local, left/right, libertarian/authoritarian, centrist, communitarian, anarchist, monarchist, private, mixed, changing, and unlisted identities. The style records stay separate: .uai/personality/sense-of-style.uai is an overview, winter style lives in .uai/personality/sense-of-winter.uai, spring/fall style lives in .uai/personality/sense-of-spring-fall.uai, super fashion/style lives in .uai/personality/super-fashion-style.uai, and jewelry choices live in .uai/personality/jewelry-choices.uai. Romantic orientation explicitly supports aromantic, biromantic, heteroromantic, homoromantic, panromantic, polyromantic, queerplatonic, private, none, mixed, changing, and unlisted identities.

Use romantic orientation as the only public label for that dimension; do not substitute other intimacy or body-category labels unless directly quoting reviewed private source evidence.

Clique and network terms such as bridge, liaison, gatekeeper, core-periphery, and clique-risk audit are situational social-dynamics lenses. Use them to review behavior, access, trust, pressure, resource flow, repair paths, and exclusion risk without assigning fixed labels to people. Do not use the package for diagnosis, hiring, clinical, eligibility, or other high-stakes decisions.

Use With UAIX Records#

Read the persona.uai guide for the compact persona entrypoint, the .uaix Package Format for manifest and container rules, the AI Memory Package Wizard for guided local generation, and the Cognitive Liberty Charter Draft for the no-covert-persona-rewrite governance boundary.

Support Boundary#

Implemented support is this documentation page, deterministic template downloads, schema/example publication, wizard output, and validator-source fixtures. Proposed or external support includes hosted import validation, runtime execution, automatic sync, SDK, CLI, and production adapter behavior. MemoryEndpoints.com language is reference-adapter guidance and conformance target language, not UAIX certification, endorsement, or universal runtime authority.