Public-claims control

Evidence is a release gate,
not a footnote.

Every public project statement must map to authenticated repository evidence, a real application capture, or information explicitly confirmed by Paul Warner. Unknowns stay unknown.

01

Source hierarchy

  1. Authenticated repository files, history, tests, actions, and deployment evidence
  2. Real captures from audited local or live applications
  3. Explicit user confirmation for personal, employment, metric, credential, and date claims
02

Status is exact

Production prelaunch is not live operations. A functional prototype is not a deployment. Architecture or recovery work is not implemented capability.

03

Protect private material

Credentials, customer data, sensitive endpoints, and internal configuration are excluded. Intended-private repository source is not linked as portfolio evidence; case studies use only sanitized behavior and control evidence.

04

Media is labeled

Live captures, local prototypes, diagrams, and concepts must identify what they are. A design panel never substitutes for a deployed screenshot.

05

Human authority is visible

AI assistance is separated from approvals, business decisions, provider activation, payments, messages, and other external effects.

06

Review remains open

Eight repair pull requests are draft and unmerged. A green check validates the proposed branch; it does not imply human approval or production release.

Status dictionary

Words used on this site

Production Prelaunch — Controlled Launch
A real deployed surface exists, while production operations or sensitive external actions remain intentionally gated.
Functional Prototype / In Development
Meaningful code and verification exist, but the product is not represented as a production service.
Recovery Candidate — Empty Remote Repository
Matching local source evidence exists outside an empty remote, but restoration still requires index, secret, provenance, intended-scope, and private-bootstrap review; it is not an implementation claim.
Learning Artifact
Planning or educational material only, with no software implementation claim.

See the system, then see its limits.

Return to case studies