Register the Joinery in CANONICAL-NAMES; PORT-REGISTRY two-plane reconciliation#478
Merged
Merged
Conversation
… the groove registry - CANONICAL-NAMES.adoc: "The Joinery" register entry — cleave (surface, the contranym), groove (protocol, seating depth = integration/trust/ gating), spline (data-form seated into the groove); consumers (gossamer, burble, panll, vext, …) are NOT layers; reject-forms listed (weft, "the groove stack", groove-* sprawl as layer names, consumer names as layer names); authority pointer to groove ADR 0009, which asked for exactly this registration. Paste-able directive block updated in sync per the file's own rule; deprecated weft row cross-referenced. - PORT-REGISTRY.md: two-plane authority rule adopted — groove-registry.json (groove ADR 0006) governs the groove-discovery surface, this file governs app/bind ports and mirrors groove assignments. Reconciled rows: burble 4020 → legacy, groove surface 6473; verisimdb groove surface 6475 (its own "8080 often intercepted" note agrees) + live-but-unregistered 8097 standards innervation instance registered; gitbot-fleet 7500 → 9100; new rows groove-ref 6465, gossamer 6470, panll 8000. New clearly-marked UNRESOLVED subsection (flagged, not fixed, owner decision needed): echidna 8081-vs-9000, boj-server vs conflow/rpa-elysium 7700/7800 double-booking, burble AI-bridge WS 6475 colliding with verisimdb's groove assignment (recommend bridge → 7474/7475). Last-audited line updated. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ECjSL2nqzn3qJEzA28V4m5
scripts/build-registry.sh run after the PORT-REGISTRY.md edit; the registry-check gate now passes locally. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ECjSL2nqzn3qJEzA28V4m5
|
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
2 participants
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.
Summary
Registers the joinery naming canon estate-wide (groove ADR 0009 asked for exactly this) and reconciles PORT-REGISTRY.md with the groove registry under an explicit two-plane authority rule. Part of the estate-wide joinery round.
Changes
weftrow cross-referencedTesting
Docs-only. Every port value cross-checked against
groove/registry/groove-registry.jsonand the live config files (e.g. standards' own.verisimdb/config.tomlport 8097). Zero licence/SPDX edits.🤖 Generated with Claude Code
https://claude.ai/code/session_01ECjSL2nqzn3qJEzA28V4m5
Generated by Claude Code