RequestSource record
Feature request
The approved request asked for an auditable route from bounded agent work into deterministic verification.
- Public source
- Approved public work ledger
- Record ID
ys-ysw-1j56- Source revision
2d2922a5c74d3b01…
End-to-end public evidence
Integrate deterministic refinery verification
Connect bounded agent work to a serialized verification lane and preserve the evidence used to admit a candidate.
This evidence snapshot may be stale.It expired on . The trace remains attributable, but newer source revisions are not represented.
No Yesod knowledge required
What the terms mean
Read the journey from top to bottom. Every item says whether it is a record, a summary, a redaction, or an explicit gap.
- Yesod note
- The durable feature record that keeps the request and outcome under one public identifier.
- Bead plan
- The small tracked work items used to turn a feature into an ordered implementation plan.
- Verification gate
- A named check that must pass before a candidate is allowed into the durable main branch.
- Run
- One observed execution attempt. It is kept separate from the delivered feature outcome.
- Development wave
- The product theme that groups related work; it provides context, not proof of delivery.
- Source record
- A reviewed public record pinned to an exact source revision.
- Derived summary
- A summary whose source inputs are linked on this page.
- Redacted
- A known category withheld under the public evidence policy.
- Missing evidence
- No approved public record was available when captured.
Request to release
The complete public journey
The order is editorial, not a claim that every system clock was synchronized. Each source date and revision remains attached to its own record.
- NoteSource record
Yesod feature note
The feature note kept the request, acceptance boundary, and delivery outcome under one durable public identifier.
- Public source
- Approved public work ledger
- Record ID
ys-ysw-1j56- Source revision
2d2922a5c74d3b01…
- PlanMissing evidence
Bead plan
No Bead plan was present in the approved public work snapshot for this feature.
What is missingNo approved public Bead record was available at snapshot capture; no private plan is inferred.
- BranchSource record
Feature branch
The bounded implementation was recorded on the feature branch before refinery admission.
- Public source
- Public GitHub repository
- Record ID
yesod-ys-ysw-1j56- Source revision
d05ac2fd1def2a07…
- CommitSource record
Integration contract commit
The first feature commit documented the connection between bounded work and the deterministic refinery.
- Public source
- Public GitHub repository
- Record ID
2e02f4c06a0164b01f248b664ad07b2f985915e4- Source revision
2e02f4c06a0164b0…
- CommitSource record
Reconciliation commit
A follow-up commit reconciled the integration wording on the same feature branch.
- Public source
- Public GitHub repository
- Record ID
d05ac2fd1def2a076e68bc4610c5f4919060bb5e- Source revision
d05ac2fd1def2a07…
- VerificationSource record
Integration contract gate
The public work record marks the responsibility and handoff contract as passed.
- Public source
- Approved public work ledger
- Record ID
integration-contract- Source revision
2d2922a5c74d3b01…
- VerificationSource record
Deterministic merge gate
The public work record marks independent candidate verification and admission as passed.
- Public source
- Approved public work ledger
- Record ID
deterministic-merge- Source revision
2d2922a5c74d3b01…
- MergeSource record
Refinery merge commit
The two-parent refinery candidate joined the verified feature branch to the durable main-branch record.
- Public source
- Public GitHub repository
- Record ID
2bcec128f372e3fe78cbd74ce6604b95d1d7ff43- Source revision
2bcec128f372e3fe…
- RunSource record
Public run observation
The allowlisted run completed successfully and records one delivered work outcome.
- Public source
- Approved public run ledger
- Record ID
run-refinery-integration-1- Source revision
df0033f2dde310fd…
- CostSource record
Public cost observation
The public ledger attributes a USD 4.28 actual metered charge to the run.
- Public source
- Approved public cost ledger
- Record ID
spend-refinery-integration-1- Source revision
df0033f2dde310fd…
- WaveSource record
Foundation development wave
The public roadmap places the released feature in the Foundation development wave.
- Public source
- Approved public roadmap
- Record ID
foundation- Source revision
issue-7-r1
- MergeDerived summary
Delivered outcome summary
A reviewed branch passed its public gates, entered main through the refinery, and produced one delivered run with attributed cost.
- RunRedacted
Execution internals
Prompts, transcripts, logs, environment values, and repository contents are not part of this public trace.
Why redactedPrivate execution material is excluded by the public-evidence-v1 policy.
Connected public surfaces
Follow the source records
These links open the already-public work, run, cost, and roadmap views used by the trace. Each keeps its own source revision.
Freshness and provenance
Pin the claim,
then read it.
The trace expires when its earliest upstream public snapshot expires. It remains readable for attribution after that date, with a stale warning.
- Snapshot
- evidence-traces-2026-08-11
- Policy
- public-evidence-v1
- Generated
- Valid through
- Source revision
dc026254c5…- Content digest
ad684ba41f60…
| Source | Snapshot | Revision |
|---|---|---|
| Work | factory-2026-08-10 | 2d2922a5c74d… |
| Run | factory-runs-2026-08-10 | df0033f2dde3… |
| Spend | factory-spend-2026-08-10 | df0033f2dde3… |
| Roadmap | roadmap-issue-7-r1 | issue-7-r1… |
Limits stay attached
What this trace does not prove
A public trace explains one approved delivery. It is not a complete view of private work, all factory activity, or total provider spend.
- 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.
← Return to all evidence tracesHow evidence-bearing outcomes work