docs(adr): clarify result row sidecar identity#1556
Merged
Conversation
Deploying agentv with
|
| Latest commit: |
e2867cc
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://173f84b7.agentv.pages.dev |
| Branch Preview URL: | https://docs-row-id-result-layout.agentv.pages.dev |
ad76759 to
0456fa6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Reconciles the accepted result-layout ADRs with the final merged layout from PR #1558: an AgentV invocation writes under
.agentv/results/<experiment>/<timestamp>/, and each target plus optional variant gets its own nested result bundle withindex.jsonl,summary.json, and deterministic<row_id>/run-1,<row_id>/run-2, etc. sidecars.This keeps
experimentas the campaign namespace and the timestamp as the invocation/batch folder, while making the target/variant folders storage isolation and manual browsing aids only. Dashboard and readers discover nestedindex.jsonlmanifests, then use manifest and row metadata for target, variant, eval path, suite, and test identity semantics.Changes
.agentv/results/<experiment>/<timestamp>/<target>/<variant?>/bundles, each with its ownindex.jsonlandsummary.json.row_iddirectories inside each target/variant bundle, with repeated runs underrun-1,run-2, and so on.index.jsonlbundles remain readable.target,variant,eval_path,suite, andtest_idsemantics come from summary/index metadata, not folder-name parsing.rows/parent folder, no new experiment artifact, and no hard-coded Next/Vercel semantics.Testing
git diff --check origin/main...HEADbun run beads:check(passes with existing warning:.beads/config.yamlmissing in this worktree)