# Qi and IXO system correspondence matrix

**Status:** verification snapshot  
**Verified:** 30 August 2026  
**Purpose:** constrain every present-state system statement in the manuscript to versioned first-party evidence.

## Status vocabulary

- **Implemented:** source and tests contain the behavior at the cited ref. This does not by itself prove production deployment.
- **Specified:** a normative contract or design exists, but the cited evidence does not prove a live implementation.
- **Draft implementation candidate:** implementation artifacts exist, but defined conformance and release gates remain open.
- **Experimental:** bounded prototype behavior exists and its limitations are explicit.
- **Proposed:** intended architecture without current implementation evidence.
- **Unknown:** the available authoritative evidence is insufficient. Unknown capabilities are omitted from present-tense manuscript claims.

## Correspondence matrix

| Cooperative concept | Qi/IXO surface | Verified present state | Status | Lifecycle | Authority boundary | Persistence | Consequence | Versioned evidence | Publication constraint |
|---|---|---|---|---|---|---|---|---|---|
| Bounded identity of a cooperative context | Topic identity and Matrix root/thread | Topic Protocol defines a stable UUIDv7 Topic ID independent of a Matrix event ID, model session, or transcript. A Topic has a root/anchor and native `m.thread` relation. | Draft implementation candidate | Topic status is separate from contract and outcome status. | Room membership governs who can perceive room content; Topic capabilities govern actions, not membership confidentiality. | The protocol projects append-only authorised operations from Matrix events. | Identity alone produces no external consequence. | [Topic README](https://github.com/ixoworld/topic-protocol/blob/5cebe6437ea8f425e26c78eaaaf86479ff1fd2d3/README.md); [status and invariants](https://github.com/ixoworld/topic-protocol/blob/5cebe6437ea8f425e26c78eaaaf86479ff1fd2d3/docs/protocol/00-status-and-invariants.md) | Do not call Topics deployed or pilot-ready on this evidence. Cold-cache discovery, E2EE agent participation, federation, index migration, and other gates remain open. |
| Legible shared state | Topic projection and accepted Overview | The protocol specifies deterministic projection from a root and authorised operations, including a singular accepted Overview and explicit conflict handling. | Draft implementation candidate | Draft, active, waiting, blocked, resolved, archived, and redirected Topic states; accepted facts and outcomes are separate record types. | Authorised operations affect shared projection; personal follow/mute/pin/unread preferences remain user state. | Append-only operations can rebuild projected state. | Projection changes shared representation, not external rights or settlement. | [core Topic](https://github.com/ixoworld/topic-protocol/blob/5cebe6437ea8f425e26c78eaaaf86479ff1fd2d3/docs/protocol/01-core-topic.md); [conformance](https://github.com/ixoworld/topic-protocol/blob/5cebe6437ea8f425e26c78eaaaf86479ff1fd2d3/docs/conformance.md) | A static-pass profile proves contract/vector compatibility only; it is not live Matrix evidence. |
| Portable participant context | Topic Capsule | A Topic Capsule is specified to contain manifest, projected state, anchor, participants, context, artifacts, accepted memory, events, capabilities, policy, and revision. | Specified within draft candidate | Capsule revision changes as authorised state changes. | Receiving a Capsule does not imply VFS access or action authority. Agents must handle stale revisions. | Capsule is a portable snapshot derived from durable events. | It provides context, not permission or proof of outcome. | [Topic Capsule](https://github.com/ixoworld/topic-protocol/blob/5cebe6437ea8f425e26c78eaaaf86479ff1fd2d3/docs/protocol/04-topic-capsule.md) | Do not present the Capsule as a verified cross-client production context object until conformance exists. |
| Identifiable agent participation | Topic agent-run records | The protocol specifies identifiable agents and run records containing Topic, revision, caller, times, status, outputs, and receipt references. | Specified within draft candidate | Runs have explicit start, status, and output records. | Subagents inherit only expressly delegated authority; tool calls are scoped and receipt-bearing. | Run records are proposed as append-only Topic operations. | A successful run cannot implicitly complete a Topic, contract, outcome, claim, approval, or settlement lifecycle. | [agent participation](https://github.com/ixoworld/topic-protocol/blob/5cebe6437ea8f425e26c78eaaaf86479ff1fd2d3/docs/protocol/05-agent-participation.md); [conformance](https://github.com/ixoworld/topic-protocol/blob/5cebe6437ea8f425e26c78eaaaf86479ff1fd2d3/docs/conformance.md) | Live signed receipts, replay rejection, durable outbox recovery, and two-client action projection still require evidence. |
| Bounded action authority | Topic and Flow UCAN profiles | Topic Protocol specifies Topic-scoped abilities and requires Flow and Topic grants to remain separate. High-risk operations require human confirmation. | Specified within draft candidate | Grants have scope and validity; revocation/replay behavior is a release gate. | VFS, Flow, Topic, signing, and settlement rights are distinct. | Capability proofs and invocation receipts may persist, subject to privacy rules. | Authorization permits an attempt; it does not establish correctness, truth, or success. | [Topic UCAN](https://github.com/ixoworld/topic-protocol/blob/5cebe6437ea8f425e26c78eaaaf86479ff1fd2d3/docs/protocol/06-topic-ucan.md); [UCAN specification](https://ucan.xyz/specification/) | Do not claim replay-safe, production-authorised Topic execution before the named conformance gate passes. |
| Collaborative artifact state | Portal editor, Yjs, Matrix CRDT | Portal's editor source and documentation implement BlockNote documents and Flow state in Yjs, synchronized through Matrix via `@ixo/matrix-crdt`, with incremental updates and snapshots. | Implemented | Template and Flow modes are distinct; collaborative runtime state has explicit structures. | Write permission and Matrix room access constrain editing; specific execution authority is a separate layer. | Yjs updates and snapshots persist through Matrix and rehydrate on reload. | Editing changes collaborative state; it is not an on-chain consequence. | [editor README](https://github.com/ixoworld/ixo-portal/blob/2488f83669cf08777ea1e2661432c3786a23dd70/packages/editor/README.md); [architecture](https://github.com/ixoworld/ixo-portal/blob/2488f83669cf08777ea1e2661432c3786a23dd70/packages/editor/docs/architecture/architecture-overview.md) | Repository evidence verifies implementation, not the current production deployment or Topic Protocol conformance. |
| Executable cooperative artifacts | Portal Flows | Portal implements template and Flow modes, action registries, shared runtime state, and execution surfaces. Some actions can request blockchain transactions. | Implemented with external dependencies | Flow, node runtime, delegation, invocation, and external system lifecycles remain distinct. | Execution depends on block/action authority and wallet or external provider controls. | Flow definition and runtime state persist in the collaborative document. | A completed UI action is not automatically a claim approval, outcome achievement, or settlement. | [editor README](https://github.com/ixoworld/ixo-portal/blob/2488f83669cf08777ea1e2661432c3786a23dd70/packages/editor/README.md); [Flow architecture](https://github.com/ixoworld/ixo-portal/blob/2488f83669cf08777ea1e2661432c3786a23dd70/packages/editor/docs/architecture/qi-flows-product-overview.md) | The paper may claim executable-artifact primitives, not cumulative culture or reliably inherited performance. |
| Model-host boundary | Qi Runtimes | The runtime repository states and structures the host as a reasoning interface: the host does not run Qi or own IXO chain state. Runtime packages mediate capabilities, authority, delegation, external services, and result verification. | Implemented | Runtime workspaces, releases, reviews, and publication receipts have distinct states. | Wallet private keys are rejected; production mutation fails closed without verified external authority. | Runtime workspaces use immutable revisions and hash-chained event records. | Compilation is local preparation and never proves network publication; network state requires a completed receipt and read-back. | [Qi Runtimes README](https://github.com/ixoworld/qi-runtimes/blob/a2b8cc77a683000fc9734af5090a6e3e503b3350/README.md); [Blueprint Runtime](https://github.com/ixoworld/qi-runtimes/blob/a2b8cc77a683000fc9734af5090a6e3e503b3350/runtimes/qi-blueprint-runtime/README.md) | Avoid describing the model, chat, or hidden reasoning as system authority or audit evidence. |
| Governed service blueprints and PODs | Qi Blueprint Runtime | The runtime implements versioned blueprint workspaces, validation, review, compilation, release preparation, registry-backed Flow templates, governed service skills, and receipt-gated publication semantics. | Implemented with network/deployment dependencies | Discovery, design, validation, testing, and deployment phases are explicit; publication readiness is separate. | Owner, reviewer, publisher, Portal, signer, and network responsibilities are separated. | Revisions are immutable and hash-addressed; sequenced event truth rebuilds workspace projections. | Only verified external publication receipts may support a live-network claim. | [Blueprint Runtime v0.6](https://github.com/ixoworld/qi-runtimes/blob/a2b8cc77a683000fc9734af5090a6e3e503b3350/runtimes/qi-blueprint-runtime/README.md) | Do not infer that every prepared blueprint or POD is published, operational, or mainnet-authorised. |
| Claim ingestion and evaluation service | Evaluations Engine | The main branch contains routes, workflows, schemas, and persistence for claim ingestion and evaluation, including explicit external chain/pull integration points. | Implemented with external dependencies | Claim intake, evaluation processing, owner submission, and settlement-related records are separate. | Chain, signer, oracle, owner, relayer, and service roles are represented in different paths. | PostgreSQL records workflow and evaluation state; chain state is external. | Service decisions are not automatically authoritative chain state unless a signed transaction is accepted and read back. | [claim pull specification](https://github.com/ixoworld/evals-engine/blob/fb380cd01fdd0cb79e981d631867d39a7324624d/docs/pull-claim-spec.md); [claim ingest](https://github.com/ixoworld/evals-engine/blob/fb380cd01fdd0cb79e981d631867d39a7324624d/src/workflows/claim-ingest.ts) | Technical-owner sign-off and environment evidence are required before calling a path production-operational. |
| Evidence-to-determination prototype | IXO Verify | IXO Verify implements a local verification ledger, client-assisted evidence envelopes with provenance and hashes, deterministic rubric evaluation, review gates, determinations, audit shells, and dry-run actions. | Experimental | Blueprint, flow, claim, evidence, evaluation, review, determination, dispute, and action states remain distinct. | Client-assisted evidence is explicitly not server-verified; actions default to dry-run. | State-changing operations emit canonical-hashed audit events. | Real IXO anchoring, payments, credentials, and external side effects are not implemented in the cited version. | [IXO Verify README](https://github.com/ixoworld/ixo-verify/blob/7f269baa4e0decab860a1be8c5cc7fd8421417e9/README.md); [security](https://github.com/ixoworld/ixo-verify/blob/7f269baa4e0decab860a1be8c5cc7fd8421417e9/docs/security.md) | Use as evidence of a bounded prototype and semantic separation, never as production settlement evidence. |
| Decentralized identifiers and controllers | IXO blockchain IID module | IXO blockchain v8 contains an IID module for creating, resolving, updating, and deactivating IID documents with controllers, verification methods, services, linked resources, claims, entities, and rights. | Implemented on-chain module | IID creation, update, resolution, and deactivation are distinct operations. | Verification relationships and chain message authorization determine permitted changes. | Accepted transactions change consensus state in the module KV store. | DID control establishes bounded cryptographic control, not civil identity, competence, or truth. | [IID concepts](https://github.com/ixofoundation/ixo-blockchain/blob/bfdd934456be01f9212d3ebc107df81b43e1566d/x/iid/spec/01_concepts.md); [IID state](https://github.com/ixofoundation/ixo-blockchain/blob/bfdd934456be01f9212d3ebc107df81b43e1566d/x/iid/spec/02_state.md) | Do not equate a DID with verified personhood or legitimate authority outside the method and policy. |
| Governed digital entity and assets | IXO blockchain Entity module | Creating an Entity deterministically creates an IID document, CW721 NFT representation, entity KV record, and controlled entity accounts. | Implemented on-chain module | Entity creation, update, account control, ownership, and linked-resource changes are distinct. | Entity controllers and account/authz rules govern changes and delegated transactions. | Entity and linked state persist in chain consensus state. | Entity transactions can change controller, account, asset, and linked-resource state. | [Entity concepts](https://github.com/ixofoundation/ixo-blockchain/blob/bfdd934456be01f9212d3ebc107df81b43e1566d/x/entity/spec/01_concepts.md); [Entity state](https://github.com/ixofoundation/ixo-blockchain/blob/bfdd934456be01f9212d3ebc107df81b43e1566d/x/entity/spec/02_state.md) | An Entity is an authoritative chain object; its linked off-chain content still requires separate integrity and access controls. |
| Claims, evaluations, intents, escrow, disputes, and payments | IXO blockchain Claims module | v8 stores collections, claims, intents, evaluations, budgets, deposits, and disputes; implements authorised submission/evaluation, terminal and flagged statuses, escrowed intent payments, configurable payments, deposits, and adjudication. | Implemented on-chain module | Submitted, approved, rejected, disputed, invalidated, and flagged states have defined semantics; flagged is non-terminal. | Collection admins, service/evaluation agents, adjudicators, accounts, authz, deposits, and signer checks have distinct roles. | Accepted transactions persist records and counters in consensus state. | Defined transitions can release payments or change deposits and dispute state. | [Claims concepts](https://github.com/ixofoundation/ixo-blockchain/blob/bfdd934456be01f9212d3ebc107df81b43e1566d/x/claims/spec/01_concepts.md); [Claims state](https://github.com/ixofoundation/ixo-blockchain/blob/bfdd934456be01f9212d3ebc107df81b43e1566d/x/claims/spec/02_state.md); [messages](https://github.com/ixofoundation/ixo-blockchain/blob/bfdd934456be01f9212d3ebc107df81b43e1566d/x/claims/spec/03_messages.md) | This proves module behavior at the cited release. It does not prove that the full Qi-to-Portal-to-evaluator-to-wallet path is currently deployed, configured, funded, or safe for automated production settlement. |
| End-to-end governed reality boundary | Topic → Flow/runtime → evaluation → signer → IXO chain → read-back | Components and contracts exist, but the reviewed sources do not establish one fully conformed, production-deployed end-to-end path covering E2EE participation, replay safety, independent evidence, signing, settlement, and authoritative read-back. | Unknown as an end-to-end production capability | All component lifecycles must remain independently observable. | No component may acquire another's authority by inference. | Receipts must bind local action to externally read-back authoritative state. | Only the authoritative system may establish the final consequence. | All sources above; especially [Topic conformance](https://github.com/ixoworld/topic-protocol/blob/5cebe6437ea8f425e26c78eaaaf86479ff1fd2d3/docs/conformance.md) | The manuscript describes the correspondence as an architecture and implementation trajectory, not a completed production guarantee. |

## Owner sign-off register

| System | Required reviewer | Scope of approval | Status |
|---|---|---|---|
| Topic Protocol | Protocol technical owner | Topic identity, projection, Capsule, authority, conformance, maturity | Pending |
| IXO Portal | Portal/editor technical owner | Matrix/Yjs state, Flow behavior, user-visible semantics | Pending |
| Qi Runtimes | Runtime technical owner | host boundary, workspace/review authority, publication receipts | Pending |
| Evaluations Engine | Evaluations technical owner | claim ingest, evaluation, decision, external dependencies | Pending |
| IXO blockchain | Protocol/chain technical owner | IID, Entity, Claims, payments, escrow, disputes, settlement boundary | Pending |

No pending owner sign-off is silently converted into approval. Factual corrections from an owner update the relevant row, manuscript claim, and version history together.
