Approvals
Nothing leaves the system without a logged human decision · every approval is recorded in the Fabric ledger, which this application cannot write
Awaiting decision
4
plans and runs
Escalation threshold
$50.0M
gated revenue above this always escalates
Current exposure
$596M
above threshold — approval required
Comms sent
0
no external communication
Pending
| Item | Kind | Subject | Owner | State |
|---|---|---|---|---|
| RP-0001 | Recovery plan | Cascade Precision Castings · PO-450112 | u-marcus | awaiting buyer |
| run-0002 | Agent run | recommendation_agent | — | pending |
| local-mts8eaho | Agent run | recovery_flow | — | pending |
| local-mts8cy5y | Agent run | recovery_flow | — | pending |
What is never autonomous
- Sending any communication to a supplier
- Writing to SAP, PLM or any system of record
- Committing to a date, price or quantity
- Quantifying revenue at risk through the BOM
- Scoring supplier risk with contributing factors
- Assembling context and drafting a plan
- Running guardrail checks on every output
Fabric’s own check is role-only and would permit a requester to approve their own request. AeroFlow refuses that above the gateway — the approver must not be the raiser (task S-6.1).