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 public website can show the service workflow today; production service-request and credit-usage Worker routes remain non-live until Cloudflare auth, Worker deploy permission, remote migrations, and pending-route smoke checks pass.

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

Local operator workflow ready; production routes pending deploy gates.

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 requestOperator records the requested service scope, requested credit hold, service type, and review status in the service request queue.
4. Human reviewOperator reviews scope, risk boundaries, user evidence, and whether the request can be answered without trading advice or custody.
5. DeliveryApproved work is delivered as a report, checklist, replay, backtest summary, risk warning, ENTRY_READY review, sizing note, or education session.
6. Credit usage recordCredit usage is recorded only after reviewed delivery or accepted delivery, with before/after credit balance and operator notes.

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, requested credit hold, status, and non-sensitive scope.
Credit usagecreditUsageId, creditLedgerId, serviceId, 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.
Worker source and D1 migrationsPrepared; dry-run and D1 visibility passed on 2026-06-18.
Production Worker routesNon-live until Cloudflare auth, Worker deploy permission, remote migration, deploy, and smoke checks pass.
Deploy handoffWorker Routes Handoff publishes the exact gate order for service-request and credit-usage route release.
Public claimSay the playbook is published and local operator recording is ready; do not say production self-service service delivery is live.

Copy-Ready Public Summary

GCA Service Delivery Playbook is now published. It explains how GCA AI Quant Access requests move through account intake, read-only wallet checks, operator review, report delivery, and credit usage records. The workflow is no-custody and operator-reviewed; production service-request and credit-usage Worker routes remain non-live until Cloudflare deploy gates pass.

Service Delivery References

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