Agent Manifest Schema

Every agent must register a signed manifest before bus participation
Manifest declares: agent ID, role, allowed packet types, capability list, PII clearance level
Bus validates manifest signature before any packet is routed from or to the agent
Undeclared capabilities blocked at runtime — no manifest entry = no permission
Manifest version controlled — changes require re-registration and re-signing
Capability inheritance — child agents inherit parent manifest constraints
Manifest hash logged to the append-only agent registry
Cross-references Patent 11 (Agent Bus) — bus enforces manifest at routing layer
Cross-references SPEC-03 (PII Gate) — PII clearance level declared in manifest
OCC-encoded manifest ID for constrained channel publishing

Schema version check—

Agent identity format (FIRST.LAST.N@DOMAIN)—

Role definition valid—

Capability list — no undeclared permissions—

PII clearance level declared—

Manifest signature valid—