Evidence and privacy

Show what exists. State what does not. Protect what should not be public.

This standard governs the maturity labels, proof artifacts, claims, limitations, and privacy boundaries used throughout the portfolio.

Maturity labels

Professional Body of Work

Work completed in a professional role. Public evidence may be reconstructed or summarized when source materials are confidential.

Operational System

A repeatable method with defined inputs, outputs, controls, and operating artifacts. It may be implemented manually, with workplace tools, or through partial automation.

Working Prototype

A functioning implementation that demonstrates key interactions or technical behavior but is not represented as production-ready.

Evaluated Demonstration

A synthetic or sanitized workflow tested against documented scenarios and acceptance criteria.

Documented Architecture

A specified system design, data model, process, or governance framework that has not yet been deployed as a complete product.

Concept or Future Work

A developed idea that may include research, requirements, or design materials but should not be read as a released product.

Claim discipline

Separate implemented behavior from proposed behavior.
Separate measured results from expected benefits.
Identify synthetic, reconstructed, representative, and real-world materials.
State the tools, methods, and personal contribution.
Document known limitations, open risks, and next validation steps.
Do not imply autonomous decision authority in high-impact settings.

Privacy boundary

No employer-confidential source records or proprietary data.
No credentials, private communications, account identifiers, or personal addresses.
No medical, legal, housing, benefits, financial, or other high-risk personal records.
No public client case study without permission and approved redaction.
Synthetic demonstrations should preserve the operational problem without imitating a real person's sensitive facts.

Correction standard

Evidence can improve after publication.

When a claim, link, test, maturity label, or limitation changes, the public page and repository should be updated together. Material corrections should be recorded in version history or release notes.

Review the Work Report a Concern