The short answer
C4CI can publicly prove the low-risk onboarding story today: Reader-role Azure discovery, project-based architecture review, and a public documentation path that explains what buyers and signed-in users should do next. Adjacent capabilities are described with proof states so the site does not overclaim.
The proof-state vocabulary
| Proof state | Meaning |
|---|---|
| available | Safe to describe as implemented and usable in the current public flow. |
| guided rollout | Available behind onboarding, tier gates, or controlled customer enablement. |
| pilot | Implemented for narrower Enterprise or partner scenarios, not a broad self-serve claim. |
| live-proof pending | Repo or route support exists, but public evidence is not yet enough for a live-proven statement. |
| planned | Directional roadmap language only. |
What is available
Reader-role discovery is the public baseline. The onboarding path asks teams to connect Azure with least privilege, verify access, run discovery, and review the generated architecture view without handing C4CI Contributor or Owner permissions for the discovery workflow.
That matters because security review usually starts with permission scope. A read-only first step is easier to approve, easier to explain, and easier to reverse if a team decides not to continue.
What is guided rollout
Paid-tier depth, drift workflows, exports, AKS topology, and PAYG usage are public capabilities with important boundaries. Public copy should describe these as guided rollout unless live readiness evidence supports a stronger claim for a specific route or workflow.
This keeps pricing, onboarding, and product readiness aligned: buyers can see what the tiers unlock without mistaking every deeper workflow for broad self-serve readiness.
What is pilot
Enterprise governance workflows and reviewed write-path scenarios belong in pilot language unless the readiness evidence says otherwise. They can be valuable, but they also carry more operational responsibility than Reader-role discovery.
What is live-proof pending
The phrase live-proof pending is deliberately plain. It means C4CI may have implementation work, route support, tests, or internal readiness records, but the public site should not sell it as live-proven until the evidence is current enough.
This is especially important for broad claims around regulated operations. C4CI provides NIS2 / DORA evidence support; it does not claim certification or replace a customer's legal, compliance, or security program.
Bottom line
The public site should help a buyer understand what C4CI can prove, what needs guided onboarding, and what is still being validated. That is more useful than a louder claim, and it makes the product easier to trust.