The Rules That Keep the System Alive.
15 principles across building, trading, and operating an AI OS — learned from failures, not textbooks.
Every pipeline fails without taking down the others. Build for containment first, performance second.
No monoliths. Every pipeline decomposes into three clean stages. Each stage has its own timeout, failure mode, and blast radius.
Always branch → PR → CI → merge. This is non-negotiable. The one time you bypass it is the time it costs you.
Forward-pushing is how you lose a week. Re-enter plan mode, reassess assumptions, propose a new approach before continuing.
Clean memory files compound over time. Dirty ones corrupt everything downstream. Treat memory curation as maintenance work, not optional cleanup.
Every system assumes Knox is asleep when it breaks. Self-healing, alerting, and graceful degradation are not nice-to-haves — they are the spec.
No score, no trade. Intuition is an input to the framework, not a bypass for it. If the setup doesn't score, it doesn't execute.
Volume confirms what structure predicts. A high-conviction pattern with volume divergence is a dead setup. Volume spikes validate — they do not lead.
Risk Context is the veto. High conviction on a bad macro setup is still a bad trade. The qualitative gate exists for a reason — use it.
The lesson is the asset. Every trade that closes — win or lose — gets a factor-level retro. The compounding value is in the feedback loop, not the outcome.
BULLISH/BEARISH are starting conditions, not guarantees. The label defines the analytical direction. The score defines conviction. Never conflate them.
Soul cannot go down. It is the nervous system of the entire ecosystem. Every other system assumes Soul is running. It gets the same uptime priority as power.
Read them all. Dismissed alerts are dismissed signals. The system fires alerts because something needs attention — not because it wants to.
Design for it. Every pipeline should produce something of value with zero human input. If a system only runs when Knox intervenes, it isn't automated — it's assisted.
The leverage comes from system design, not human attention. Each app should operate independently. Knox directs strategy — Soul and Claude Code handle execution.
These principles are not aspirational. They are operational constraints extracted from real incidents, failed deployments, and trades that went wrong. Each one exists because something broke.