Fleet dogfood wiring for WP2 telemetry and WP3 return accounting

[kyle-sexton]

Context

WP2 (telemetry) and WP3 (return accounting) shipped contracts, capture slices, and live-proven demos, but the standing fleet does not yet emit the telemetry contract or write return-accounting records in production use. Until the fleet is wired, the contracts have no continuous real-world exercise and regressions surface only in demos.

Proposed work

• Wire the standing fleet's trigger/pipeline path to emit the WP2 telemetry contract (TRACEPARENT inheritance, autonomy.work_item.url resource attribute) on every autonomous run.
• Wire work-item close/attestation flow to write WP3 return-accounting records (marker record at close, attestation upsert) for fleet-executed items.
• Verify the join (telemetry ↔ return records) end-to-end on a real fleet work item.

Acceptance criteria

• A fleet-executed work item produces a single trace with the pinned contract emissions and a joinable return-accounting record.
• The join query (as demoed with DuckDB in WP3) succeeds against production-path data.

References

• WP2 PR: feat(autonomy): telemetry contract + setup slice, conformance check, live-proven demo (WP2) #343
• WP3 branch: feat/autonomy-return-accounting
• Demo fixtures: plugins/autonomy/skills/setup/evals/fixtures/otlp-demo/

---

Reference: Boris Cherny, "Steps of AI Adoption" (Google Doc)

[kyle-sexton]

Reference — Boris Cherny AI Software Factory autonomy-levels doc (upstream source for the autonomy/WP program): https://docs.google.com/document/d/1R91ayvj7uvlxgNi--__2-Bf3w8x5r1nF-xIBN7ds8Ns/edit — companion artifact link (currently failing to load, may need re-share): https://claude.ai/code/artifact/bfdfaef9-bc62-4dfe-ba9e-c58a26c9accf

[kyle-sexton]

Fleet dogfood wiring — delivered and proven end-to-end (2026-07-20)

Standing emission (WP2 leg): dotfiles PR melodic-software/dotfiles#236 (MERGED, applied) adds the session-telemetry env block to the chezmoi-owned settings overlay — every session on a converged machine now emits all three signals OTLP to the provisioning-owned loopback collector. Verified live post-apply (env present in ~/.claude/settings.json; fresh emissions in the collector store).

Production-path run (WP2+WP3 join): proving-ground item kyle-sexton/autonomy-demo-scratch#4 executed through the new tools/autonomy-demo/dispatch-item.sh wrapper: seam claim (binding TTL) → per-item OTEL_RESOURCE_ATTRIBUTES + TRACEPARENT injection (per the #351 decision) → agent session did the work and pushed → contract-authored wrapper span (pinned schemaUrl 1.43.0) → item closed with the WP3 marker-keyed return record + two-question attestation prompt.

Acceptance query (DuckDB, tools/autonomy-demo/verify-join.sh):

[{"item_url":"https://github.com/kyle-sexton/autonomy-demo-scratch/issues/4","trace_id":"c1dd1fe7d66d3401084c9c91d5044cad","schema_url":"https://opentelemetry.io/schemas/1.43.0","session_emissions":1,"attested":false}]

One row: the work item joins the wrapper span, the native session telemetry, and the return-accounting record on the Pillar-2 attribute. Both acceptance criteria hold: single trace with pinned contract emissions + joinable record ✔; the DuckDB join succeeds against production-path data ✔.

attested:false is correct pending the human reply to the attestation prompt on item #4 (record stays conforming; attestation upserts it per the WP3 lifecycle).