Skip to content

Add trace artifact v0 for bean-run#2

Merged
aid-ninja merged 2 commits into
mainfrom
trace-artifact-v0
Jun 21, 2026
Merged

Add trace artifact v0 for bean-run#2
aid-ninja merged 2 commits into
mainfrom
trace-artifact-v0

Conversation

@aid-ninja

Copy link
Copy Markdown
Contributor

Summary

  • Writes one post-run trace artifact to .bean/runs/<run_id>.json
  • Adds schemas/trace.schema.json and skills/bean/references/trace.md
  • Covers the stable artifact shape in conformance
  • Ignores emitted runtime traces (**/.bean/runs/, **/.bean/verdicts-raw/); schema/docs stay tracked

Scope

This does not add cross-task learning, memory mutation, prompt rewriting, or cross-run optimization. It only emits a stable trace/certificate artifact for future tooling to consume.

Validation

  • npm test
  • node test/conformance.mjs
  • cargo fmt --check --manifest-path rs/Cargo.toml

🤖 Generated with Claude Code

aid-ninja and others added 2 commits June 20, 2026 23:08
bean-run now writes .bean/runs/<run_id>.json after every run: schema_version, run_id, goal,
started_at/ended_at, status, certificate, rounds, pivot_count, blockers_opened/blockers_closed,
verifier_verdicts, residuals, artifacts_changed. One file per run (not a rolling file), so
future tooling can analyze a corpus of runs without scraping transcripts.

Scope: this does NOT make bean learn across tasks — no memory mutation, prompt rewriting, or
cross-run optimization. It only emits the artifact so a future hill-climbing loop has a stable
format to build on.

- schemas/trace.schema.json — the v0 shape (required keys, types).
- skills/bean/references/trace.md — schema docs + the scope note.
- test/conformance.mjs — asserts a driver run writes the artifact with the stable shape
  (schema_version, all required keys, filename == run_id, status matches the run outcome).

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
…write

- Schema top-level is now additionalProperties:false (unknown keys rejected, catches drift);
  additive/experimental fields go under a documented `metadata` object hatch (emitted as {}).
- bean-run fails CLOSED on a trace-write failure: prints the outcome to stderr and exits 3
  (infra/load error, distinct from any convergence outcome) instead of reporting a clean run.
- Conformance asserts metadata present + no unknown top-level keys; docs note the stability
  rules and that sample-trace fixtures belong in test/fixtures/traces/, never under the ignored
  .bean/runs/.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
@aid-ninja aid-ninja merged commit ea363b8 into main Jun 21, 2026
3 checks passed
@aid-ninja aid-ninja deleted the trace-artifact-v0 branch June 21, 2026 04:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant