07 / baz trade signal stack prospect
BAZ Trade Signal Stack
A three-part systematic trading toolkit: glither.hft for strategy compilation, Palantir for orchestration and enrichment, and Luna for notebook-grade browser inspection.
compilerorchestrationnotebook widgets
status
active embryo
active embryo lane
Systematic trading toolkit — glither.hft compiler dialect compiles strategies to WASM with Ed25519 audit receipts, Palantir Rust orchestration server enriches tick data, Luna Vite browser notebook for live inspection.
completion
47%
finished scope progress
Completion estimate across public surface, working system parts, and remaining implementation depth.
current value
$122k
derived from current completion
Estimated present studio asset value at the current scope and maturity level.
finished estimate
$260k
pricing signal —
Target studio asset value at the planned finished scope. Revenue status: pre-revenue.
Internal studio value estimates in USD. Current value is derived from completion percentage and is not booked revenue.
What is done
The stack already has a real conceptual split instead of a single overloaded prototype bucket.
- baz.hft is identified as the dialect layer around executable strategy artifacts and audit-friendly monetary planning receipts.
- Palantir is established as the Rust orchestration and enrichment surface rather than leaving stream handling implicit.
- Luna is positioned as the browser notebook and charting layer, giving the stack a concrete operator-facing inspection surface.
What is left
The largest remaining work is compiler/runtime maturity and keeping browser and backend execution in parity.
- Finish dialect semantics around baz.hft and glither.hft so strategies become stable, reviewable, and testable artifacts.
- Extend the WASM bridge so web applications can execute or inspect the same compiled parts the Pharo/runtime side uses.
- Harden live data adapters, signal transport, and notebook widgets so the operator surface becomes more than an architecture sketch.
Commercial frame
This has high eventual value because it joins language, execution, audit receipts, and operator notebook into one traceable lane.
- Current public posture: active embryo and research-heavy stack rather than ready sellable product.
- Best fit: teams that want executable strategy artifacts with auditability, not just disconnected notebooks and charts.
- Finished-value estimate assumes compiler maturity, live stream integration, and a browser/runtime bridge strong enough for daily operator use.
The value here is not just charting or indicators. It is the continuity from strategy language to execution receipt to operator notebook, with monetary planning visible the whole way through.