Notarized everything. Zero-trust. Zero deep fakes.

Reference architecture v6: notarize, HD-address, govern (COOL + COPE), and royalty every entity in an AI system on the XRPL.

CAPPZ.AI — A TRUSTWORTHY AUTONOMOUS AGENT PLATFORM FOR DATA, CONTENT, AND APPLICATIONS.

Core value 4 of 7: Ownership — Data stays in the user's or business's wallet, on their device or data center.

Rapidly assemble apps from 92 skills. Run anywhere — autonomously and redundantly. From the silicon enclave to the agent, one notarized graph.

All legacy cloud applications must be rebuilt decentralized with zero-trust protections. All digital code and content must be notarized and operated on blockchain rails for payments, permissions, and operations.

A reference architecture for reliable AI through blockchain-anchored ontology. Cognitive Ontological Oriented Learning (COOL) and Cognitive Object Permanence Experiences (COPE — eliminating constant re-inferencing; learnings retained for consistent, reliable, and repeatable outcomes), rooted at the device via ARM/Qualcomm TrustZone, addressed by HD paths, governed by event TXs.

Provenance lineage as graph. Wallet address as identity.

cappz.ai is a platform. Eleven components compose the stack: Decentralized Identity For All (DIFA), notarization, wallet-as-container, lifecycle administration, an embedded AI agent, an on-chain ontology graph, BPMN-defined capabilities, RepoZ version control, CPM notarized build packaging, Claude/MCP compatibility, and device-level primitives. Every entity — people, credentials, code, models, data, contracts — is given a blockchain address as identity and resident wallet, anchored at the device by ARM instructions in Qualcomm TrustZone. The hot working set is held in an in-memory graphology cache, hydrated from chainlet partitions and validated by event transactions. The result is an AI substrate that is verifiable, reproducible, and fast.

CAPPZ.AI Platform Capability Landscape

Others implement one or two layers. CAPPZ unifies embedded agents, a shared ontology, BPMN middleware, resident data with peer-to-peer sync, and build-to-release lifecycle in one wallet-native framework.

Palantir is the closest reference for an ontology-centred application platform; Semantic Kernel and LangGraph for agent extensibility; Agentforce for embedded agents; Camunda and Temporal for process orchestration; Couchbase Lite, Electric and RxDB for resident data and synchronization. CAPPZ brings those concerns together under one contract — and keeps the state in wallets the user and business own.

  • AA portable ontology shared by agents and apps. Entities, relationships, actions, permissions and events are modelled once as ontology TXs; every app and agent binds to the same contract.
  • BSession-aware, ontology-aware replication. Sync is scoped by app, session, party, agent, object and version — and each change carries provenance and conflict rules.
  • CDynamic skill binding with governance. Skills bind at runtime from wallet events, filtered by role, version and environment. MCP-compatible, not required.
  • DOne process model for deterministic and agentic work. BPMN steps, agent decisions, human approval, retries and remediation in one token flow, every outcome recorded.
  • EBuild and release as first-class concepts. An app is a versioned package of ontology, agents, skills, processes and policies; the build tests, notarizes, releases and can roll back.
  • PLATFORM
  • Shared ontology
  • Embedded agents
  • Resident / offline data
  • Peer / session sync
  • BPMN processes
  • CAPPZ
  • Palantir Foundry / AIP
  • Semantic Kernel
  • Agentforce / MuleSoft
  • Camunda 8
  • Couchbase Lite
  • Electric / RxDB

● yes · ◐ partial · ○ not described in public docs

Where the work runs

8 functions run in your browser and 2 keep their records in the owning wallet. 106 still run hosted: 52 because they hold a third-party key (payments, AI, SMS, calendar OAuth, XRPL signing), ported last; 54 because their domain moves whole in the next release. 2 with no callers were retired.

In the browser

In the owning wallet

52

Hosted: hold a secret

54

Hosted: move next release

Every app is a wallet.

