Documentation Completeness Review in-progress
This page is the portal quality gate. It answers a direct question:
Can each audience use the portal without reading raw repo docs first?
Current Readiness By Audience
| Audience | Current posture | Strongest pages | Still thin |
|---|---|---|---|
| Product team | usable but needs more screenshots and journey proof | Product Team Handoff, Current State And Roadmap, Use AI Cloud, Screenshot Flow Coverage | fresh screenshots beyond MFA |
| Architecture / ARB | strong enough for review | Overall Platform Architecture, System Overview, Code Structure And Layer Model, Service Design Matrix, Detailed Design Index | deeper service-specific diagrams as code changes |
| CISO / Security | usable, evidence-aware | Security & Production Readiness, Current Controls, Evidence Readiness Model | clearer claim readiness per environment and less inherited CISO ceremony language |
| Developers | usable for orientation | Developer Implementation Map, Developer APIs, Code Structure And Layer Model, Service Design Matrix | feature-specific implementation packets as new work starts |
| App / SDK developers | strong for concept, improving for build path | Build on AI Cloud, App SDK Proof, Add a New App | screenshot-backed app launch/connect guide and more example-code walkthrough |
| Token Factory / shared-platform builders | good first-pass | Token Factory Builder Path, Shared Platform Consumer Track, Product Onboarding, Shared Services | implementation packet once Token Factory moves from design to code |
| IAM | good model coverage | IAM Capabilities, Resource Model and Naming, MFA Walkthrough | service-account UX and recovery/admin operation screenshots |
| Infra | good environment/deployment start | Infra and Environments, Production Deployment Model, Demo and Staging Setup, Node Lifecycle | live staging/demo evidence once environments are created |
| Operations | good operating model start | Operators, Release Operations, CI/CD Delivery System, Service Version Readback | implementation of version/readback API/UX |
| End users | partially usable | End User Guide, Screenshot Flow Coverage, MFA Walkthrough, Launch and Operate | full fresh screenshot coverage for launch, connect, billing, storage, tenant admin, and troubleshooting |
Completion Criteria
The portal should not be called complete until these are true:
- Each top persona has one clear entry path and one “what this proves” page.
- User-facing workflows have screenshot-backed guides for the main happy, blocked, recovery, and cleanup paths.
- Architecture pages include a top-down overview plus detailed design packets with diagrams that are enough to start implementation.
- Developer pages connect contracts, generated artifacts, state models, package ownership, local validation, and CI gates.
- Security pages distinguish implemented controls, environment posture, evidence, deferred claims, and accepted residual risk.
- Operations pages show deploy, rollback, evidence, monitor, and version readback procedures.
- Canonical source links render as readable portal pages where possible and raw artifacts remain available for audit.
Active Backlog
| Backlog item | Owner | Priority | Notes |
|---|---|---|---|
| screenshot-backed user guide for launch/connect/storage/billing/tenant-admin | docs + product quality | P0 | coverage model exists at Screenshot Flow Coverage; fresh screenshots still needed |
| service-level ER/sequence/state diagrams | architecture | P0 | cross-service matrix exists at Service Design Matrix; add deeper diagrams as service code changes |
| environment version/readback page | ops | P0 | target model exists at Service Version Readback; API/UX implementation still needed |
| Token Factory builder path | architecture + product | P1 | first builder page exists at Token Factory Builder Path |
| demo/staging setup walkthrough | infra + ops | P1 | first setup model exists at Demo and Staging Setup |
| prose reduction pass | product + UX | P1 | move explanation into help/info affordances and guides |
| AI Cloud naming sweep | docs | P1 | keep GPUaaS only where it names the GPU product/resource domain |
Review Method
For each portal section, use this test:
Could a competent person in this audience do the next real task from this page?
If the answer is no, add a concrete backlog row here or fix the page directly.