Privacy
Confirm the boundary
The user is shown what may be preserved, what remains private, and what should never be submitted through the selected route.
Golden Gate
The governed threshold between intent and action.
Golden Gate is the access-control layer of Golden Bridge. It checks privacy, wallet state, route availability, provider readiness, and stop conditions before a Golden Query is allowed to proceed.
The purpose is simple: no hidden route, no accidental spending, and no claim that an unavailable capability is live. A user should be able to see what is open, what it costs, what will be preserved, and where the work will travel before approving the run.
What the gate examines
Wallet
Approve cost before work
The estimated Golden Credit cost is shown before the run. A route should not begin without enough available balance and explicit approval.
Route
Use only available capability
Provider, policy, safety, and operating checks determine whether a route is available. Parked or unavailable routes stay unavailable.
Stop valves
Close an unsafe path
A route can be stopped when privacy, abuse, payment, provider, reliability, or safety conditions fall outside the allowed gate.
Golden Gate sequence
Price, approve, route, preserve.
1. PriceEstimate the Golden Credit cost and show the route before any paid work begins.
2. ApproveConfirm the privacy boundary, wallet state, and human authorization to proceed.
3. RouteSend the task only through the capability and provider path that has passed the required gates.
4. PreserveKeep the resulting answer, receipt, cost, and route context inside the correct private or public-safe record boundary.
Fair-wallet discipline
Golden Gate follows a hold, settle, and release pattern where the live route supports it. The approved amount may be held before work, completed cost is settled after delivery, and unused or failed-route credits are released when the applicable release rule is satisfied.
This is a wallet-safety design rule, not a promise that every payment, refund, provider, or settlement route is available at all times.
What each gate protects
Customer controlThe user sees the route, estimated cost, and preservation boundary before authorizing work.
Economic controlProvider readiness, spend controls, settlement rules, and failure release help prevent invisible cost leakage.
Operational controlUnavailable routes remain closed instead of being presented as functioning capability.
Evidence controlRecords preserve custody and sequence without pretending that preservation alone proves every claim inside an answer.
Public and private boundaries
Public ledger records may expose public-safe references, status, scope, and custody information. They do not expose private prompts, private answers, wallet identifiers, payment details, uploaded files, provider credentials, or admin notes.
Golden Gate controls access and routing. It does not prove that every answer is factually true, and agreement among AI systems does not replace evidence, review, or human responsibility.