System diagrams
See the boundaries before relying on them.
These diagrams explain the current Ember direction without implying that a draft standard, application, or access model has been approved.
Cloudflare Access is the proposed entry point for every Ember application, with Microsoft Entra ID as its identity provider. Each application authorizes behind it and uses reusable platform services without handing over its purpose, code, data, or application-specific risk.
The demonstration implements the full learning flow. Authoritative records and access enforcement remain future capabilities.
- 01Shared foundationLanguage, boundaries, responsibility
- 02Role learningDeveloper duties and supported patterns
- 03Applied scenariosSecurity, delivery, and operations judgment
- 04Readiness assessmentKnowledge and responsibility check
- 05Qualification recordFuture authoritative credential
- 06Access eligibilityFuture enforcement decision
Managed services change who performs work. Named people still own the result, decisions, and evidence.
Defines purpose, users, priorities, and acceptable operation
Owns capabilities, roadmap, service expectations, and limits
Owns code, data, authorization, tests, release, and evidence
Builds, verifies, documents, and evolves the supported path
Triages, communicates, coordinates recovery, and escalates
Operate contracted services within their service boundaries
Proposed design. Every Ember project moves from a developer laptop to a production candidate through the same gates. Synthetic data only applies through sandbox. An Accreditation project ID becomes required at the production-candidate gate. Production sits outside the Ember flow.
- Tier 1
localhostWho acts Any developer
- Workstation doctor passes
- Repository under ~/gitroot/<app-slug> with routing files
- Git with secret scan and context lint
- Local Supabase on Rancher Desktop
- No provider accounts
- Accreditation ID is MISSING
- GateGate to sandbox
Who acts Developer prepares, sandbox operator confirms
- Owner named and purpose stated
- Data classification with synthetic-data attestation
- Expiry date set
- Context lint and secret scan clean
- Onboarding request filed by ember-app-onboard
- Tier 2
sandboxWho acts Sandbox operator runs ember-sandbox-provision
- sbx-<app> Supabase, Render, and Vercel where needed
- Cloudflare Access with Entra, airport network by default
- Least-privilege invites with expiry
- CI required
- AiRB Level 0 intake stub under ARB-ENG-16
- GateGate to production-candidate
Who acts Developer and project owner, with Accreditation
- Accreditation project record created, its ID replaces MISSING
- Review level 0 to 3 determined
- Evidence index started in Accreditation
- ember-airb-readiness check run
- Tier 3
production-candidateWho acts Developer and project owner, then AiRB reviewers
- Readiness gap report against the versioned AiRB control catalog
- AiRB stages 01 to 06 proceed
- Submission through the AiRB application handoff contract
- Developer Qualification signals readiness only
- Outside EmberProduction
Who acts AiRB and ARB human decision, then operations handover
- Not an Ember tier
- Owned by Accreditation
- Ember links to the project record and does not duplicate it
The provider split is confirmed Engineering direction. Cloudflare Access as the entry point for every Ember application, with Microsoft Entra ID as its identity provider, is owner direction proposed on October 14, 2026 and awaits identity, security, and data approval. Detailed implementation standards, qualification authority, authoritative records, and access enforcement remain incomplete or awaiting approval.