Shows what the Architectural Review Board (AiRB) will look for in your project and what is still missing, long before your review. It reads the pinned AiRB control catalog and checks your repository against it.
When to Use
- Early, even at
localhost. A preview runs before your review level is assigned. - Before you request a sandbox, and again before you submit to AiRB.
- When you want to know where a piece of evidence should be recorded.
What to Say
- "Check AiRB readiness for this repo."
- "What will AiRB ask for?"
- "Help me close my readiness gaps."
- "Set up my evidence index."
What Happens
- The agent runs the check and reads you the header: the catalog version, its integrity check, and the review level used.
PREVIEW, review level not assigned means only the Level 0 controls ran. - It explains the results by domain (Data, Operations, Engineering, Security) and by control, such as
ARB-ENG-15:- whether each control applies to your project, and why
- which repository signals it found
- which evidence locations are still
MISSING
- It offers to work through gaps one at a time:
- answering a question about your project, recorded under
applicability in ember-project.yaml - making a small file change
- recording where a piece of evidence lives
- It reruns the check after each fix.
How to Read the Results
| Result | Meaning |
|---|
APPLIES | AiRB will look at this control for your project |
NOT APPLICABLE | Your declarations rule it out. AiRB can disagree |
APPLICABILITY UNDECLARED | A question about your project is unanswered. Counts as a gap |
DECLARATION CONFLICT | Your declaration contradicts what the repository shows. Counts as a gap |
AIRB DETERMINED | AiRB decides this. Shown for awareness, never a gap |
SIGNAL FOUND | Evidence exists. It does not mean the control is met |
NOT CHECKED | The check could not run here, with the reason |
What It Never Does
- Say a control is met or evidence is accepted. AiRB reviewers decide that.
- Copy controlled accreditation evidence into your repository. It records a link to the Accreditation project record instead.
- Edit the pinned catalog. A failed integrity check stops it.
- Call GitHub or any external service. Checks that need them report
NOT CHECKED.
What It Changes
| Where | When |
|---|
docs/evidence/evidence-index.yaml | When you ask it to set up or refresh the index. It never deletes a location you filled |
docs/evidence/YYYY-MM-DD-readiness-report.md | When you ask for a dated report |
ember-project.yaml applicability | When you answer a question about your project and confirm |
Run It Without an Agent
node ~/gitroot/ember-platform-skills/skills/ember-airb-readiness/scripts/readiness.mjs ~/gitroot/<slug> --report
node ~/gitroot/ember-platform-skills/skills/ember-airb-readiness/scripts/readiness.mjs ~/gitroot/<slug> --scaffold-index
Add --write-report for a dated record, or --format json for tooling.
Common Problems
| You see | Do this |
|---|
| Catalog hash mismatch | A pinned catalog file changed. Restore it from Git, never edit it |
review_level is MISSING at production-candidate | AiRB assigns the level at intake. Record it in ember-project.yaml |
ARB-ENG-15.S1 deployment configuration present | A localhost project should have no render.yaml, vercel.json, or CI deploy step. Remove it, or promote to sandbox |
Many MISSING locations | Normal early on. Fill them as you write each document |
