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
Every public project statement must map to authenticated repository evidence, a real application capture, or information explicitly confirmed by Paul Warner. Unknowns stay unknown.
Production prelaunch is not live operations. A functional prototype is not a deployment. Architecture or recovery work is not implemented capability.
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.
Live captures, local prototypes, diagrams, and concepts must identify what they are. A design panel never substitutes for a deployed screenshot.
AI assistance is separated from approvals, business decisions, provider activation, payments, messages, and other external effects.
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