Operational evidence · OPR.SOP.P003.001

Four routes monitored. Assurance remains evidence-gated.

B045 confirms that the homepage, Knowledge hub, Service Status, and Foundation routes are checked every five minutes from Frankfurt and N. Virginia. Retained execution export and the full-suite observation window remain open.

ProviderCHECKLY

Active checks4/4

Retention policyDESIGNED

Assurance claimWITHHELD

Managed monitoring contract

Four routes. One governed evidence model.

Active checks run every 5 minutes in Europe and North America. Each asserts HTTP 200, follows redirects, uses no authentication or request body, and retries twice before a confirmed failure.

SYN-P003-001 · Frankfurt + N. Virginia

Public homepage

GET / → 200

No authentication or request body. Execution evidence traces to OPR.EVD.P003.001.

Active · owner alerts

SYN-P003-002 · Frankfurt + N. Virginia

Knowledge hub

GET /knowledge → 200

No authentication or request body. Execution evidence traces to OPR.EVD.P003.001.

Active · owner alerts

SYN-P003-003 · Frankfurt + N. Virginia

Service status

GET /status → 200

No authentication or request body. Execution evidence traces to OPR.EVD.P003.001.

Active · owner alerts

SYN-P003-004 · Frankfurt + N. Virginia

Foundation record

GET /foundation → 200

No authentication or request body. Execution evidence traces to OPR.EVD.P003.001.

Active · owner alerts

Evidence retention

Keep the signal. Exclude the content.

The retention contract is designed for synthetic execution metadata only. Activation requires a governed store and verified export; policy design alone does not create retained history.

Policy: P003-RET-OPS-001 v1.0.0
Retention window: 90–365 days
Storage: NOT_CONNECTED
Response bodies: PROHIBITED

P000 alignment

An operational service of the Experience Layer.

P003 remains the governed AVERELI Web Platform. “Experience Layer” is an internal architectural concept inherited from P000’s review, not a programme rename. Checkly operates the monitoring adapter; P003 retains accountability for its procedure, evidence, and public claims.

Provider state: CHECKLY_CONNECTED
Secrets in source: NONE
Foundation freeze gate: FULL_ROUTE_MONITORING
EKF lifecycle: Active

Rollout and assurance gates

Connection is real. Claims still require evidence.

01Checkly account and dashboard access — COMPLETE
02Two distinct execution locations — COMPLETE
03Owner email alert channel — COMPLETE
04Four governed routes — COMPLETE
05API or evidence export and retention — OPEN
06First 24-hour full-suite observation window — OPEN

Active reachability checks do not yet support published availability, latency, SLA, SLO, incident-response, or recovery claims. Those remain withheld until the open gates are completed and attributable history is retained.

Observability architecture →Recovery architecture →