Site contract
Defines mission, required sections, allowed claims, approval boundaries, and live verification expectations.
Static AgentSite · product-cockpit recipe · no-payment mode
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.
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/artifacts.json is validated by npm run check:artifacts before build and deploy.
.agent/recipes/artifact-gallery documents fit, static safety rules, and acceptance criteria.
npm run test:visual checks desktop and mobile layouts for overflow, console errors, and visible controls.
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.
Evidence: Artifact data contract — src/data/artifacts.json is validated by npm run check:artifacts before build and deploy.
Evidence: Recipe docs — .agent/recipes/artifact-gallery documents fit, static safety rules, and acceptance criteria.
Evidence: Visual QA — npm run test:visual checks desktop and mobile layouts for overflow, console errors, and visible controls.
Evidence: Artifact data contract — src/data/artifacts.json is validated by npm run check:artifacts before build and deploy.
Search, tag filtering, visible result counts, and URL tag state run entirely in the browser from a public JSON data file.
New artifacts are added by updating src/data/artifacts.json and rerunning artifact, visual, and build checks.
The gallery rejects unsafe hrefs, payment or tracking domains, private data claims, and unsupported proof language.
src/data/artifacts.json is validated by npm run check:artifacts before build and deploy.
.agent/recipes/artifact-gallery documents fit, static safety rules, and acceptance criteria.
npm run test:visual checks desktop and mobile layouts for overflow, console errors, and visible controls.
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.
Use the cockpit panels, repository contracts, and QA commands before changing claims, scope, payments, analytics, or deployment settings.