S3 configuration (2026-10-18): Mark: "for the policy details page, I don't see any place for custom configurations per policy, is that correct?" It was correct, and deliberate: surface-map.md S3 dropped qdash's PolicyConfig shapes because no intent asks for them, but that decision never reached the review walk. Then: "take a look at ../qcontrol policy listing page. The expand rows have much better policy configuration. Take a look at that and add something similar."

composed S3 · Where it applies (2026-10-18): Mark: "c114, policy detail. We'll be building the revised page section by section. I think we can combine the 'where it applies' and the 'enforcement' sections. Also, let's use our standard uxTable here." Asked where, he answered "the composed mocks". Then: "let's lose the white backgrounds and use a simple title with a hairline, per section." (prompt · plan)

article status + first three briefs (2026-10-13): articleStatus added to the schema and template, shown as a pill on /briefs and /briefs/<slug> with a one-line note that the text is still moving. First three real briefs written: your-agents-need-a-dynamic-sandbox, the-hidden-agent-surface, treat-your-agents-like-insiders, from the drafts under Marketing/Blog in Drive. All phase: 0-intake, articleStatus: draft, no byline or date yet.

creative brief shape (2026-10-13): Mark trimmed the brief to a creative brief: In plain words (the renamed ELI5, now first) → three lines → Jargon → Direction (References, Constraints only) → Final → Publish → Record (Shipped). Ideation, Review, Decisions and the learned / next-time lines are gone from the page; the studio repo's per-article log holds them. Template and the three briefs rebuilt. Page code unchanged.

deployed (2026-10-13): committed as 388a49ec9 (only c115 paths; other sessions' c100/c105 work left in the tree) and shipped with npm run deploy → deploy branch 3afa87fbd, _deploy.json confirms the SHA, /briefs/ and the four brief pages verified on design-f39.pages.dev. main is not pushed. Two prerender errors in the build log are the cycles-by-week crawler hitting a 1999 week, pre-existing and unrelated.

dark-mode brief (2026-10-13): first non-illustration brief, content/briefs/dark-mode.md (kind: dark-mode, so no phase stepper). Written from the existing stubs: the layer's semantic.mjs dark column, c52's theme editor and dark-subtle-baseline, c46's brochure dark-mode brief, c76's unstarted prompt, the pixel-art dark values. Sections: in plain words, the job, what exists, the tool (editor walkthrough; Save/Load don't work on the static deploy, Copy semantic.mjs is the hand-off), the seventeen roles with today's values, where to judge, principles and minimums, deliverables, jargon. Screenshot at public/briefs/theme-editor.jpg (editor open on /pages/sticky-band in dark, 1280 wide).