Start here
C4CI docs are public for search, buyers, architects, and security reviewers. When someone is signed in, the same documentation renders inside the platform shell so it stays close to project work.
The first path is deliberately simple: create a project, connect Azure with Reader role, verify access, run discovery, then review the generated architecture view and its proof state.
Proof state vocabulary
Public docs use proof-state labels so buyers can tell the difference between implemented onboarding, guided rollout, pilot work, planned direction, and live-proof pending claims.
| Proof state | Meaning |
|---|---|
| available | Documented behavior is implemented and customer-safe to follow. |
| guided rollout | The capability exists, but teams should use guided onboarding. |
| live-proof pending | Repo implementation exists, but public proof still needs evidence. |
| planned | The docs name the direction without presenting it as shipped. |