INFORMATIVEACTIVE
Truth Source: Repository schemas and tests are authoritative.
Observability Overview
[!NOTE] Non-Normative Document
This page is informative only. It restates schema structure for navigation purposes.
SSOT Reference: Authoritative observability definitions live in Repository schemas.
What This Section Contains
MPLP specifies observability contracts for event and trace visibility. This section routes readers through the event, invariant, and trace references without creating a second observability doctrine layer.
| Document | Purpose |
|---|---|
| Event Taxonomy | Event family classification |
| Common Schemas Reference | Shared schema elements |
| Physical Schemas Reference | Storage format schemas |
| Observability Invariants | Correctness constraints |
| Module-Event Matrix | Module to event mapping |
| Runtime Trace Format | Trace and export reference |
| Observability Overview | High-level orientation |
Reading Path
- Start with: Event Taxonomy Establish the event families first.
- Then: Common Schemas Reference and Physical Schemas Reference Ground the event family model in the underlying schemas.
- Then: Observability Invariants Read the observability correctness layer.
- Then: Module-Event Matrix Read module-to-event routing after the family and schema baseline is clear.
- Last: Runtime Trace Format and Observability Overview Use these as downstream trace/export and orientation surfaces.
Related Resources
- Architecture Overview — L1-L4 layer model
- Modules Overview — Module definitions
- Repository Schemas — SSOT
schemas/v2/taxonomy/event-taxonomy.yaml— machine-readable event taxonomyschemas/v2/taxonomy/module-event-matrix.yaml— machine-readable module/event mapping
Establish event-family and schema meaning before reading trace/export guidance.