Operating standards
Last updated: April 2026. Supporting appendix for technical or procurement follow-up.
Dated examples of delivery timing, site controls, and publication verification. This page is shared directly when a reviewer needs more detail. It is not part of the main buying path and it does not show customer outcomes.
- • Internal and synthetic examples only. No client names and no outcome claims.
- • Delivery timing is tracked from payment cleared + intake complete.
- • This appendix is shared case by case. It is not linked from the main public navigation.
Related trust pages: Procurement · Security
Delivery timing example
Example from one internal delivery run. This shows the timer starts when payment is cleared + intake is complete, not when scope is discussed or an invoice is approved.
| Time (CET) | Step | What this shows |
|---|---|---|
| 2026-02-14 19:42 | Intake marked complete | Start of delivery window tracking |
| 2026-02-14 19:45 | Artifact build started | Execution under a defined pipeline |
| 2026-02-14 20:34 | Artifacts built + QA passed | Pack can be produced the same way each run |
Download: Timeline receipt (.txt)
Site controls
Non-outcome checks against the public site: privacy signals, first-party hosts, analytics suppression, and the optional scheduling path.
| Check | Result | What we measured |
|---|---|---|
| Do Not Track checks | 2 | Two runs: DNT off and DNT on |
| Do Not Track suppression | 1 | DNT-on run sent 0 analytics requests |
| Analytics endpoint health | 1 | Valid POST returned 204 on production |
| First-party hosting | 1 | Waterfall list is first-party only |
| Optional scheduling cookies | 2 | Functional cookies on the optional scheduling-by-request host |
| Optional scheduling redirect | 1 | Optional scheduling path validated separately from manual intake |
Downloads: Scoreboard (.csv) · Test receipt (.txt)
Supporting files: Security headers, Negative request tests, CSP header
Internal note: Readiness memo (.txt)
Publication verification
Final checks for copy, linked artifacts, build output, and release captures. This confirms the published trust surfaces were regenerated and reviewed before release. It does not claim business outcomes.
- Copy review completed
- Artifact refresh completed
- Build and link verification completed
- Release captures completed
Release run referenced: 2026-02-15.
Download: Publication receipt (.txt)
Deeper supporting evidence
If a reviewer needs a deeper file-level walkthrough or operational appendix, we share it directly during procurement or scope follow-up rather than routing it from the public site.
Questions
Procurement or security follow-up: hello@revivalops.com. Deeper operational evidence is shared directly when a reviewer needs it. See also Procurement and Security.