Source hierarchy
- Authenticated repository files, history, tests, actions, and deployment evidence
- Real captures from audited local or live applications
- Explicit user confirmation for personal, employment, metric, credential, and date claims
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.
Status is exact
Production prelaunch is not live operations. A tested local product can work through MCP or a CLI without a hosted service or graphical interface. A functional prototype is not a deployment, and recovery work is not implemented capability.
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.
Evidence fits the interface
Application captures and implemented-architecture schematics are labeled separately. A headless MCP server can be represented by its tested protocol, workflow, and architecture without inventing a graphical screen. Schematics do not count as application captures.
Human authority is visible
AI assistance is separated from approvals, business decisions, provider activation, payments, messages, and other external effects.
Review remains open
The audit summary counts eight previous repository-repair pull requests separately from later publication work. 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.
- Tested Local Product — MCP Server; Not Hosted
- An implemented MCP server operates locally, with verified tests and an operator-confirmed working product. A hosted endpoint or graphical interface is not required; case-specific limits still apply.
- 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.