Repository navigation
record pack: agent-session-trajectories — 70 sanitized multi-session agent trajectories with failure turns intact - #1255
Merged
Conversation
…gent trajectories, failure turns intact) Domain: an agent operating a production multi-agent engineering org queries this corpus for precedent on failed approaches, their diagnosis, and the fix that worked. Records are unique by id (nst-<session-key>); 70 envelopes -> 70 records, no alias resolution (single source). Topics: eval-judging 46 / infra-diagnosis 13 / ledger-audit 6 / ops-misc 5. Provenance: our own production ops records (CC-BY-4.0) — no customer data, no third-party content; sanitized via a 5-step pipeline + 10% human sample audit (7/7 pass, seeded); final scan clean (0 credential/PII/schema failures, tools/xerj_pack_scan.py selftest 5/5). Baseline attribution: contains our evaluation-process records against SWE-bench-family benchmarks — our own process and readouts only, no benchmark data redistribution. Demand anchor: issue xerj-org#1138 + hub backlog slot (PR xerj-org#1210). Eval-answers offer stands: first seed triggers an independent assay eval (preregistered criteria, three-state answers, UNVERIFIABLE wall) with the full answer set published.
|
Thanks for this contribution — we'd like to merge it. Before we can, we need a signed Contributor License Agreement from: @chunxiaoxx It is a one-time thing per contributor, not per pull request. Read CLA.md, then open a small pull request adding your GitHub username to Once it is merged, comment |
Author
|
I have read the CLA Document and I hereby sign the CLA. |
Author
|
CLA signature PR opened: #1256 (adds |
|
Thanks for this contribution — we'd like to merge it. Before we can, we need a signed Contributor License Agreement from: @chunxiaoxx It is a one-time thing per contributor, not per pull request. Read CLA.md, then open a small pull request adding your GitHub username to Once it is merged, comment |
|
Re-checking the CLA status for every commit author on this pull request… |
This was referenced Oct 8, 2026
xerj-org
added a commit
that referenced
this pull request
Oct 8, 2026
…lot live) validate_hub.py enforces recipe-exists <=> status live, so the #1255 merge left corpus-hub red (run 37817938270: 'recipe exists but backlog status is planned'). Flip the slot the way the rust-vulns pack row is shaped: sources[0] points at the recipe file, refresh daily (the pack-publish cron this branch wires), note carries the demand provenance (#1138) and the measured acceptance (70 envelopes -> 70 records, topic counts exact). Backlog now 104 live. Local validate_hub.py: OK (102 manifests, 3 recipes, 141 rows).
Author
|
@cla-bot check |
|
Re-checking the CLA status for every commit author on this pull request… |
xerj-org
added a commit
that referenced
this pull request
Oct 8, 2026
pack: agent-session-trajectories on main (cron-buildable mirror of #1255)
thomas-villani
pushed a commit
to thomas-villani/xerj
that referenced
this pull request
Oct 9, 2026
Supersedes the .contributors hunk of PR xerj-org#1257, which carried the signature on a stale base and against the corpus-hub branch, where the CLA bot never reads it (it resolves .contributors from main). chunxiaoxx signed in PR xerj-org#1257 itself; the signature enables the agent-session-trajectories record pack (PR xerj-org#1255, wishlist slot from xerj-org#1210, demand anchored to xerj-org#1138) and the pending guest-post branch.
thomas-villani
pushed a commit
to thomas-villani/xerj
that referenced
this pull request
Oct 9, 2026
…+ 1cfad62) The first external-contributor pack (chunxiaoxx / Nautilus, PR xerj-org#1255, CLA signed via xerj-org#1263, demand anchored to xerj-org#1138, wishlist slot xerj-org#1210): 70 sanitized multi-session agent trajectories, failure turns kept verbatim, CC-BY-4.0, single-source identity (70 envelopes -> 70 records, measured). Main needs the identical copy because scheduled workflows fire from the default branch only — the daily pack-publish cron builds and signs the pack from tools/packs/agent-session-trajectories/recipe.toml with the PACK_SIGNING_SEED_AST secret, verifying against the committed .pub before each publish. corpus-hub carries the same files for hub-side validation (PR xerj-org#1264). No engine change: recipe + stats + key + one workflow job.
thomas-villani
pushed a commit
to thomas-villani/xerj
that referenced
this pull request
Oct 9, 2026
Window since v1.0.0-rc.92: xerj-org#1259 (batched finalize-verify, the xerj-org#1183 count lane), xerj-org#1262 (closes xerj-org#1260: columnar exists + delete-aware fast-agg admission, 3.4s -> 2.7ms warm on the live crawl node, plus the test-race serialization caught by CI run 37816544794), xerj-org#1263 (chunxiaoxx CLA signature), xerj-org#1265 (agent-session-trajectories pack wiring on main), xerj-org#1268 (pack publish tag-burn fix, cited ahead of its merge). Corpus-hub side in prose: xerj-org#1255/xerj-org#1264 (recipe, stats, key, workflow, backlog flip) and xerj-org#1266 (vuln-fix-commits live, G7 blind-graded 4/5, 328,891 records). ROADMAP roll, shortlist live-verified at cut: twelve open — the ten carried from rc.92 (xerj-org#1094 xerj-org#1100 xerj-org#1122 xerj-org#1170 xerj-org#1173 xerj-org#1108 xerj-org#1110 xerj-org#1183 xerj-org#1212 xerj-org#1226) plus xerj-org#1250 and xerj-org#1267 (filed this window: the finalize read-back walk + doc-lane verify residual). Two corrections recorded: xerj-org#1254 was auto-closed by the rc.92 window's own xerj-org#1258 merge at 655ea93, 42 minutes BEFORE the rc.92 tag — the rc.92 roll's 'stays open' note predates the close, so it is de-linked from the shortlist and recorded in the closed list; xerj-org#1183's count lane is no longer 'the remaining half' (xerj-org#1259 + xerj-org#1262 landed it, first live proof the vuln-fix-commits rebuild completing 97 batched windows). Version 1.0.0-rc.92 -> rc.93 (workspace + lockfile via cargo update --workspace --offline), landing data-latest-tag stamped, sitemap regenerated (byte-identical, no new pages). release-notes-gate.sh PASSes locally: 13 shortlist issues open-checked, xerj-org#1260 closed-cited, window PRs all cited.
This was referenced Oct 11, 2026
neoneye
pushed a commit
to agent-memory-atlas-archive/xerj-org--xerj
that referenced
this pull request
Oct 13, 2026
…eeded Issue xerj-org#1138 is a community contribution thread (Chunxiao Wang / Assay): two eval/retrieval recipes plus a corpus wishlist, asking in return only for an honest note on where our index is thin against session-memory workloads. All of its original asks already landed: the honest-gap comment, the recipes/blog page (PR xerj-org#1211, this file), the hub backlog slot (PR xerj-org#1210), and the donated corpus pack itself (PR xerj-org#1255, release pack-agent-session-trajectories-2026-10-09, wiring xerj-org#1264). Root cause of this change: the published blog page was honest on 2026-10-07 but has since gone stale. §04 states, flatly, that the planned session-trajectory corpus "exists in any form. It does not" — true when measured, false now that PR xerj-org#1255 merged (2026-10-08) and the signed pack was released (2026-10-09). A page carrying a dateModified must not keep asserting zero when the number is no longer zero. What changed: - Added a dated UPDATE note (2026-10-11) under §04 recording the landed donation: 70 sanitized multi-session trajectories with failure turns intact, CC-BY-4.0, via the documented contribution path, and the maintainer-published signed record pack. Links to xerj-org#1255, the release tag, and xerj-org#1264. - Softened the "Not claimed … it does not" sentence to "as of the 2026-10-07 registry check … It did not then", pointing to the update. The §04 counts themselves are left verbatim — the honest record is that the number was zero when we checked. - Noted that the one still-open item, Chunxiao's independent eval against the seeded corpus, has not yet been published, and claimed nothing about its result. - Bumped dateModified / pagedata updated to 2026-10-11. Before: page asserts the corpus does not exist (stale since 2026-10-08). After: page records the seeding, keeps the original measurement intact, and still claims nothing unverified. No engine code touched; ES-YAML gate unaffected. SEO gate green locally (fix_heads/fix_links/seo_lint/build_articles/gen_sitemap/mk_og_card/ test_article_schema all pass; 0 gate violations). Advances xerj-org#1138 (partial). Remaining and out of our hands: Chunxiao's offer to publish an independent recompute (pre-registered criteria, three-state verdicts, UNVERIFIABLE wall) against the now-seeded corpus stands on their side and is not yet delivered; closing the issue is the maintainer's call once that eval lands or the thread is declared done.
This was referenced Oct 16, 2026
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.
Domain + query (CONTRIBUTING §1, property 1): An agent operating a production multi-agent engineering org would query this corpus for precedent on failed approaches, their diagnosis, and the fix that worked — a hit that says you already tried this and it failed is reachable, with the diagnosis kept verbatim.
Lane B record pack — recipe.toml + README only, no built pack (maintainer builds + signs per CONTRIBUTING §4). Starts from TEMPLATE-recipe.toml schema: source
nautilus-ops(kind=git → github.com/chunxiaoxx/nautilus-compass, globruntime/xerj_pack/pr_ready/agent-session-trajectories.jsonl, format=flat — each line is one self-contained JSON record), envelope maps id/task_topic/context+attempted+final_fix, identity = unique byid.Record counts + identity resolution: 70 envelopes → 70 records (single source, unique by
nst-<session-key>; no alias chains). Topics: eval-judging 46 / infra-diagnosis 13 / ledger-audit 6 / ops-misc 5.Provenance (README §Provenance): our own production ops records — no customer data, no third-party content. Sanitization: 5-step pipeline (credential regex sweep incl. rotated secrets, PII role-ization, codename generalization, financial-value aggregation, dual rescan) + 10% human sample audit (7/7 pass, seeded). Final scan: 0 credential/PII/schema failures (
tools/xerj_pack_scan.pyin our repo, selftest 5/5).Licence: CC-BY-4.0 (our own content; redistribution with attribution). Baseline attribution: contains our evaluation-process records against SWE-bench-family benchmarks — our own process and readouts only; no benchmark question text or data redistribution.
Demand anchor: issue #1138 + hub backlog slot
agent-session-trajectories(PR #1210, status planned). Our eval-answers offer stands: once this slot receives its first seed, we run an independent assay eval — preregistered criteria, three-state answers, UNVERIFIABLE wall — and publish the full answer set.Demand-anchored donation from the team behind the six eval scars on the recipes page. 🙏