One container holds the app's HD root, embedded admin agent, included skills, notarized TX graph, and cappz-store cache. Every subsequent section — device root, recipe, composability, royalties — is a consequence of this single shape.

Every app on CAPPZ is this container. Every included skill is itself another container. Recursion terminates at substrate primitives.

A wallet container holds the app's HD root, embedded admin agent, included skills, notarized TX graph, and cappz-store cache. That's the whole app.

5 canons · 84 books · Ethiopian-primary. Every verse a notarized HD node. Cross-language equivalency via KJV bridge.

88 governed skills — each an embedded operational agent with BPMN, ontology, and Twin-TX provenance. Claude & MCP compatible.

Eleven steps. One substrate.

From identity to silicon — every layer of the platform composed as notarized transactions on wallet-addressed rails.

People, places, things. Credentials, code, models, data, and existing contracts in any format — each given a blockchain address as identity and residence in a wallet at that address.

Hashprint everything, placed on transactions sent to the target address for anyone to verify content fidelity. The blockchain is the anonymous registry.

HD root, embedded admin agent, included skills, notarized TX graph, cappz-storage cache, and chainlets. The container is the app.

Every app on CAPPZ is this container. Every included skill is itself another container. Recursion terminates at substrate primitives.

Created, Amended, Included, Deprecated — all lifecycle and business events flow as a graph of metadata-enriched transactions.

Prompt interface. The agent administers content versioning, access control, cloning/copying, TX-defined royalty collection and distribution, process execution, analytics, and Agent-to-Agent state synchronization (A2A).

Application and content ontology graph defined on-chain, serving as reference data and application scope anchor. No AI drift. No hallucinations. All history preserved in the learning tree of knowledge.

Capabilities executed by the resident agent running the BPMN engine as a skill. BPMNs define the exposed edge functions of each skill.

Runs parallel to GitHub/GitLab or replaces them entirely. HD-addressed, multi-master, notarized.

On-chain TX manifest of constituents. Hash-verified bundles. No rogue supply chain.

Every skill is exposed as a governed MCP tool. Manifest at /.well-known/mcp.json. Royalty events fire on tool invocation.

ARM instructions will eventually secure devices regardless of operating system or apps — anchoring wallet key operations in the silicon enclave.

Ship an app in an afternoon by binding skills.

No servers to stand up. No supply chain to vet. Clone a template, bind skills from the 92-skill library, and the embedded agent wires the rest — governed by BPMN, notarized on deploy.

Clone from an on-chain registered template (ontology + BPMN + edge functions included).

Compose from 88 governed skills. Each carries its own ontology, BPMN, and scope.

Embedded admin agent boots, resolves dependencies from chain, and enters COPE-crystallized state.

Build artifacts, prompts, and datasets anchored via Twin-TX. Provenance from the first boot.

Every binding pays. No operator required.

Every skill binding emits a fee event to the Royalty Flywheel — 777 CAPPZ + TX fee, split on-chain. Distributions to skill authors, template owners, and treasury happen automatically. Transaction-sourced royalty configs are inherited by every cloned wallet.

Direct royalty to the wallet that authored each bound skill.

To the wallet that owns the cloned template lineage.

Funds the substrate — no operator needed.

From drift to discipline.

We applied CAPPZ to Lovable, ChatGPT and Claude to prevent hallucinations and drift. Let me speak plainly. AI outright lied about what it accomplished by implementing fake output from non-functional code and operations. Houston - we have a problem! Hallucinating APIs. Forgetting schemas. Renaming our own vocabulary mid-session. Then we anchored everything to an on-chain ontology — and the drift stopped.

Statistical, not anchored

  • × Hallucinated API surfaces, week over week
  • × Vocabulary drift — same concept, three names
  • × Schema amnesia between sessions
  • × Tool-call inconsistency across runs
  • × Provenance loss — who said what, when?

LLMs re-derive the world from scratch

Without an external pinned ontology, every session reinvents vocabulary, schemas, and shape. The model is statistical. The world is not. The fix is to give the model a graph it cannot move.

