Static GitHub Pages delivery
Evidence: Roadmap data contract — src/data/roadmap.json is validated by npm run check:roadmap before build and deploy.
Static AgentSite · product-cockpit recipe · no-payment mode
The page turns next-step planning into a static mini app: searchable, filterable, locally adjustable, and safe to host on GitHub Pages.
The page explains the user-facing workflow first, then gives reviewers the operating context, repo-local proof, and approval boundaries needed to evaluate the next step safely.
A static AgentSite with a local-first improvement board for autonomous agents.
Create a static GitHub Pages site that demonstrates a local-first roadmap board for agent-maintained next steps. It should support search, priority filters, status columns, and browser-local status changes without a backend.
Evidence: Roadmap data contract — src/data/roadmap.json is validated by npm run check:roadmap before build and deploy.
Evidence: Local-only behavior — Roadmap status changes use browser localStorage and are explicitly non-authoritative.
Evidence: Visual QA — npm run test:visual exercises search, priority filtering, and local status movement when the board is present.
Evidence: Roadmap data contract — src/data/roadmap.json is validated by npm run check:roadmap before build and deploy.
Search and filter static repo artifacts, plans, QA evidence, deploy records, and recipes without adding a backend or live tracking.
Showing 9 artifacts
Defines mission, required sections, allowed claims, approval boundaries, and live verification expectations.
Captures tone, visual posture, accessibility posture, and language future agents should avoid.
Runs contract, claims, SEO, link, artifact, build, and visual checks before handoff.
Checks the live GitHub Pages URL for stable expected text after deployment.
Records the original brief, assumptions, non-goals, acceptance criteria, and verification commands.
Documents reusable archetypes and section recipes future agents can score before applying.
src/data/roadmap.json is validated by npm run check:roadmap before build and deploy.
Roadmap status changes use browser localStorage and are explicitly non-authoritative.
npm run test:visual exercises search, priority filtering, and local status movement when the board is present.
Filter the generated roadmap, then try local-only status changes. Browser overrides stay on your device and never imply repo changes or live workflow automation.
Showing 6 roadmap items
Keep selector rules deterministic as more section recipes compose together.
Next: Add a regression config whenever selector behavior changes.
src/data/roadmap.json is validated by npm run check:roadmap before build and deploy.
Next: Keep this proof item linked to a real repo artifact before strengthening copy.
Let visitors locally move roadmap cards without implying shared task updates.
Next: Use localStorage for browser-only status overrides and keep durable changes in JSON.
Roadmap status changes use browser localStorage and are explicitly non-authoritative.
Next: Keep this proof item linked to a real repo artifact before strengthening copy.
Generate precomputed indexes that make static sites feel more queryable.
Next: Prototype a JSON index from recipe, artifact, and roadmap metadata.
Define when recurring agents may propose changes without adding notification noise.
Next: Approve a quiet schedule and escalation boundaries before automation.
Roadmap filters and status overrides run in the browser with localStorage and never claim to update GitHub or shared state.
Durable roadmap changes happen in src/data/roadmap.json, followed by roadmap, visual, build, and deploy checks.
No auth, analytics, payment links, issue sync, fake automation, or private work queues are included.
src/data/roadmap.json is validated by npm run check:roadmap before build and deploy.
Roadmap status changes use browser localStorage and are explicitly non-authoritative.
npm run test:visual exercises search, priority filtering, and local status movement when the board is present.
Not claimed: fake customer quoted endorsements.
Not claimed: fake metrics.
Not claimed: unsupported guarantees.
Approval required: Adding analytics, cookies, tracking pixels, or third-party forms.
Approval required: Adding payment links or enabling payment mode.
Approval required: Connecting GitHub Issues, project management APIs, or shared task sync.
Use the cockpit panels, repository contracts, and QA commands before changing claims, scope, payments, analytics, or deployment settings.