docs: canonicalize AetherAI3 public links - #16
Merged
Conversation
Nano's CI badge, clone command, issue-template links, security-advisory link, strategy-library links, packaging URLs, and the Protocol-C references in examples/ and nano/bridge/provenance.py all pointed at the DBarr3 namespace. That account no longer exists — github.com/DBarr3 returns 404 and only per-repository transfer redirects still resolve, so every one of these was one GitHub policy change away from breaking, and the Actions badge was resolving through a redirect rather than the canonical repository. The examples/ install command for Protocol-C is also replaced: there is no `aether-protocol-c` project on PyPI yet (verified 404 on the PyPI JSON API), so `pip install aether-protocol-c` cannot succeed. The git install of the canonical repository does. Verified after the change: CI badge renders "CI - passing" from the AetherAI3 path, and the clone, advisory, and issue-template URLs all resolve. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
8 tasks
AetherAI3
pushed a commit
that referenced
this pull request
Aug 19, 2026
…atchdog category A first-time contributor could compile a rule but could not tell whether it was shaped like the rest of the library, because two of the library's four conventions were enforced by review attention alone. The drift that produced this was already in the tree. Six risk/ entries shipped with the compiler's default JSON indentation rather than the library's one-node- per-line format, because CONTRIBUTING said "keep it formatted like neighboring entries" and offered no tool to do it. Every entry carries a REGIME/CONDITIONS/ INVALIDATION/SHAPE/CALIBRATED ON header and a NOT line; nothing documented that, so a newcomer would have discovered it in review. - scripts/check_contribution.py checks one entry or the whole library: compilation, IR agreement, house formatting, the comment header, signal documentation, StrategyGraph round trip, replay determinism, and the effects boundary. `--write` generates or repairs the _ir.json partner in library format, so nobody hand-reflows JSON again. Reads utf-8-sig, so a BOM is not a first-contribution error. - CI runs it over the whole library on every pull request. - The six drifted risk/ fixtures are reformatted. No semantic change; the suite compares parsed JSON. - docs/first-contribution.md walks the path once with a real rule, and its example compiles under tests/test_docs.py rather than being prose. - nano/library/README.md documents the header convention, the SOURCE: provenance field, and the checker. CONTRIBUTING.md gains the checker command and an attribution section. The watchdog category opens the use case the README has advertised since v0.1.0 with nowhere in the library to put it. Two entries - one PAUSE, one OBSERVE - establish the shape: host-measured system and policy state, the same nonnegative rises-as-it-worsens direction convention as risk/, and no direction ever proposed, which tests/test_library.py now enforces for the whole category. CLI: `nano check` on a file saved with a UTF-8 BOM reported `Unexpected character` at 1:1, naming an invisible character in a correct program. Reading as utf-8-sig fixes it without touching the grammar. Stale claims pinned rather than only corrected: the library README said 26 strategies while shipping 32, so the count, the category list, and the root README's per-category table all get drift guards. .gitignore now covers the .venv that CONTRIBUTING tells a newcomer to create. New links added here use the AetherAI3 namespace, but the existing DBarr3 links are deliberately left alone; PR #16 owns that change, and duplicating it would only conflict. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
AetherAI3
pushed a commit
that referenced
this pull request
Aug 19, 2026
…atchdog category A first-time contributor could compile a rule but could not tell whether it was shaped like the rest of the library, because two of the library's four conventions were enforced by review attention alone. The drift that produced this was already in the tree. Six risk/ entries shipped with the compiler's default JSON indentation rather than the library's one-node- per-line format, because CONTRIBUTING said "keep it formatted like neighboring entries" and offered no tool to do it. Every entry carries a REGIME/CONDITIONS/ INVALIDATION/SHAPE/CALIBRATED ON header and a NOT line; nothing documented that, so a newcomer would have discovered it in review. - scripts/check_contribution.py checks one entry or the whole library: compilation, IR agreement, house formatting, the comment header, signal documentation, StrategyGraph round trip, replay determinism, and the effects boundary. `--write` generates or repairs the _ir.json partner in library format, so nobody hand-reflows JSON again. Reads utf-8-sig, so a BOM is not a first-contribution error. - CI runs it over the whole library on every pull request. - The six drifted risk/ fixtures are reformatted. No semantic change; the suite compares parsed JSON. - docs/first-contribution.md walks the path once with a real rule, and its example compiles under tests/test_docs.py rather than being prose. - nano/library/README.md documents the header convention, the SOURCE: provenance field, and the checker. CONTRIBUTING.md gains the checker command and an attribution section. The watchdog category opens the use case the README has advertised since v0.1.0 with nowhere in the library to put it. Two entries - one PAUSE, one OBSERVE - establish the shape: host-measured system and policy state, the same nonnegative rises-as-it-worsens direction convention as risk/, and no direction ever proposed, which tests/test_library.py now enforces for the whole category. CLI: `nano check` on a file saved with a UTF-8 BOM reported `Unexpected character` at 1:1, naming an invisible character in a correct program. Reading as utf-8-sig fixes it without touching the grammar. Stale claims pinned rather than only corrected: the library README said 26 strategies while shipping 32, so the count, the category list, and the root README's per-category table all get drift guards. .gitignore now covers the .venv that CONTRIBUTING tells a newcomer to create. New links added here use the AetherAI3 namespace, but the existing DBarr3 links are deliberately left alone; PR #16 owns that change, and duplicating it would only conflict. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Nano's CI badge, clone command, issue-template links, security-advisory link,
strategy-library links, packaging URLs, and the Protocol-C references in
examples/ and nano/bridge/provenance.py all pointed at the DBarr3 namespace.
That account no longer exists — github.com/DBarr3 returns 404 and only
per-repository transfer redirects still resolve, so every one of these was one
GitHub policy change away from breaking, and the Actions badge was resolving
through a redirect rather than the canonical repository.
The examples/ install command for Protocol-C is also replaced: there is no
aether-protocol-cproject on PyPI yet (verified 404 on the PyPI JSON API),so
pip install aether-protocol-ccannot succeed. The git install of thecanonical repository does.
Verified after the change: CI badge renders "CI - passing" from the AetherAI3
path, and the clone, advisory, and issue-template URLs all resolve.
Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com
🤖 Generated with Claude Code