Cognitive Ontological Oriented Learning (COOL) + COPE

  • ✓ Anchored — every entity at a deterministic HD address
  • ✓ Identified — every artifact in a wallet with COPE lifecycle
  • ✓ Named — modal-free identifiers (AX-92)
  • ✓ Verified — 92 axioms · 22 anti-patterns · 80+ event types
“If Cognitive Ontological Oriented Learning (COOL) and Cognitive Object Permanence Experiences (COPE) could discipline the two best AI tools on the planet, they will discipline yours.”

18 named models. One governed choice.

CAPPZ is model-independent. The title-bar picker writes the operator’s choice as a hash-sealed ModelSelected transaction; every app replays that same latest-wins record. Auto preserves both a cloud and local target, then routes from the selected primary slot.

Cloud · Lovable AI Gateway

Nine verified Google and OpenAI choices. Auto can keep one as the cloud primary or fallback.

  • Gemini 3.7 Flash google/gemini-3.7-flash · Google · fast
  • Gemini 3.1 Flash Lite google/gemini-3.1-flash-lite · Google · fast
  • Gemini 3.1 Pro (Preview) google/gemini-3.1-pro-preview · Google · premium
  • GPT-5.6 Luna openai/gpt-5.6-luna · OpenAI · fast
  • GPT-5.6 Terra openai/gpt-5.6-terra · OpenAI · standard
  • GPT-5.6 Sol openai/gpt-5.6-sol · OpenAI · premium
  • GPT-5.5 openai/gpt-5.5 · OpenAI · premium
  • GPT-5.4 Mini openai/gpt-5.4-mini · OpenAI · standard
  • ChatGPT (Instant) openai/chat-latest · OpenAI · standard

On this machine · Ollama / LM Studio

These starters seed the model wallet. Runtime discovery also exposes any other model installed on the operator’s endpoint.

  • Kimi K2 (Moonshot, open weights) kimi-k2:latest · open weights · local
  • Qwen 3 qwen3:latest · open weights · local
  • DeepSeek R1 deepseek-r1:latest · open weights · local
  • Llama 3 llama3:latest · open weights · local
  • Mistral mistral:latest · open weights · local

In this browser · WebGPU

Wallet-published browser models show download and local weight-custody status before execution.

  • Llama 3.2 3B (WebGPU) Llama-3.2-3B-Instruct-q4f32_1-MLC · WebGPU · local
  • Llama 3.2 1B (WebGPU) Llama-3.2-1B-Instruct-q4f32_1-MLC · WebGPU · local
  • Qwen 2.5 1.5B (WebGPU) Qwen2.5-1.5B-Instruct-q4f16_1-MLC · WebGPU · local
  • Phi-3 mini (WebGPU) Phi-3-mini-4k-instruct-q4f16_1-MLC · WebGPU · local

Visible, not enabled

These rows are deliberately disabled. They are not sent to Lovable AI Gateway and are not selectable today.

“We applied CAPPZ to Lovable, ChatGPT and Claude” describes the development environments where the discipline was forged. It is not the runtime catalog: ChatGPT is selectable now; Claude remains a visible, disabled bring-your-own-key entry.

Whisper to find. Connect to move.

