EmberApplication Platform
Menu
Proposed designOnboarding guidance, not accreditation or production access

Ember Onboarding

From a new laptop to a running sandbox.

Every Ember project follows the same path. You talk to your agent in VS Code, and an Ember skill answers each step. This section presents the skill guides from the Ember Platform Skills repository.

The journey

Eight steps, one hand-off

Developers run every step except provisioning. The sandbox request is the hand-off to the sandbox operator. Unsure where you are? Ask Ember Help for your next step.

  1. 01
    Developer

    Meet the prerequisites

    Windows 11, VS Code, a separate local admin account, and access to the ATL-Trip-Planner GitHub organization. Then clone the skills repository.

    Workstation prerequisites
  2. 02
    Developer

    Set up the workstation

    Install and check the pinned toolchain. Ask "Check my machine." until nothing is pending.

    Ember Workstation
  3. 03
    Developer

    Start or adopt a project

    Create a new project under ~/gitroot/<app-slug>, or retrofit an existing repository. The project starts at the localhost tier with synthetic data only.

    Ember App Onboard
  4. 04
    Developer

    Keep it on the standard

    Run the context linter whenever instructions or docs change. The pre-commit hook runs it too.

    Ember Context Lint
  5. 05
    Developer

    Preview AiRB readiness

    See what AiRB will look for and fill the evidence index as you write each document.

    Ember AiRB Readiness
  6. 06
    Developer, hand-off to the sandbox operator

    Request a sandbox

    Promote the project. The gate checks run, the request is recorded, and an issue opens for the sandbox operator.

    Ember App Onboard
  7. 07
    Sandbox operator

    Provision the sandbox

    The sandbox operator validates the request, confirms the plan, provisions the sbx resources, and closes the issue.

    Ember Sandbox Provision
  8. 08
    Developer

    Move to the sandbox tier

    Promote again after the issue closes. Production-candidate work continues in Accreditation.

    Ember App Onboard
Diagram 04Project promotion tiers

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.

  1. Tier 1localhost

    Who 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

    Synthetic data only

  2. 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

    Synthetic data only

  3. Tier 2sandbox

    Who 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

    Synthetic data only

  4. 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

    Accreditation ID required

  5. Tier 3production-candidate

    Who 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

    Accreditation ID required

  6. 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
    Open Accreditation

Skill guides

Onboarding topics

Each page renders the guide from the skills repository as it was copied into Ember.

Developer guide

Workstation prerequisites

What you need before setup: Windows 11, VS Code, a separate local admin account, GitHub organization access, and the clone of the skills repository.

Developer skill

Ember Workstation

Sets up a Windows 11 machine for Ember development with the pinned toolchain, then checks it on later runs.

Developer skill

Ember Help

Tells you where you stand and which Ember skill to use next. It only reads.

Developer skill

Ember App Onboard

Starts a new project, retrofits an existing repository to the standard, and files the sandbox request.

Developer skill

Ember Context Lint

Checks a repository against the Ember LLM context standard on every commit and pull request.

Developer skill

Ember AiRB Readiness

Reports gaps against the pinned AiRB control catalog. It never says a control is met.

Sandbox operator skill

Ember Sandbox Provision

For the sandbox operator. Turns a confirmed sandbox request into running resources and tears them down at expiry.

Developer reference

Ember Platform Skills repository

The skills repository overview: setup on a new machine, contributing, checking a repository, and its layout.

Production-candidate and production

The production-candidate tier needs an Accreditation project ID, and production is reached only through the AiRB and ARB human decision and the operations handover. Project entry, evidence, and review status live in Accreditation. Ember Developer Qualification signals readiness only. It is not accreditation or production-access authorization.

Guides copied from ember-platform-skills at commit 0b01dcf on 2026-10-19.