Architecture
JEP provides a signed event structure that other layers can reference or compose.
Why judgment events need structure
Existing logs, traces, and API records often show execution. They may not consistently represent judgment-related assertions, delegation claims, verification scope, references, independent validation checks, or signed event integrity.
Comparison
API calls, timestamps, traces, tool activity
Event Identity, event verb, claim or digest, reference, extension, signature, independent check results
JEP is not a replacement for logs. It defines a narrow event structure for judgment-related records.
Layered architecture
End-user applications, dashboards, interfaces
MCP, A2A, ACP, AGTP, agent frameworks
Signed JSON events with 11 standard top-level members, including version, event identifier, verb, actor, declared time, claim, references, extensions, and signature.
Deployment-specific trust and validation rules
Long-term storage, timestamping, receipts
JAC and similar chain structures
Analysis, verification, compliance tools
jep · id · verb · who · when · what · aud · ref · ext · ext_crit · sigSeven members are unconditionally required; the rest are conditional or optional.
JEP does not replace any layer. It provides a signed event structure that other layers can reference or compose.
Use cases
JEP may be useful for...