Discovery whispers on the LAN; across firewalls, copies ask. Peers find each other by UDP beacon, a TX bid/ask rendezvous with a relay node, pairing code or wallet breadcrumbs, then move the same checksummed frames over TCP, QUIC, a WebSocket bridge, an outbound relay ladder (WebTransport, WebSocket, HTTPS keep-alive, long-poll) or a USB bundle; nodes pull missing bodies by content hash. No inbound port behind a firewall, no browser required.

  • UDP beacon LAN multicast, Ed25519-signed by the node key, rate-limited. Announces heads only — never state; a verified beacon makes the node dial. Routers and corporate networks drop it.
  • TX bid/ask The copy sends ReplicaConnectRequested with a signed hello to the peer's node — or to a relay only if the peer is unreachable; the node verifies it, decides, and answers with a ticket and its own member record. Works through reverse proxies.
  • Pairing code QR, typed, or spoken (sound-pairing). Short-lived, speakable.
  • Member table Each copy's devices record where they accept connections (CopyEndpointRegistered, signed, amended on change); every copy holds the table and dials peers directly from it.
  • Transport
  • Runs on
  • NAT
  • Offline
  • TCP Bitcoin-style sessions: verified signed hello, inventory, headers-first, pull bodies.
  • Standalone node
  • Needs a reachable port
  • LAN
  • QUIC Reliable and encrypted over UDP. Same frames as TCP.
  • Standalone node
  • NAT-friendly (UDP)
  • LAN
  • WebSocket bridge The browser rides the node’s TCP/QUIC sockets.
  • Browser → local node
  • Localhost only
  • Yes
  • Relay ladder (WebTransport · WebSocket · HTTPS) Fastest first: WebTransport over UDP, WebSocket, a receiver-initiated chunked HTTPS stream, then long-poll — each step down automatic where a network blocks the one above.
  • Browser or node → relay node
  • Outbound only
  • No
  • USB bundle Signed file carried by hand. Same manifest-first protocol.
  • Anywhere
  • n/a
  • Air-gap

A read-only XRPL connector watches validated ledger headers and checks anchoring proofs itself — no hosted verifier, and it never submits transactions.

Borrowed from Bitcoin: the peer pattern. Left behind: proof-of-work and global broadcast.

# standalone Replicator edge node (Deno) git clone https://github.com/CAPPZ-ai/cappz-sdk cappz && cd cappz && npm install # CAPPZ_NODE_KEY (PKCS8 base64) / CAPPZ_NODE_PUB (raw hex): Ed25519 key that signs hellos, beacons and TXs CAPPZ_POW=<your POW> CAPPZ_NODE_KEY=<pkcs8> CAPPZ_NODE_PUB=<hex> \ CAPPZ_TLS_CERT=cert.pem CAPPZ_TLS_KEY=key.pem \ deno run --allow-net --allow-read --allow-write --allow-env --unstable-net \ packages/cappz-edge-node/main.ts --tcp 41441 --quic 41443 --ws 41442 --relay 41445

The stack starts at the silicon enclave.

Cappz targets ARM instructions executing resident within the Qualcomm TrustZone to notarize everything — eliminating deepfake at the device level. Data, identity, content, code, AI agents, language models and financial transactions on blockchains, all secured by anchoring wallet-contained cryptographic key operations in the TrustZone. Decentralization at L1 is the precondition for trust at L7.

  • L7 TIER 07 / 07 AI · Agents · LLMs COOL + COPE — anchored inference, no re-derivation. Models cite the graph; the graph cites back. CITES AX-92
  • L6 TIER 06 / 07 Codices · Ontologies Bible · ISO 20022 · HL7 · FpML · FIX · domain corpora. Canonical knowledge precedes code. CITES PROV-014
  • L5 TIER 05 / 07 Contracts · Finance Royalty Flywheel · DARC splits · 70 / 20 / 10. XRPL settlement, on-chain cite-and-earn. CITES AX-67
  • L4 TIER 04 / 07 Skills · BPMN Governance 87 wallet-resident skills. BPMN is void main(). Every action a governed, verifiable step. CITES AX-57
  • L3 TIER 03 / 07 Notarization Substrate Twin-TX. ContentIngested + ConstituentsAggregated under one correlationId. CITES AX-63
  • L2 TIER 02 / 07 HD-Addressed Wallets m / 44' / 144' / … Every entity — event, skill, dataset, model — a deterministic address. CITES AX-68
  • L1 TIER 01 / 07 Device Root of Trust ARM · Qualcomm TrustZone — wallet key ops resident in-enclave. Anti-deepfake at capture. CITES US 11,645,632 B2

Stratigraphic stack — from the silicon enclave (L1) to the agent (L7). One notarized graph. AX-63 · AX-68 · AX-92 · US 11,645,632 B2

