Rules
The ORB process is explicit enough to version, test, and compare instead of living only in memory.
Founder proving ground
Mason ORB is where Signal Bridge gets tested in the real workflow: define the rules, watch the session, route chart events, capture the trade or pass, review the decision, and keep the exact strategy version attached.
Why this page exists
Signal Bridge is not “Mason’s indicator site.” Mason ORB is the first complete example used to prove that the product can keep a real strategy, chart state, journal, alerts, and research history connected without rewriting the past.
The ORB process is explicit enough to version, test, and compare instead of living only in memory.
Wins, losses, passes, screenshots, forward observations, and historical tests stay separated by source and version.
The same architecture can support another member’s strategy without mixing their rules or records into Mason’s.
The live loop
This is the part worth copying: the operating structure. The specific ORB rules remain Mason’s own strategy.
ORB rules, session, setup, trigger, invalidation, target, and pass conditions.
Chart-side levels and lifecycle state tied to a known version.
Trade or no-trade evidence attached to the session and strategy identity.
Compare repeated evidence before deciding whether the next version deserves to exist.
Go deeper only if you want to
Historical backtests, source material, strategy lineage, open questions, and detailed decision logic still exist. They just belong in the proof layer instead of making every visitor read the entire development history.
Use the flagship pages to inspect the actual process and the evidence behind the product development.
Mason ORB →The real product