Crosscut PSG Event Binding
Status: Draft runtime reference
Authority: Non-authoritative documentation surface
Boundary: This page is a conceptual binding aid. It does not create new protocol obligations beyond repository-backed truth sources.
1. Purpose
This page provides a conceptual bridge between:
- crosscut concerns
- PSG-oriented runtime thinking
- existing protocol event families
- learning-oriented runtime hooks
It is intended for runtime designers and reviewers. It is not a canonical event or PSG contract.
2. Reading Rule
Use this page only after reading:
schemas/v2/taxonomy/kernel-duties.yamlschemas/v2/taxonomy/module-event-matrix.yamlschemas/v2/taxonomy/event-taxonomy.yaml- Runtime Glue and related runtime concept pages
If this page appears broader than those sources, those sources prevail.
3. Illustrative Crosscut View
| Concern | Typical Runtime Focus | Typical Existing Event Families |
|---|---|---|
| coordination | collaboration and handoff state | profile-specific MAP events, runtime execution |
| error-handling | failure and recovery state | runtime execution, pipeline stage |
| event-bus | routing/collection of emitted events | all existing protocol event families |
| orchestration | plan/stage progression | pipeline stage, graph update |
| performance | timing/cost/resource signal | cost budget, runtime execution |
| protocol-version | version-carrying object state | graph update, core metadata |
| security | access and control boundaries | implementation-specific evidence around existing protocol artifacts |
| state-sync | consistency between runtime views | graph update |
| transaction | grouped state change and compensation reasoning | graph update, compensation plan |
4. What This Page Does Not Claim
This page does not claim that MPLP mandates:
- one PSG representation per crosscut
- one event-family mapping per local runtime operation
- one learning-family trigger model
- product-specific telemetry fields as protocol truth
It also does not elevate local runtime events into canonical protocol event types.
5. Safe Interpretation
The safest way to use this page is:
- start from the existing protocol event families
- start from the existing kernel-duty and taxonomy sources
- use this page only as an interpretive guide for runtime architecture reviews
6. References
schemas/v2/taxonomy/kernel-duties.yamlschemas/v2/taxonomy/module-event-matrix.yamlschemas/v2/taxonomy/event-taxonomy.yaml- Runtime Glue Overview
- Module PSG Paths
Final Boundary: this page is an interpretive runtime aid. It does not define canonical PSG structures or canonical per-crosscut event obligations.