Chapter 3 of 6
Confirm these prerequisites:
- The agent exists in the approved nonproduction Foundry project from the governed agent baseline.
- The agent owner can name the exact agent version, tool list, runtime owner, and approved release path.
- The product owner, responsible-AI lead, and legal or compliance reviewer can resolve the inventory, impact, and transparency decisions.
- The runtime owner can deploy the approval gate through the approved application pipeline and can protect any tool execution endpoint outside this repository.
- The approval gate runs behind App Service authentication with Microsoft Entra ID, so App Service injects
X-MS-CLIENT-PRINCIPAL,X-MS-CLIENT-PRINCIPAL-ID, andX-MS-CLIENT-PRINCIPAL-NAMEfor the authenticated requester and approver. - The Entra app role or group claim in
oversight-decision.jsonis assigned to the approver identity and not to the requester identity used in the delivery check. - The delivery owner has two synthetic payload files outside this repository, one for the approved path and one for the rejected path.
- The approver role is trained on this system, has authority to reject the action, and can trigger the recorded stop mechanism.
Implementation files#
| Type | File | Consumer |
|---|---|---|
| Runtime | artifacts/records/ai-system-inventory-entry.schema.json | The responsible-AI inventory workflow and preflight scripts |
| Record | artifacts/records/ai-system-inventory-entry.json | The responsible-AI inventory owner and preflight scripts |
| Record | artifacts/records/impact-assessment.md | The product owner, responsible-AI lead, and legal or privacy reviewers |
| Record | artifacts/records/transparency-note.md | The product owner, communications reviewer, and transparency owner |
| Record | artifacts/oversight/oversight-decision.json | The runtime owner, approver role, delivery owner, and preflight scripts |
| Runtime | artifacts/runtime/foundry_human_approval_gate.py | The approved Foundry agent runtime |
| Runtime | artifacts/runtime/requirements.txt | The agent runtime build process |
Resolve artifact values in the approved private configuration path. Keep customer data, tenant IDs, endpoints, prompts, traces, access tokens, and raw approval payloads out of this repository.