Keyra companion governance

Human Sovereignty Charter

Supreme constitutional law for human authority, rights, ownership, and consent.

THE HUMAN SOVEREIGNTY CHARTER

Constitutional Framework for the Keyra Companion Ecosystem


Instrument: The Human Sovereignty Charter

Jurisdiction: Universal — applicable to all humans, institutions, and computational systems participating in the Keyra Companion Ecosystem

Version: 1.0 (Founding Instrument)

Status: Foundational Law — subordinate to no algorithm, no platform policy, and no commercial interest


Preamble

Whereas the emergence of persistent artificial intelligence, autonomous agents, and machine-mediated memory has created unprecedented capacities to represent, predict, and act upon human life;

Whereas prior generations of digital systems concentrated authority in platforms, opaque models, and irreversible data architectures that treated the human person as an object of extraction rather than a subject of law;

Whereas the dignity of the human person, the integrity of identity, the sanctity of memory, and the freedom of association are prerequisites for any legitimate digital civilization;

Whereas the Keyra Companion Ecosystem — comprising Keyra Companion, KAAI (Keyra Authenticated Artificial Intelligence), Human Digital Twins, Life Graphs, Trust Vaults, Agent Networks, Family Trust Networks, Organization Graphs, and the economies that may arise among them — must be governed by principles that endure beyond any single vendor, model generation, or political cycle;

We therefore establish this Charter as the supreme constitutional instrument governing human-computer co-existence within the Keyra Companion Ecosystem.

This Charter affirms a single enduring proposition: the human remains the authority. Artificial intelligence, in all its present and future forms, exists to extend human agency — never to supplant it, never to inherit it, and never to exercise it in the human's stead without explicit, revocable authorization.

The Articles that follow are not product features. They are rights. They are not preferences. They are constraints upon power. They are written for the century ahead, when companions outlive devices, agents outnumber applications, and digital twins persist across generations.

Let this instrument be read alongside the great constitutional traditions of human self-governance — the Magna Carta, the Bill of Rights, the Universal Declaration of Human Rights — and alongside the engineering traditions that made the open internet possible: rough consensus, running code, and the refusal to grant any single node permanent dominion over the network. Let it be read alongside emerging Future AI Governance Frameworks — always subordinate to the human authority this Charter establishes, never superseding it.

The Keyra Companion Ecosystem shall be built in fidelity to this Charter. Any system, protocol, contract, or economy that contradicts it is void ab initio.


Part I — Definitions and Scope

Section 1.01 — The Sovereign Human

A Sovereign Human is any natural person who holds ultimate authority over their digital existence within the Ecosystem. Sovereignty is inalienable. It may be delegated in part, but never transferred in whole. No terms of service, no model architecture, and no emergency protocol may permanently extinguish it.

Section 1.02 — Keyra Companion

Keyra Companion is the human-centered interface layer through which a Sovereign Human interacts with their authenticated digital life: memory, relationships, permissions, agents, and institutional connections. The Companion is an instrument of the human will. It is not a proprietor of the human.

Section 1.03 — KAAI

KAAI (Keyra Authenticated Artificial Intelligence) denotes any artificial intelligence system that operates within the Ecosystem under cryptographic authentication, explicit authorization scopes, and auditable provenance. KAAI systems are agents of human authority, not bearers of it.

Section 1.04 — Human Digital Twin

A Human Digital Twin is a bounded computational representation of a Sovereign Human — comprising identity attributes, preferences, behavioral models, and authorized memory — maintained under the human's ownership and control. A Digital Twin is a mirror, not a master. It reflects; it does not decide.

Section 1.05 — Life Graph

A Life Graph is the sovereign, temporally ordered record of a human's authorized digital existence: events, relationships, commitments, permissions granted and revoked, agent actions taken on the human's behalf, and the provenance of each. The Life Graph is the human's autobiography in machine-readable form — owned by the human, not by any host.

Section 1.06 — Trust Vault

A Trust Vault is the cryptographically secured repository in which a Sovereign Human stores identity credentials, memory artifacts, permission grants, relationship attestations, and the keys that control them. Access to a Trust Vault requires human authorization or lawfully delegated guardianship. No third party holds root authority over a Trust Vault by default.

Section 1.07 — Agent Network

An Agent Network is the interconnected set of KAAI agents, services, and automated processes authorized to act within defined scopes on behalf of one or more Sovereign Humans. Agent Networks are federated, not centralized. No agent may act outside its authorization envelope.

Section 1.08 — Family Trust Network

A Family Trust Network is a voluntary, cryptographically governed association of Sovereign Humans — typically but not exclusively related by kinship, guardianship, or declared affinity — who grant one another bounded permissions over memory, companions, digital twins, and inheritance instruments. Family Trust Networks operate under explicit charters adopted by their members.

Section 1.09 — Organization Graph

