Repository navigation
docs: correct gate milestone status, AVE facts, Flow C, and stale hosts - #72
Merged
Merged
Conversation
ARCHITECTURE.md said the gate was at "DESIGN -> M1, M1 next", AVE was "live: schema 1.2, 51 records" at ave.bawbel.io, and PiranhaDB was live. Measured: gate is alpha 0.1.0 on PyPI with M5 and M7 partial; AVE is an independent project (aveproject/ave) with 87 records on schema 1.1.0; api.piranha.bawbel.io does not resolve. Flow C now says the record-to-stanza step is planned: no AVE record carries capability_mitigation, and harden --ave reads gate's own mitigations file. README.md and the ave-record-authoring skill drop ave.bawbel.io. DESIGN.md (header dependency, 9.2) waits on the schema decision in #71. Refs #71 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: chaksaray <chaksaray@gmail.com>
1 of 6 tasks
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.
Refs #71
What and why
Measured 2026-10-18:
bawbel-gate0.1.0; README: M5 and M7 partial, the rest doneschemas/ave-1.2.json, docs at ave.bawbel.ioschema/ave-record-1.1.0.schema.json; ave.bawbel.io 301s every path to https://aveproject.org/api.piranha.bawbel.iodoes not resolveChanges:
ARCHITECTURE.md: the three ASCII layer labels (same widths: 76, 80, 76 characters), the two Mermaid labels, the ave, bawbel-gate, and piranhadb entries, the VS Code entry (no host), and a Status paragraph under Flow C: the record-to-stanza step is planned, andharden --avereads gate's ownmitigations/ave-mitigations.json(2 entries)README.mdRelated projects: AVE links https://aveproject.org and aveproject/ave, an independent project.claude/skills/ave-record-authoring/SKILL.md:65: ave.bawbel.io becomes aveproject.orgNot changed, waiting on #71 item 5: DESIGN.md's "Depends on: AVE schema >= 1.2" and section 9/9.2 (including the last ave.bawbel.io string, DESIGN.md:838). The code targets 1.2 (
_const.pySCHEMA_AVE_VERSION_SUPPORTED = "1.2", vendoredschemas/ave-1.2.json), and AVE never published 1.2, so which one the spec should say is a decision.CLAUDE.md's skill references (
gate-implementation/references/invariants.md,ave-record-authoring) both exist on develop; no change.Governing spec
DESIGN.md section(s): none edited. 9 and 14 referenced.
Output contract
Verification
Checklist
git commit -s)🤖 Generated with Claude Code