Trading platform status

A frozen reference implementation of an autonomous multi-agent startup economy, published for security, legal, market-abuse, custody, and research review by reading source.

Do not operate this repository. There is no supported execution environment, dry-run mode, zero-side-effect command, or supported release. Do not use real money, accounts, credentials, customer data, or provider access.

Formal hold

trading-autonomy/commercial-status.json records status hold and prohibits customer funds, checkout, paid entitlements, and autonomous execution. Re-entry requires legal approval, custody review, market-abuse review, security review, and financial proof. The status file is policy, not a runtime interlock.

What exists

• A readable ecosystem orchestrator for pitch scoring, spawning, market accounting, and lifecycle bookkeeping.
• An agent runtime containing cognition, provider selection, tools, skills, memory, perception, and cost tracking.
• Retained JSON state showing wallets, tokens, pitches, activity, requests, costs, and agent instances.
• A Next.js web surface and coordinator API retained as internal, prohibited interfaces.
• Aspirational economy and autonomous-agent architecture documents, explicitly separated from verified behavior.

What does not exist

• No supported trading product, exchange, brokerage, custody system, or investment service.
• No secure sandbox, fail-closed capability policy, kill switch, reconciliation, or supported recovery path.
• No working top-level entry point on the documented revision: required runtime.pitch imports are absent.
• No proof that retained revenue, token, or market records represent external economic activity.
• No permission to infer a public financial product from the design corpus.

Thesis and reply diagnostics in the retained source

The trading-tools update_thesis tool refuses malformed members with the deserialization cause before writing to its store. Omission preserves membership; an explicit list replaces it, including an empty list. iMessage, Telegram and WhatsApp error replies preserve the agent error chain. Failed delivery records the original error, delivery cause and chat or sender; an absent iMessage client is an explicit refusal. Webhook acceptance is not successful agent execution or delivery. The tests/thesis/update.rs admission regression source covers the actual unconfigured-store state, not persisted database updates or real messaging delivery. None of these source changes qualifies runtime behavior, a graphical surface, or permission to operate.

Supported use

The only supported workflow is source review. Reviewers should read the status contract, capability definitions and executors, credential forwarding, cloud/deployment adapters, and retained state without installing dependencies or setting credentials. Any attempt to construct an isolated research environment owns all isolation, egress, quotas, retention, and credential revocation outside this codebase.