Repository navigation
feat: aggregate per-platform acceptance reports into a verification matrix - #289
Merged
Merged
Conversation
…atrix Issue #287 asks that cross-platform parity stop being implicit. The acceptance orchestrator already emits a machine-readable report per platform; what was missing is the place where those reports become one verdict an agent can act on from any editing OS. raco rivet matrix folds the reports for one commit into that verdict: a required kind/platform cell is proven only by a passing suite of that kind on that platform's report, failed evidence fails the cell, and an unreported platform is missing - never silently green. All reports must describe one project, so a green leg cannot vouch for another product. docs/product-acceptance.md adds the guaranteed / conditional / platform-specific capability classification and the matrix contract; docs/agent-native.md and AGENTS.md state that the local operating system bounds only where checks can run, never the required verification scope.
turinglambdaai
force-pushed
the
feature/acceptance-matrix
branch
from
October 19, 2026 04:16
76c41c2 to
ef4e26b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Takes the first implementation slice of #287: the acceptance orchestrator
already emits a machine-readable report per platform — what was missing is
where those reports become one verdict.
raco rivet matrix <report.json>... [--json]kind in a report from that platform; ran-but-failed evidence fails the
cell; an unreported platform is missing, never silently green.
cannot vouch for another.
--suiteruns are accepted and flagged as partial; merge gatesfeed complete reports.
project checkout — the aggregation host is anywhere.
Contracts and classification
docs/product-acceptance.md: adds the guaranteed / conditional /platform-specific capability classification from desktop: make feature parity and cross-platform agent verification first-class gates #287 (conditional
adapters must report availability explicitly instead of failing silently),
and the matrix aggregation contract with the deterministic cell rules.
docs/agent-native.md+AGENTS.md: the agent contract now states thelocal OS bounds only where checks can run, never the required verification
scope — the exact rule desktop: make feature parity and cross-platform agent verification first-class gates #287 proposed.
Deferred (still open on #287)
Remote job triggering/orchestration and rich per-suite artifacts
(accessibility snapshots, screenshots) — the matrix consumes whatever the
legs archive today, so those can land incrementally behind the same command.
Verification
raco test rivet/tests/— 10065 passed (21 new inacceptance-matrix.rkt: cell pass/fail/missing, partial runs, malformedand foreign-project rejection, exit codes, CLI smoke).
raco rivet matrixon synthetic reports; usage line viaraco rivet help.Closes part of #287; the issue stays open for the orchestration roadmap.