stop-the-leaks

ARCHIVED

"consider these the explore artifact of an openspec changes. Stop the leaks could be one, publish the graveyard could be two, etc. I want to focus on writing out some of these plans today." "I want the details page to just show a few more guiding statements - why it matters, hypothesis, etc."

STAGES

  1. proposal07-20
  2. requirements07-20
  3. design07-20predates the Figma as-is + proposed pair
  4. tasks07-20
  5. build—
  6. archived—

CAPABILITY

  • public-content-gate5 requirements

OUTCOMES — AND HOW EACH IS MEASURED

  • ✓1.1Private row is hidden from public routesautomated test
  • ✓1.2Backfilled public rows still render *(code reads `Public`; verify after the §2.1 backfill)*code path
  • ✓1.3Bookkeeping fields are filtered outautomated test
  • ✓1.4New Notion properties stay private by defaultautomated test
  • ✓1.5Statements render in narrative orderhuman review
  • ✓1.6Missing fields are omitted silentlyhuman review
  • ✓1.7Phase chip gated to edit modehuman review
  • ✓1.8Ghost prompts appear only in edit modehuman review
  • ✓1.9Copy fixes verified on live pages *(post-deploy, §4.3)*code path

WHAT HAPPENED

  1. TASKS

    proposal and specs and design and tasks landed

    2026-07-20 · 1 pull request
    • #308chore(openspec): archive stop-the-leaks + sync public-content-gate spec

History read from a manifest built at 2026-09-30 (09e7bcc).

1 pull request, found by commits touching the change folder