Packets
Packet Intake
Packets are treated as untrusted exchange objects until schema, provenance, permission, compatibility, Memory Firewall, audit, and rollback gates pass.
Packets
Cognitive Packet Classes
What flows through the exchange: persona.packet.v2, memory.packet.v2, skill.packet.v2, protocol.packet.v2, capability.packet.v2, and governance.packet.v2.
Packets
Packet Classes
persona.packet.v2 defines identity and behavioral posture. memory.packet.v2 carries durable context with provenance and import rules. skill.packet.v2 describes task capability and least-privilege tool boundaries. protocol.packet.v2 defines rules of engagement and escalation. capability.packet.v2 bundles reviewed packet state behind readiness scoring. governance.packet.v2 defines runtime policy thresholds, continuation rules, pause/explain requirements, observability, and human approval triggers.
Packets
Zero Blind Imports
The exchange does not endorse copying loose prompts or unreviewed memories into active context. Review and rollback gates come first.
Packets
Trust Metadata
Every packet-facing surface must be able to represent packet class, schema identifier, schema reference, schema version, source provenance, source confidence, risk level, compatibility score, scope boundary, permission class, import rule, quarantine status, review status, contradiction status, evidence path, approval state, rollback readiness, adoption preview result, supersession state, last reviewed UTC, durable mutation status, operator authorization requirement, human-readable inspection summary, and machine-readable JSON representation.