Maintain Connected System integrations over time — download online truth, repair local drift, re-certify when vendor APIs or policy change, and configure operator-facing surfaces such as document approval.
Who this is for
| Role | Use this band when… |
|---|---|
| Integration developer | Pulling online config, repairing manifest lists, re-uploading |
| Governance operator | Re-running certification after protection or dimension changes |
| Operator | Content Review and document approval workflows |
Operate is ongoing maintenance after initial certification. Role Assistant design and task configuration live under Role Assistants and Adopt.
In this phase
| Page | Outcome |
|---|---|
| Download, repair, and show online | Drift control and online comparison |
| Deliver assistant channels | Channel delivery patterns for workers |
| Configure document approval | Content Review / document approval (feature-flagged) |
Connected System lifecycle commands also appear in Lifecycle, download, and repair under the Connected Systems band — same commands, UI-aligned context.
Typical maintenance loop
aifabrix show <systemKey> --online
↓
aifabrix download <systemKey> (when intentional)
↓
aifabrix repair <systemKey> --rbac --expose
↓
aifabrix validate <systemKey>
↓
aifabrix upload <systemKey> --probe → upload
↓
Re-run certification pillars when scope changed
Integrators publish governed capabilities during Publish and certify.
Limits
download overwrites local files — commit or branch before pull. delete is destructive online. Document approval APIs and UI require tenant feature flags; confirm deployment before operator training.