Connect bounded agent work to a serialized verification lane and preserve the evidence used to admit a candidate.
- Source record
- 11
- Derived summary
- 1
- Redacted
- 1
- Missing evidence
- 1
Public delivery evidence
Follow a feature.
Check every handoff.
Each trace connects a completed feature request to its planning record, code, verification, merge, run, cost, and development wave. Gaps and redactions remain visible instead of being filled with guesses.
This evidence snapshot may be stale.It expired on . The trace remains attributable, but newer source revisions are not represented.
Eligible completed work
Published traces
A trace exists only after explicit public approval and only when its work, run, cost, and roadmap references all resolve. An unresolved connection fails generation.
How to read the record
Four evidence states
Every item prints its state in words. Color helps with scanning, but never carries the meaning alone.
- Source record
- An allowlisted public record with its permanent ID and checked source revision.
- Derived summary
- An interpretation computed only from source records linked on the same trace.
- Redacted
- A known evidence category deliberately withheld under the named publication policy.
- Missing evidence
- No approved public record was available at capture; nothing private is inferred.
Publication boundary
Approved records only
The static site cannot query Yesod, Beads, GitHub, a runner, or billing data. It renders a field-by-field export produced under public-evidence-v1.
- This snapshot joins approved public records; it is not a view into private Yesod, Beads, GitHub, runner, or billing stores.
- A missing item means no approved public record was available at capture, not that no private record exists.
- Redacted execution internals are deliberately outside the public evidence allowlist.
- Run and cost observations are bounded by their own public snapshot windows and should not be read as complete fleet or account history.
Explore the public work ledger →Learn how non-code work is verifiedSee the development roadmap