Reference architecture · July 2026

One accountability trace. Six independent planes.

Web7 does not require one cloud, model, database, runtime, or product suite. It defines the contracts and receipts that survive across those boundaries.

Explore the planes Read the specifications
Architecture

Separate ownership. Shared evidence.

The architecture keeps deterministic product state away from model orchestration, keeps approvals away from deployment execution, and keeps the protocol independent from every reference product.
01

Experience plane

Humans and agents express outcomes, inspect plans, approve exceptions, and review evidence.

Reference systemsQuantumOS · AIStudio · product interfaces

02

Domain plane

Deterministic services own money, orders, inventory, consent, access, and other business invariants.

Reference systemsQuantumOS modules · Kynetra applications

03

Action plane

Typed, idempotent actions convert authorized intent into bounded changes without exposing implementation internals.

Reference systemsKynetra FX · KYRx · HBForge

04

Evidence plane

Events, memory, sources, vectors, lineage, receipts, and proof records form the accountable intelligence graph.

Reference systemsKynetraDB · Search · AIG

05

Intelligence plane

Planning, model selection, retrieval, evaluation, approvals, and learning operate within explicit policy and evidence gates.

Reference systemsPrime · KynML · Foundry

06

Operations plane

Releases, canaries, rollback, incident ownership, workload packaging, and audited web actions remain observable and reversible.

Reference systemsDeploy · Resolve · Pods · Browser

The cross-plane contract

The envelope travels. Product ownership does not.

An AMP envelope carries the authority and desired outcome. Each plane adds evidence to the trace while retaining responsibility for its own state, policy, and failure behavior.
01 Intent receipt Principal, goal, scope, budget, deadline, jurisdiction, and acceptance evidence. AMP
02 Authority receipt Identity, delegation chain, tenant, role, consent, and approval state. DID
03 Execution receipt Contract version, idempotency key, tools, resources, runtime, and state transition. Action
04 Intelligence receipt Model, prompt or plan hash, retrieved evidence, evaluation, confidence, and overrides. AIG
05 Outcome receipt Observed result, acceptance checks, SLA, settlement state, exception, and recovery route. PoO
Protocol boundary

What Web7 owns—and what it deliberately leaves open.

Interoperability requires a small, stable center. Product innovation stays outside that center.

Web7 standardizes

  • Intent, delegation, and outcome envelope schemas
  • Identity and actor references
  • Consent, policy, and approval receipts
  • Evidence, provenance, and trace linkage
  • Outcome verification and exception semantics
  • Conformance fixtures and interoperability profiles

Implementers choose

  • Models, prompts, planners, and retrieval systems
  • Application frameworks and programming languages
  • Databases, vector stores, queues, and clouds
  • Domain schemas and business authorization rules
  • Deployment topology and operational tooling
  • Settlement rails and recovery mechanisms
Initial reference stack

Kynetra supplies an implementation—not a dependency.

Teams can adopt the full reference stack, replace one plane at a time, or implement only the protocol receipts around an existing system.

Prime + Auth + KTL

govern

Canonical planning, policy, approval, identity, tenant, consent, and governed-learning control surface.

Prime ↗ Auth ↗ KTL ↗

FX + KYRx + HBForge

execute

Contract-first APIs, portable action handlers, compiler-checked workflows, and zero-dependency application modules.

Kynetra FX KYRx ↗ HBForge ↗

KynetraDB + Search

evidence

Portable events, memory, full-text and vector retrieval, graph relationships, lineage, proofs, and answer traces.

KynetraDB ↗ Search ↗

KynML + Foundry + Deploy

lifecycle

Compiler-checked training intent, evaluation evidence, promotion candidates, release plans, canaries, and rollback.

KynML ↗ Foundry ↗ Deploy
Proposed conformance profiles

Adopt accountability in bounded steps.

The profiles below describe the direction of the conformance suite. They are marked proposed until their fixtures and test harnesses complete RFC review.
proposed W7 Core Signed intent, actor reference, versioned action contract, evidence linkage, and outcome receipt.
proposed W7 Governed Core plus tenant scope, consent, policy decision, approval state, and accountable overrides.
proposed W7 Verifiable Governed plus independent outcome checks, tamper-evident trace continuity, and declared recovery behavior.
Start with one action

Map its authority, contract, evidence, and outcome.

A useful Web7 implementation begins with one material workflow—not a wholesale platform replacement.

Open the quick start Read AMP Review the RFCs