Architecture
AXIS system architecture: AXIS vs engine, plugin registry, topologies, ADRs, and state namespaces.
This page
Architecture
AXIS architecture is the discipline of separable axes—price history, live time, calculation, and library storage—coordinated by a Solid AXIS UI that never owns a closed interpreter.
Abstract
| Layer | Responsibility |
|---|---|
| AXIS | UI, store, plugin orchestration, chart apply |
| Plugin contracts | source | stream | engine | storage | dataset (+ reserved component) |
| Engines | PYNE evaluation (browser Pyodide or remote /run) |
| On-chain plane | Parallel non-OHLCV datasets (TVL, DEX, events) via Worker allowlist proxy — ADR-015 |
| Optional edge | Cloudflare Pages + Worker + DO/KV/D1/R2 |
| Optional desk API | Flask Pro API |
Invariant: AXIS ≠ engine. Evaluation always crosses an engine plugin boundary.
Track map
| Page | Contents |
|---|---|
| Overview | End-to-end data/control flow |
| ADRs | ADR-001 … ADR-015 |
| Topologies | Dev, static, edge deploy shapes |
| State namespaces | Keys, migration, hash, IDB |
| Drawings and plot parity | User tools vs Pine plots/drawings vs PYNE export |
Conceptual model
Rendering…
Formal namespaces
Contract namespace: pynescript.axis.plugins.v1
App state key: pynescript.axis.v1
App state prefix: pynescript.axis.*
Pages project id: axis
Pages URL: https://axis.hoox.sh
Worker script id: worker-axis
Worker URL: https://worker.axis.hoox.sh
Health service id: worker-axis
Related tracks
- End User — operator workflows
- UI — UI subsystem design
- Plugins — contracts & catalogs
- Worker — edge data plane
- DevOps — build & CORS
- PYNE runtime — language evaluation
See also
- Root
README.md— package-level map LEGACY.md— pre-Solid shell boundary- AXIS CLI — operator install / deploy