Open protocol · Reference implementation active

The accountability layer for agentic systems.

Web7 defines portable contracts for identity, consent, delegation, policy, provenance, outcomes, and rollback—so an AI action can be understood before it runs and proven after it completes.

Explore the protocol See the architecture Ask the standards corpus
Protocol, not a chain Model-neutral Runtime-neutral
Web7 standardizes Accountability contracts
Kynetra implements The reference control stack
HyperBridge proves The contracts in production
Why now

AI can act. The web still cannot explain why.

Today’s protocols prove that a request was sent or a transaction was accepted. They do not consistently prove who authorized an agent, which policy constrained it, what evidence it used, or whether the outcome matched the original intent.

Web7 fills that gap. It is a protocol layer between an agent’s intent and any system the agent can change—not another model, application framework, wallet, or blockchain.

Accountability path

One trace from intent to evidence.

Every material action carries enough context to authorize, execute, inspect, verify, and—when the underlying system supports it—reverse the change.
01 Express intent A principal states the desired outcome, constraints, budget, and acceptance evidence. AMP
02 Authorize scope Identity, delegation, tenant, consent, and policy are evaluated before execution. DID + policy
03 Execute safely A typed, bounded, idempotent action runs through a runtime chosen by the implementer. Action contract
04 Record evidence Inputs, actor, model, approvals, tool calls, state changes, and outputs form one trace. AIG
05 Verify outcome The result is checked against acceptance evidence, policy, and operational guardrails. PoO
06 Settle or recover Systems can release value, compensate, escalate, or invoke a declared rollback path. Receipt
Reference implementation

The surrounding stack caught up with the protocol.

Recent Kynetra advances turn Web7’s primitives into an inspectable implementation across governance, execution, evidence, model lifecycle, operations, and real business systems. Each product keeps a clear boundary; Web7 owns only the portable contracts between them.

Govern

active

Plan work, bind tenant and identity, evaluate policy, request approvals, and govern learning without silently mutating production.

Prime ↗ Auth ↗ KTL ↗

Execute

active

Turn approved intent into typed actions, portable services, application modules, and runtime-specific adapters.

Kynetra FX KYRx ↗ HBForge ↗

Remember and retrieve

active

Keep events, memory, vectors, graphs, lineage, proof records, retrieval traces, and tenant boundaries behind versioned interfaces.

KynetraDB ↗ Search ↗

Build and evaluate

active

Compile training intent, track evaluation evidence, promote bounded candidates, and keep deployment and rollback explicit.

KynML ↗ Foundry ↗ Deploy

Operate

expanding

Give operators visible plans, approval queues, audited browser actions, incident ownership, and governed workload packaging.

AIStudio ↗ Resolve ↗ Browser ↗ Pods
Evidence snapshot · July 2026

Proof before promotion.

These figures describe the current proving ground—not the size of the Web7 standard and not a promise about future throughput.
24 live Kynetra applications across six domains Kynetra ecosystem ↗
40+ HyperBridge platforms shipped to production HyperBridge Digital ↗
77 HBForge modules with zero npm dependencies HBForge evidence ↗
157 semantic passages in the Web7 i18n corpus Query the corpus →
Clear boundaries

Standard, implementation, proving ground.

Web7 becomes more credible when the protocol is not confused with the products implementing it.
01 · Web7 Foundation

Defines portable contracts

Stewards AMP, AIG, Proof-of-Outcome, identity, provenance, conformance profiles, RFCs, and interoperability guidance.

02 · Kynetra

Builds the reference stack

Implements governance, identity, action, evidence, model lifecycle, operations, and developer surfaces without making them protocol requirements.

03 · HyperBridge

Provides production pressure

Runs the architecture against real products and workflows, turning edge cases into specifications, tests, and implementation feedback.

Maturity

What is live—and what is not.

Product evidence and protocol maturity are reported separately. Research targets are not presented as shipped infrastructure.
active Protocol v0.1 AMP, AIG, identity, and outcome-proof specifications are open for implementation and RFC review.
live Reference integrations Kynetra products already exercise typed actions, policy, identity, audit, evidence, retrieval, and governed workflows.
building Conformance suite Portable fixtures, receipts, trace validation, interoperability profiles, and implementation badges are being formalized.
research Trust substrate DAG settlement, ZK-ML, decentralized availability, and performance targets remain research—not production claims.
Build accountable systems

Keep your model. Keep your runtime. Standardize the evidence.

Start with the protocol, map one material action, and make its authority, policy, trace, and outcome independently inspectable.

Start implementing Join the RFC process Read the whitepaper