Sources and interpretation
External factual claims should cite authoritative primary sources. ZeroUI interpretations and product principles should be identified as such.
Editorial standards
Clear distinctions between product direction, conceptual models, and verified evidence.
These standards explain how ZeroUI materials about software change governance, AI-assisted engineering, production learning, and human accountability should be interpreted.
Claim status
Four labels protect meaning.
Product direction
Describes what ZeroUI is building, is designed to do, or intends to support.
Conceptual model
Explains a ZeroUI approach or framework; it is not presented as an independent industry standard.
Illustrative example
Demonstrates an idea and is not a customer result or production-confirmed interface.
Verified result
Should be used only when supporting evidence, scope, and methodology are available.
Product accuracy
Planned or unvalidated behavior uses language such as “is building,” “is designed to,” or “is intended to.”
Evidence integrity
ZeroUI does not present invented customers, testimonials, metrics, benchmarks, certifications, integrations, or participants as evidence.
Dates and corrections
Substantive content displays its latest material-review date. Corrections should be identified when they change a reader’s understanding.
Scope
Without a documented method and supporting evidence, a page should be read as a ZeroUI perspective or conceptual model—not peer-reviewed research.
Human authorship
Named authors or reviewers will be added only when their identity and role can be verified. Until then, ZeroUI is the organizational author.
Current library
Explore the material these standards govern.
Start with the foundational definition, conceptual reference model, glossary, and clearly labeled perspectives.