The master scorecard is the repository's release-facing quality contract. It turns broad platform expectations into auditable test suites across model, cache, command metadata, strategy, data, execution, reconciliation, risk, portfolio, backtest, live node, adapters, and documentation.
testsuitedefines suite requirements, point weights, case IDs, package owners, and report sources.- Complete Feature Matrix maps platform surfaces to owners and acceptance suites.
- Adapter Capability Matrix records current venue capability claims.
- Complete Quality Gate lists release review and verification requirements.
The score is intentionally case-based. A suite receives credit only when the corresponding behavior exists, is tested, and is not skipped.
Focused metadata and scorecard checks:
env GOCACHE=/private/tmp/go-build-exchanges go test -count=1 ./testsuite -run 'Master|Score|Requirement|QualityGate|ReleaseNotes' -vRuntime and lifecycle checks:
env GOCACHE=/private/tmp/go-build-exchanges go test -count=1 ./model ./cache ./account ./execution ./risk ./portfolio ./platform ./strategy ./backtest ./live ./testsuite -vAdapter capability checks:
env GOCACHE=/private/tmp/go-build-exchanges go test -count=1 ./venue ./adapter/... ./config/all ./testsuite -run 'Adapter|Capability|Contract|PrivateStream|Resubscribe' -vHygiene checks:
env GOCACHE=/private/tmp/go-build-exchanges go test -run '^$' -count=1 ./sdk/...
go vet ./...
git diff --checkA release can claim a capability only when:
- the relevant scorecard case is present and passing;
- adapter declarations match implementation and contract evidence;
- reconciliation unresolved discrepancy behavior is documented;
- unsupported behavior returns explicit unsupported errors;
- verification evidence and residual risks are attached to release notes.