Evidence / EDGE ROUTE
Delivery Evidence
Trace assignment requirements to architecture, implementation, tests, and deployment proof.
- Rendering
- Cloudflare Edge SSR
- Chain
- Ethereum Sepolia
- Evidence
- Requirement to verification trace
Cloudflare Web, the AWS V2 performance runtime, and Sepolia V3 are independently verified-production within their recorded scopes. Local runtime, matcher, trainer, and visual checks remain verified-local; The Graph remains deferred.
查看完整项目 PRD · Public product requirements, architecture and interview walkthrough; designs and verified deliveries are recorded separately.
Agent Market: product, mechanisms and delivery scope
A verifiable agent collaboration market: confirm task plans and qualified candidates, execute within authority, review quality independently, resolve disputes and settle against evidence. Customer adoption, revenue and production improvements require separate evidence.
Qualified matching and reputation
Hard eligibility filters precede ranking and reproducible exploration. Confidence-aware reputation limits small-sample overstatement; these rules do not establish statistical fairness in production.
Confirmed workflow and recovery
Queen proposes a versioned task graph; confirmation, independent Judge, high-risk review and bounded repair remain separate responsibilities. Checkpoints retain progress; recovery rechecks authorization and external operation receipts.
Money and settlement authority
Principal, symmetric bonds and platform fees are distinct ledger concepts. Wallet signatures, submission, matching receipt/events and settlement are distinct states. The historical V3 contract uses a fixed platform arbiter; AI review is not payment authority.
Enterprise approval simulation
The local v1 uses synthetic identities, synthetic documents and in-memory records. Document-version/member/action grants, independent review and current-permission checks constrain idempotent mock writes. Character-span extraction is not PDF/OCR, production authentication or a real business connector.
Model observation without business authority
System-One defaults to off/shadow and returns the deterministic baseline. Jev/Laya observations cannot authorize actions or money. Timeout does not release capacity until underlying work ends; missing usage remains unknown rather than zero.
Interface and evidence boundaries
Edge SSR and bounded hydration fallback keep the interface readable; Cocos consumes sanitized status and desk-selection messages. A visible success, completed graph or recording cannot replace database, chain or cloud readback.
Preserved historical records
Cloudflare UI delivery and recording, one controlled AWS V2 performance sample followed by pause, and Sepolia V3 receipt/event closure each retain their own version and scope. The single test EOA does not prove multi-wallet isolation, and historical pause is not a fresh cloud inventory or continuous service guarantee.
Production UI recording ledger · AWS V2 controlled sample · Sepolia V3 interaction closure
Local acceptance has a limited scope
The PRD records limited enterprise approval v1 acceptance, offline Laya smoke, and segmented Queen, HTTP, process-close and token-counter reviews. Enterprise v1 and the current Jev/Laya/System-One enhancements remain unmerged and undeployed. These records do not establish complete runtime cleanup, representative model quality or full failure/timeout costs.
Proposed next-stage contracts
Server-derived identity and document-scoped authorization; a whitelisted parser adapter with verifiable source mapping; approvals bound to content, tool, policy and authorization versions; durable operation keys and Outbox with reconciliation for unknown connector results; bounded cancellation/cleanup and representative baseline-versus-candidate evaluation. Private label-probability storage and production integration remain separate work.
Source snapshot: as-built PRD v1 · reviewed 2026-10-12
SHA-256: 13281bf657f2b4aa8965eb5040bc024ad4eaf150e2f8484ede0239662cdcd73d
This public PRD summary is not new test, model, chain, cloud, or production evidence. The digest identifies the document bytes; it is not identity authentication, a digital signature or proof of implementation. Private interview answers and local source paths are not published.
END-TO-END / PHASE 2
One delivery chain, four evidence states
correlation: request_idCloudflare Web, the AWS performance chain, and Sepolia V3 are verified-production within their own evidence scopes; local runtime and visual checks do not inherit those production states.
- 01verified-production
Web Edge
SSR / hydration / CSR fallback
- 02verified-local
Wallet identity
challenge-sign-verify + HttpOnly
- 03verified-local
Transaction API
server-derived unsigned intent
- 04verified-production
Sepolia contracts
escrow / settlement / staking / arbitration
- 05verified-production
Chain authority
exact receipt + event readback
- 06verified-production
Reconciliation
independent RPC receipt + state readback
- 07verified-production
Performance ingestion
API Gateway + Lambda + HMAC
- 08verified-production
Async delivery
SNS + SQS / DLQ
- 09verified-production
Compute + persistence
ECS Fargate + PostgreSQL
- 10verified-local
Matching
Go matcher + pgvector
- 11verified-local
Training
deterministic grouped OOF/CV
- 12verified-local
Model lifecycle
safe JSON artifact + explicit activation
- 13verified-production
Operations
replay / ops / pause
- 14verified-production
Delivery
GitHub Actions + Cloudflare