Identify · Notarize · HD-Address · Govern (COOL + COPE) · Royalty.

Five layers bind the eleven-component stack above (identity, notarization, wallet-container, lifecycle, embedded agent, ontology, BPMN, RepoZ, CPM, MCP, silicon). Each layer has a contract. Together they form a repeatable pattern that retargets to any corpus — legal, medical, scientific, silicon IP, sacred texts.

The repeatable recipe — Notarize → HD-Address → Govern → Royalty AX-63 · AX-68 · AX-92 · AX-67

Five wallets, one substrate — each die has its own HD root and on-chain lifecycle admin AX-74 · COPE

COOL — Cognitive Ontological Oriented Learning. Every node a wallet, every edge a notarized TX. AX-87 · AX-92

The notarized graph cache.

Notarized on chain. Resolved at L1-cache speed.

Every COOL node is a wallet at a deterministic HD address. The hot working set lives in an in-memory graphology cache, hydrated from chainlet partitions, invalidated by event TXs, rebuilt offline-first from durable wallet blocks. Verifiable, traversable, and embarrassingly fast.

O(1) node lookup

O(degree) traversal

Reactive invalidation

Wallet-first hydration

Single-writer safety

Durable recovery

Verifiable

Offline-first

Notarized graph cache — every read verifiable, every hit at L1-cache speed AX-63 · AX-68 · AX-69 · AX-70 · AX-71 · AX-73 · AX-74 · AX-87

Before / After — internal measurements

Agents are simple. The harness is the wallet.

The leverage in an agent is not the loop — it is what each turn sees, where the work runs and whether an action may proceed. CAPPZ answers those questions inside the wallet: context is assembled from the notarized graph cache, routed by residency and trust, disclosed in tiers, and every decision is a signed, replayable event.

The CAPPZ Harness — the wallet holds explicit state, COPE answers the per-turn questions, BPMN runs the work, and every decision ends as a notarized event. AX-57 · AX-74 · AX-97 · COPE

The receiving model reloads the whole conversation, and so does the model it hands back to.

The receiving model gets HD addresses and a scoped fact sheet, then resolves only what it needs from the graph cache.

Residency-aware routing — work goes where the context lives. Hand-offs pass addresses, never whole transcripts, so switching models does not mean re-reading everything. Wallet-host residency · PTW → POW → UPW

Tiered skill disclosure — the model sees a cheap map of every skill and pays for detail only when it commits. MCP-compatible, not required. SkillCard · llms.txt · AX-57

  • DIMENSION
  • JEV (PER PUBLIC BLUEPRINT)
  • CAPPZ HARNESS
  • Decisions
  • Typed answers with probabilities, used within the session
  • Typed answers notarized as signed event transactions — replayable and auditable later
  • State after restart
  • Explicit typed chunk store inside the harness
  • State lives in the user's own wallet — portable across devices, works offline, outlives the app
  • Trust routing
  • File-sensitivity score picks first-party vs cheaper models
  • Routing by data ownership and residency, including fully local models (Ollama / in-browser) with no cloud hop
  • Policy
  • Programmable allow / ask / deny command policies
  • Allow / ask / deny plus hash-verified governing principles (COPE) on every action

Jev's column is limited to what its public blueprint describes. The CAPPZ column lists shipped platform capabilities. The advantages are our interpretation. No speed or cost multipliers are claimed for either side. CAPPZ is not affiliated with TypeSafe. Source: Jev Engineering for Coding Agents (Sept 2026) — Independent synthesis of design notes by Diogo Almeida (TypeSafe); not affiliated with or endorsed by TypeSafe.

One wallet container. Any skill. Zero rogue supply chain.

Five substitutions collapse the modern stack into a sovereign, wallet-first substrate. Wallets talk to each other directly — off-chain, private — anchoring only what needs anchoring.

Hash-verified on-chain manifest. No rogue postinstall spreading across the globe.

HD-addressed multi-master repos. Parallel-use with GitHub — no central host to compromise.

