Expand description
OCSF ai_operation-profile event model (Module E of the brief).
Every event binds agent config state — ai_agent.version, ai_agent.charter,
ai_agent.instance_uid — alongside stop_reason_id, per the pattern authored
in Levaj2000/ocsf-schema PR #1 (merged, aligned with upstream ocsf#1704 /
v1.10.0). The roadmap Fingerprint chaining (per-forward-pass inventory) is
implemented behind OcsfEvent::inventory fields, default None.
Evolution policy (EVOLUTION.md): inbound-tolerant (top-level unknown
fields land in unmapped; nested objects stay strict), outbound-strict
(emitters always produce the current schema).
Re-exports§
pub use model::AgentIdentity;pub use model::CharterFile;pub use model::EventClass;pub use model::EventMetrics;pub use model::Fingerprint;pub use model::Metadata;pub use model::OcsfEvent;pub use model::OcsfEventBuilder;pub use model::Product;pub use model::StatusId;pub use model::CATEGORY_UID;pub use model::OCSF_VERSION;pub use model::PRODUCT_NAME;pub use stop_reason::StopReason;pub use validate::validate_event;pub use validate::ValidationError;
Modules§
- model
- Event envelope, agent identity block, event classes, metrics, fingerprints.
- stop_
reason - Stop-reason identifiers.
- validate
- Structural validation for events, independent of (and cross-checked against) the shipped JSON Schema.