Evidence
Evidence you can inspect.
When we can show the method, we do not ask a statement to be accepted on trust. This page brings together Cenit Labs–owned artifacts that show how decisions are recorded, quality is verified, operations are protected, and handoff is prepared.
Recorded architecture decisions
Context, decision, and consequences: a sanitized representation of the pattern used to record material technical decisions.
Acceptance criteria and release gates
Acceptance criteria, review in an immutable Preview, approval, and a post-promotion smoke check leave a verifiable sequence before and after each site release.
- Acceptance criteria
- Immutable Preview review
- Approval
- Post-promotion smoke
Operational events with allowlisted fields
A typed contract and an automated verification reduce the risk of personal data, secrets, or raw request bodies appearing accidentally in operational logs.
Operational runbooks
Routine scenarios, incidents, severity, containment, recovery, and rollback organized before an emergency occurs.
- Routine scenarios
- Incidents
- Severity
- Containment
- Recovery
- Rollback
Security checked at build time
The site build verifies its Content Security Policy and stops when it finds a disallowed condition. The production site makes the result directly inspectable: accessibility, progressive enhancement, performance, and security headers.
R1–R6 as decision tools
R1–R6 are conceptual references for explaining inputs, transformations, human-control points, and intended outcomes. They are not presented as client implementations or client results.
We do not publish client identities, logos, or results without written authorization. Cenit Labs–owned artifacts and conceptual examples are labeled by type so that a method is never presented as a client result.