diff --git a/.gitignore b/.gitignore index 443e335..ce7629f 100644 --- a/.gitignore +++ b/.gitignore @@ -1,4 +1,4 @@ -# Task board credentials and local working notes. This repo goes public; +# Task board credentials and local working notes. This repo is public; # neither the key nor pipeline detail may ever enter history. .env CLAUDE.local.md diff --git a/CLAUDE.md b/CLAUDE.md index 03630f9..c0ca81c 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -6,7 +6,7 @@ Instructions for Claude Code working in this repository. A reference implementation of an agent-run incident response layer, built on [Open Agent Spec](https://github.com/prime-vector/open-agent-spec). Read `SCENARIO.md` before touching anything. It is the source of truth, and every spec, fixture and piece of copy derives from it. `PLAN.md` has the milestones. -This repo is currently private. It goes public. Write everything as though it is already public. +This repo is public. Everything written here is read by strangers. --- diff --git a/PLAN.md b/PLAN.md index 32f0f2a..c202828 100644 --- a/PLAN.md +++ b/PLAN.md @@ -59,7 +59,7 @@ This milestone is the product. If it is not visible on screen, this is just anot **Done when:** the repo is public, the video is recorded, and the site points at both. - [x] Sanitisation review, second pass, by someone other than the author. Read in the week of 17 to 23 Aug 2026 by an observability engineer who knows the pattern this composite is drawn from, which is a stronger pass than a cold reader can give: someone who never saw the source material can apply the rules but cannot confirm an absence. Nothing identifiable found. Scope recorded rather than assumed, because the tree grew in four steps and only the dates say what was in it: eleven corpus documents landed 16 Aug, `DRAFT-2601` on 17 Aug, the five distractors on 18 Aug in `3706dd2`, and both `docs/samples/` directories on 24 Aug. Seventeen, which is the count `README.md` and M6 carry, and the twelve M1 records as read by the first pass are the 16 Aug eleven plus `DRAFT-2601`. The whole corpus was in the tree by 18 Aug and the read ran to 23 Aug, so the corpus was covered in full and the samples postdate the read. That gap is deliberate rather than outstanding: the samples are model output, the model only ever saw synthetic fixtures and the synthetic corpus, so it cannot emit source material it never had, and its one real exposure is naming a vendor in a causal role. The reproducible half of the pass is a sweep anyone can re-run and it is clean: no email addresses anywhere in tracked files, no routable IP other than loopback, no external hostname beyond `api.anthropic.com`, `github.com`, `genai.com.au` and `www.w3.org`, and four vendor mentions all in capability tables or market positioning rather than a causal role -- [x] Repo moved to the org. Already there: `prime-vector/response-engineering`, which is the standards home the brand decision put it under. **Still private**, and that is the separate condition in this milestone's done-when rather than a leftover of this item. Nothing in the tree gates going public: the sanitisation second pass is done and recorded above, and the mechanical sweep in that item is the part a reader can re-run. What gated it was outside the tree: the pull request refs GitHub retains, recorded in the third-pass sweep item below, and that is settled by publishing from a fresh repository rather than waiting on a purge +- [x] Repo moved to the org. Already there: `prime-vector/response-engineering`, which is the standards home the brand decision put it under. **Public since 21 Oct 2026**, which is the first condition in this milestone's done-when; of the three, the site pointing at the repository and the video is the one outstanding, and the README read below is open beside it. Nothing in the tree gated going public: the sanitisation second pass was done and is recorded above, and the mechanical sweep in that item is the part a reader can re-run. What gated it was outside the tree: the pull request refs GitHub retains, recorded in the third-pass sweep item below, settled by publishing from a fresh repository rather than waiting on a purge - [x] Four minute walkthrough recorded. 4:37, uploaded unlisted on 7 Oct 2026: https://youtu.be/OTdecUh1C98. Over the four minute name on purpose, for the reason `docs/walkthrough-script.md` gives: the length is where the spoken copy and a phrased read came out, and words were not cut to a clock. The shot list's timings are cut from the recorded takes - [ ] README readable by someone with no context - [x] Mechanical sanitisation sweep, third pass, re-run 10 Oct 2026 against `main` at `a18f46f` (`fc7dfb7` after the history rewrite of 11 Oct, see `docs/history-rewrite-2026-10-11.txt`), 141 tracked files, after the tree grew again in October: agent traces, the OpenTelemetry document, the model split and its measurements, the objectives. Clean on every axis the second pass recorded, stated as what each grep found rather than as a count: no email address in any tracked file; no IP beyond loopback; the external hostnames are the four named above plus `youtu.be`, the walkthrough link added on 7 Oct, and no other; no vendor is named in a causal role, which is rule 2 and the only thing a sweep for product names can attest, since no list of names is closed and where a name sits is a reading, not a grep. Three axes the second pass did not record were swept as well: the two record directories, `evals/results/` and `docs/samples/`, name the model provider and model ids, which is what a record of a run must carry, and no other vendor; no tracked file carries a rate, revenue figure, client name or pipeline detail; and the added and removed lines of every commit on every branch were searched for addresses and routable IPs, finding only the SSH form of the GitHub remote. Untracked files: none. What a mechanical sweep cannot do is confirm an absence of source material, which is why the second pass was a read by someone who knows the pattern, and nothing added since then was derived from anything but the generators and the model. Separately, and outside what any sweep of tracked files can see, the pre-publication review of 19 Oct 2026 found that GitHub keeps a head ref for every pull request, and 54 of the 58 still pointed at pre-rewrite commits carrying the personal address and the model-version trailers, fetchable by hash as well. Those refs cannot be deleted by the repository owner, so on 21 Oct 2026 the development repository, its pull requests included, was renamed `prime-vector/response-engineering-archive` and kept private, and this repository was created under the original name from `main` alone, with no pull request refs to retain. Pull request numbers cited before that date, in this tree and in commit messages, refer to the archive, although GitHub links a `#n` in a commit message to this repository's pull request of that number. The twelve commits of 19 to 21 Oct that had carried a model-version co-author trailer were rewritten to the generic one first. That rewrite also drops the signature GitHub puts on a merge it makes, so every commit from the merge of #55 on 11 Oct onward has a new hash, 33 in all, with messages otherwise unchanged and the tree identical. A sweep of the tree says nothing about what the host retains.