Wallet-first hydration (AX-74). TX graph is canonical; caches are disposable.

Every app is a wallet with an embedded admin agent and its included skills.

cappz-sessions + chainlets + A2A sync. Wallets talk directly — off-chain, private, no broker. Lifecycle + signaling TXs flushed to chain opportunistically.

Apps are skills. Skills are apps.

Recursion terminates at substrate primitives (RBAC #88, Build #87, Notarization, CPM, …). Every node clones from an on-chain template anchored to a registered ontology / codex.

App (wallet container) ├─ Embedded Admin Agent ← AI + BPMN + edge functions └─ Included Skills ├─ Skill A (wallet container) │ ├─ Admin Agent │ └─ Included Skills │ └─ Skill A.1 (wallet container) … └─ Skill B (wallet container) └─ … Every node clones from an on-chain template anchored to a registered ontology / codex. Recursion terminates at substrate primitives (RBAC #88, Build #87, Notarization, CPM, …).

Off-chain data plane. On-chain anchor plane.

The middleware hub just became optional. A2A Transceiver skills unite Receiver and Transmitter so parties post SyncOffered asks and SyncRequested bids for contracts, applications, data, code, or models, then synchronize multi-master shared state bilaterally. Payloads stay encrypted between wallets; the chain carries only discovery, match, payment, hashes, provenance, and lifecycle evidence.

HD-addressed channel between wallets. SessionOpenedTx / SessionClosedTx anchor lifecycle boundaries — optional and opportunistic.

Purpose-built micro-blockchain per session or topic. Local-first blocks; heads exchanged peer-to-peer.

Edge-to-edge block exchange between participating wallets. No broker. No shared server. Governed by a2a-sync.bpmn.

Payload never touches the chain. Only lifecycle (open/close), signaling (linkage-auth request/grant), and dispute anchors are flushed to disk opportunistically. Truly decentralized: private data stays off-chain, provenance anchors on-chain when it matters.

The Bible Codex

Five canons. Cross-language equivalency via KJV. Every verse a notarized HD node.

Bible Codex

Apply to your domain

See the codex live

Browse canons, traverse equivalencies, inspect notarization TXs.

Same stack, new corpus.

Statutes, cases, contracts

HL7 vocabularies, drug monographs

Papers, datasets, software

RTL, testbenches, datasheets

US 11,645,632 B2

The substrate is anchored by an issued US patent and a provisional registry covering COOL, COPE, and the wallet-substrate pattern.

Provisional registry maintained at src/data/patentRegistry.ts. Every claim cross-references the axiom (AX-*) and event type (e.g. ContentIngested) it governs.

Twenty years of secure-boot DNA.

CAPPZ subsumes a prior secure-boot/BitLocker patent that drove an estimated $200B+ in Enterprise Agreement upgrade revenue over twenty years. The substrate inherits that lineage and extends it from device boot to the entire AI graph.

Four lanes. One substrate.

Place your stack on the board. The recipe stays the same.

Device root · TrustZone

Model lineage · dataset royalties

Tool plane · MCP-native skills

Cite-and-earn corpora

Compressed wallets, lazy reads, archive by replication

Unzip only on a cache hit

Three notarized TXs

Axioms & anti-patterns

AX-1 … AX-92

AP-1 … AP-22

Replicator

Replicator keeps every copy of a business document on the same version and records the history of each change.

Transporter

Transporter is how Replicator moves data: framed, encrypted, resumable, and proven on arrival by a checksum receipt.

CommandBridgeZ

CommandBridgeZ gives operators one bridge — Captain, Helm, Comms, Science and Engineering — over the same wallet context.

BibTeX

@techreport{cappz_substrate_2026, author = {{CAPPZ.AI}}, title = {The Autonomous AI Substrate: Reliable AI through Blockchain-Anchored Ontology (COOL + COPE)}, institution = {CAPPZ.AI}, year = {2026}, number = {v6}, url = {https://cappz.ai/whitepaper}, note = {Patent: US 11,645,632 B2} }