Static GitHub Pages delivery
Evidence: Contract file — The generated site contract records allowed claims and approval-required changes.
Static AgentSite · product-cockpit recipe · no-payment mode
Trustworthy service copy with proof attached
Every claim points back to a contract, QA check, deployment receipt, or documented scope boundary so future agents can improve the site without inventing credibility.
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 landing page that uses proof artifacts to keep service copy credible and maintainable.
Create a credibility-focused static landing page for a service where every marketing claim is paired with proof, evidence artifacts, QA output, contracts, and deployment receipts. Keep it static and avoid fake quoted endorsements, fake metrics, analytics, and payment links.
Copy evidence strip
Every strong line gets paired with a verifiable artifact.
Repo-local QA scripts
Evidence: QA scripts — Repo-local checks scan contracts, claims, links, SEO basics, and build output.
Contract-backed maintenance boundaries
Evidence: Deploy receipt — The deploy verifier checks the live GitHub Pages URL for expected text.
Audience named in the brief
Built for the people who need the workflow explained clearly.
- Founders refining service positioning
- Agents maintaining trustworthy marketing copy
- Reviewers who need evidence before approving stronger claims
Cockpit panels
Status, workflow, proof, and constraints in one scan.
The brief in plain language
Create a credibility-focused static landing page for a service where every marketing claim is paired with proof, evidence artifacts, QA output, contracts, and deployment receipts. Keep it static and avoid fake quoted endorsements, fake metrics, analytics, and payment links.
Who the site speaks to
Primary readers include Founders refining service positioning, Agents maintaining trustworthy marketing copy, Reviewers who need evidence before approving stronger claims.
Safe static delivery
The repository includes contracts, QA scripts, and GitHub Pages deployment without analytics, payments, or server runtime.
Proof artifacts
Evidence a future maintainer can verify.
Contract file
The generated site contract records allowed claims and approval-required changes.
QA scripts
Repo-local checks scan contracts, claims, links, SEO basics, and build output.
Deploy receipt
The deploy verifier checks the live GitHub Pages URL for expected text.
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: Configuring custom domains or DNS.
Safe next step
Inspect the evidence
Use the cockpit panels, repository contracts, and QA commands before changing claims, scope, payments, analytics, or deployment settings.