Event Release Integrity Halt
Nano identifier: EventReleaseIntegrityHalt
Release integrity circuit breaker. RELEASE_CONFLICT = 1 when the host's release plane detects any integrity failure: conflicting values between sources, a CONFLICTED or LATE MacroReleasePacket status, calendar/source disagreement about the schedule, or a failed payload hash check. The host folds every integrity failure into this single flag so the halt cannot miss a new failure mode. REGIME: any armed macro event window. Control only - emits PAUSE, never promoted, never counted as a setup. The host's fail-closed gates enforce the same rule directly; this published rule is the auditable explanation. CONDITIONS: none beyond the conflict flag. INVALIDATION: none - releases only if the host downgrades the conflict, which in v1 it does not do during the event window. SHAPE: 1s, so a conflicted release halts proposals before the first 5s qualify tick can act on poisoned numbers. NOT event_liquidity_halt: that halts on market conditions; this halts on data trust. A perfectly liquid tape with a conflicted release must still halt every release-aware branch. CALIBRATED ON: not calibrated - the flag is binary by contract and travels unchanged across all event types and instruments.
Nano source
This is the strategy exactly as published. Nano has no import, no file access and no network primitive, so reading or copying this source cannot execute anything.
// Release integrity circuit breaker. RELEASE_CONFLICT = 1 when the host's// release plane detects any integrity failure: conflicting values between// sources, a CONFLICTED or LATE MacroReleasePacket status, calendar/source// disagreement about the schedule, or a failed payload hash check. The host// folds every integrity failure into this single flag so the halt cannot// miss a new failure mode.// REGIME: any armed macro event window. Control only - emits PAUSE, never// promoted, never counted as a setup. The host's fail-closed gates enforce// the same rule directly; this published rule is the auditable explanation.// CONDITIONS: none beyond the conflict flag.// INVALIDATION: none - releases only if the host downgrades the conflict,// which in v1 it does not do during the event window.// SHAPE: 1s, so a conflicted release halts proposals before the first 5s// qualify tick can act on poisoned numbers.// NOT event_liquidity_halt: that halts on market conditions; this halts on// data trust. A perfectly liquid tape with a conflicted release must still// halt every release-aware branch.// CALIBRATED ON: not calibrated - the flag is binary by contract and travels// unchanged across all event types and instruments.strategy EventReleaseIntegrityHalt { every 1s { if RELEASE_CONFLICT > 0.5 { pause() } }}Compiled IR
Nano compiles to a pinned intermediate representation. This is the artifact a runtime would actually load — inspectable before anything runs, and byte-diffable against the published source.
{ "type": "Strategy", "nanoIrVersion": "0.1.0", "name": "EventReleaseIntegrityHalt", "effects": [ "intent.emit", "log.append" ], "nodes": [ { "type": "Schedule", "interval": "1s" }, { "type": "Condition", "signal": "RELEASE_CONFLICT", "operator": ">", "value": 0.5 }, { "type": "Intent", "action": "PAUSE" } ]}What it proposes
On a 1 second cadence, when RELEASE_CONFLICT > 0.5, it emits pause intent.
An intent is a proposal, not an order. A separate risk gate — outside the language, and outside this library — decides whether anything is acted on.
Risk disclosure
This strategy is published as an educational, verified example. It compiles to the IR shown above and replays deterministically. It has not been backtested against market data, forward-tested, paper-traded, or traded live by Aether, and no performance statistics are published because none have been produced.
Nothing on this page is financial advice, an offer, or a recommendation to trade. Trading carries risk of loss. Any decision to run logic derived from this strategy — and the risk gate that governs it — is entirely your own responsibility.