feat: hardcode dev-time TX kill-switch URL + transparent docs - #129
Merged
Conversation
The centralised kill-switch URL is now a constant pointing at the project author's published JSON file. Cadence, staleness window, and fail-open behaviour are constants too. Operators cannot disable the polling, repoint it, or relax the timings - that's the whole point of a development-phase safety net. - TxKillSwitchUrl, TxKillSwitchPollSeconds, TxKillSwitchFailOpen, TxKillSwitchStaleSeconds removed from SystemOptions and from the /Config surface entirely. - TxKillSwitchPoller carries them as public consts so a code reviewer can see them at a glance, and a pin test fails on accidental edit. - Reason text from the JSON is now prefixed "dev-time kill-switch:" in the dashboard banner so operators always know why TX is gated. New docs/dev-time-tx-kill-switch.md spells out, transparently: - the URL being polled and the wire shape; - why the mechanism exists (alpha software on shared bandwidth); - what the operator cannot do (disable / repoint / configure); - failure modes (fail-open at boot, fail-open after staleness); - when it goes away (before 1.0, deleted not configurable); - what the network sees (one GET/min, no operator-identifying headers, no body). Linked from getting-started.md "Before you put it on the air" and nav under Operate / Audit log. Tests: 637/637 (dropped 4 tests for the removed disabled-URL and fail-closed cases that no longer apply; added a pin test for the hardcoded constants). Manual smoke confirmed the daemon polls the real OARC URL and parses the live "normal operations" response.
This was referenced May 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Strips the configurability from the centralised kill-switch added in #128 and adds operator-facing documentation explaining the mechanism honestly.
The URL, poll cadence (60s), staleness window (10 min), and fail-open behaviour are now constants on `TxKillSwitchPoller`. Operators cannot disable the polling, repoint it, or relax the timings. That is the point: the URL is a development-phase safety net controlled by the project author so a release that ships a regression flooding the air can be gagged within a minute.
`SystemOptions` no longer exposes the kill-switch fields at all - they're gone from `/Config`, gone from the systemoptions table.
Docs
New page `docs/dev-time-tx-kill-switch.md` covers:
Linked from `getting-started.md` ("Before you put it on the air" section) and added to the mkdocs nav under Operate / Audit log.
Test plan
🤖 Generated with Claude Code