Role-scoped access
A participant or authorized reviewer sees the context permitted for its role.
TRUST & SECURITY
Keep authority where it belongs.
Institutions keep their policies, approvals, systems and execution. StratX is designed to coordinate scoped decisions, make missing determinations visible and preserve the evidence for authorized review.
PROTOTYPE CONTROLS AND INTENDED INSTITUTIONAL BOUNDARIES
DECISIONBUY 250,000 XYZ
INT-0042 v1proposed in Asset Manager OMS
- Asset ManagerOrder, mandate and selectionREADY
- Broker AMarket access and acceptancePERMISSIBLE
- Broker BMarket access and acceptanceBLOCKED
- TreasuryFunding availabilityWAITING ON FUNDING ASSERTION
- CustodianCustody and instruction supportSUPPORTED
- ClearingClearing eligibilityELIGIBLE
- Available paths
- 0none cleared yet
- Waiting paths
- 1on Treasury
- Blocked paths
- 1by Broker B
- Decision evidence
- 14records
CLEAR RESPONSIBILITY
Shared visibility does not transfer control.
StratX
Receives scoped inputs, evaluates, coordinates, explains and records the result.
Each institution
Owns its rules and data, decides, authorizes, executes and settles in its own systems.
THE TRUST MODEL
Controls visible at the decision.
Fail-closed behavior
A missing or unknown required response never becomes permission.
Consistent decision context
Versioned inputs and rules make the basis of each recorded result inspectable.
No custody or execution
StratX does not hold assets or private keys, initiate transactions, or act for an institution.
EVIDENCE & OVERSIGHT
Inspect without gaining authority to act.
The illustrative role selector demonstrates scoped visibility and a read-only reviewer view. Production regulator access is not established.
DECISIONBUY 250,000 XYZ
REFERENCEINT-0042 v1
EVIDENCE14 records · append-only
| Time | Participant | Determination | Policy / version | Reason | Evidence |
|---|---|---|---|---|---|
| Asset Manager OMS | Intent normalizedREADY | SYN-INTENT-SCHEMA · v1 | Scoped order context from OMS-88213 normalized into INT-0042 v1. | RECORDEDR-01 · R-023f3e…80aa | |
| Broker A | Broker A permissiblePERMISSIBLE | SYN-BRKA-ACCESS · v3 | Instrument and size are within Broker A’s access policy. | RECORDEDR-03 · R-043256…4350 | |
| Broker B | Broker B blockedBLOCKED | SYN-BRKB-ELIG · v2 | Internal eligibility restriction applies to this order. | RECORDEDR-05 · R-068949…14b6 | |
| Treasury | Treasury funding confirmedREADY | SYN-TRSY-FUND · v1 | Funding availability asserted for the settlement date. | RECORDEDR-07 · R-08ffa1…2801 | |
| Custodian | Custodian supportedPERMISSIBLE | SYN-CUST-ACCEPT · v2 | Custody instructions for this instrument are supported. | RECORDEDR-09 · R-10109f…a4ef | |
| Clearing | Clearing eligiblePERMISSIBLE | SYN-CLR-ELIG · v1 | Instrument is eligible for the relevant clearing route. | RECORDEDR-11 · R-12d8eb…d328 | |
| StratX coordinationcoordination output, not an authority | Route set producedPERMISSIBLE | SYN-FEAS-GATES · v1 | 1 path permissible, 1 excluded. Hand-back to the institution; StratX does not select. | RECORDEDR-13 · R-140cb1…d24d |
AS OF 09:31:21Path 01 PERMISSIBLEPath 02 BLOCKED
THE NEXT CONVERSATION
Evaluate the boundary on one workflow.
Name the participants, approvals and evidence that matter. The prototype can demonstrate the coordination model without implying a live institutional deployment.