Phylons Liquidity Orquestration

This paper reconstructs the coordination and execution architecture of JUBAP/Phylons from the 2018 design corpus and the supplied xbot source snapshot. The system did not treat a signal as an executable order. It separated contextual detection, local intent formation, shared-resource authorization, exchange commitment, and realized feedback. The code now verifies a substantial substrate beneath that design: user–exchange credentials, books and currencies, balance snapshots, resource allocations, capital instances, resource-utilization statistics, executable transactions, market-operation lifecycle records, request/response audit logs, an event-driven feed–strategy–broker loop, exchange-neutral order submission through CCXT, order-completion polling, and stop-loss/profit closure through an opposite order. The complete tf15→tf5→tf1 book-supervisor logic, HQ/LQ classification, cross-book netting, sell-first priority, proportional proration, A/B/C/D sale taxonomy, and rich partial-fill ledger remain design-grounded where their full implementation is not present in the supplied snapshot. The contribution is therefore not a claim of autonomous multi-agent trading or investment performance. It is a code-grounded account of an explicit coordination contract: detectors propose; local supervisors size; shared-liquidity governance authorizes; exchange adapters commit; operation records reconcile; and feedback changes the next cycle. This contract is interpretable, testable, and portable to other domains in which many local actors compete for scarce shared resources.

Keywords: multi-agent coordination; expert systems; liquidity orchestration; resource governance; exchange broker; event-driven execution; auditability; replay evaluation

JUBAP separated epistemic confidence from economic authority. The supplied code verifies the resource and execution substrate; the historical design specifies the richer multi-book coordination policy that can now be replayed as an explicit, playable algorithm.

Partial fills, reason-coded A/B/C/D inventory attribution, full HQ/LQ arbitration and tf15→tf5→tf1 quantity synchronization are retained as design-grounded mechanisms, not silently promoted to code-verified behavior.