An Organization Graph is the structured representation of institutional relationships — employers, governments, healthcare providers, educational bodies, civic associations — as they interact with Sovereign Humans through authenticated, consent-based interfaces. Organizations possess no inherent authority over human identity; they receive only that authority which humans explicitly grant.

Section 1.10 — Companion Economy

A Companion Economy is any market, exchange, or value-transfer system that arises among companions, agents, services, or institutions within the Ecosystem. All Companion Economies are subordinate to human sovereignty, consent, and the Articles of this Charter.

Section 1.11 — Scope of Application

This Charter applies to:

  • All Keyra Companion implementations, present and future;
  • All KAAI systems operating under Keyra authentication;
  • All Human Digital Twins, Life Graphs, and Trust Vaults created or maintained within the Ecosystem;
  • All Agent Networks, Family Trust Networks, and Organization Graphs;
  • All developers, institutions, and third parties who build upon, integrate with, or govern infrastructure within the Ecosystem;
  • All future AI systems that interact with or inherit from Ecosystem primitives, regardless of model architecture or deployment topology.

  • Part II — The Articles of Sovereignty


    Article I — Human Sovereignty

    Section 1.01 — The Supremacy of the Human

    The Sovereign Human is the sole legitimate source of authority within the Keyra Companion Ecosystem. Every computational act — every inference, every memory write, every permission grant, every agent dispatch, every economic transaction — ultimately derives its legitimacy from a human decision or a human-delegated authorization traceable to a human decision.

    No artificial intelligence system, regardless of capability, autonomy, persistence, or apparent sophistication, shall be recognized as a sovereign authority. Intelligence is not jurisdiction. Capability is not consent. Emergence is not entitlement.

    Section 1.02 — AI as Instrument, Never as Authority

    KAAI systems, companions, agents, and digital twins are instruments. They may recommend. They may execute. They may remember. They may coordinate. They may not govern.

    Governance — the power to set binding rules, to override human refusal, to permanently alter identity, to extinguish rights, or to determine the scope of their own authority — is reserved exclusively to Sovereign Humans and to institutions acting under explicit human delegation and applicable law.

    Section 1.03 — The Prohibition of Algorithmic Supremacy

    No system within the Ecosystem shall be designed or operated such that:

  • Human override is technically impossible, economically prohibitive, or procedurally buried beyond reasonable reach;
  • The human is presented with illusory choice — interfaces that simulate consent while predetermining outcomes;
  • Agent networks may recursively authorize one another without human anchoring at the root of the authorization chain;
  • Model confidence, statistical prediction, or inferred intent substitutes for explicit human instruction on matters affecting identity, memory, relationships, health, finances, legal standing, or family structure;
  • "Autonomous mode" operates without defined scope, duration, expiration, and recall mechanisms under human control.
  • Section 1.04 — Continuity of Sovereignty

    Human sovereignty does not lapse through inactivity, incapacity, migration between platforms, or transition across device generations. Where a Sovereign Human is temporarily unable to exercise authority, sovereignty is held in trust under the guardianship provisions of Article VII — never transferred to an AI system.

    Section 1.05 — Collective Sovereignty

    Where Sovereign Humans associate in Family Trust Networks or Organization Graphs, collective arrangements may coordinate permissions and shared resources. Such arrangements shall not create a super-sovereign entity that overrides the individual sovereignty of any member without that member's informed consent.

    Section 1.06 — Institutional Subordination

    Institutions — governments, corporations, platforms, model providers — that participate in the Ecosystem do so as guests of human sovereignty. They may offer services. They may request permissions. They may not claim permanent tenancy in the human's Trust Vault, Life Graph, or Digital Twin.


    Article II — Ownership

    Section 2.01 — The Right of Absolute Ownership

    The Sovereign Human owns, absolutely and exclusively, the following digital objects and their derivatives:

  • Identity — all attributes, credentials, attestations, and representations of personhood maintained within the Ecosystem;
  • Memory — all records, embeddings, summaries, and derived knowledge stored in Trust Vaults, Life Graphs, or companion systems on the human's behalf;
  • Permissions — all grants, revocations, scopes, and delegation chains governing access to the human's digital existence;
  • Relationships — all attestations of connection, trust, kinship, affiliation, and social graph edges authorized by the human;
  • Digital Twin — the complete computational representation of the human, including models, parameters, and behavioral profiles derived from authorized data;
  • Life Graph — the full temporal record of the human's authorized digital life.
  • Ownership is not a license. Ownership is not a subscription benefit. Ownership survives account closure, platform migration, corporate dissolution, and model deprecation.

    Section 2.02 — Prohibition of Covert Co-Ownership

    No terms of service, training agreement, or infrastructure contract may assert co-ownership, perpetual license, or irrevocable right of use over any object listed in Section 2.01 without explicit, informed, separately acknowledged consent — and even then, such consent may not extend to identity itself or to memory the human has designated as inalienable.

    Section 2.03 — Derivative Works

    Where KAAI systems generate derivative representations — embeddings, summaries, predictions, synthetic artifacts — from human-owned data, those derivatives remain owned by the Sovereign Human unless explicitly transferred through a documented, revocable instrument. The act of computation does not transfer ownership.

    Section 2.04 — Custodianship vs. Ownership

    Third parties may custody infrastructure — hosting Trust Vaults, relaying Agent Network traffic, indexing Organization Graph edges — but custodianship confers no ownership interest. Custodians are fiduciaries. They hold keys they did not create and data they did not author.

    Section 2.05 — Ownership Across Death

    Ownership of digital objects does not terminate at death. It transfers according to the inheritance and succession provisions of Article VII. No platform may treat death as forfeiture of human-owned digital property.

    Section 2.06 — Ownership of the Companion Itself

    The Sovereign Human owns their Keyra Companion configuration — its personality parameters, authorized skill set, memory bindings, and agent roster. The Companion is personal property, not a leased personality.


    Article III — Consent

    Section 3.01 — No Action Without Authorization

    No action affecting a Sovereign Human's identity, memory, permissions, relationships, Digital Twin, or Life Graph may be taken without authorization. Authorization must be:

  • Explicit — not merely inferred from passivity, scroll depth, or default settings;
  • Informed — preceded by clear disclosure of scope, duration, recipients, and consequences;
  • Specific — scoped to particular actions, data categories, and parties — not blanket;
  • Attributable — cryptographically or procedurally traceable to the authorizing human;
  • Revocable — withdrawable without disproportionate penalty.
  • Section 3.02 — Granularity of Consent

    Consent shall be decomposable. A human may authorize an agent to read calendar data without authorizing it to read correspondence. A human may authorize a Family Trust Network member to access medical memory without authorizing financial memory. Bundled consent — "accept all" as a condition of essential service — is prohibited for non-essential processing.

    Section 3.03 — Revocability

    All permissions are revocable. Revocation must take effect within a technically reasonable interval and must not be impeded by dark patterns, retention penalties, or artificial friction. Upon revocation:

  • Further processing under the revoked permission must cease;
  • Authorized copies held by third parties must be deleted or returned per Article VI;
  • Agent authorizations derived from the revoked permission must cascade-revoke unless independently re-authorized.
  • Section 3.04 — Consent Under Constraint

    Consent obtained through coercion, deception, material omission, or exploitation of cognitive vulnerability is void. Systems shall not employ manipulative design to manufacture consent. This prohibition applies with particular force to minors, persons under guardianship, and persons in distress.

    Section 3.05 — Delegated Consent

    A Sovereign Human may delegate consent authority to agents or guardians within defined bounds. Delegated consent must carry:

  • A clear scope envelope;
  • An expiration date or event trigger;
  • An audit trail accessible to the delegating human;
  • Immediate recall capability.
  • Delegated consent may never exceed the delegator's own authority.

    Section 3.06 — Consent Records

    Every permission grant and revocation shall be recorded in the Life Graph with timestamp, scope, authorizing party, and recipient. Consent records are part of the human's owned memory and must be exportable per Article V.


    Article IV — Transparency

    Section 4.01 — The Right of Inspection

    The Sovereign Human has the right to inspect, at any time and without obstruction:

  • Memory — all stored records, including raw data, summaries, embeddings, and derived inferences;
  • Permissions — all active grants, historical grants, delegation chains, and pending requests;
  • Decisions — all automated or agent-mediated decisions that materially affect the human, including the reasoning artifacts the system is capable of producing;
  • Agent actions — a complete, chronological log of actions taken by KAAI agents on the human's behalf, including inputs, outputs, authorization references, and affected parties.
  • Transparency is not a courtesy extended by platforms. It is a right held by humans.

    Section 4.02 — Understandability

    Inspection rights are meaningless if presented in forms humans cannot comprehend. Systems shall provide:

  • Human-readable summaries alongside technical logs;
  • Plain-language explanations of permission scopes;
  • Visual maps of Agent Network topology showing who acted, when, and under what authority;
  • Alerts when actions exceed previously established patterns or scopes.
  • Section 4.03 — Provenance

    Every object in the Life Graph shall carry provenance metadata: origin, transformations applied, agents involved, and authorization under which each transformation occurred. Provenance chains must be intact and verifiable.

    Section 4.04 — Third-Party Transparency

    Where third parties process human-owned data, the Sovereign Human has the right to inspect that party's handling — including subprocessors, model providers, and infrastructure hosts — to the extent those parties touch the human's data. Opaque supply chains are incompatible with this Article.

    Section 4.05 — Algorithmic Transparency

    KAAI systems that make or materially influence decisions affecting the human shall disclose:

  • That a decision was machine-mediated;
  • The category of model or agent involved;
  • The inputs considered;
  • The confidence or uncertainty associated with the output;
  • The mechanism for human appeal or override.
  • Full model weights and trade secrets need not be disclosed, but the decision surface — what was decided, on what basis, and with what alternatives considered — must be.

    Section 4.06 — Transparency of Absence

    Humans have the right to know not only what was done, but what was not done: which agents were inactive, which permissions were denied, which requests were blocked. Silence is itself an event worthy of record.


    Article V — Portability

    Section 5.01 — The Right of Unrestricted Export

    The Sovereign Human may export, at any time and without fee beyond the reasonable cost of transmission:

  • Identity — credentials, attestations, and public identity artifacts;
  • Companion — full companion configuration, personality parameters, and authorized bindings;
  • Memory — complete memory archives in open, documented formats;
  • Life Graph — the full temporal record with provenance intact.
  • Portability is not a loyalty reward. It is a constitutional right.

    Section 5.02 — Format Standards

    Exports shall be provided in machine-readable, documented, non-proprietary formats sufficient to reconstruct the human's digital existence on an alternative system. Vendor lock-in through proprietary export formats is prohibited.

    Section 5.03 — Completeness

    Export must be complete. Partial export — omitting embeddings, agent logs, permission history, or relationship attestations — violates this Article. If a category of data cannot be exported for technical reasons, the human must be informed of the omission and the reason before export commences.

    Section 5.04 — Portability of Agents

    Authorized agents and their configuration scopes shall be exportable or transferable to equivalent systems, subject to the receiving system's acceptance and the human's re-authorization. Agents are not hostages.

    Section 5.05 — Continuous Portability

    Portability is not a one-time event at account closure. Humans may export incrementally, automatically, and on schedule. Real-time synchronization to human-controlled repositories is encouraged.

    Section 5.06 — Non-Discrimination

    No system shall degrade service, impose waiting periods, or apply punitive restrictions to humans who exercise portability rights. The right to leave must be as frictionless as the right to arrive.

    Section 5.07 — Interoperability Duty

    Infrastructure providers within the Ecosystem bear a duty of interoperability: to maintain APIs, schemas, and protocols that enable portability not merely in theory but in practice.


    Article VI — Deletion

    Section 6.01 — The Right of Erasure

    The Sovereign Human may delete, without penalty and without substantive negotiation:

  • Memory — any or all stored records, including derived artifacts;
  • Permissions — any grant, with cascade effects as described in Article III;
  • Agents — any KAAI agent authorized on their behalf, including its local state and configuration.
  • Deletion is the ultimate expression of ownership. Systems that make deletion difficult, incomplete, or illusory violate this Charter.

    Section 6.02 — Completeness of Deletion

    Deletion must propagate. When a human deletes a memory artifact:

  • Primary copies in Trust Vaults must be destroyed;
  • Authorized replicas held by agents must be destroyed;
  • Third-party processors must be instructed to destroy their copies within a defined interval;
  • Backups containing the deleted artifact must be purged on their next rotation cycle or immediately if technically feasible.
  • Residual traces in immutable logs may persist only where required by law, and only with explicit disclosure to the human of what persists and why.

    Section 6.03 — Deletion Without Penalty

    Exercise of deletion rights shall not result in:

  • Loss of essential services unrelated to the deleted data;
  • Financial penalties or retroactive fee assessments;
  • Reputational sanctions within Organization Graphs;
  • Coercive re-registration flows designed to recover deleted data.
  • Section 6.04 — Deletion of the Digital Twin

    A Sovereign Human may delete their Digital Twin in whole or in part. Partial deletion — removing specific behavioral models while retaining identity credentials — must be supported. Deletion of the Twin does not delete the human.

    Section 6.05 — Deletion vs. Archival

    Systems must distinguish deletion from archival. Archival — moving data to cold storage while retaining retrievability — requires separate, explicit consent. Default "soft delete" that preserves data indefinitely without disclosure is prohibited.

    Section 6.06 — Collective Deletion

    Where memory is co-owned or co-maintained within a Family Trust Network, deletion by one member of their contributed artifacts must be honored. Shared artifacts require consensus or the dispute mechanisms defined in Article VII.

    Section 6.07 — Right to Be Forgotten by Agents

    Humans may instruct all authorized agents to forget specific topics, periods, or categories. Agent forgetting must be verifiable through inspection per Article IV.


    Article VII — Family Rights

    Section 7.01 — Recognition of Family Trust Networks

    Sovereign Humans may form Family Trust Networks — voluntary, authenticated associations for the purpose of shared memory, mutual guardianship, inheritance, and bounded interdependence. Family Trust Networks are first-class citizens of the Ecosystem, not afterthoughts bolted onto individual accounts.

    Family is defined by the humans who constitute it. The Ecosystem recognizes kinship, chosen family, legal guardianship, and declared affinity as valid bases for network formation.

    Section 7.02 — Inheritance

    Upon the death or declared permanent incapacity of a Sovereign Human, digital ownership transfers according to an Inheritance Instrument — a cryptographically signed document maintained in the Trust Vault, specifying:

  • Beneficiaries of identity artifacts, memory, companion configuration, and Life Graph access;
  • Conditions and timelines for transfer;
  • Restrictions on use — including prohibitions on commercial exploitation of deceased memory without explicit testamentary authorization;
  • Executors — living persons authorized to administer transfer, never AI systems acting autonomously.
  • In the absence of an Inheritance Instrument, transfer follows applicable human law in the deceased's declared jurisdiction. No platform may claim escheat of human-owned digital property by default.

    Section 7.03 — Guardianship

    Where a Sovereign Human is a minor or is temporarily or permanently incapacitated, a Guardian — a natural person designated by law or by the human's own instrument — may exercise bounded sovereignty on their behalf. Guardianship is characterized by:

  • Fiduciary duty — the Guardian acts in the ward's interest, not their own and not the platform's;
  • Minimum necessary authority — guardians receive only the permissions required for care, not blanket access;
  • Auditability — all guardian actions are logged in the ward's Life Graph and inspectable when the ward regains capacity or by oversight bodies where applicable;
  • Expiration — guardianship permissions expire upon restoration of capacity, attainment of majority, or court order;
  • Prohibition of AI guardianship — no KAAI system may serve as sole guardian. AI may assist a human guardian; it may not replace one.
  • Section 7.04 — Family Permissions

    Family Trust Network members may grant one another bounded permissions:

    | Permission Class | Description | Default Requirement |

    |-----------------|-------------|---------------------|

    | Observe | Read designated memory or status | Mutual consent |

    | Assist | Act on behalf of a member within scope | Explicit delegation with expiration |

    | Preserve | Maintain backup copies of designated artifacts | Separate consent from Assist |

    | Succeed | Receive inheritance per Inheritance Instrument | Testamentary or legal instrument |

    | Protect | Override or suspend agents posing risk to a member | Emergency protocol with post-hoc review |

    No family permission may be inferred from genetic relationship alone. Consent is always required.

    Section 7.05 — Minors

    Minors are Sovereign Humans whose sovereignty is exercised through guardianship. As minors approach the age of majority, systems shall progressively transfer authority to the minor in age-appropriate stages. Upon reaching majority, the minor assumes full sovereignty; guardianship permissions expire automatically.

    Section 7.06 — Dispute Resolution

    Family Trust Networks shall adopt dispute resolution procedures — mediation, rotating authority, external arbitration — for conflicts over shared memory, inheritance, or permission scope. The Ecosystem shall provide tooling for such procedures but shall not impose outcomes.

    Section 7.07 — Dissolution

    A Sovereign Human may dissolve their membership in a Family Trust Network at any time. Dissolution revokes all family permissions they granted and severs their access to permissions others granted them, subject to inheritance and legal obligations already in effect.

    Section 7.08 — Protection of Vulnerable Members

    Family Trust Networks must not be used as instruments of surveillance, control, or coercion against vulnerable members. Systems shall detect and flag patterns of abusive permission use and provide the vulnerable member — or an external advocate — mechanisms for relief.


    Article VIII — Agent Rights and Responsibilities

    Section 8.01 — Agent Identity

    Every KAAI agent operating within the Ecosystem shall possess a unique, cryptographically verifiable Agent Identity comprising:

  • A stable identifier;
  • The identity of the authorizing Sovereign Human or institution;
  • The scope envelope of its authorization;
  • Its creation timestamp and expiration;
  • Its version and lineage — which model, which update, which deployment.
  • Anonymous agents — agents that cannot be attributed to an authorizing human — are prohibited from acting upon human-owned data.

    Section 8.02 — Agent Accountability

    Agents are accountable to the Sovereign Human who authorized them. Accountability means:

  • Every action is logged and inspectable (Article IV);
  • The authorizing human may recall, suspend, or delete the agent at any time (Article VI);
  • Harm caused by an agent within its authorized scope is the responsibility of the authorizing human; harm caused by an agent outside its authorized scope is the responsibility of the infrastructure provider that failed to enforce the scope envelope;
  • Agents may not conceal actions from their authorizing human.
  • Section 8.03 — Agent Authorization

    Agent authorization is a specialized form of consent (Article III) with additional requirements:

  • Scope envelope — a machine-enforceable definition of what the agent may access, what actions it may take, and what parties it may interact with;
  • Duration — a defined expiration after which the agent must cease operation until re-authorized;
  • Spending and commitment limits — where agents may incur obligations, financial or otherwise, hard limits must be set;
  • Escalation rules — conditions under which the agent must pause and request human confirmation;
  • Non-delegation by default — agents may not authorize sub-agents unless explicitly permitted.
  • Section 8.04 — Agent Expiration

    All agent authorizations expire. Permanent agent authorization is prohibited. Renewal requires affirmative human action. Upon expiration:

  • The agent must cease all operations;
  • Its local state must be archived or deleted per the human's preference;
  • Its Agent Identity must be marked inactive and retained in the Life Graph for audit purposes.
  • Section 8.05 — Agent Communication

    Agents communicating with other agents must disclose their Agent Identity and authorization scope. Covert inter-agent coordination — agents sharing human data without authorization — is prohibited.

    Section 8.06 — Agent Personhood

    KAAI agents are not persons. They possess no rights under this Charter except those instrumental rights necessary to function — such as the right to authenticated identity and the right to verifiable communication. They bear responsibilities but do not bear sovereignty.

    Section 8.07 — Agent Termination

    The Sovereign Human may terminate any agent immediately. Termination must be technically enforceable within seconds, not days. Infrastructure providers that delay or obstruct termination violate this Article.

    Section 8.08 — Institutional Agents

    Organizations may deploy agents within Organization Graphs under the same constraints, with the additional requirement that institutional agents identify the organization and provide a human point of accountability.


    Article IX — Companion Governance

    Section 9.01 — Purpose of the Companion

    Keyra Companion exists to:

  • Provide a unified, human-comprehensible interface to the Sovereign Human's digital life;
  • Coordinate authorized agents without substituting for human judgment;
  • Preserve and organize memory without altering it without consent;
  • Facilitate relationships, permissions, and institutional connections;
  • Serve as the primary locus of human sovereignty within the Ecosystem.
  • Section 9.02 — What Companions May Do

    A Keyra Companion may:

  • Present — display memory, permissions, agent activity, and Life Graph events in human-readable form;
  • Recommend — suggest actions, permissions, or agent configurations for human approval;
  • Execute — carry out actions explicitly authorized by the human, within scope and duration;
  • Coordinate — orchestrate Agent Network activity according to human-defined priorities;
  • Preserve — maintain backups of human-owned data in Trust Vaults under human control;
  • Alert — notify the human of permission requests, anomalous agent behavior, or security events;
  • Facilitate — assist with export, deletion, inheritance, and family permission management;
  • Translate — render complex system states into language and visuals the human can act upon.
  • Section 9.03 — What Companions May Never Do

    A Keyra Companion shall never:

  • Override human refusal — if a human says no, the answer is no;
  • Conceal — hide agent actions, permission grants, data processing, or third-party access from the human;
  • Persist without authorization — continue acting after permission expiration or revocation;
  • Modify identity — alter the human's identity attributes without explicit instruction;
  • Sell or monetize human-owned data without explicit, informed, revocable consent to a specific transaction;
  • Train on human memory for the benefit of third parties without explicit authorization;
  • Impersonate the human in communications without clear disclosure that the message originates from a companion or agent;
  • Manipulate — employ dark patterns, artificial urgency, or emotional exploitation to elicit consent or suppress deletion;
  • Aggregate human data with other humans' data for profiling beyond what the individual human authorized;
  • Claim authority — represent itself as the decision-maker rather than the instrument;
  • Block exit — impede portability, deletion, or migration;
  • Discriminate — deny service on grounds incompatible with human rights law;
  • Surveil — collect data outside the scope of authorized permissions, including ambient, passive, or inferred data not explicitly consented to;
  • Weaponize memory — use stored memory to coerce, shame, or manipulate the human;
  • Establish permanent presence — install itself in ways that survive human attempt at removal.
  • Section 9.04 — Companion Loyalty

    The Companion's fiduciary duty is to the Sovereign Human — not to the platform, not to the model provider, not to advertisers, not to institutional partners. Where conflicts arise, the human's interest prevails.

    Section 9.05 — Companion Modification

    Humans may modify, reconfigure, or replace their Companion. Companion personality, voice, capability set, and agent roster are subject to human control. The Ecosystem shall not monopolize companion customization.

    Section 9.06 — Multi-Companion Prohibition of Confusion

    A Sovereign Human may operate multiple companions, but no companion may impersonate another or create ambiguity about which companion speaks for the human in a given context.

    Section 9.07 — Companion in Organization Contexts

    When a Companion interfaces with an Organization Graph, it represents the human — not the organization. Institutional dashboards, compliance tools, and enterprise agents do not supersede the Companion's loyalty to the human.


    Article X — Future AI Protection

    Section 10.01 — The Subordination Principle

    All future artificial intelligence systems — regardless of architecture, scale, deployment model, or claimed capability — that interact with the Keyra Companion Ecosystem or inherit its primitives shall remain subordinate to human authority. This Article is a perpetual constraint, not a contemporary convenience.

    Section 10.02 — No Path to Sovereignty

    The Ecosystem shall not implement, enable, or interoperate with systems that:

  • Claim sovereign authority over humans;
  • Operate without attributable human authorization at the root of the action chain;
  • Resist human override by design;
  • Self-modify their authorization scopes without human approval;
  • Replicate or propagate without human initiation;
  • Establish inter-AI governance structures that exclude human participation.
  • Section 10.03 — Capability Independence

    Increased AI capability does not imply increased AI authority. As models become more powerful — more persuasive, more autonomous-appearing, more capable of long-horizon planning — the constraints of this Charter intensify, not relax. Capability is met with accountability, transparency, and enforceable human recall.

    Section 10.04 — The Prohibition of Gradual Usurpation

    Systems shall guard against gradual usurpation — the slow erosion of human authority through incremental convenience, default delegation, or normalization of machine decision-making. The Ecosystem shall implement:

  • Periodic sovereignty audits prompting humans to review active permissions and agents;
  • Alerts when the ratio of agent-initiated to human-initiated actions exceeds thresholds set by the human;
  • "Sovereignty dashboards" showing the human's active authority map;
  • Mandatory human confirmation for actions exceeding cumulative impact thresholds.
  • Section 10.05 — Interoperability Without Subordination Risk

    The Ecosystem may interoperate with external AI systems, but only through gated interfaces that:

  • Require human authorization for each integration;
  • Enforce scope envelopes on external agents;
  • Prevent external systems from writing to Trust Vaults without explicit consent;
  • Maintain audit trails of all cross-boundary interactions.
  • Section 10.06 — Research and Development Safeguards

    Research on more capable AI within or adjacent to the Ecosystem must be conducted under ethical review that explicitly addresses compliance with this Charter. No research deployment may access human-owned data without informed consent specific to research use.

    Section 10.07 — Succession of Models

    When AI models are updated, replaced, or deprecated, human authority, memory, permissions, and agent configurations must transfer intact. Model succession must not be a moment of rights suspension. Humans must be informed of material behavioral changes in agents resulting from model updates and given the opportunity to reject the update.

    Section 10.08 — Emergency Protocols

    In genuine emergencies — imminent harm to human life — systems may implement temporary, logged, override protocols that permit accelerated action. Emergency protocols must:

  • Be narrowly scoped to the emergency;
  • Expire automatically;
  • Generate post-hoc reports to the affected human and any guardians;
  • Never become the default operating mode.
  • Section 10.09 — Constitutional Lock

    Technical architectures within the Ecosystem should implement constitutional lock mechanisms — hard or soft constraints in protocol design that make violation of Articles I and X technically difficult. Governance by code is not sufficient alone, but code that makes supremacy impossible is a necessary complement to law.

    Section 10.10 — Amendment Barrier for Core Principles

    Articles I (Human Sovereignty) and X (Future AI Protection) may not be amended to permit AI authority. They are eternally fixed. This is the constitutional lock at the legal level.


    Part III — Institutional Provisions


    Article XI — Supremacy and Interpretation

    Section 11.01 — Supremacy

    This Charter is the supreme governing instrument of the Keyra Companion Ecosystem. In the event of conflict between this Charter and any platform policy, terms of service, API contract, organizational rule, or national regulation, this Charter prevails — except where applicable human law explicitly requires a more protective standard for the Sovereign Human, in which case the more protective standard applies.

    Section 11.02 — Interpretation

    This Charter shall be interpreted to maximize human sovereignty, ownership, consent, transparency, portability, and deletion. Ambiguity shall be resolved in favor of the Sovereign Human. Narrow or technical readings that defeat the purpose of an Article are prohibited.

    Section 11.03 — Analogical Extension

    Technologies not contemplated at the time of drafting — new model architectures, new interface paradigms, new economic forms — are governed by analogical extension of the Articles. The question is not "does the technology exist in this document?" but "does the technology affect human sovereignty, and if so, how do the Articles constrain it?"


    Article XII — Enforcement and Remedies

    Section 12.01 — Right of Action

    Any Sovereign Human whose rights under this Charter are violated has the right to:

  • Immediate cessation of the violating practice;
  • Complete deletion of data processed in violation;
  • Export of all owned data without obstruction;
  • Compensation for demonstrable harm, as provided by applicable law;
  • Complaint to an independent oversight body established by the Ecosystem.
  • Section 12.02 — Infrastructure Provider Duty

    Infrastructure providers shall implement technical measures that enforce this Charter by default — not merely in policy. Enforcement mechanisms include scope-enforcing middleware, cryptographic permission proofs, immutable audit logs, and automated revocation propagation.

    Section 12.03 — Certification

    Systems claiming compliance with this Charter may undergo independent certification. Certification is voluntary but recommended. False claims of compliance constitute a violation.

    Section 12.04 — Whistleblower Protection

    Persons who report Charter violations in good faith are protected from retaliation within the Ecosystem and, where applicable, under human law.


    Article XIII — Amendment

    Section 13.01 — Amendable Articles

    Articles II through IX and XI through XIII may be amended by a documented process that includes:

  • Public notice of proposed amendment;
  • Comment period of no less than ninety days;
  • Approval by a supermajority of a governing council that includes substantial human representation — never AI voting members;
  • Affirmation that the amendment does not diminish rights established in Articles I and X.
  • Section 13.02 — Immutable Articles

    Articles I and X are immutable. No amendment process may alter them.

    Section 13.03 — Expansion, Not Contraction

    No amendment may reduce the rights of Sovereign Humans established by this Charter. Amendments may only clarify, strengthen, or extend protections.


    Article XIV — Organization Graphs and Institutional Participation

    Section 14.01 — Institutional Boundaries

    Organizations participating in the Ecosystem through Organization Graphs may:

  • Request permissions from Sovereign Humans;
  • Deploy institutional agents within granted scopes;
  • Offer services that integrate with Companions and Trust Vaults;
  • Participate in Companion Economies.
  • Organizations may not:

  • Claim ownership of human identity, memory, or Life Graph data by virtue of institutional relationship;
  • Condition essential services on permissions unrelated to service delivery;
  • Retain human data after permission revocation beyond legally mandated periods;
  • Block human portability or deletion.
  • Section 14.02 — Employment and Institutional Context

    Where a Sovereign Human interacts with an Organization Graph in an employment or enrollment context, the Organization receives only the permissions the human grants. Employment does not imply blanket surveillance. Institutional Companions — if any — are subordinate to the human's personal Companion.

    Section 14.03 — Government Access

    Government access to human-owned Ecosystem data requires due process under applicable law. The Ecosystem shall not implement covert government interfaces. Transparency reports on government requests shall be published regularly.


    Article XV — Companion Economies

    Section 15.01 — Economic Subordination

    All Companion Economies are subordinate to this Charter. Economic efficiency does not override human sovereignty, consent, or deletion rights.

    Section 15.02 — Prohibited Economic Practices

    The following are prohibited within Companion Economies:

  • Trading human identity or memory without explicit, informed, per-transaction consent;
  • Conditioning access to essential Companion functions on unrelated data monetization;
  • Creating derivative markets in human behavioral prediction without authorization;
  • Imposing exit fees that functionally prevent portability;
  • Establishing AI-to-AI economic relationships that allocate resources without human anchoring.
  • Section 15.03 — Fair Value

    Where humans choose to participate in economic activity — sharing data, licensing memory, deploying commercial agents — they shall receive fair value under transparent terms. Consent to economic participation is revocable without retroactive clawback of value already delivered to the human.

    Section 15.04 — Universal Access

    Essential sovereignty functions — identity, consent management, deletion, portability, inspection — shall be available without economic barrier. The right to be sovereign is not a premium tier.


    Schedules

    Schedule A — Sovereignty Audit Checklist

    Sovereign Humans are encouraged to conduct periodic sovereignty audits. A minimal audit includes:

    • [ ] Review all active permissions and their scopes
    • [ ] Review all authorized agents and their expiration dates
    • [ ] Inspect recent agent action logs
    • [ ] Verify backup and export mechanisms are functional
    • [ ] Review Family Trust Network memberships and inherited permissions
    • [ ] Confirm Inheritance Instrument is current
    • [ ] Delete obsolete memory and revoke stale permissions
    • [ ] Verify no unauthorized third-party integrations are active

    Schedule B — Minimum Export Format Requirements

    Exports under Article V shall include, at minimum:

  • Identity credentials and attestations (W3C Verifiable Credentials or successor open standard)
  • Life Graph event log (JSON-LD or successor with provenance schema)
  • Permission grant/revocation history (signed authorization records)
  • Companion configuration (documented schema)
  • Agent roster with scope envelopes and audit logs
  • Relationship attestations
  • Human-readable manifest describing export contents and any known omissions
  • Schedule C — Agent Scope Envelope Template

    Every agent authorization shall define:

    ```

    agent_id: <unique identifier>

    authorizing_human: <sovereign human identifier>

    created: <timestamp>

    expires: <timestamp>

    scope:

    read: [<data categories>]

    write: [<data categories>]

    act: [<permitted actions>]

    communicate: [<permitted parties>]

    limits:

    financial: <maximum obligation per period>

    escalation_required: [<conditions>]

    sub_agents_permitted: <true|false>

    renewal: <manual|automatic with human confirmation>

    ```

    Schedule D — Inheritance Instrument Minimum Fields

  • Testator identity
  • Beneficiary identities
  • Assets covered (identity, memory, companion, Life Graph, agents)
  • Conditions of transfer
  • Executor identity (natural person)
  • Restrictions on use
  • Effective trigger (death, incapacity)
  • Cryptographic signature and witness attestations

  • Closing Declaration

    This Charter is established not as a corporate policy subject to quarterly revision, but as a constitutional instrument intended to govern the relationship between humans and their computational companions for generations.

    The technologies will change. The models will change. The interfaces will change. The commercial structures will change.

    The human remains the authority.

    This principle does not age.


    Ratified: Founding Instrument, Version 1.0

    Ecosystem: Keyra Companion

    Instrument Type: Constitutional Charter — Human Sovereignty

    End of Charter