Repository navigation
Conversation
The Layer 3 box and the mermaid node labelled PiranhaDB LIVE and named api.piranha.bawbel.io, while the piranhadb section of the same file says the host does not resolve. Both now say offline, and the box points at api.aveproject.org for the corpus, matching that section. The box width is unchanged. The data-flow arrows are not rewritten here. Closes #80 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: chaksaray <chaksaray@gmail.com>
This branch has not been deployed
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.
Closes #80
What and why
ARCHITECTURE.md labelled PiranhaDB LIVE and named api.piranha.bawbel.io in two places (the Layer 3 box and the mermaid node), while the "piranhadb (Layer 3, offline)" section of the same file says the host does not resolve. The diagram now agrees with that section. Applied the ecosystem classifier (ECOSYSTEM-RUNBOOK STEP 3, D3 approved).
[LIVE]becomes[OFFLINE], the host line becomes "hosted API offline (host does not resolve)", and the third line points at api.aveproject.org for the corpus. Box width unchanged: 76 characters on all five linesPiranhaDB<br/>OFFLINE · host does not resolveGoverning spec
DESIGN.md section(s): none. ARCHITECTURE.md only; no behavior change.
Not in this PR: DESIGN.md:838 names the retired AVE host. PR #76 rewrites that section, and DESIGN.md changes merge alone. The data-flow arrows that route through the PiranhaDB node are not rewritten here.
Output contract
Verification
The one remaining match is the sentence in the offline section that says the host does not resolve.
Trial merges (git merge, no conflicts): with #78 (docs/77-bawbel-mcp-facts) and with #76 (docs/74-design-ave-1-1-0).
Found while editing, not changed here: the same diagram says "schema 1.2 · 51 records · LIVE" for AVE (ARCHITECTURE.md:63), but AVE publishes schema 1.1.0 and 87 records. That is GATE-4 territory (#71, with #75).
Checklist
git commit -s)tests/replay/if this blocks an attack class (not applicable)🤖 Generated with Claude Code