Repository navigation
docs: a single-page project flowchart - #71
Open
CodexManvik wants to merge 1 commit into
Open
CodexManvik wants to merge 1 commit into
CodexManvik wants to merge 1 commit into
Conversation
The judge's note on the deck was that it covers a lot and takes too long to get through, and asked for a 10-minute pitch. One page that carries the whole product does more for that than any amount of trimming, so this adds a sixth diagram: five steps along a spine, a decision diamond under each, and every exit the system can take. The point the picture makes is that three of the five exits are the system declining to touch production. The geometry gate earned its keep again: the first cut routed the rollback branch straight through the "runbook fits?" diamond, which no amount of looking at the code would have shown. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
The judge's review of the capstone deck was that it covers the topics in detail
but takes too long to get through, and asked for a pitch that fits a 10 minute
window. One page that carries the whole product answers that better than any
amount of trimming, so this adds a sixth diagram.
Five steps along a spine, a decision diamond under each, and every exit the
system can take:
The point the picture makes is that three of the five exits are the system
declining to touch production.
Notes
The geometry gate earned its keep again. The first cut routed the rollback
branch straight through the
runbook fits?diamond:No amount of reading the generator would have shown that. Fixed by stacking the
two
recovered?outcomes and routing the rollback down a gutter to the left ofthe column.
What is in here
scripts/make-diagrams.mjs: adiamond()primitive that registers itsbounding box with the gate, and
projectFlow()docs/diagrams/06-project-flowchart.{dark,light}.svg🤖 Generated with Claude Code