OUTCOME · Planned · Inspect
What changes
None today: this route is not executable. Its intended behavior is: read-only projection; it grants no mutation, settlement, traffic, or authority change.
Programmable barriers
/api/v2/barriers/{barrier_uuid}This page describes intended capability and integration boundaries so people and agents can prepare safely. Do not send this request or register it as an executable tool. Wait until the capability registry marks it implemented-contract, then re-fetch the deployed OpenAPI document and build the request from that machine contract.
Purpose and usage
Planned capability: return one barrier definition, observations, state transitions, and evidence.
When to use it
Do not call or register this operation as an executable agent tool yet. Use this page to plan the future barrier workflow; enable it only after the status becomes implemented-contract and the exact operation appears in deployed OpenAPI.
OUTCOME · Planned · Inspect
None today: this route is not executable. Its intended behavior is: read-only projection; it grants no mutation, settlement, traffic, or authority change.
WHY IT MATTERS
ISOLATION + AUTHORITY
Issuer, owner, product definition, underlying, price source, observation schedule, validation, activation, position, trigger, valuation, cancellation, closeout, wallet, and settlement remain distinct. No barrier record grants order, matching, publisher, custody, or trading authority, and current trading controls remain frozen. This planning record grants no runtime authority, and only deployed OpenAPI can define an executable public contract.
BEFORE YOU CALL
WHAT TO DO NEXT
AGENT GUIDANCE
This is a planned, non-executable contract. Do not send requests or register it as an executable agent tool.
Request and response
Examples describe the reviewed planning contract and remain non-executable until promoted into OpenAPI.
PARAMETERS
AuthorizationheaderRequiredBearer tokenCredential containing barriers:read authority.EXAMPLEBearer hc_live_…
barrier_uuidpathRequiredidentifierCanonical barrier uuid.EXAMPLEbarrier-uuid-01
RESPONSES
{
"result": "See the operation's authoritative OpenAPI response schema."
}{
"code": "request_failed",
"message": "Bearer credential is missing, expired, or invalid."
}request_failed{
"code": "request_failed",
"message": "The principal lacks the required scope, role, tenant, or step-up authority."
}request_failed{
"code": "request_failed",
"message": "Path, query, or body validation failed."
}request_failed{
"code": "request_failed",
"message": "The authoritative service or read model is unavailable."
}request_failedOPERATIONAL NOTES
This planned contract now defines its public parameters, authorization boundary, replay behavior, responses, and authoritative owner. It remains non-executable until its owner adapter and conformance tests are promoted into the Rust gateway.
Return to the V2 directory