Skip to main content
INFORMATIVEDRAFTprotocol
Truth Source: Repository schemas and tests are authoritative.

Observability Overview

This page provides a navigational overview of MPLP observability specifications. It does not define normative requirements.

Observability in MPLP ensures that:

  • All agent actions are traceable — Every step, decision, and state change is recorded
  • Lifecycle transitions are auditable — Plan/Step status changes emit structured events
  • Events are consistent across modules — 12 Event Families with schema validation
  • Runtime traces can be exported — W3C Trace Context and OTLP compatibility

Design Principle: "If it happened, it's in the trace"

Normative Specifications​

The following documents define the normative observability semantics:

DocumentPurpose
Event TaxonomyDefines all 12 event families and their semantics
Module–Event MatrixMaps which modules emit which events
Observability InvariantsDefines 12 global observability correctness rules
Runtime Trace FormatDefines trace structure and OTLP compatibility

Reference Artifacts​

ArtifactType
event-taxonomy.yamlMachine-readable event definitions (Schema Truth Source)
module-event-matrix.yamlMachine-readable module mapping (Schema Truth Source)
Common Schemas ReferenceShared schema components
Physical Schemas ReferenceEvent schema details

Required Events (Quick Reference)​

Event FamilyComplianceSchema
pipeline_stageREQUIREDmplp-pipeline-stage-event.schema.json
graph_updateREQUIREDmplp-graph-update-event.schema.json

See Event Taxonomy for all 12 families.

Reading Path​

  1. Start with Event Taxonomy — Understand the 12 event families
  2. Review Module–Event Matrix — See which modules emit which events
  3. Validate with Observability Invariants — Understand correctness rules
  4. Implement export using Runtime Trace Format — Export to external tools

Required Events: pipeline_stage, graph_update
Total Event Families: 12
Export Formats: JSON, JSONL, OTLP, Jaeger