Repository navigation
D-003: this repository is the platform - #19
Merged
Merged
Conversation
The program's page repeated the repositories it pointed at and its plan went stale here while it moved there. What this repository held that nothing else did was about the platform, so the repository becomes the platform: an AWS estate as code with its choices explained, the Phase 3 plan already in place, monitoring and recovery beside it. The map of the program is the account's page; the pipelines overview lives in build-doctrine's enforcement record and the README links it there; the figures check, which kept another repository's counts honest on a page that no longer states them, goes. Co-authored-by: Claude <noreply@anthropic.com>
tltaylor1
approved these changes
Sep 30, 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.
The repository becomes what its name and banner say: the platform the applications run on, an AWS estate as code with every security choice explained beside it. The README says what it will hold, the two stacks, the phases from 3 to 7, the documents kept here and why, and the posture. D-003 records the decision and what was rejected. The pipelines overview now lives in build-doctrine's enforcement record (its pull request 47), and the README links it there; the figures check goes, because the page no longer states another repository's counts.