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

A static proof browser future agents can maintain

The page turns repo artifacts into a searchable, filterable interface without adding a backend, analytics, payments, or private data.

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 proof browser with searchable artifacts and agent-maintainable evidence data.

Create a static GitHub Pages site that demonstrates a searchable and filterable artifact gallery for contracts, QA output, deploy evidence, recipes, plans, and screenshots. Keep it backend-free and safe for autonomous agents to maintain.

Copy evidence strip

Every strong line gets paired with a verifiable artifact.

Claim 01

Static GitHub Pages delivery

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

Claim 02

Search and tag filtering run in browser-only JavaScript

Evidence: Recipe docs — .agent/recipes/artifact-gallery documents fit, static safety rules, and acceptance criteria.

Claim 03

Artifact data is repo-local JSON

Evidence: Visual QA — npm run test:visual checks desktop and mobile layouts for overflow, console errors, and visible controls.

Claim 04

Payment disabled / no-payment mode

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

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 · Behavior

Static behavior that feels like software

Search, tag filtering, visible result counts, and URL tag state run entirely in the browser from a public JSON data file.

02 · Maintenance

Future agents edit the data, not the architecture

New artifacts are added by updating src/data/artifacts.json and rerunning artifact, visual, and build checks.

03 · Safety

Proof stays public-safe and static

The gallery rejects unsafe hrefs, payment or tracking domains, private data claims, and unsupported proof language.

Proof artifacts

Evidence a future maintainer can verify.

Repo-verifiable artifact

Artifact data contract

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

Repo-verifiable artifact

Recipe docs

.agent/recipes/artifact-gallery documents fit, static safety rules, and acceptance criteria.

Repo-verifiable artifact

Visual QA

npm run test:visual checks desktop and mobile layouts for overflow, console errors, and visible controls.

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: Linking private artifacts or secrets.

Safe next step

Browse artifacts

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

Browse artifacts