Vertical acceptance matrix
Prove rules, package behavior, input equivalence, product journeys, creator evidence, and release integrity at the right layers.
One giant UI test is not sufficient evidence. A deep vertical closes through a layered matrix whose failures explain what broke.
| Layer | Required proof |
|---|---|
| Pure domain | rules, normalization, edge cases, exact metrics, deterministic fixtures |
| Engine conformance | initialization, revisions, idempotency, terminal behavior, effects |
| Input equivalence | paired manual/automatic sequences produce identical semantic outcomes |
| Workbench | real player, overlay, lifecycle, viewports, reduced motion, accessibility |
| Connector Lab | raw source fixture, protocol lifecycle, exact observation, diagnostics |
| Runtime/API | release pinning, persistence, history, progression, Sprint evidence, isolation |
| Member product | Library → installed Suite → Attempt → result → repeat, on real hosts |
| Creator | Story Events → Station → OBS clock → anchors → sealed evidence → Studio |
| Evolution | presentation-compatible upgrade, breaking lane split, rollback, old-run pinning |
Failure cases are part of the product
Inject at least:
- duplicate commands and observations;
- stale source revision and reconnect replay;
- connector unavailable before and during an Attempt;
- manual fallback while automatic input is unavailable;
- invalid schema identity and revoked grant;
- overlay, narration, capture, and Studio unavailable after commit;
- active and terminal correction with Story Event retraction;
- package upgrade while an older run remains active.
The invariant is simple: authoritative activity commit never waits for a derived consumer. A disconnected overlay or failed narration may reduce the creator experience, but it cannot erase valid practice.
Retained evidence
A release gate should produce a typed report with exact source fingerprint, stage results, artifact digests, fixtures, safe logs, JUnit where useful, screenshots, accessibility results, and clear deferrals. Cached evidence is reusable only when every relevant source byte and retained prefix artifact is unchanged.
Darts commands to study
packages/darts-core/package.jsonThe package-local test and readiness commands for the immutable release.
scripts/station-api-smoke.mjsDomain-neutral composition from Library through Studio intake when CM_CAPABILITY_STACK is enabled.
scripts/darts-gold-path.mjsLayered orchestration and exact evidence validation for the reference vertical.
scripts/darts-legacy-migration.mjsHistorical comparability, isolation, recovery, and cross-surface migration evidence.
Physical hardware and subjective art direction remain deliberate launch checks; they do not replace deterministic correctness and they should not block earlier engineering tranches.