Skip to content

docs: correct gate milestone status, AVE facts, Flow C, and stale hosts - #72

Merged
chaksaray merged 1 commit into
developfrom
docs/71-status-and-ave-facts
Oct 18, 2026
Merged

chaksaray merged 1 commit into
developfrom
docs/71-status-and-ave-facts

Conversation

@chaksaray

Copy link
Copy Markdown
Member

Refs #71

What and why

Measured 2026-10-18:

Claim in the docs Measured
gate "[DESIGN → M1]", "M1 next" PyPI bawbel-gate 0.1.0; README: M5 and M7 partial, the rest done
hub "DESIGN → M7" README: M7 partial
AVE "live: schema 1.2, 51 records", schemas/ave-1.2.json, docs at ave.bawbel.io aveproject/ave (independent; bawbel/ave redirects): 87 records, schema_version 1.1.0 for all, schema/ave-record-1.1.0.schema.json; ave.bawbel.io 301s every path to https://aveproject.org/
AVE records carry "an executable mitigation stanza" provenance_vector 87/87, trifecta_profile 77/87, capability_mitigation 0/87
PiranhaDB "live: Railway" api.piranha.bawbel.io does not resolve

Changes:

  • 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, and harden --ave reads gate's own mitigations/ave-mitigations.json (2 entries)
  • README.md Related 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.org

Not 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.py SCHEMA_AVE_VERSION_SUPPORTED = "1.2", vendored schemas/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

  • Changes: ARCHITECTURE.md, README.md, one skill file
  • Does not change: code, tests, DESIGN.md
  • New or changed CLI flags, manifest fields, reason strings, audit record fields: none

Verification

$ git grep -n -E 'ave\.bawbel\.io|bawbel/bawbel-ave'
DESIGN.md:838:   ave.bawbel.io.            (left for the DESIGN.md PR)

pytest                          -> 346 passed in 12.61s
pytest tests/property/ -x       -> 26 passed in 1.34s
pytest tests/replay/            -> 32 passed in 0.37s
pytest tests/test_m4_corpus.py  -> 10 passed in 0.18s   (approval budget)
pre-commit run --all-files      -> 7 hooks Passed
em dashes on added lines: 0

Checklist

🤖 Generated with Claude Code

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>
@chaksaray
chaksaray merged commit 5a0ceb7 into develop Oct 18, 2026
4 checks passed
@chaksaray
chaksaray deleted the docs/71-status-and-ave-facts branch October 18, 2026 15:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Correct milestone status, AVE facts, Flow C, and stale hosts; decide the AVE schema target

1 participant