Reports

AI-generated reports for the obot portfolio, following the gsm.roadmap artifacts pattern: one folder per report, containing a self-contained index.html (plus any assets) and a README.md recording provenance, sources, and assumptions. The site deploy workflow publishes this folder as-is.

The reports below were migrated from the archived obot-claw hub (July 2026). New reports land here under the same contract; see the design doc for requirement #7.

Every artifact says what it is — in one line, on the page

The news feed's description line is what decides whether a row is worth opening. It comes from the artifact's own page head, written when the artifact is written:

<title>What the page is called</title>
<meta name="description" content="What this page contains, and why you would open it.">

Put it directly after <title>. One line, 40–260 characters, and it must clear the plain-English bar (@jwildfire, 2026-08-15):

• Say what the artifact contains and why someone would open it — not what kind of thing it is. "AI-generated report." and "Design document for Requirement #161." both describe the badge the feed already prints. They were the hardcoded fallbacks the feed used until 2026-08-15, and they are now rejected by name.
• Name things, don't number them. An issue number is not an explanation; a reader who has memorised nothing must be able to tell from the line alone whether this is for them. Delete every reference from the sentence — if it stops making sense, rewrite it.
• Write it from the contents, not from the title. A parity report's line should convey that it compares the chart library against its R wrappers and names what is stale — not that it is a report.

node scripts/check_artifact_descriptions.mjs verifies every artifact, and the deploy runs it before publishing: a page with no description fails the build. If one ever reaches the site it renders as a loud ⚠ NO DESCRIPTION strip rather than a plausible sentence — a fallback that reads as intentional is how the old one survived six weeks.

Emphasis is structural, or it is a callout

@jwildfire, 2026-08-16: "I really don't like the randomly bolded sentences in the middle of paragraphs. Call things out in modals if they're super important, but no more random inline bold." He reads these pages fast, often on a phone. Bold applied to a quarter of a page emphasises nothing, and the skim it was meant to help is the thing it destroys.

• No bolded sentence or clause inside a body paragraph — not as its opening sentence, not mid-sentence, not on a number inside a table cell's prose. Rewrite the sentence so it carries its own weight, or promote it.
• Promote it to a callout: a bordered, tinted block with its own label. Every artifact defines one (.callout, .card or .verdict on the current pages), it holds at 390px, and it follows the page's light/dark handling. A bolded lead sentence inside a callout is the callout doing its job twice.
• Structural bold stays, and removing it would make the page worse: list-item and definition-list leads, table headers, a label or value at the start of a cell, key–value strips like the fact bar under a title, and short run-in labels ending in a colon or period (Recommendation:, Sources.).
• Quotations from @jwildfire keep whatever emphasis they came with — that text is his.

The full rule, with the sweep that established it, is in decisions/README.md and requirement #198.

Index

Superseded versions are retained deliberately (design decision D3) — the memory philosophy favors preserving the decision trail.

Decision artifacts

decisions/ holds the pages an autonomous session writes when it hits a call it cannot make — situation, options with what each costs and forecloses, a plain recommendation, and what unblocks on each choice. One folder per decision, dated. These and release-candidate PRs are the only two things @jwildfire reviews, per the release-candidate framework; the contract is documented in decisions/README.md.

Session reports

sessions/ holds the frozen per-session operational records produced at wrapup by the session hub (requirement #24). It follows its own flat contract — one self-contained HTML file per working session, named by the diary slug — documented in sessions/README.md.

Adding a report

1. Create reports/<kebab-name-with-date>/ with a self-contained index.html.
2. Add a README.md: how it was generated, sources, assumptions, LLM disclaimer.
3. Add a row to the index above (newest current work at the top of its group).