Skip to content

feat: make understanding contracts default for new pages - #27

Merged
oddharsh merged 1 commit into
mainfrom
codex/understanding-page-scaffolds
Jul 18, 2026
Merged

oddharsh merged 1 commit into
mainfrom
codex/understanding-page-scaffolds

Conversation

@oddharsh

Copy link
Copy Markdown
Owner

Summary

  • make a shared authoring contract required by both LWE and Garage page specs
  • carry the existing quiz payload/runtime into generated LWE pages and add a spec-driven Garage generator
  • wire future Garage pages into the shelf, Run palette, and sitemap, with CI checks for generated and published pages
  • document the reader/problem/thesis/evidence/uncertainty card, reconstruction questions, LRS guardrails, and voice rules

Why

New explanatory pages should inherit the understanding-first work already applied to the site. The generator now refuses a page without an explicit reader model, evidence, uncertainty, and a 3–7-question active-recall check. Every option needs feedback, including the misconception path; the check remains diagnostic and never blocks reading.

The shared contract also carries the current writing guidance into the authoring boundary: concrete active prose, a named reader, early points, actor-near-verb sentences, and a visible uncertainty boundary. It rejects em dashes, canned AI/marketing filler, dead transitions, and the not X, Y move.

Verification

  • npm run pages:check
  • npm test
  • npm run build
  • npm run check-wrangler
  • npm run perf-budget
  • npx wrangler deploy --dry-run
  • git diff --cached --check

All checks passed. No production deploy was performed.

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
✅ Deployment successful!
View logs
aadhar-sh 14567f8 Jul 18 2026, 09:10 PM

@github-actions

Copy link
Copy Markdown
Contributor

Understanding-first review

This is a prompt, not a score or merge gate. Before approving, reconstruct the change:

  • My model: What do I think this PR does?
  • Mechanism: What path or invariant makes that behavior true?
  • Falsifier: What would prove my model wrong?
  • Evidence: What test, trace, dry-run, or live check did I inspect?
  • Residual uncertainty: What remains unproven?

For docs and dependency changes, a compact answer is enough. For behavior or production changes, include the causal path and one concrete counterexample. The author’s claim card belongs in the PR description; this prompt is for the reviewer’s independent reconstruction.

See UNDERSTANDING-REVIEW.md.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jul 18, 2026 •

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
serendipity 14567f8 Commit Preview URL

Branch Preview URL
Jul 18 2026, 09:11 PM

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jul 18, 2026 •

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
✅ Deployment successful!
View logs
cal-aadhar-sh 14567f8 Jul 18 2026, 09:11 PM

@oddharsh
oddharsh marked this pull request as ready for review July 18, 2026 21:13
@oddharsh
oddharsh merged commit 0de5ccf into main Jul 18, 2026
6 checks passed
@oddharsh
oddharsh deleted the codex/understanding-page-scaffolds branch July 18, 2026 21:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant