Session dossiers
A dossier is a folder under docs/sessions/<date>-<slug>/ that wraps one working session so a fresh session can resume it. There are seven. Each has a README.md with the state, the repo state, a copy-paste resume prompt, a read-first list and a first action. Read the newest first.
This index is written from each README.md. It is a snapshot of when each dossier was written. Verify with git status and git log before acting on any "first action".
Index
| Date | Slug | State when written | Resume pointer (first action) |
|---|---|---|---|
| 2026-11-10 | 2026-11-10-agentforge-p1-p2a-build | P1 (runtime, ledger, Claude adapter) built and verified keyless and with a real key. P2a (Hono REST API, Docker image, CI additions, Coolify checklist) built and verified keyless. Local real-key run of P2a in flight. P2b, P2.T, P2c, P2.G, P3 planned only. CI never ran on GitHub, nothing pushed | Open docs/p2-findings.md, read "P2a real-key (local)" and report PASS or FAIL per check |
| 2026-11-10 | 2026-11-10-agentforge-p2b-to-p2g-s4 | Built, pushed and verified locally: P2b (SSE), P2.T T0 to T4 (Temporal sessions), P2c (agent-client), post-P2 fixes, P2.G S0a to S4 (gateway, MCP gateway, policy, OBO core, context stub), each followed by an independent security review. Not done: P2.G S5, P2.5, P3, real Zitadel, VPS checks. Open decision: allowlists unfrozen because the CLI sends max_tokens 128000 | gh run list --limit 8; for any failure gh run view <id> --log-failed. Then P2.G S5 and plan the P2.5 sandbox spike |
| 2026-11-11 | 2026-11-11-agentforge-p25-to-p3-build | P2.5 (sandbox runner, SandboxRuntime, real-key RK-P1..P4, G2-local closed with APPROVE WITH CONDITIONS) and P3-0..P3-5 plus P3-3 built and pushed (35ba380, CI green). A verify-and-record agent was mid-flight and left uncommitted edits in apps/gateway/test/security-review.test.ts and turbo.json | Run git diff --stat. If the two uncommitted files are test or turbo fixes with a passing gate, commit them (own paths only); otherwise ask. Then check whether docs/p2-findings.md has ## P3-3 |
| 2026-11-13 | 2026-11-13-agentforge-app02-test-and-worker-fleet | P3 proven on real GitHub (private same-org fork, real model, PR, retry, closed-PR rules); two independent security reviews fixed; throwaway app-02 deploy smoke-passed and fully torn down; three owner decisions and built design (all model calls through the gateway, database-free exec worker, baked gateway policy). FL-1..FL-4 pushed at df34246. Not built: the production deploy (bead .87). Blocked on the owner: ACL edit, deploy go, Console cost comparison, VPS and Zitadel items | Check the CI re-run for df34246. If the gateway timing test fails again, treat it as a real regression of apps/gateway/src/control.ts and bisect with 97ddf69 |
| 2026-11-15 | 2026-11-15-app03-deploy-and-smoke | AgentForge deployed on the core host and smoke-tested through the whole stack (two runs, 0.00038 USD each). Release v0.2.0 on 8d7a615. Mid-flight: the Postgres persistent volume (drafted by the hostinger session) and the gateway exposure design. Blocked on the owner: that go, the pg_dump decision, a release approval for the next gateway change, later ACL grants for 8787. Test key deliberately not rotated | Ask the hostinger session for the status of the Postgres volume PR; do nothing live until it says the owner gave the go. Then (when merged): confirm no turns are running, let it apply, run node dist/migrate.js in the api container, rerun the smoke test, implement GATEWAY_CONTROL_BIND_CIDR (bead .93) |
| 2026-11-16 | 2026-11-16-codecrucible-and-gateway-cidr | Postgres volume applied and proven across a restart; nightly pg_dump live; GATEWAY_CONTROL_BIND_CIDR coded (not released); CodeCrucible plan through a five-iteration consensus loop, Phase 0 spikes S1, S2, S4 pass; first packages/quality-core slice (CC-1.1 to CC-1.3) on main at fbc370c, CI green. Blocked on the owner: gateway CIDR release approval, PRE-0, app-04, key rotation | Start CC-1.4 (gate evaluator and QualityPolicy) in packages/quality-core (bead .98); read .omc/plans/codecrucible-mutant-hunter.md sections 4 and 5 first |
| 2026-11-16 (second half) | 2026-11-16-codecrucible-build | CodeCrucible built end to end locally on main (last commit 719fc45): library, REST routes, both workflows, exec worker, quality image, verify steps. Nothing deployed or enabled (QUALITY_ENABLED unset). Gateway CIDR release tag declined for now. CI queued or failed on load-related timeouts; five runs (c21f154 to 5039f88) still queued behind a load average of about 51 | After 10:00 local on 2026-11-17: run uptime, gh run list --limit 6, re-run failed jobs of the newest commit, then the local dogfood (baseline plus one real verify of packages/agent-core). Before 10:00 do no heavy docker or mutation work |
What each dossier produced
| Dossier | Phases and outcomes | ADRs |
|---|---|---|
| p1-p2a-build | P1 foundation, P2a API; independent mutation reviews (P1 core 22 probes, 20 killed; adapter 46, 44 killed; API 29, 23 killed plus gaps fixed); last gate 24 of 24 turbo tasks | 0001 to 0005 of that dossier |
| p2b-to-p2g-s4 | SSE, Temporal sessions, client, governance gateway; test counts at the last full gate (gateway 261, claude runtime 85, api 190, db 98, agent-types 148, agent-core 75, agent-mcp 27, governance 40, workflows 39, worker 39, context 19, client 17, smoke 52); real-key spend about 0.2 USD | none |
| p25-to-p3-build | Sandbox, factory contracts and workflow, API intake routes; 51 commits 7a084bf..35ba380 | none |
| app02-test-and-worker-fleet | P3 security hardening, real-GitHub proof, throwaway deploy and teardown, worker fleet FL-1 to FL-4 | 0001 to 0003 of that dossier |
| app03-deploy-and-smoke | Release v0.2.0, secrets generator, core host deploy, smoke tests, fleet exposure design | 0004 to 0006 |
| codecrucible-and-gateway-cidr | Volume, pg_dump, GATEWAY_CONTROL_BIND_CIDR, CodeCrucible plan and spikes, quality-core slice | 0007, 0008 |
| codecrucible-build | CC-1.4 to CC-3.2, .111, .112, runbook; 95 files and about 21,000 lines added | 0009 |
ADR numbers restart: the first two dossiers' ADRs are numbered 0001 to 0005 and 0001 to 0003 (the second set belongs to the 2026-11-13 dossier), so "ADR 0001" is ambiguous. See Decisions.
Anatomy of a dossier
| File | Purpose | Present in |
|---|---|---|
README.md | State in one paragraph, repo state, resume prompt, read-first list, first action | all seven |
SUMMARY.md | Commits (with SHAs), verified state, measured numbers | all seven |
LESSONS.md | What went wrong or surprised, with the rule it produced | all seven |
FOLLOWUPS.md | What is blocked on the owner and what is blocked on work | all seven |
ARCHITECTURE.md | Architecture as built at that time | p1-p2a-build, app03-deploy-and-smoke |
BLOG.md | A sanitized public write-up | p1-p2a-build, app02-test-and-worker-fleet, app03-deploy-and-smoke, codecrucible-and-gateway-cidr, codecrucible-build |
adr/NNNN-*.md | Decision records: status, context, decision, consequences, alternatives rejected | five of seven (see the table above) |
Rules for resuming:
- Read
README.md, thenFOLLOWUPS.md. - Re-check the repo (
git status --short --branch,git log,gh run list). The dossier records a moment, not the present. - Do nothing live (apply, restart, release) without the owner's go in that session.
- The plans (
.omc/plans/*.md) are git-ignored (excluded locally via.git/info/exclude; beadhawkeye-81e.17tracks the risk) and exist only in the owner's checkout. Dossiers cite them; this site does not reproduce them. - The repo directory was renamed from
hawkeyetoagentforgebetween the second and third sessions. Old documents keep the name Hawkeye and the@hawkeye/*scope; the code uses@agentforge/*. The beads epic id is stillhawkeye-81e.
Writing a new dossier: the repository documents the format only through the existing dossiers. Copy the file set above, put the resume pointer (state, repo state, resume prompt, first action) first, and keep names and counts, never secret values.
Sources
docs/sessions/2026-11-10-agentforge-p1-p2a-build/README.md,SUMMARY.md,LESSONS.md,FOLLOWUPS.md,ARCHITECTURE.mddocs/sessions/2026-11-10-agentforge-p2b-to-p2g-s4/README.md,SUMMARY.mddocs/sessions/2026-11-11-agentforge-p25-to-p3-build/README.md,SUMMARY.mddocs/sessions/2026-11-13-agentforge-app02-test-and-worker-fleet/README.md,SUMMARY.mddocs/sessions/2026-11-15-app03-deploy-and-smoke/README.md,SUMMARY.mddocs/sessions/2026-11-16-codecrucible-and-gateway-cidr/README.md,SUMMARY.mddocs/sessions/2026-11-16-codecrucible-build/README.md,SUMMARY.md