Static AgentSite · editorial-ledger archetype · no-payment mode

A calm memo where every claim has provenance

Operating note

A calm static memo page that shows how every claim maps to a verifiable artifact.

Create an editorial ledger style static site for a credibility-focused service memo. It should feel like a polished briefing, not a dashboard. Pair claims with evidence, artifacts, contracts, QA output, and deployment receipts. Keep it static with no analytics, no payments, no fake quoted endorsements, no fake metrics, and no live data.

Claim ledger

Every major statement stays attached to evidence.

01 Static GitHub Pages delivery

Site contract — .agent/site.contract.yaml records allowed claims, required sections, and approval boundaries.

02 Repo-local QA scripts

QA scripts — npm run qa checks contracts, claims, links, SEO basics, and the production build.

03 Contract-backed maintenance boundaries

Visual QA screenshots — npm run test:visual verifies desktop and mobile layouts and saves inspection screenshots.

04 Deploy verification workflow

Deploy verification — npm run verify:deploy confirms the GitHub Pages URL contains expected live copy.

Sections

The page reads like a concise operating memo.

01

Claim provenance before persuasion

The page treats every strong line as something that needs a source, not just a better adjective.

02

Future maintainers need a short audit trail

Contracts, QA scripts, screenshots, runbooks, and deploy receipts make it easier for agents to improve copy without drifting.

03

The limits are part of the trust surface

The memo says what is not included: no live data, no payment flow, no analytics, no fabricated customer proof, and no unsupported guarantees.

Proof artifacts

Evidence future agents can inspect before strengthening copy.

01

Site contract

.agent/site.contract.yaml records allowed claims, required sections, and approval boundaries.

02

QA scripts

npm run qa checks contracts, claims, links, SEO basics, and the production build.

03

Visual QA screenshots

npm run test:visual verifies desktop and mobile layouts and saves inspection screenshots.

04

Deploy verification

npm run verify:deploy confirms the GitHub Pages URL contains expected live copy.

Boundaries

Trust comes from saying what is not included.

Next step

Read the claim ledger

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

Read the claim ledger