Website Ownership Standard
Source access, domain control, deployment portability, content ownership, integration inventory, and a practical exit path.
Public standards
What we expect the work to survive.
A custom website should survive a release, a future developer, a vendor change, and eventually a handoff. These standards document the parts of that promise that should not depend on sales language.
The standards are intentionally practical. They describe ownership, portability, build validation, and release behavior that can be checked against the repository and the delivered project.
Release Quality Gate
Production compilation, editorial validation, generated-HTML SEO checks, representative browser QA, and measurable release thresholds.
Measurement Methodology
The definitions and limits behind public lead, attribution, revenue, and case-study claims.