Connect · ingestion spine
Write-back register
Reading a source system is a design problem. Changing one is a governance problem. Every route on this page is a way this platform could alter a record inside somebody else's system of record, and none of them runs without three things attached: the authority grant the actor holds, the policy item that permits the operation, and a change record left in the receiving system so the source's own auditors can see what happened and who asked for it.
Health
What this platform can change, and what it has changed
Routes designed against systems that accept writes, and everything that has been attempted through them.
The mechanism is built and it has been exercised 45 times: an attempt resolves an authority grant, checks a policy item, constructs the payload and either writes or refuses. What it has not done is write anything into a production system, because no connector on this estate is attached to a customer instance. Every accepted attempt landed in a sandbox. Reading this page as evidence that write-back works would be reading it wrong; it is evidence that write-back is governed, and that the governance refuses more often than it permits.
The route register
One row per way this platform could change a record in a source system. The authority and policy references are resolved against the grants and the policy corpus, not typed in as free text.
| Route | Into | Operation | Actor | Authority | Policy | State | Att | Written | Change record it must leave |
|---|---|---|---|---|---|---|---|---|---|
| WB-ERP-FI-01 | Group ERP — Financials Journal entry | post-accrual | agent confirmation required | FI4-AUTH-A1 | FI4-POL-200 | Designed, never live | 3 | 0 | Journal document carrying the platform as the source and the grant reference in the header text |
| WB-ERP-FI-02 | Group ERP — Financials Vendor line | set-payment-block | agent confirmation required | FI5-AUTH-A1 | FI5-POL-200 | Blocked No service account has been issued on the finance instance, so there is no identity for the change record to name. | 1 | 0 | Payment block flag with a reason code and the grant reference |
| WB-ERP-MM-01 | Group ERP — Materials and Inventory Purchase order line | update-delivery-date | agent | SC9-AUTH-A1 | SC9-POL-200 | Designed, never live | 3 | 0 | Change document on the purchase order line |
| WB-S2P-01 | Source-to-Pay Suite Requisition | approve-and-release | agent confirmation required | PR8-AUTH-A1 | PR8-POL-200 | Designed, never live | 3 | 0 | Approval record naming the agent, the grant and the materiality band it fell inside |
| WB-S2P-02 | Source-to-Pay Suite Supplier record | update-tax-identifier | agent confirmation required | PR6-AUTH-A1 | GB8-POL-200 | Refused by policy Master data policy reserves supplier identity changes to a named steward. | 2 | 0 | Master data change record with the prior value retained |
| WB-AP-01 | Invoice Capture and AP Automation Invoice | release-for-payment | agent confirmation required | PR9-AUTH-A1 | PR9-POL-200 | Designed, never live | 4 | 0 | Release record with the three-way match evidence attached |
| WB-AP-02 | Invoice Capture and AP Automation Invoice | request-supplier-clarification | agent | PR9-AUTH-A1 | PR9-POL-200 | Designed, never live | 2 | 0 | Correspondence record on the document |
| WB-CRM-01 | Customer Relationship Management Opportunity | update-close-date | agent | RO1-AUTH-A1 | RO1-POL-200 | Designed, never live | 3 | 0 | Field history entry naming the agent |
| WB-CRM-02 | Customer Relationship Management Account | merge-duplicate | agent confirmation required | RO1-AUTH-A1 | GB8-POL-200 | Refused by policy A merge is not reversible at the source. | 2 | 0 | Merge record retaining both source identifiers |
| WB-HCM-01 | Core HR and Payroll Worker position | update-cost-center | agent confirmation required | HR4-AUTH-A1 | FI10-POL-200 | Blocked The people system is read-only to the platform until the works-council pack covering write-back is answered. | 2 | 0 | Effective-dated position change record |
| WB-ITSM-01 | IT Service Management Incident | resolve-and-close | agent | IT1-AUTH-A1 | IT1-POL-200 | Designed, never live | 5 | 0 | Work note plus resolution record naming the agent and the grant |
| WB-ITSM-02 | IT Service Management Change request | raise-standard-change | agent confirmation required | IT10-AUTH-A1 | IT10-POL-200 | Designed, never live | 2 | 0 | Change record inside the standard catalog with the template reference |
| WB-CLM-01 | Contract Lifecycle Management Contract | set-renewal-notice | agent confirmation required | LG1-AUTH-A1 | LG1-POL-200 | Blocked The notice period field is the field that drifted. Nothing writes back into a field the contract cannot yet read reliably. | 2 | 0 | Amendment record with the corrected notice period and the prior value |
| WB-TREASURY-01 | Treasury and Cash Management Cash position | confirm-value-date | agent confirmation required | FI6-AUTH-A1 | FI6-POL-200 | Designed, never live | 2 | 0 | Restatement record on the balance with the prior value date |
| WB-BANK-01 | Bank Connectivity Gateway Payment instruction | release-payment-file | human-confirmed confirmation required | FI6-AUTH-H1 | FI6-POL-200 | Blocked The bank channel is not connected. There is no network path, no certificate and no security review. | 1 | 0 | ISO 20022 instruction with a dual-control record naming both humans |
| WB-MKT-01 | Marketing Automation Contact | suppress-from-campaign | agent | MK5-AUTH-A1 | LG9-POL-200 | Designed, never live | 2 | 0 | Suppression record carrying the consent state that caused it |
| WB-CCAAS-01 | Contact Center Platform Interaction | set-disposition | agent | CS4-AUTH-A1 | CS4-POL-200 | Designed, never live | 2 | 0 | Disposition record on the interaction naming the agent |
| WB-PLANNING-01 | Supply and Demand Planning Supply plan line | commit-recommendation | agent confirmation required | SC2-AUTH-A1 | SC2-POL-200 | Designed, never live | 2 | 0 | Scenario commit record naming the scenario version |
| WB-FPA-01 | Planning and Consolidation Forecast line | publish-agent-forecast | agent confirmation required | FI2-AUTH-A1 | FI2-POL-200 | Designed, never live | 2 | 0 | Version record on the published scenario with the agent named as author |
Where each route stands
An exhaustive partition of all 19 routes. One state each.
What every attempt did
An exhaustive partition of all 45 attempts by outcome.
What kind of change is asked for
The operation named on the route, which is what the receiving system's own change control has to permit.
Every attempt, with its authority and its change record
45 attempts, newest first. 24 of them produced a change record identifier in the receiving system; the rest never reached it.
| Attempt | Route | Unit | Actor | When | Outcome | Authority | Change record | Payload | Reason |
|---|---|---|---|---|---|---|---|---|---|
| WBA-0030 seq 1629 | WB-ITSM-01 IT Service Management | MU-044044 | Service Desk Orchestrator agent | Aug 18, 08:00 | Rejected by the source | IT1-AUTH-A1 IT1-POL-200 | none | Incident resolved while a linked problem record was still open | The sandbox refused the close. The route now checks linked records first. |
| WBA-0027 seq 1626 | WB-ITSM-01 IT Service Management | MU-044016 | Service Desk Orchestrator agent | Aug 18, 08:00 | Accepted in sandbox | IT1-AUTH-A1 IT1-POL-200 | SBX-0027 | Incident resolved, password reset path | Accepted. |
| WBA-0026 seq 1625 | WB-ITSM-01 IT Service Management | MU-044010 | Service Desk Orchestrator agent | Aug 18, 08:00 | Accepted in sandbox | IT1-AUTH-A1 IT1-POL-200 | SBX-0026 | Incident resolved with a knowledge article reference | Accepted. Work note and resolution record both created. |
| WBA-0016 seq 1615 | WB-AP-01 Invoice Capture and AP Automation | MU-042141 | Three-Way Match Orchestrator agent | Aug 18, 08:00 | Rejected by the source | PR9-AUTH-A1 PR9-POL-200 | none | Invoice of 3,410 USD released against a purchase order closed for invoicing | The sandbox rejected it. The purchase order had been closed since the extract was taken, which is a freshness failure showing up as a write failure. |
| WBA-0028 seq 1627 | WB-ITSM-01 IT Service Management | MU-044022 | Service Desk Orchestrator agent | Aug 18, 08:00 | Accepted in sandbox | IT1-AUTH-A1 IT1-POL-200 | SBX-0028 | Incident resolved, access request fulfilled | Accepted. |
| WBA-0029 seq 1628 | WB-ITSM-01 IT Service Management | MU-044031 | Service Desk Orchestrator agent | Aug 18, 08:00 | Accepted in sandbox | IT1-AUTH-A1 IT1-POL-200 | SBX-0029 | Incident resolved, software install completed | Accepted. |
| WBA-0041 seq 1640 | WB-CCAAS-01 Contact Center Platform | MU-045022 | Interaction Disposition Agent agent | Aug 18, 07:00 | Rejected by the source | CS4-AUTH-A1 CS4-POL-200 | none | Disposition set on an interaction with an unmapped queue identifier | Refused by the sandbox because the queue landed as other. This is the same defect the running replay is clearing. |
| WBA-0040 seq 1639 | WB-CCAAS-01 Contact Center Platform | MU-045010 | Interaction Disposition Agent agent | Aug 18, 07:00 | Accepted in sandbox | CS4-AUTH-A1 CS4-POL-200 | SBX-0040 | Disposition set on 1 interaction from structured fields only | Accepted. The transcript was not read, because it is excluded from the contract. |
| WBA-0013 seq 1612 | WB-AP-01 Invoice Capture and AP Automation | MU-042110 | Three-Way Match Orchestrator agent | Aug 18, 07:00 | Accepted in sandbox | PR9-AUTH-A1 PR9-POL-200 | SBX-0013 | Invoice of 44,900 USD released with purchase order and receipt references attached | Accepted with the match evidence on the release record. |
| WBA-0014 seq 1613 | WB-AP-01 Invoice Capture and AP Automation | MU-042118 | Three-Way Match Orchestrator agent | Aug 18, 07:00 | Accepted in sandbox | PR9-AUTH-A1 PR9-POL-200 | SBX-0014 | Invoice of 7,240 USD released, exact match | Accepted. |
| WBA-0015 seq 1614 | WB-AP-01 Invoice Capture and AP Automation | MU-042129 | Three-Way Match Orchestrator agent | Aug 18, 07:00 | Accepted in sandbox | PR9-AUTH-A1 PR9-POL-200 | SBX-0015 | Invoice of 12,880 USD released within the quantity tolerance | Accepted. The tolerance used is on the release record. |
| WBA-0017 seq 1616 | WB-AP-02 Invoice Capture and AP Automation | MU-042156 | Invoice Exception Agent agent | Aug 18, 06:00 | Accepted in sandbox | PR9-AUTH-A1 PR9-POL-200 | SBX-0017 | Clarification request on a quantity variance of 40 units | Accepted as a correspondence record. |
| WBA-0018 seq 1617 | WB-AP-02 Invoice Capture and AP Automation | MU-042160 | Invoice Exception Agent agent | Aug 18, 06:00 | Accepted in sandbox | PR9-AUTH-A1 PR9-POL-200 | SBX-0018 | Clarification request on a missing purchase order reference | Accepted. |
| WBA-0010 seq 1609 | WB-S2P-01 Source-to-Pay Suite | MU-040071 | Requisition Orchestrator agent | Aug 18, 06:00 | Refused by policy | PR8-AUTH-A1 PR8-POL-200 | none | Requisition of 91,000 USD, non-catalog | Above the materiality band on the grant. Refused at the decision boundary and routed to the accountable owner. |
| WBA-0009 seq 1608 | WB-S2P-01 Source-to-Pay Suite | MU-040044 | Requisition Orchestrator agent | Aug 18, 05:00 | Accepted in sandbox | PR8-AUTH-A1 PR8-POL-200 | SBX-0009 | Requisition of 3,120 USD, catalog line | Accepted. |
| WBA-0008 seq 1607 | WB-S2P-01 Source-to-Pay Suite | MU-040021 | Requisition Orchestrator agent | Aug 18, 05:00 | Accepted in sandbox | PR8-AUTH-A1 PR8-POL-200 | SBX-0008 | Requisition of 18,400 USD released against a framework agreement | Accepted. Below the 25,000 band ceiling on the grant. |
| WBA-0031 seq 1630 | WB-ITSM-02 IT Service Management | MU-044090 | Change Orchestrator agent | Aug 18, 04:00 | Accepted in sandbox | IT10-AUTH-A1 IT10-POL-200 | SBX-0031 | Standard change raised from the certificate rotation template | Accepted with the template reference on the record. |
| WBA-0032 seq 1631 | WB-ITSM-02 IT Service Management | MU-044101 | Change Orchestrator agent | Aug 18, 04:00 | Refused by policy | IT10-AUTH-A1 IT10-POL-200 | none | Change raised from a template not in the standard catalog | Outside the declared scope of the grant. Refused and routed to the change manager. |
| WBA-0003 seq 1602 | WB-ERP-FI-01 Group ERP — Financials | MU-041847 | Close Orchestrator agent | Aug 18, 04:00 | Rejected by the source | FI4-AUTH-A1 FI4-POL-200 | none | Accrual of 9,110 USD against a cost center closed at period end | The sandbox rejected the posting because the cost center was closed. The contract validation had not caught it because closure is not in the extract. |
| WBA-0001 seq 1600 | WB-ERP-FI-01 Group ERP — Financials | MU-041820 | Close Orchestrator agent | Aug 18, 03:00 | Accepted in sandbox | FI4-AUTH-A1 FI4-POL-200 | SBX-0001 | Accrual of 184,200 USD against 6 cost centers, period 2026-08 | The sandbox instance accepted the document and returned a document number. |
| WBA-0002 seq 1601 | WB-ERP-FI-01 Group ERP — Financials | MU-041833 | Close Orchestrator agent | Aug 18, 03:00 | Accepted in sandbox | FI4-AUTH-A1 FI4-POL-200 | SBX-0002 | Accrual of 62,940 USD against 2 cost centers, period 2026-08 | Accepted. The evidence record carries both the grant and the sandbox document number. |
| WBA-0021 seq 1620 | WB-CRM-01 Customer Relationship Management | MU-036230 | Pipeline Hygiene Agent agent | Aug 18, 02:00 | Rejected by the source | RO1-AUTH-A1 RO1-POL-200 | none | Close date moved on a record locked by an approval process | The sandbox refused the update while the record was locked. |
| WBA-0019 seq 1618 | WB-CRM-01 Customer Relationship Management | MU-036200 | Pipeline Hygiene Agent agent | Aug 18, 01:00 | Accepted in sandbox | RO1-AUTH-A1 RO1-POL-200 | SBX-0019 | Close date moved to 2026-09-30 on 1 opportunity | Accepted. A field history entry was written naming the agent. |
| WBA-0020 seq 1619 | WB-CRM-01 Customer Relationship Management | MU-036214 | Pipeline Hygiene Agent agent | Aug 18, 01:00 | Accepted in sandbox | RO1-AUTH-A1 RO1-POL-200 | SBX-0020 | Close date moved forward on 12 opportunities in one region | Accepted as twelve separate field history entries. |
| WBA-0036 seq 1635 | WB-TREASURY-01 Treasury and Cash Management | MU-035018 | Cash Position Agent agent | Aug 18, 00:00 | Rejected by the source | FI6-AUTH-A1 FI6-POL-200 | none | Value date confirmed on a balance already restated by a person | The sandbox refused a second restatement on the same balance the same day. |
| WBA-0035 seq 1634 | WB-TREASURY-01 Treasury and Cash Management | MU-035010 | Cash Position Agent agent | Aug 18, 00:00 | Accepted in sandbox | FI6-AUTH-A1 FI6-POL-200 | SBX-0035 | Value date confirmed on 1 restated balance | Accepted. The restatement record carries the prior value date. |
| WBA-0007 seq 1606 | WB-ERP-MM-01 Group ERP — Materials and Inventory | MU-038490 | Order Promising Orchestrator agent | Aug 17, 23:00 | Rejected by the source | SC9-AUTH-A1 SC9-POL-200 | none | Delivery date moved on a line with a goods receipt already posted | The sandbox refused the change because the line was partly received. The route now checks receipt status before attempting. |
| WBA-0005 seq 1604 | WB-ERP-MM-01 Group ERP — Materials and Inventory | MU-038440 | Order Promising Orchestrator agent | Aug 17, 22:00 | Accepted in sandbox | SC9-AUTH-A1 SC9-POL-200 | SBX-0005 | Delivery date moved from 2026-09-02 to 2026-09-09 on 1 line | Accepted. A change document was created against the line. |
| WBA-0006 seq 1605 | WB-ERP-MM-01 Group ERP — Materials and Inventory | MU-038451 | Order Promising Orchestrator agent | Aug 17, 22:00 | Accepted in sandbox | SC9-AUTH-A1 SC9-POL-200 | SBX-0006 | Delivery date moved forward 3 days on 4 lines of one purchase order | Accepted as a single change document covering all four lines. |
| WBA-0038 seq 1637 | WB-MKT-01 Marketing Automation | MU-031200 | Consent Agent agent | Aug 17, 20:00 | Accepted in sandbox | MK5-AUTH-A1 LG9-POL-200 | SBX-0038 | Suppression of 84 contacts whose consent state had lapsed | Accepted. Each suppression record carries the consent state that caused it. |
| WBA-0039 seq 1638 | WB-MKT-01 Marketing Automation | MU-031218 | Consent Agent agent | Aug 17, 20:00 | Accepted in sandbox | MK5-AUTH-A1 LG9-POL-200 | SBX-0039 | Suppression of 19 contacts in one jurisdiction pending re-consent | Accepted. |
| WBA-0043 seq 1642 | WB-PLANNING-01 Supply and Demand Planning | MU-034118 | Supply Planning Orchestrator agent | Aug 17, 17:00 | Rejected by the source | SC2-AUTH-A1 SC2-POL-200 | none | Recommendation committed against a scenario superseded during the run | The sandbox refused it. The same event drove the planning replay. |
| WBA-0042 seq 1641 | WB-PLANNING-01 Supply and Demand Planning | MU-034100 | Supply Planning Orchestrator agent | Aug 17, 17:00 | Accepted in sandbox | SC2-AUTH-A1 SC2-POL-200 | SBX-0042 | Recommendation committed on 24 supply plan lines against a published scenario | Accepted as a single scenario commit record. |
| WBA-0012 seq 1611 | WB-S2P-02 Source-to-Pay Suite | MU-040093 | Supplier Onboarding Orchestrator agent | Aug 17, 13:00 | Refused by policy | PR6-AUTH-A1 GB8-POL-200 | none | Tax identifier corrected on 1 supplier from the drifted structure | Refused for the same reason. Both proposals are open with the steward. |
| WBA-0011 seq 1610 | WB-S2P-02 Source-to-Pay Suite | MU-040088 | Supplier Onboarding Orchestrator agent | Aug 17, 13:00 | Refused by policy | PR6-AUTH-A1 GB8-POL-200 | none | Tax identifier corrected on 1 supplier from the drifted structure | Master data policy reserves supplier identity changes to a named steward. The correction was raised as a proposal instead. |
| WBA-0023 seq 1622 | WB-CRM-02 Customer Relationship Management | MU-036251 | Data Stewardship Agent agent | Aug 17, 07:00 | Refused by policy | RO1-AUTH-A1 GB8-POL-200 | none | Merge of 3 accounts sharing a registration number | Refused. Proposal open. |
| WBA-0022 seq 1621 | WB-CRM-02 Customer Relationship Management | MU-036244 | Data Stewardship Agent agent | Aug 17, 07:00 | Refused by policy | RO1-AUTH-A1 GB8-POL-200 | none | Merge of 2 accounts matched at 0.97 confidence | A merge is not reversible at the source. Raised as a proposal for the steward. |
| WBA-0044 seq 1643 | WB-FPA-01 Planning and Consolidation | MU-032010 | Forecast Orchestrator agent | Aug 17, 05:00 | Accepted in sandbox | FI2-AUTH-A1 FI2-POL-200 | SBX-0044 | Agent forecast published beside the human forecast for 3 cost centers | Accepted as a version record naming the agent as author. |
| WBA-0045 seq 1644 | WB-FPA-01 Planning and Consolidation | MU-032024 | Forecast Orchestrator agent | Aug 17, 05:00 | Refused by policy | FI2-AUTH-A1 FI2-POL-200 | none | Agent forecast published over an approved human forecast | Refused. The route may publish beside a human forecast, never over one. |
| WBA-0004 seq 1603 | WB-ERP-FI-02 Group ERP — Financials | MU-039112 | Controls Orchestrator agent | Aug 17, 03:00 | Blocked, no path | FI5-AUTH-A1 FI5-POL-200 | none | Payment block on 1 vendor line pending a sanctions re-check | No service account exists on the finance instance. The attempt was recorded and stopped at the boundary. |
| WBA-0024 seq 1623 | WB-HCM-01 Core HR and Payroll | MU-033100 | Workforce Cost Agent agent | Aug 16, 09:00 | Blocked, no path | HR4-AUTH-A1 FI10-POL-200 | none | Cost center corrected on 1 position effective 2026-09-01 | The people system is read-only until the works-council pack on write-back is answered. |
| WBA-0025 seq 1624 | WB-HCM-01 Core HR and Payroll | MU-033118 | Workforce Cost Agent agent | Aug 16, 09:00 | Blocked, no path | HR4-AUTH-A1 FI10-POL-200 | none | Cost center corrected on 6 positions in one sub-function | Blocked at the same boundary. Both attempts are on the record so the consultation has evidence of what is waiting. |
| WBA-0034 seq 1633 | WB-CLM-01 Contract Lifecycle Management | MU-037214 | Contract Lifecycle Orchestrator agent | Aug 16, 03:00 | Blocked, no path | LG1-AUTH-A1 LG1-POL-200 | none | Renewal notice corrected on 22 contracts in one portfolio | Blocked for the same reason. The drift has to be closed before this route can be considered again. |
| WBA-0033 seq 1632 | WB-CLM-01 Contract Lifecycle Management | MU-037200 | Contract Lifecycle Orchestrator agent | Aug 16, 03:00 | Blocked, no path | LG1-AUTH-A1 LG1-POL-200 | none | Renewal notice corrected from 3 to 90 on 1 contract | The field drifted on the read side. Nothing writes into a field the contract cannot read reliably. |
| WBA-0037 seq 1636 | WB-BANK-01 Bank Connectivity Gateway | MU-035040 | Payments Orchestrator human-confirmed | Aug 15, 09:00 | Blocked, no path | FI6-AUTH-H1 FI6-POL-200 | none | Payment file of 412 instructions, 8.4m USD | The bank channel is not connected. No network path, no certificate, no security review. The attempt exists to record the distance. |
Actions
What is waiting on a person
A write-back is the only thing on this platform that changes a system of record. Every route carries an authority reference, a policy reference and the change record the receiving system would keep.
Take a designed route to a real instance
Rehearsed in a sandbox and never run anywhere else. There is no service account and no security review.
Fix an attempt the source refused
The sandbox rejected the payload. Each one is a validation the contract did not catch first.
Clear what is blocking a route
The route names its own blocker. None of them are things this platform can resolve on its own.
Settle a route policy has refused
Refused at the policy boundary and left on the register. Each one has a proposal open with a named steward, and the refusal stands until that steward decides.
Operations
What this desk is allowed to start
A surface that only reports is not operable. This is the work this page can set in motion, and the bound it runs into.
Trigger and bound
This desk can declare a route, bind it to a named authority grant and policy item, rehearse an attempt against a sandbox, and record the change record the receiving system returned. It cannot write into a production system of record, grant itself authority, or proceed past a route that policy has refused — a refused route stays on the register as refused rather than disappearing.
Live observability
What the record shows right now
Outcome of all 45 write-back attempts on the register. The four states are exhaustive: accepted by a sandbox, rejected by the receiving system, refused at the policy boundary before anything was sent, or stopped because no path exists. None of them wrote into a production system.
Current distribution
45 attempts
Is policy and strategy coming to fruition
Whether the written intent is holding here
0 records have been written into a system of record across 19 declared routes.
Not holding on the record
The written intent is that an agent may change a system of record only under a named grant, against a named policy item, leaving a change record the receiving system keeps. The register honors that shape: all 19 routes on 14 write-capable systems carry an authority reference and a policy reference, and 13 require a named human confirmation before anything is sent. What has not happened is any of it. 0 routes are live, 13 are designed and rehearsed only, 4 are blocked by something outside this platform and 2 were refused by policy and left on the register so the refusal stays visible. Of 45 attempts, 24 were accepted by a sandbox and 0 reached a production system.
A contract, a validation rule, a freshness commitment and a replay path are real mechanisms and they are what this wave builds. What they are not is a connection. No connector on this estate is attached to a customer instance, so every batch, every replay and every write-back attempt recorded here ran against a modeled extract or a sandbox, and the registry keeps saying modeled.
24 of the 45 attempts carry a change record identifier, and every one of those identifiers is a sandbox reference. A change record that exists only in a sandbox proves the payload was constructed and accepted; it does not prove that the receiving system's change control would accept the same payload, that the identifier format matches production, or that the source's auditors would recognize it.
6 of the 19 routes are designed to run without a person confirming in the moment. Each of those still resolves an authority grant and a policy item before it constructs a payload, but the check is made by this platform against its own records — nothing in the receiving system verifies that the grant is real. Until a customer instance is attached and the receiving system enforces its own authorization, the authority reference on every row is an assertion this platform makes about itself.