Weaver Conformance Scoreboard
August 10, 2026 · View on GitHub
Important
This checked-in file is a snapshot copied from a successful Scoreboard
workflow run. For the latest sibling reachability/conformance results, use the
most recent Scoreboard Actions run and its job summary/artifact. The timestamp
below identifies exactly when this snapshot was generated.
Public, automatically-generated conformance status for the Weaver Stack.
Each sibling repo opts in by publishing a signed TraceBundle at a
well-known URL; the scoreboard fetches it and runs the conformance pack
(conformance/run.py) against it. See SCOREBOARD.md to
participate.
- Spec contract version:
v0.8.0 - Last updated: 2026-08-10T07:53:12Z
| Repository | Status | Checks | Detail |
|---|---|---|---|
| weaver-spec | ✅ pass | 47 | reference corpus |
| contextweaver | ⚪ not-submitted | — | no bundle published this run |
| agent-kernel | ⚪ not-submitted | — | no bundle published this run |
| ChainWeaver | ⚪ not-submitted | — | no bundle published this run |
Status meanings: pass — the published bundle satisfies the schemas, invariants, and signature checks; fail — it was reachable but did not; not-submitted — no bundle was reachable at the registered URL this run.
Note
A passing row attests that a published artifact satisfies the conformance suite at the listed contract version. It does not attest to the correctness or security of the implementation behind it.