Skip to main content
⚠️ Draft — Non-authoritative content (noindex)
NORMATIVE DRAFTDRAFTprotocol
Truth Source: Repository schemas and tests are authoritative.

Module Event Matrix

Scope​

This page documents the frozen MPLP module/event mapping as declared in:

  • schemas/v2/taxonomy/module-event-matrix.yaml

It records the machine-readable module-to-family relationships carried by that file. It does not add emission doctrine, trigger algorithms, or runtime implementation rules beyond the frozen matrix.

Non-Goals​

This page does not define:

  • new module emission obligations
  • new trigger-point doctrine
  • event-bus implementations
  • SDK emitters
  • derived validation rules beyond the frozen matrix artifact

1. Purpose​

The module-event matrix is the frozen mapping layer that relates L2 modules to general event families for observability coverage.

It records:

  • primary vs secondary family associations
  • machine-readable event-type examples and trigger labels
  • a compliance summary block

2. Frozen Module-to-Family Mapping​

2.1 Primary and Secondary Family Associations​

From schemas/v2/taxonomy/module-event-matrix.yaml:

ModulePrimary FamiliesSecondary Families
contextimport_process, graph_updateintent
planpipeline_stage, graph_updatemethodology, impact_analysis
tracenone (consumer role)cost_budget
rolegraph_updatenone
confirmpipeline_stage, graph_updatereasoning_graph
dialogintent, delta_intentnone
collabpipeline_stage, runtime_executionreasoning_graph
extensionruntime_execution, external_integrationnone
networkgraph_updateruntime_execution
corepipeline_stagecost_budget, compensation_plan

2.2 Trace Special Case​

The frozen matrix marks trace with:

  • role: "consumer"
  • primary_events: []

This page does not expand that into a broader persistence doctrine.

3. Frozen Compliance Summary​

The matrix file includes this compliance summary:

Required Event Families​

  • graph_update
  • pipeline_stage

Required Producers​

FamilyRequired Producers
graph_updatecontext, plan
pipeline_stageplan

Validation Rule Labels In Matrix​

The frozen matrix also includes:

  • all_modules_emit_required
  • trace_receives_all

These labels belong to the frozen machine-readable matrix artifact. This page does not expand them into an independent prose doctrine.

4. Relationship to Other Frozen Sources​

Use this page together with:

  • schemas/v2/taxonomy/event-taxonomy.yaml
  • the referenced event schema files
  • schemas/v2/invariants/observability-invariants.yaml

This page should not be read as overriding any of those sources.

5. What This Page Does Not Create​

This page does not create any of the following as new protocol obligations:

  • “every module MUST emit X” rules beyond the frozen matrix summary
  • per-trigger lifecycle rules
  • event payload requirements beyond the referenced event schemas
  • implementation helper classes or emitter APIs

If a specific obligation is not present in the frozen matrix, taxonomy, or event schemas, this page should not be read as creating it.

6. Canonical Reading Path​

Read module/event meaning in this order:

  1. schemas/v2/taxonomy/event-taxonomy.yaml
  2. schemas/v2/taxonomy/module-event-matrix.yaml
  3. the relevant event schema file
  4. schemas/v2/invariants/observability-invariants.yaml

7. References​

  • schemas/v2/taxonomy/module-event-matrix.yaml
  • schemas/v2/taxonomy/event-taxonomy.yaml
  • schemas/v2/invariants/observability-invariants.yaml
  • Event Taxonomy

Final Boundary: this page identifies the frozen module/event mapping only. It does not create new emission or trigger doctrine beyond the frozen matrix.