Architecture

Attestia proves that an event, a transaction, or a state transition happened, and binds that proof to a chain: an append-only event store and Merkle proofs. Cognate does not build a second store. It uses that one for AI — model lineage, policy decisions, agent capabilities, and prompt integrity.

RepoMesh is the other neighbour. It is the release network: signed events, node manifests, and an XRPL-anchored trust clock, on its own RFC 6962 ledger. @cognate/repomesh-bridge calls that ledger to check a release. It does not use Attestia’s Merkle tree.

policy  ── evaluate before inference
   │
   ├─ model-registry ── version hashes, approval, deploy
   ├─ agent-identity ── who may act, and under which grant
   └─ prompt-store ── what was asked, and what came back
          │
          └─ types ── the shared nouns
                 │
                 └─ Attestia ── attest the record

Boundaries

Package	Owns	Does not own
@cognate/types	The nouns: model, version, policy, agent, hash, tenant	Behavior
@cognate/policy	Whether this call is allowed	Fetching the policy
@cognate/model-registry	Whether this version may be deployed	Storing weight files
@cognate/agent-identity	Whether this agent holds a live capability	Issuing keys
@cognate/prompt-store	The append-only encrypted log	Choosing a database

The Docker image builds all five and then starts a health process. That process is not a sixth package. When a service layer arrives, it should call these functions rather than grow a second policy engine beside them.

Regulatory map

Requirement	Where it lands
EU AI Act Article 12, logging over the system lifetime	Prompt store, append-only
EU AI Act Article 14(5), a natural person in the loop	Agent identity approvals, model-registry transitions
NIST AI RMF Govern, Map, Measure, Manage	Policy, registry, prompt store, and the human gate on deploy
ISO/IEC 42001	The same gates, as an AI management record rather than a vote