Purpose
Alpavo is a local-first workspace for creating a reusable AI persona or story character. It turns character intent into a portable, editable identity card rather than locking it inside a single chat product.
The first release is intentionally narrow: create and manage multiple personas, preview their exact prompt, define an appearance recipe, keep version snapshots, and export or import a documented format.
Portable schema
Schema version 1 records a stable persona identifier, name, purpose, tone, background or world, opening line, dialogue examples, response boundaries, appearance recipe, timestamps, and version number. An export contains the live persona plus its local snapshot history.
The JSON schema identifier is https://alpavo.app/schemas/persona/v1. Markdown export is a human-readable prompt. Both are general formats; an external model or platform may interpret, truncate, or reject fields differently.
Versions and verification
Saving creates a new snapshot instead of silently rewriting the previous one. Each snapshot and export receives a SHA-256 digest calculated from canonicalized content.
A hash can verify that content still matches a recorded digest. It cannot independently prove who authored the content, whether the content is true, or whether the user has legal or intellectual-property rights to it.
Import verification fails when the bundle body or a historical snapshot is changed without recalculating its digest. Verification does not scan the character for truth, safety, originality, or third-party compatibility.
Appearance recipe
The card preview uses deterministic browser styling: a palette, layout style, and accessory marker. It is a visible local composition, not a generated image. Alpavo does not claim that a model created or approved the preview.
The recipe travels with the persona so another implementation can map the same intent to its own visual system. Pixel-identical rendering is not promised.
Wallet association
Wallet connection is optional and read-only. It requests the user-selected public address and active chain ID only. Connecting does not ask for a message signature, token approval, or transaction.
Three contract actions are separate from connection: publish a saved persona version, record fork lineage, and purchase an optional export pass. Before opening the wallet, Alpavo shows the exact role, method, arguments, wallet, network, target, calldata, and value. The first two transfer zero BOT. The pass transfers exactly 0.01 BOT and never gates local file export.
Contract receipts and recovery
PersonaVersions anchors the canonical hash of a saved snapshot; ForkLineage records a child's parent version and a hash of the stated reason; ExportPass records an optional wallet/persona pass. These public records do not establish identity, authorship, factual truth, or legal rights.
Local history distinguishes awaiting-wallet, pending, confirmed, failed, and recovery states. Confirmation requires a successful receipt plus an exact match against the original sender, target, calldata, value, and block evidence. Pending records can be checked again after a reload, and valid transaction hashes link to the public BOT Chain Explorer.
Data flow and privacy
Persona content, version history, and proof receipt history are stored in the browser. Export is initiated by the user. Import reads a selected local JSON file and verifies its digest before adding an independent persona.
The MVP has no character chat backend and no live AI model credential. Static hosting and basic operational analytics may process ordinary request metadata as described in the Privacy Policy.
Safety and limitations
Users remain responsible for reviewing prompts, respecting third-party rights, avoiding sensitive personal data, and checking the policies of any external tool. Response boundaries are instructions inside the persona, not a technical guarantee that another model will comply.
Alpavo does not guarantee availability, interoperability, uniqueness, factual accuracy, safety outcomes, financial value, or continued support for a particular external tool.
Roadmap
Near-term work may include a published JSON Schema document, local diff views, encrypted backup, additional appearance-recipe adapters, and independent contract audits. Later research may explore consent-aware collaboration and platform adapters.
Roadmap items are intentions, not commitments. Any live model or new contract integration requires explicit configuration, security review, deployment evidence, and honest status reporting before release.