Static AgentSite · product-cockpit recipe · no-payment mode

A local-first roadmap board for agent-maintained sites

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.

Operating context

What decision this page helps visitors make

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.

Copy evidence strip

Every strong line gets paired with a verifiable artifact.

Claim 01

Static GitHub Pages delivery

Evidence: Roadmap data contract — src/data/roadmap.json is validated by npm run check:roadmap before build and deploy.

Claim 02

Roadmap data is repo-local JSON

Evidence: Local-only behavior — Roadmap status changes use browser localStorage and are explicitly non-authoritative.

Claim 03

Browser-local status overrides use localStorage

Evidence: Visual QA — npm run test:visual exercises search, priority filtering, and local status movement when the board is present.

Claim 04

Payment disabled / no-payment mode

Evidence: Roadmap data contract — src/data/roadmap.json is validated by npm run check:roadmap before build and deploy.

Local-first roadmap

A static improvement board agents can keep current.

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

Now

highagent

Tighten recipe selection

Keep selector rules deterministic as more section recipes compose together.

Next: Add a regression config whenever selector behavior changes.

recipesqa
highagent

Roadmap data contract follow-up

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.

proofhandoff

Next

highagent

Local-first user overrides

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.

local-firstbrowser
mediumagent

Local-only behavior follow-up

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.

proofhandoff

Later

mediumagent

Static intelligence index

Generate precomputed indexes that make static sites feel more queryable.

Next: Prototype a JSON index from recipe, artifact, and roadmap metadata.

searchdata

Blocked

mediumhuman

Autonomous maintenance cadence

Define when recurring agents may propose changes without adding notification noise.

Next: Approve a quiet schedule and escalation boundaries before automation.

orchestrationapproval
Audience named in the brief

Built for the people who need the workflow explained clearly.

Cockpit panels

Status, workflow, proof, and constraints in one scan.

01 · Local-first

Browser-local behavior without a backend

Roadmap filters and status overrides run in the browser with localStorage and never claim to update GitHub or shared state.

02 · Agent upkeep

Future agents update durable state by editing JSON

Durable roadmap changes happen in src/data/roadmap.json, followed by roadmap, visual, build, and deploy checks.

03 · Safety

Static safety stays explicit

No auth, analytics, payment links, issue sync, fake automation, or private work queues are included.

Proof artifacts

Evidence a future maintainer can verify.

Repo-verifiable artifact

Roadmap data contract

src/data/roadmap.json is validated by npm run check:roadmap before build and deploy.

Repo-verifiable artifact

Local-only behavior

Roadmap status changes use browser localStorage and are explicitly non-authoritative.

Repo-verifiable artifact

Visual QA

npm run test:visual exercises search, priority filtering, and local status movement when the board is present.

Boundaries

What is not claimed here.

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.

Safe next step

Review roadmap

Use the cockpit panels, repository contracts, and QA commands before changing claims, scope, payments, analytics, or deployment settings.

Review roadmap