Decision guide
Compare the base subscription with optional add-ons.
Compliance copy is restricted to control evidence and explicit non-claims.
Control disclosure
No unsupported certification claims
Control evidence, not unsupported certification claims.
The compliance route exists to show which controls are already visible in the platform, which evidence sources exist, and which certification statements are intentionally not made on this public surface.
No unsupported SOC 2, ISO, HIPAA, or PCI claim on this route.
Control evidence is tied to real platform behaviors.
Operational trust routes remain separate from legal promises.
Compliance copy is restricted to control evidence and explicit non-claims.
0 allowed
Unsupported certification claims
5
Public-safe trust routes
Code + contract + aggregate ops
Control sources
Compliance disclosure route
This route distinguishes present control evidence from absent certification claims.
Contract truth
Shipped now
What we can evidence now
Browse-only public routes, billing-driven subscriptions, audit expectations, and release validation status are all evidence-backed today.
- Public mutation Browse-only
- Subscription source Billing state
- Release validation Snapshot release records
- Evidence surfaces Security, status, reliability, and release-notes routes provide the supporting public-safe disclosures.
Contract truth
What we do not claim here
This route does not assert third-party certifications or sector-specific compliance programs unless separately evidenced.
- SOC 2 claim Not claimed
- HIPAA claim Not claimed
- PCI claim Not claimed
- Why it matters Public trust falls apart when unsupported certification language appears.
Control matrix
Public-safe control areas
The route distinguishes control evidence from non-claims so compliance language stays accurate.
| Control area | Current public-safe statement | Evidence route |
|---|---|---|
| Public mutation boundaries | Logged-out routes are browse-only. | /security |
| Included access authority | Billing state drives control-plane included features. | /compare |
| Release validation | Snapshot releases carry validation state. | /release-notes |
| Operational health | Aggregate signals only, not raw tenant logs. | /reliability |
| External certification claims | Not made on this route without separate evidence. | /compliance |
Disclosure rule
Setup truth
Why this route is intentionally narrower than enterprise marketing boilerplate
It is better to expose fewer, evidence-backed control statements than to overstate a compliance posture.
- Allowed Control boundaries, aggregate evidence sources, and explicit non-claims.
- Not allowed Unsupported certification badges or sector-specific assurances not present in the current run evidence.
Validated
validation-1771969452 (beta)
Snapshot-backed release record with module and post-type version governance.
- Snapshot id 218346347
- Module versions 119
- Post type versions 64
- Built at 2026-02-24T21:46:30.140013
- Hero Initial release
- Rich Text Initial release
- Cta Initial release
- Split Initial release
Compliance disclosure: external certification claims are intentionally absent here unless later workflows add direct evidence for them.
Take operational guide back into the core public path
Security and compliance guide should still route back into compare, launch-path, and protected entry points.