Organisation-scoped incident records
Criticl’s protected domain is designed around explicit organisation scope rather than public or cross-tenant incident access.
Criticl is being built for high-stakes coordination, so the product should be as explicit about what is gated as it is about what is available. This page separates implemented product foundations from integrations that still require reviewed ecosystem work.
These statements describe repository-backed foundations. They are not certifications, legal opinions or evidence of a completed customer production acceptance.
Criticl’s protected domain is designed around explicit organisation scope rather than public or cross-tenant incident access.
Protected incident access does not become authorised merely because authentication succeeds; production governance adapters remain deliberately closed until reviewed.
Timeline events and handover snapshots are designed to preserve chronology and integrity rather than silently rewriting the response record.
Current evidence handling records references and digests. Criticl does not claim verified production object storage or legal evidentiary status.
The public tour and current incident application do not independently send emergency notifications or execute high-impact recovery actions.
Criticl already preserves these boundaries in its architecture. They become customer capabilities only after the owning Alphareon and 1App contracts are reviewed and accepted.
A reviewed Criticl relying-application contract is required before customer production identity claims are made.
External reviewed contract requiredShared permission and consequential-action governance remain an external authority boundary.
External reviewed contract requiredPeople, assets, dependencies and shared evidence context require reviewed tenant-scoped Vector integration.
External reviewed contract requiredReasoning must remain evidence-linked, bounded and non-authoritative until separately evaluated and approved.
External reviewed contract requiredDurable cross-system coordination and external actions remain separate reviewed integration responsibilities.
External reviewed contract requiredWe would rather be precise about the current product than imply a certification, residency guarantee or automated emergency capability that has not been proven.