MIDI2 documentation
The machine-readable MIDI 2.0 object, its normative coverage, implementation boundaries, and engineering evidence—published as a human-readable projection of Fountain-Coach/midi2.
Read the contract from source to evidence.
Governance supplies the publication rules. This subdomain supplies the MIDI2 specification, object, implementation, and verification record.
Documentation
docs/README.md
DOCUMENTATIONmidi2
README.md
DOCUMENTATIONSpec Compliance Dashboard (generated)
docs/spec-compliance-dashboard.md
DOCUMENTATIONEvidence-backed Claim Register
docs/claim-register.md
DOCUMENTATIONRuntime Completeness Boundary
docs/runtime-completeness.md
DOCUMENTATIONMIDI 2.0 Conformance Checklist (Status Quo)
docs/conformance-checklist.md
DOCUMENTATIONNormative coverage methodology
docs/normative-coverage-methodology.md
DOCUMENTATIONMIDI semantics and Fountain Coach extensions
docs/midi-vs-fountain-extensions.md
DOCUMENTATIONThird-party MIDI specification sources
docs/third-party-specification-sources.md
DOCUMENTATIONNegative Test Matrix (Reserved/Invalid Values)
docs/negative-test-matrix.md
DOCUMENTATIONNormative MIDI 2.0 Coverage
docs/generated/normative-coverage.md
DOCUMENTATIONGenerated MIDI 2.0 Semantic Traceability
docs/generated/spec-traceability.md
DOCUMENTATIONComprehensive MIDI 2.0 Specification Audit Report
docs/comprehensive-spec-audit-report.md
DOCUMENTATIONMIDI 2.0 Gap Closure Tracker
docs/gap-closure-tracker.md
DOCUMENTATIONMIDI 2.0 Specification Traceability Matrix (generated)
docs/spec-traceability-matrix.md
DOCUMENTATIONSpec Audit Log (generated)
docs/spec-audit.md
DOCUMENTATIONDefinition of Done Traceability
docs/traceability.md
DOCUMENTATIONFountain Coach publication estate crawl
docs/publication-estate-audit.md
Inspect the canonical projections.
These files are published for agents and engineers; their source commit and paths remain explicit.
The repository maintains a versioned, source-traceable machine-readable MIDI2 representation. MIDI Association documents remain normative. Runtime completeness and physical hardware interoperability are separate claims.