Cymetica Flow Runtime — deterministic, auditable execution runtime with Liquidity Streams surface (aBugSlayer proposal, 44 sections)

Received in the VSB-Corp / Pee Wee-Kasian group on 2026-08-08, as two text documents with the message 'Read this': 13:11 v1.0 29,129 bytes 13:26 v1.1 45,859 bytes ('Evidence & Economic Integrity Revision') Saved by the capture bot at: /app/data/telegram_media/-5138500274_6571_aBugSlayer_e8a14faa5739_1786194704.bin /app/data/telegram_media/-5138500274_6585_aBugSlayer_fa4469b41d86_1786195600.bin (inside the qa-support-bot container) Core recommendation: do NOT build a GraphLinq-style visual workflow IDE first. Instead turn the existing capabilities into one deterministic, auditable 'Flow Runtime' with Liquidity Streams as its user surface — recipes/templates rather than drag-and-drop, a small compiler + runtime, thin adapters to existing services, one immutable Run Artifact per run, and a requested -> normalized -> compiled -> executed integrity chain. Read-only flows first, then backtest, then paper, then controlled live. Explicitly argues NEXUS should not be the execution engine. 44 sections including a data model, delivery phases, acceptance criteria per mode, indicative effort and cost control. Why it deserves a real read rather than a filing: its 'integrity lessons' section is a generalisation of defects THIS project actually shipped — routing intent mistaken for measured settlement; a hash-shaped identifier mistaken for a receipt; an internal/simulated balance mistaken for withdrawable value; recovery settlement using a later price instead of canonical boundary evidence; a manual resume silently creating a new risk baseline; an equipped model mistaken for a contributing one; a historical correction distorting later path-dependent sizing. Its central v1.1 rule — runtime MODE and economic EXECUTION CLASS are different concepts — is the same distinction behind the paper/live conflation class and today's ET-16652, where a cached aggregate was displayed in place of the ledger sum that was the actual truth. NOT actioned: whether to build a new product runtime is a product decision, so nothing has been committed to the sender beyond confirming both versions were received and read. No roadmap promise made.