Back to Build AI-ready systems overview.
Prove schemas, mappings, and runtime behavior before publish. Tests are a first-class platform contract — not an optional CI garnish. Local validate is cheap; debugging cloud drift after a bad upload is not.
There are two prove families:
| Family | Proves | Home |
|---|---|---|
| Connected System | Package manifests, pipeline, live vendor or CIP | Connected System tests |
| Role Assistant | Governed assistant in dev / tst / pro |
Role Assistant tests |
Neither family replaces the other. Why both proofs exist before production — and why agent SDKs and encoded workflow graphs are not substitutes — is on Proving Role Assistants.
Connected System structure, pipeline, and live E2E tests prove technical readiness — that the capability executes safely and correctly. Role Assistant and business test cases prove something different: that the assistant's answers reflect the capability contract the business actually meant — its business/semantic readiness. A green Connected System ladder is required but does not by itself prove the second; see Technical readiness vs business/semantic readiness and Business meaning as governed content for why both proofs stay separate.
Applying a Builder Integration Definition is a create path, not a test — see Apply an integration definition.
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 | Protection, governance, and certification overlay |
| Connected System tests | Structure, pipeline, live E2E, and gold rows |
| Role Assistant tests | role-assistant test catalog (YAML authoring stays in Operate) |
Typical ladder
What this shows: Connected System proof from local validate through live E2E, then protection and certify. Role Assistant prove is a separate family.
What this is not: BID apply (create path) or YAML case authoring (Operate). Command flags live on the how-to pages.
Configure pages define what to set; this band defines how to prove. After green tests, continue to Publish and certify.
Limits
E2E and governance tests hit live vendor APIs and identity — use sandbox credentials and scoped test subjects, not production admin tokens. Some test layers are optional in early scaffold phases; certification requires the full Connected System ladder in Certification. Role Assistant prove does not replace that ladder.
Next: Publish and certify.