Operator-Reviewed Service Delivery

GCA Service Delivery Playbook

This playbook explains how GCA AI Quant Access services should move from account intake to manual review, report delivery, and credit usage records without custody, wallet signatures, exchange API secrets, or automatic trading access. It is not automated trading and not a self-service trading product.

The controlled account UI accepts device-key protected catalog requests and returns a redacted account-scoped history. Submission uses server-defined service units and does not reserve or deduct credits. Append-only manual review, approved delivery recording, and at-most-once credit settlement are now live.

Access Portal Credits Catalog Review Queue Operations Runbook Worker Routes Handoff Liquidation Replay 001
Playbook ID service-delivery-playbook-v1

Published operator-reviewed delivery workflow.

Status Public playbook published

Account request, append-only review, delivery, and usage-ledger routes are live with separate access controls.

Delivery Model Manual review first

No self-service deduction and no automatic member benefit transfer.

Safety Boundary No custody

No private keys, seed phrases, signatures, withdrawal rights, or exchange API secrets.

Delivery Flow

1. Account intakeUser registers through the official account path and submits one Base wallet for read-only GCA balance review.
2. Eligibility checkThe backend or operator verifies the wallet with read-only ERC-20 balanceOf data; no signature or transaction is required.
3. Service requestAn authenticated account submits a catalog service and non-sensitive scope. The Worker applies the server catalog unit, enforces idempotency and a daily limit, and queues manual review without reserving or deducting credits.
4. Optional queued cancellationBefore any manual review, the matching device-key account may permanently cancel its own queued request. Retries are idempotent; no credits, wallet, token, member, or audit history are changed.
5. Human reviewThe operator appends approved, needs-more-information, or rejected. A more-information decision requires a non-sensitive public prompt; private operator notes remain hidden.
6. Optional account follow-upThe matched device-key account may append a bounded response after a more-information review. It returns the request to manual review; public history shows only prompt, time, and count.
7. DeliveryApproved work is delivered manually, then the operator confirms completion with a non-sensitive delivery reference. No wallet action or trading permission is created.
8. Credit settlementThe Worker uses the server catalog unit and atomically writes one linked usage record, ledger deduction, delivered review, and request status. Replays cannot deduct twice.

Risk Reports

Liquidation Replay, risk warning review, and position-size review focus on what happened, what invalidated the setup, and what risk rule should be used next.

Research Tools

Backtest Lab, ENTRY_READY Review, and China Narrative Radar are research workflows. They do not create an order, guarantee an outcome, or bypass risk controls.

Member Support

GCA Member accounts can receive priority queue handling after eligibility review, but member status does not create automatic transfers or trading permission.

What Gets Recorded

Service requestserviceRequestId, serviceId, server catalog unit, lifecycle status, and non-sensitive scope.
Service reviewAppend-only decision, reason code, review time, delivery reference, and linked settlement. Account history omits reviewer identity and operator notes.
Service follow-upAppend-only account response for operator review; public history exposes only the member prompt, follow-up time, and count.
Credit usageOne linked creditUsageId per service request, credits used, before/after remaining credits, and delivery status.
Review evidencePublic wallet address, public transaction hash when relevant, review status, and operator decision category.

What Never Happens Here

  • No private key, seed phrase, wallet signature, custody, withdrawal permission, or exchange API secret collection.
  • No production trading connection, no automatic order placement, and no automatic trading access.
  • No self-service credit deduction before operator review.
  • No cash, income, reimbursement, price target, or market outcome promise.

Route Status

Local operator backendReady for service_requests and credit_usage ledger records.
Account request createPOST /gca/account-service-requests is device-key protected, account-scoped, rate-limited, and idempotent.
Account request historyPOST /gca/account-service-requests/status returns at most 25 redacted account records.
Account follow-upPOST /gca/account-service-requests/follow-ups is device-key protected, more-information only, bounded, and idempotent.
Account request cancellationPOST /gca/account-service-requests/cancellations is account-scoped, limited to queued requests before review, permanent, and idempotent.
Service review and deliveryGET/POST /gca/service-request-reviews is live and token-protected with gca_service_request_review_v1.
Worker source and D1 migrations0014_service_request_cancellations.sql and 0015_service_request_followups.sql, the Worker deploy, and latest public/admin read-only smoke passed on 2026-08-10 UTC.
Public route checkService queue, review, follow-up, and credit routes return HTTP 401 to anonymous reads and are token-protected.
Production Worker routesLive and token-protected after Cloudflare auth, remote migration, deploy, and public/admin smoke checks passed.
Deploy handoffWorker Routes Handoff publishes the exact gate order for service-request and credit-usage route release.
Public claimSay manual reviewed delivery and one-time credit settlement are live; do not describe delivery as automatic or trading execution.

Copy-Ready Public Summary

GCA Service Delivery Playbook is live. Authenticated accounts can submit catalog requests, answer a public more-information prompt, cancel their own queued request before review, and read redacted lifecycle history. Manual delivery requires prior approval, and one service request can settle its server-catalog credit unit at most once. No route connects an exchange or creates trading permission.

Service Delivery References

Access Portal Credits Catalog Review Queue Operations Runbook Access API Status Worker Routes Handoff Release Gates