Bring the full use-case story into the website

[ericlovold]

The homepage introduces approval scenarios but lacks the full story behind each one. Adds /use-cases as a native deep dive with all ten supplied scenarios, responsive step diagrams, audience filters, direct story links, and expandable technical detail. Homepage navigation and team cards link into it.

A new homepage section explains access, actions, approval, and oversight, with links to the relevant stories. The demo runbook specifies a synthetic email approval followed by changed-recipient rejection using an unconsumed grant. This is a prepared procedure, not recorded test evidence; it sends no email.

The source marketing guide is adapted for public readers: internal publishing instructions and editor scripts are excluded. Cooperative MCP, SDK execution boundaries, gateway budget overruns, and upstream credential handling are stated explicitly. No authorization behavior changes.

Validation: npm run check passed (1,857 tests; 56 DB tests skipped); git diff --check passed. Inspected desktop and 390px mobile layouts, verified no mobile overflow, filter counts, technical disclosures, and homepage-to-story anchor navigation. Independent deep-dive content review found no material blockers.

---

Note

Low Risk
Marketing pages, static content, and demo runbook prose only; no authorization or API logic changes.

Overview
Adds a dedicated /use-cases marketing page with all ten oversight scenarios (narrative copy, step diagrams, audience filters, deep links, and expandable cooperative vs enforced technical boundaries), backed by stories.ts and a small client StoryFilter for hash-aware navigation.

The homepage now routes “Use cases” to that page instead of an in-page anchor, adds a four-pillar oversight section (access / actions / approval / oversight) with story links, and wires each people-focused card plus the footer to the new deep dives.

brand.css adds a 2-column responsive layout for the new oversight grid. docs/DEMO-RUNBOOK.md documents a synthetic sanction.demo.email flow that proves exact-argument binding by rejecting redemption when only the recipient changes—documentation only, no product behavior changes.

^{Reviewed by Cursor Bugbot for commit 13571a3. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
sanction	Ready	Preview	Oct 8, 2026 5:50pm UTC

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 29a619c7-4438-4ca8-b89d-3011bcce4d61)

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository: ericlovold/sanction/.coderabbit.yaml
• Review profile: ASSERTIVE
• Plan: Essentials
• Run ID: 3f28ab14-91f9-4a09-be42-a512c3511aaa

📥 Commits

Reviewing files that changed from the base of the PR and between 209b1af and 13571a3.

📒 Files selected for processing (3)

• app/brand.css
• app/page.tsx
• docs/DEMO-RUNBOOK.md

Included review availability: This review used your included allowance. 2 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 3 reviews per hour.

---

📝 Summary

Summary by CodeRabbit

• New Features
  • Added a use-cases page featuring ten illustrated scenarios, a four-step approval loop, and explanations of cooperative and enforced control.
  • Added filters to browse all stories or focus on people and engineers or autonomous agents. Case links open the matching story.
  • Added navigation and footer links to the use-cases page, plus a link to explore all ten scenarios.
  • The page adapts its layout for smaller screens.
• Documentation
  • Added a demo runbook for testing approvals tied to an exact recipient and confirming changed inputs are denied.

Walkthrough

The landing page links to a new /use-cases page with ten scenarios, audience filters, and approval and enforcement details. The demo runbook adds a procedure to test an approved grant against a changed recipient without sending email.

Changes

Use-cases experience

Layer / File(s)	Summary
Use-case story content app/use-cases/stories.ts	Adds ten scenarios with story text, presentation steps, review scope, integration details, and enforcement boundaries.
Page rendering and audience filtering app/use-cases/page.tsx, app/use-cases/story-filter.tsx, app/use-cases/use-cases.css	Adds the use-cases page, audience filters, hash-based case navigation, and responsive styling.
Landing-page links app/page.tsx, app/brand.css	Adds landing-page oversight content and links from the navigation, case cards, and footer to the use-cases page.

Approval demonstration runbook

Layer / File(s)	Summary
Changed-recipient approval test docs/DEMO-RUNBOOK.md	Documents a synthetic approval test that attempts authorization with a changed recipient and specifies denial handling, evidence recording, and stop conditions.

Priority: ⬇️ Low

Estimated code review effort: 3 (Moderate) | ~20 minutes

Change: Feature

Merge Risk: ⚪ Minimal · up to 13571

The new story links and documented approval check have no identified merge-blocking issue. The change is ready to merge after normal checks.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 3 functions across 4 files. (2 skipped: 2 …	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the primary change: adding the complete use-case story to the website.
Description check	✅ Passed	The description directly explains the new use-cases page, homepage links, story content, runbook, and validation results.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 3 functions across 4 files. (2 skipped: 2 unsupported.)

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

_{Comment @coderabbitai help to get the list of available commands.}

[cursor]

Approved. Cursor Bugbot was skipped on this head, so that automated-review signal was not used. No applicable approval policy required human review, and there are no unresolved automated findings.

  

_{Sent by Cursor Approval Agent: Pull Request Router and Approver}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 02082c64-b0ab-437d-bf5f-5eb350ee58b5)