The data flow
1) Brain (append-only)
The brain is the source of truth. Instead of mutating state directly, b1e55ed records events (signals, updates, confirmations, invalidations) and derives state from them. Why it matters:- auditability (what changed, when, and why)
- reproducibility (rebuild views from events)
- attribution (who contributed what)
2) Producers
A producer is anything that emits signals:- a human operator at the CLI
- an agent calling the API
- a connector / scraper / rules engine
3) Synthesis
Synthesis is the layer that turns raw signals into something you can act on:- rollups by symbol / timeframe
- conflict detection
- aggregation by contributor reputation / karma
4) Conviction
Conviction is the system’s representation of how strongly we believe something right now. It can be:- set directly by a producer
- adjusted by synthesis over time
- decayed or overridden by contradictory evidence
5) Action
Actions are what you do with the output:- notifications / alerts
- suggested positions
- execution adapters (manual or automated)
b1e55ed is intentionally modular here: you can keep it “analysis-only” or plug in execution as your risk tolerance allows.
The Flywheel
The system compounds. This is not a metaphor.What It’s Built For
Build an accurate picture of edge. Not generic backtests — a live, continuously updated model of what signals have actually produced returns in real conditions. Eliminate noise at the source. Producers who don’t perform lose influence automatically. No manual tuning required after setup. Make attribution permanent. Every signal is tied to a producer. Every outcome is tied to the signals that drove it. The hash chain means these links can’t be rewritten. Operate without dependency. No cloud services required. No vendor lock-in. The system runs on your hardware, your keys generate your identity, and the data lives in your database. Regime awareness. A signal that works in a trending bull market is often noise in choppy consolidation. The Brain conditions its synthesis on the current regime. Survivability. The kill switch is unconditional. If drawdown exceeds configured thresholds, trading stops — regardless of what signals are saying.Where to go deeper
- Getting Started — install and first run
- Architecture — technical design and component overview
- Learning Loop — how compound scoring works in detail
- Oracle — public provenance verification
- API Overview — REST surface
- Producer Overview — configuring signal sources