Repository navigation
docs(architecture): ntfy as it stands, deployed and cut over (#136) - #741
Merged
Merged
Conversation
The trinity row still said ntfy was "not yet deployed and not yet cut over". The changelog's 2026-09-29 entry records the cutover run across both hosts with both phones, and sensitive-ntfy has been running and healthy since that morning. The row now says so, links the cutover section, and keeps the ntfy.sh copy for urgent and security. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
What changed
In
docs/architecture.md,trinity's row still said ntfy was "not yet deployed and not yet cut over". It now says ntfy was deployed and cut over 2026-09-29, links the cutover section ofverify-the-alert-path.md, and keeps the ntfy.sh copy forurgentandsecurity.Why
This fix was pushed to #737 after that PR had already merged, so it never reached
main. The changelog's 2026-09-29 entry records the cutover on both hosts with both phones, andsensitive-ntfyhas been running and healthy since that morning.Blast radius
Docs only, one line.
secrets/*.sops.yamlVerification
make validatepasses🤖 Generated with Claude Code