Conversation
* Create CNAME * Update CNAME to aveproject.org * feat: rebuild records.js with 8 new AVE records (51 -> 59) Pulled the latest records from bawbel/ave/records and regenerated records.js via scripts/build-records.js, validating against the v1.0.0 schema. Updates the records badge count in README. * chore: replace ave.bawbel.io references with aveproject.org Updates canonical URLs, meta tags, JSON-LD, sitemap, robots.txt, crosswalk schema references, and docs to point at the new aveproject.org domain.
…e API (#28) * Create CNAME * Update CNAME to aveproject.org * fix: repoint record citation to the aveproject/ave source, not the private API The drawer's citation text was hardcoded to api.piranha.bawbel.io, a separate Bawbel product endpoint, independent of what a record's own references say. Point it at the actual records/*.json source file in aveproject/ave instead, and drop the "Bawbel/" prefix from the citation string itself — a researcher pasting this into their own paper shouldn't carry Bawbel branding in a citation meant to reference the open standard.
* Create CNAME * Update CNAME to aveproject.org * feat: rewrite schema.html for v1.1.0 The live page still documented the v1.0.0 shape: no provenance_vector, trifecta_profile, mitigation, or example_patterns; owasp_mapping and mitre_atlas_mapping shown as live field names; a flat 15-required-fields list that didn't reflect the draft/active conditional split; and github.com/bawbel/ave links throughout. Rewritten against the canonical schema/ave-record-1.1.0.schema.json in aveproject/ave: documents the two new v1.1.0 classification objects, renames the framework mapping fields, splits required fields into the 8 always-required plus the 7 that apply once a record leaves draft, and repoints domain/GitHub links to aveproject.org and aveproject/ave.
* Create CNAME * Update CNAME to aveproject.org * fix: remove Bawbel vendor coupling from architecture.html The detection-layers table's scanner column, the runtime-records callout, and the validation section's SVG and prose all named or implied a single reference implementation (bawbel scan, bawbel-scanner, PiranhaDB, api.piranha.bawbel.io) as if it were part of the standard. AVE is meant to be implementation-neutral: describe what a conforming scanner or fixture relationship looks like in the abstract, not which vendor ships it.
Every footer carried Bawbel's own consumer-facing slogan ("Sense. Protect.
Secure. — ocean & beyond") and bare domain directly beneath the sentence
stating AVE is meant to outlive any single implementation, including
Bawbel's — a direct contradiction on every page of the standard's site.
Replaced with a copyright line and license, keeping two spans so the
.base flex layout (justify-content: space-between) isn't disturbed. Six
files needed this, not four: schema.html was not already fixed as assumed,
and scoring.html carries the same footer template but wasn't in scope of
the original audit.
…mn (#36) The crosswalk table's row builder still read owasp_mapping and mitre_atlas_mapping, both renamed away, and never read nist_ai_rmf at all since that field didn't exist when this table was first built. Reading a missing property returns undefined silently, so this failed with no console error. Adds a fourth NIST AI RMF column and reads owasp_asi/mitre_atlas/ nist_ai_rmf directly from each record. Verified against the live records.js: AVE-2026-00001 now populates real values in all four framework columns.
Reworks sentences, headings, and the shared footer paragraph across all six pages to read without em-dashes, per house style. Title tags, meta descriptions, SVG diagram labels, and JS placeholder/label strings are left untouched as non-prose exceptions.
Transcribes docs/specs/ave-implementer-guide.md from aveproject/ave (post em-dash and stale-endpoint fixes in PR #65) using the site's existing page template (topbar/pagehead/footer from schema.html). Not yet linked from nav or footer on any page; that's a separate change.
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.
No description provided.