PRODUCT EVIDENCE · REVISION 2026-08-09

Claims with limits—not borrowed credibility.

This register separates verified product behavior from launch work that remains incomplete. It is operational evidence, not a security certification, regulatory approval, investment-performance record or legal opinion.

Public pre-launch previewProduct information is public; applications and payments remain closed.

Area and verified claimEvidence methodImportant limit

Commercial website

English-first product, pricing, use-case, trust and policy pages are available in a public pre-launch preview.

Production build plus server-rendered route checks

Public availability is not evidence of customer adoption, paid access or commercial demand.

Inquiry boundary

The application form and its write endpoint stay closed when any required entity, scope, contact or secure-relay gate is missing.

Fail-closed configuration and route regression cases

No real commercial inquiry has been accepted in preview mode.

Pilot privacy

Detailed Pilot cases remain in the tester's browser by default; eligible feedback is separately redacted and voluntary.

Rendered-interface, schema allowlist and rejection tests

A tester can still disclose private information outside the approved workflow; training and support boundaries remain necessary.

AI safety boundary

Pilot AI help is independently gated, receives bounded workflow context and refuses likely secrets or individualized trade instructions before a provider call.

Multilingual safety corpus and provider-adapter regression cases

These controls reduce risk; they do not certify every possible model response or replace human review.

Payment activation

A browser return from checkout cannot activate access; a verified, matching payment event and completed onboarding acknowledgements are required.

Signed-event rehearsal and customer-account regression cases

The production payment provider is not configured and no real customer payment has been processed.

Production execution

Production order execution is excluded from the initial paid product and remains disabled in the audited launch configuration.

Product-scope review, runtime gate evidence and public-surface checks

Internal testnet and gated research components exist; they are not a customer execution service.

NOT YET PROVEN

These items remain launch gates.

Until the relevant evidence exists, Project Anchor will not describe these items as complete or use them to open a dependent feature.

01Verified US contracting entity and final operator disclosures
02Counsel-approved initial service regions and commercial product scope
03Live public-inquiry response-time and staffed brand-reply evidence
04Payment-provider sandbox approval followed by a controlled live first payment
05Customer adoption, retention or independently substantiated outcome evidence

Evidence expires

Runtime, provider and policy evidence must be refreshed after a material change.

Tests have scope

A passing check proves only the behavior it actually covers.

Absence is not approval

No finding is treated as a regulator, bank, exchange or payment-provider endorsement.

PRODUCT BOUNDARY

Understand the controls behind these claims.

Open Trust Center View use cases