You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Research: small formal contract for canonical score transformations and explicit lossy boundaries #217
P3 / bounded proof-engineering spike / no production rewrite. Inspect the current stage and stop if the planned acceptance tests/fuzz targets already cover this exact invariant.
Why
CreuSAT suggests a useful discipline: specify one algorithm's preconditions, postconditions and state invariants, test a deliberately broken variant, and label trust boundaries honestly. For griff, the boundary matters: per docs/SPEC.md, Guitar Pro/tab is source of truth; MIDI is lossy, so we must not assert that all Guitar Pro articulations/positions survive a MIDI round trip.
Pick one real pure seam
Potential targets, subject to code inspection:
A canonical Score/phrase slicing or shift/transpose operation: preserve event cardinality and relative timing where the operation's documented semantics require it, and preserve unrelated tracks.
Fixed-seed generation: determinism for identical canonical input and policy version, including observable provenance, without conflating different formats.
Swang lowering / program lifting: re-executed program agrees with the supported canonical projection, as required by ADR-0029.
Write an operation-specific contract. For import/export, specify the supported projection and require a typed loss report; do not prove impossible full MIDI↔Guitar Pro identity.
Activity