Protocol infrastructure for AI state

The commit layer for the semantic internet.

ZiiBii is the runtime that decides when AI-generated meaning can become trusted state. Models propose meaning. CAM Wire commits only what is evidence-backed, authority-valid, replay-safe, and allowed to become real.

State machine CAM Wire packet

semantic_state_machine.v0mode: default-deny

PROPOSED

A model, agent, user, or system proposes meaning.

CHECKING

The microkernel checks evidence, authority, scope, registry, hash, replay, and permission.

COMMIT

Only validated semantic state is allowed to become real.

COMMITValidated state change with receipt.

DENYUnsupported or unauthorized meaning fails closed.

HOLDNeeds more evidence, scope, or authority.

ESCALATERoutes to stronger verification or human review.

REPLAY_NOOPDuplicate semantic state is recognized without side effects.

The core correction

AI output is not trusted state.

The old internet is good at moving pages, files, and API calls. The semantic internet needs a deeper boundary: a way to decide whether generated meaning is allowed to become durable state.

ZiiBii makes that boundary explicit. Every proposed semantic change must pass through a small default-deny kernel before software, people, records, or downstream agents can rely on it.

evidence_idauthoritytenant_scopeschemapermissionpacket_hashregistryreplay

Semantic microkernel

Small core. Strict boundary. Large systems above it.

Encode

Turn free-form model output into a compact semantic packet with fixed fields.

Bind

Attach evidence, authority, tenant, permission, schema, and packet identity.

Validate

Run the proposal through deterministic checks before state can change.

Commit

Emit a receipt, denial, hold, escalation, or replay-safe no-op.

CAM Wire packet

kindsemantic_commit

proposalagent.claim:settlement_ready

whyevidence-backed state change

avoidunsupported mutation

evidence_idssrc:042, src:117

authoritytenant.authority.grant

commit_actioncommit_or_deny

packet_hash7b91...e2c4

CAM Wire

A compact semantic packet, not another chat format.

CAM Wire is the syscall-like boundary inside ZiiBii. It turns proposed meaning into a typed packet, binds the packet to evidence and authority, and gives the state machine something deterministic to accept, deny, hold, escalate, or replay.

This is what separates ZiiBii from normal guardrails. The question is not only whether an agent can call a tool. The deeper question is whether the semantic claim or action can become trusted state.

Applications above the kernel

Vertical products prove the layer. They are not the layer.

Litigation work product

ProofDocs

Relativity exports become claim ledgers, exact quote tables, denial logs, chronologies, attorney queues, and audit bundles.

Regulatory decisions

PermitCheck

Permit and compliance claims become source-bound review state before a reviewer signs off.

Semantic contracts

Agent transactions

Agent work can move through contracts, escrow, settlement, and receipt states without trusting free text.

Durable semantic context

Matter Memory

Important facts, permissions, sources, and decisions can persist as inspected state instead of disappearing into chat history.

Future commit envelopes

Media and robotics

Visual, temporal, and physical actions can be treated as proposals until evidence and policy authorize the state change.

Proof discipline

Claims should compile down to artifacts.

ZiiBii should be judged by packets, manifests, tests, denial behavior, replay receipts, and bounded benchmarks. Not by a polished dashboard mockup.

default-deny

Kernel posture

If evidence, authority, packet integrity, registry, permission, or replay checks fail, the safe outcome is non-commit.

semantic receipts

Replay surface

Committed state is tied to packet identity and receipts, not a loose chat transcript.

bounded benchmarks

Internal evidence

CAM Wire, bridge, tripwire, and ProofDocs runs are tracked with conservative claim boundaries before external validation.

Build on the commit boundary

Bring the semantic state your system cannot afford to trust blindly.

The right first conversation is not a generic demo. It is a boundary review: what proposes meaning, what evidence exists, who has authority, what must never commit, and what receipt would make the result inspectable later.

Talk protocol fit