Prove schemas, mappings, and runtime behavior before publish. This band is the integrator safety net — local validate is cheap; debugging cloud drift after a bad upload is not.
Who this is for
| Role | Use this band when… |
|---|---|
| Integration developer | Every JSON edit — run validate before upload |
| Governance operator | Running protection validate and subject-scoped governance tests |
| CI pipeline | Gating merge on validate, integration, and optional E2E |
Validation runs against Connected System and Business Entity manifests on disk. Integration and E2E commands require a published dataplane and resolved credentials.
In this phase
| Page | Proves |
|---|---|
| Validation, schemas, and repair | JSON matches schemas; repair fixes manifest drift |
| CLI workflow reference | Command order from scaffold to certify |
| Test ladder and protection | Which test command at which phase |
Typical ladder
aifabrix validate <systemKey>
↓
aifabrix upload <systemKey> --probe
↓
aifabrix test-integration <systemKey>
↓
aifabrix test-e2e <systemKey>
↓
aifabrix protection validate + upload
↓
aifabrix verify-governance <systemKey> --subject-email <scoped-user>
Configure pages define what to set; this band defines how to prove it. After green tests, continue to Publish and certify.
Limits
E2E and governance tests hit live vendor APIs and identity sync — use sandbox credentials and scoped test subjects, not production admin tokens. Some test layers are optional in early scaffold phases; certification requires the full ladder in Certification.