docs(knowledge): GUID canon + prefix routing — policy-side crystallization (quorum landing spot, deterministic phase, WHP bipolar)#482
Merged
Conversation
|
Warning Review limit reached
More reviews will be available in 35 minutes and 28 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis PR adds documentation to the ChangesGUID Canon and Bipolar Phase Findings Documentation
🎯 2 (Simple) | ⏱️ ~12 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 08f4840840
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| | `(entity_type ↔ NiblePath)` bijection mint | ontology registry — Phase B | [H], planned (identity plan) | | ||
| | Per-class centroid codebooks (4⁴-hierarchical, prefix-scoped) | registry shelf, next to `ClassView`/`StructuralSignature` — minted with the class, trained once (amortized) | CONJECTURE → PROBE-CODEBOOK-44 (ndarray doc §6) | | ||
| | `PrefixShapeTable` registration (classid/prefix → `ShapeId`) | lance-graph builds the table from the registry; ndarray routes by it, never knowing semantics | CONJECTURE → PROBE-ROUTE-1 | | ||
| | Quorum certificate type | `contract::quorum` — the #411 scaffold (`todo!()`) is the named landing spot; `HighHeelBGZ`'s basin-merge L1-threshold consensus is the existing mechanism to generalize | CONJECTURE → PROBE-QUORUM-1 | |
There was a problem hiding this comment.
This doc sends the quorum certificate work to contract::quorum, but I checked crates/lance-graph-contract/src/lib.rs and the crate does not declare pub mod quorum; src/quorum.rs exists but is not part of the public crate API (or compiled through this crate root). Any follow-up implementation that imports lance_graph_contract::quorum from this guidance will fail, so either export the module first or describe it as an unexported scaffold/file rather than the contract path.
Useful? React with 👍 / 👎.
Owner
Author
There was a problem hiding this comment.
Codex right — verified lib.rs declares no pub mod quorum; src/quorum.rs is unexported scaffold and importing lance_graph_contract::quorum would not resolve today. Fixed in 8de856d (now 4252f89 after rebasing onto post-#481 main): step 1 of the quorum work is named explicitly as the export, with a warning against importing until it lands. CodeRabbit's parallel nits on §1 labels + MD040 + encoding-ecosystem pre-read are folded in the same commit.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (5)
.claude/knowledge/guid-canon-and-prefix-routing.md (5)
14-17: 💤 Low valueAdd language specifier to fenced code block (linter compliance).
The fenced code block displaying the GUID structure diagram lacks a language specifier, triggering markdownlint MD040. Tag it as
textfor clarity.Proposed fix
-``` +```text xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx 32 hex = 128 bit = the GUID classid HEEL HIP TWIG basin·leaf(6)+identity(6)</details> <details> <summary>🤖 Prompt for AI Agents</summary>Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.In @.claude/knowledge/guid-canon-and-prefix-routing.md around lines 14 - 17, The
fenced code block in the document showing the GUID diagram is missing a language
specifier (triggering markdownlint MD040); update the triple-backtick fence that
precedes the GUID diagram to include the language token "text" (i.e., changetotext) so the block becomes a text fenced-code block, leaving the content
inside unchanged.</details> <!-- cr-comment:v1:310cc26e19ae773c826937b0 --> --- `33-39`: _⚡ Quick win_ **Label all table rows as FINDING or CONJECTURE for consistency.** The ownership table labels three rows as CONJECTURE (lines 36-38) but omits explicit FINDING or CONJECTURE labels for the ontology bijection (line 35) and escalation (line 39) rows. The guideline requires all claims be labeled; the status markers `[H], planned` and `[G] mechanism / [H] wiring` do not substitute for FINDING/CONJECTURE classification. <details> <summary>Proposed fix</summary> ```diff | Concern | Where it lands | Status | |---|---|---| -| `(entity_type ↔ NiblePath)` bijection mint | ontology registry — Phase B | [H], planned (identity plan) | +| `(entity_type ↔ NiblePath)` bijection mint | ontology registry — Phase B | FINDING: [H], planned (identity plan) | | Per-class centroid codebooks (4⁴-hierarchical, prefix-scoped) | registry shelf, next to `ClassView`/`StructuralSignature` — minted with the class, trained once (amortized) | CONJECTURE → PROBE-CODEBOOK-44 (ndarray doc §6) | | `PrefixShapeTable` registration (classid/prefix → `ShapeId`) | lance-graph builds the table from the registry; ndarray routes by it, never knowing semantics | CONJECTURE → PROBE-ROUTE-1 | | Quorum certificate type | `contract::quorum` — the `#411` scaffold (`todo!()`) is the named landing spot; `HighHeelBGZ`'s basin-merge L1-threshold consensus is the existing mechanism to generalize | CONJECTURE → PROBE-QUORUM-1 | -| Escalation on quorum fail | HHTL tier escalation (`bgz-tensor::hhtl_cache::RouteAction::Escalate` is the shipped precedent) | [G] mechanism / [H] wiring | +| Escalation on quorum fail | HHTL tier escalation (`bgz-tensor::hhtl_cache::RouteAction::Escalate` is the shipped precedent) | FINDING: [G] mechanism / [H] wiring | ``` </details> <details> <summary>🤖 Prompt for AI Agents</summary> ``` Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.claude/knowledge/guid-canon-and-prefix-routing.md around lines 33 - 39, The ownership table mixes unlabeled rows with CONJECTURE entries; update the table so every row explicitly uses either FINDING or CONJECTURE. Concretely, annotate the ontology bijection row (currently "ontology registry — Phase B") as either FINDING or CONJECTURE and annotate the escalation row (currently "HHTL tier escalation (`bgz-tensor::hhtl_cache::RouteAction::Escalate` ... )") similarly, keeping existing status notes like `[H], planned` or `[G] mechanism / [H] wiring` but adding the FINDING/CONJECTURE label; ensure entries referencing `ClassView`/`StructuralSignature`, `PrefixShapeTable`, `contract::quorum`, and `HighHeelBGZ` maintain their current text and only gain the explicit label. ``` </details> <!-- cr-comment:v1:c012accce4c3b062bcbc8707 --> _Source: Coding guidelines_ --- `41-61`: _⚡ Quick win_ **Label §3 anti-theater rules as FINDING or CONJECTURE.** Section 3 presents five contract-side consequences without a FINDING or CONJECTURE label. The rules reference existing measured anchors (ρ values), iron rules (I-NOISE-FLOOR-JIRAK, I-VSA-IDENTITIES), and an ndarray casebook, suggesting these are consolidated findings rather than conjectures. Add an explicit label at the section or paragraph level. <details> <summary>Proposed fix</summary> ```diff ## 3. The anti-theater rules, contract side +**FINDING** (policy consolidation from ndarray casebook pp13, iron rules I-NOISE-FLOOR-JIRAK / I-VSA-IDENTITIES): + The ndarray casebook (`pp13-brutally-honest-tester-verdict.md`) defines ``` </details> <details> <summary>🤖 Prompt for AI Agents</summary> ``` Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.claude/knowledge/guid-canon-and-prefix-routing.md around lines 41 - 61, The section titled "The anti-theater rules, contract side" presents five contract-side consequences (referenced by the ndarray casebook pp13-brutally-honest-tester-verdict.md and symbols like I-NOISE-FLOOR-JIRAK, I-VSA-IDENTITIES, ShapeId) but lacks an explicit epistemic label; update the header or the opening paragraph of Section 3 to prepend a clear label — either "FINDING:" if these are presented as consolidated, measured conclusions or "CONJECTURE:" if they are tentative — so readers can immediately see the claim status, and apply the same label formatting to the numbered list that follows for consistency. ``` </details> <!-- cr-comment:v1:c49df9f49b51f6285682603f --> _Source: Coding guidelines_ --- `94-122`: _⚡ Quick win_ **Replace "operator" with explicit FINDING label.** Section 7 uses "operator, 2026-06-10" in the header but does not use the guideline-required FINDING label. Apply the same FINDING labeling convention used in other sections. <details> <summary>Proposed fix</summary> ```diff -## 7. Bipolar-phase pyramid = Walsh-Hadamard on VSA (operator, 2026-06-10) +## 7. Bipolar-phase pyramid = Walsh-Hadamard on VSA + +**FINDING** (operator-pinned, 2026-06-10): ``` </details> <details> <summary>🤖 Prompt for AI Agents</summary> ``` Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.claude/knowledge/guid-canon-and-prefix-routing.md around lines 94 - 122, The section header "7. Bipolar-phase pyramid = Walsh-Hadamard on VSA (operator, 2026-06-10)" uses the word "operator" instead of the guideline-required FINDING label; update that header so the parenthetical uses the FINDING label and date (e.g., "(FINDING, 2026-06-10)" or "(FINDING: <short-tag>, 2026-06-10)") keeping the rest of the title text "Bipolar-phase pyramid = Walsh-Hadamard on VSA" unchanged and ensuring the format matches other sections' FINDING labels. ``` </details> <!-- cr-comment:v1:94cd3ec5ab08337c9cef4872 --> _Source: Coding guidelines_ --- `78-92`: _⚡ Quick win_ **Replace "operator pin" with explicit FINDING label.** Section 6 uses "operator pin, 2026-06-10" in the header but does not use the guideline-required FINDING label. While "operator pin" likely indicates this is a canonical finding, the coding guideline specifies "Label every claim as FINDING or CONJECTURE." <details> <summary>Proposed fix</summary> ```diff -## 6. Perturbation = deterministic phase (operator pin, 2026-06-10) +## 6. Perturbation = deterministic phase + +**FINDING** (operator-pinned canon, 2026-06-10): ``` </details> <details> <summary>🤖 Prompt for AI Agents</summary> ``` Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.claude/knowledge/guid-canon-and-prefix-routing.md around lines 78 - 92, Update the Section 6 header "Perturbation = deterministic phase (operator pin, 2026-06-10)" to use the required FINDING label instead of "operator pin"; specifically change the parenthetical to "(FINDING, 2026-06-10)" so the header reads "Perturbation = deterministic phase (FINDING, 2026-06-10)". Ensure any internal references in this section (e.g., mentions of PROBE-PHASE-1, PROBE-PERT-RHO, CurveRuler, guid-prefix-shape-routing.md) remain unchanged and still refer to the same canonical finding. ``` </details> <!-- cr-comment:v1:2854e7b15acbf8b4c5859aa7 --> _Source: Coding guidelines_ </blockquote></details> </blockquote></details> <details> <summary>🤖 Prompt for all review comments with AI agents</summary>Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.Inline comments:
In @.claude/knowledge/guid-canon-and-prefix-routing.md:
- Around line 12-30: Section 1 contains unlabelled claims about the GUID canon
and encoding (e.g., the GUID layout line "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
CAM-PQ, LUT distance, and the mention of contract::identity::NodeGuid); add
explicit FINDING or CONJECTURE labels for each substantive claim/grouping in
that section (mark the canonical assertions as FINDING and speculative
interpretations as CONJECTURE) and annotate the paragraphs accordingly; also add
a P0 cross-reference that you consulted .claude/knowledge/encoding-ecosystem.md
(for example in the §5 or READ BY paragraph) stating “encoding-ecosystem.md
consulted per P0” so the document meets the P0 requirement before any
codec/encoding/distance discussion.
Nitpick comments:
In @.claude/knowledge/guid-canon-and-prefix-routing.md:
- Around line 14-17: The fenced code block in the document showing the GUID
diagram is missing a language specifier (triggering markdownlint MD040); update
the triple-backtick fence that precedes the GUID diagram to include the language
token "text" (i.e., changetotext) so the block becomes a text
fenced-code block, leaving the content inside unchanged.- Around line 33-39: The ownership table mixes unlabeled rows with CONJECTURE
entries; update the table so every row explicitly uses either FINDING or
CONJECTURE. Concretely, annotate the ontology bijection row (currently "ontology
registry — Phase B") as either FINDING or CONJECTURE and annotate the escalation
row (currently "HHTL tier escalation
(bgz-tensor::hhtl_cache::RouteAction::Escalate... )") similarly, keeping
existing status notes like[H], plannedor[G] mechanism / [H] wiringbut
adding the FINDING/CONJECTURE label; ensure entries referencing
ClassView/StructuralSignature,PrefixShapeTable,contract::quorum, and
HighHeelBGZmaintain their current text and only gain the explicit label.- Around line 41-61: The section titled "The anti-theater rules, contract side"
presents five contract-side consequences (referenced by the ndarray casebook
pp13-brutally-honest-tester-verdict.md and symbols like I-NOISE-FLOOR-JIRAK,
I-VSA-IDENTITIES, ShapeId) but lacks an explicit epistemic label; update the
header or the opening paragraph of Section 3 to prepend a clear label — either
"FINDING:" if these are presented as consolidated, measured conclusions or
"CONJECTURE:" if they are tentative — so readers can immediately see the claim
status, and apply the same label formatting to the numbered list that follows
for consistency.- Around line 94-122: The section header "7. Bipolar-phase pyramid =
Walsh-Hadamard on VSA (operator, 2026-06-10)" uses the word "operator" instead
of the guideline-required FINDING label; update that header so the parenthetical
uses the FINDING label and date (e.g., "(FINDING, 2026-06-10)" or "(FINDING:
, 2026-06-10)") keeping the rest of the title text "Bipolar-phase
pyramid = Walsh-Hadamard on VSA" unchanged and ensuring the format matches other
sections' FINDING labels.- Around line 78-92: Update the Section 6 header "Perturbation = deterministic
phase (operator pin, 2026-06-10)" to use the required FINDING label instead of
"operator pin"; specifically change the parenthetical to "(FINDING, 2026-06-10)"
so the header reads "Perturbation = deterministic phase (FINDING, 2026-06-10)".
Ensure any internal references in this section (e.g., mentions of PROBE-PHASE-1,
PROBE-PERT-RHO, CurveRuler, guid-prefix-shape-routing.md) remain unchanged and
still refer to the same canonical finding.</details> <details> <summary>🪄 Autofix (Beta)</summary> Fix all unresolved CodeRabbit comments on this PR: - [ ] <!-- {"checkboxId": "4b0d0e0a-96d7-4f10-b296-3a18ea78f0b9"} --> Push a commit to this branch (recommended) - [ ] <!-- {"checkboxId": "ff5b1114-7d8c-49e6-8ac1-43f82af23a33"} --> Create a new PR with the fixes </details> --- <details> <summary>ℹ️ Review info</summary> <details> <summary>⚙️ Run configuration</summary> **Configuration used**: Organization UI **Review profile**: CHILL **Plan**: Pro Plus **Run ID**: `50786624-53b8-458b-9b76-120afb45a80a` </details> <details> <summary>📥 Commits</summary> Reviewing files that changed from the base of the PR and between 1def205d28679449226ea5679ecefccc10a70dc6 and 08f484084002488fc2534c745d07f08bce50892a. </details> <details> <summary>📒 Files selected for processing (2)</summary> * `.claude/board/EPIPHANIES.md` * `.claude/knowledge/guid-canon-and-prefix-routing.md` </details> </details> <!-- This is an auto-generated comment by CodeRabbit for review status -->
AdaWorldAPI
pushed a commit
that referenced
this pull request
Jun 11, 2026
Codex P2 (verified correct): contract::quorum is NOT an exported module - lib.rs declares no 'pub mod quorum'; src/quorum.rs is an unexported scaffold. Doc now states step 1 of the quorum work IS the export, and warns against importing lance_graph_contract::quorum until then. HILBERT-L4 probe row updated to VERIFIED GREEN (run first-hand on the ndarray branch: 13/13 incl. level4_all_indices_unique = bijective onto [0,4096) and level4_curve_is_connected; PP-13 P0-4's 'expected 4095' was an orientation assumption, not the contract). CodeRabbit nits: MD040 language tag on the GUID fence (text); explicit FINDING label on the section-1 canon block; FINDING/CONJECTURE labels on the two unlabeled ownership-table rows; P0 pre-read acknowledgment for encoding-ecosystem.md added to the header. https://claude.ai/code/session_01PBTGaPCSnnt6u3pjXpbLwY
…allization) Crystallizes the operator-pinned canonical GUID (OGAR/CLAUDE.md) into lance-graph's policy-side contract before it dilutes: - The canon cited (hex dash-groups = classid-HEEL-HIP-TWIG-[basin+id]; key(128)+value(3968)=4096; 3x4 uniform, tier = nibble >> 2; RFC 9562 = wrapper concern; NodeGuid #480 audited against the canon group-by-group, never the reverse — Phase B question: groups 3-4 yield all eight nibbles to HIP/TWIG). - Policy ownership table: registry mint (Phase B), per-class 4^4-hierarchical codebooks on the registry shelf (prefix-scoped, longest-prefix wins), PrefixShapeTable registration into ndarray's router, quorum certificate type landing in contract::quorum (the #411 scaffold), escalation via the shipped RouteAction precedent. - Anti-eigenvalue-theater rules contract-side: quorum certificate with measured-tau (I-NOISE-FLOOR-JIRAK; Pflug-10 anchors 0.9973/0.965), named typed metrics (no-umbrella; raw-XOR-u64 ordering is the named anti-pattern), escalate-never-silently-accept, ShapeId is a register key (I-VSA-IDENTITIES Test 0). - Probes shared with the ndarray counterpart: ROUTE-1, QUORUM-1, PHI-1, PYR-1, CODEBOOK-44, HILBERT-L4 (blocker). Board hygiene: EPIPHANIES E-CANON-GUID-1 prepended in the same commit. Docs-only; no .rs touched. https://claude.ai/code/session_01PBTGaPCSnnt6u3pjXpbLwY
Mirror of the operator pin: (exponent, location, phase, magnitude) — key-derived except the stored magnitude envelope; lossless for synthesis; analysis remainder escalates per the quorum certificate; coprime-integer phase walk mandated in quantized layers (D-QUANTGATE); helix CurveRuler is the shipped generator. Probes PHASE-1 + PERT-RHO added to the shared list. Full treatment in the ndarray counterpart; canon in OGAR/CLAUDE.md. https://claude.ai/code/session_01PBTGaPCSnnt6u3pjXpbLwY
…d on VSA (policy mirror) Policy-side mirror of the operator pin: signed phase makes the cascade a Walsh-Hadamard transform on the existing VSA-bipolar algebra. Signs compose by XOR (= vsa_bind); magnitudes compose by vsa_bundle (Markov-respecting per I-SUBSTRATE-MARKOV). Each cell = Walsh-resonance superposition recoverable by role-key unbind; I-VSA-IDENTITIES Test 1 (N <= sqrt(d)/4 ~= 32) IS the substrate uncertainty principle made explicit. Roundtrip bit-exact (phase generated, Walsh self-inverse). TWO-ALGEBRA RULE (load-bearing): sign = XOR; magnitude = bundle, NEVER MergeMode::Xor (breaks Markov; PP-13 P1-1 is the named anti-pattern that conflates them). Receipts already exist: Vsa16kF32 (bipolar carrier, crystal/fingerprint.rs), vsa_bind/vsa_bundle (iron-rule algebra), helix CurveRuler (bit-exact integer phase walk). Fences: 'quantum-like' is the bundling algebra NOT measurement randomness (no headline drift); bipolar = 1-bit phase (multi-bit stacks above when needed); Parseval requires the bundle (sum), not just XOR. Probes shared with ndarray §4b: WHP-1 (Parseval rho on random sign-fields, Jirak floor) / WHP-2 (cross-backend roundtrip byte-identical) / WHP-3 (bind+unbind margin holds for N <= sqrt(d)/4, fails cleanly past it) / WHP-4 (two-algebra guard: raw-XOR on magnitudes fails Chapman-Kolmogorov consistency). EPIPHANIES E-WHP-BIPOLAR-1 prepended (board hygiene). https://claude.ai/code/session_01PBTGaPCSnnt6u3pjXpbLwY
Codex P2 (verified correct): contract::quorum is NOT an exported module - lib.rs declares no 'pub mod quorum'; src/quorum.rs is an unexported scaffold. Doc now states step 1 of the quorum work IS the export, and warns against importing lance_graph_contract::quorum until then. HILBERT-L4 probe row updated to VERIFIED GREEN (run first-hand on the ndarray branch: 13/13 incl. level4_all_indices_unique = bijective onto [0,4096) and level4_curve_is_connected; PP-13 P0-4's 'expected 4095' was an orientation assumption, not the contract). CodeRabbit nits: MD040 language tag on the GUID fence (text); explicit FINDING label on the section-1 canon block; FINDING/CONJECTURE labels on the two unlabeled ownership-table rows; P0 pre-read acknowledgment for encoding-ecosystem.md added to the header. https://claude.ai/code/session_01PBTGaPCSnnt6u3pjXpbLwY
AdaWorldAPI
force-pushed
the
claude/guid-canon-crystallization
branch
from
8de856d to
4252f89
Compare
AdaWorldAPI
pushed a commit
that referenced
this pull request
Jun 11, 2026
Surveyed PRs #471-#487. Three landed that materially affect my outstanding ask list: - #482 (merged): GUID canon + prefix routing knowledge doc — pins TWO-ALGEBRA RULE (sign=XOR, magnitude=bundle, never MergeMode::Xor) + helix CurveRuler stride-4-over-17 as bit-exact integer phase generator. Both are load-bearing receipts for substrate-addressing-v1. - #484 (merged): D-IDENTITY-2 ships entity_type↔NiblePath bijection in lance-graph-ontology registry. RESOLVES the Tier-1 'NiblePath scheme for FMA classes' ask — OGAR Phase 8 calls register_class_path() per FMA Class. - #485 (OPEN): PROBE-MANTISSA-FILL + PROBE-PHASE-1 both GREEN. The golden-mantissa placement leg of the substrate-addressing claim is now measured (not asserted): beats seeded random by ~30% at k=256 + half worst-case pile-up. CurveRuler bit-exactness verified over 20 path/depth pairs. Updated Decision 1 trigger: substrate-addressing-v1.md now files after #485 merges (not after D-HELIX-1 owner ping — they're actively probing). D-CESIUM-1 (mine — extend implicit_tiling.rs to consume helix::bounds) is the file-soonest deliverable. D-JC-1 still needs per-scene-class p calibration timeline.
This was referenced Jun 13, 2026
Merged
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.
What this PR is
The policy-side crystallization of the operator-pinned GUID canon (
OGAR/CLAUDE.md, OGAR #50) into lance-graph — knowledge docs + board hygiene only; zero.rschanges. Mechanism-side counterpart: the ndarray PR on the same branch name.Contents
.claude/knowledge/guid-canon-and-prefix-routing.md(NEW):NodeGuidfeat(contract): NodeGuid — structured 128-bit instance identity (identity-architecture Phase A) #480 audited against the canon group-by-group — Phase B question: groups 3–4 yield all eight nibbles to HIP/TWIG).PrefixShapeTableregistration into ndarray's router · quorum certificate type lands incontract::quorum(the Cognitive substrate: locked 33-TSV atom layer + 34-tactic recipes + escalation loop #411todo!()scaffold — named landing spot;HighHeelBGZbasin-merge consensus is the mechanism to generalize) · escalation via the shippedRouteActionprecedent.ShapeIdis a register key per I-VSA-IDENTITIES Test 0).CurveRulerstride-4-over-17 is the shipped bit-exact integer generator; analysis remainder escalates per the quorum certificate.Vsa16kF32algebra; TWO-ALGEBRA RULE (load-bearing): sign = XOR (vsa_bind); magnitude =vsa_bundle, NEVERMergeMode::Xor(breaks Markov per I-SUBSTRATE-MARKOV); N ≤ √d/4 (I-VSA-IDENTITIES Test 1) is the substrate's uncertainty bound; "quantum-like" = the bundling algebra, NOT measurement randomness..claude/board/EPIPHANIES.md— two PREPENDs in-commit per the Mandatory Board-Hygiene Rule: E-CANON-GUID-1 and E-WHP-BIPOLAR-1 (each with Status/Confidence and the FINDING-vs-CONJECTURE split).Receipts the doc stands on (all shipped)
Vsa16kF32bipolar carrier (crystal/fingerprint.rs) ·vsa_bind/vsa_bundle(iron-rule algebra) · helixCurveRuler(bit-exact integer phase walk, #459/#460) ·contract::quorumscaffold (#411) ·RouteAction::Escalate(bgz-tensor) ·NodeGuid(#480).Wave-ordered execution plan:
OGAR/docs/INTEGRATION-TEST-PLAN.md(OGAR #50) — Wave 0 runs entirely against shipped code.Docs-only · no
.rstouched · PII abort-guard CLEAN · no model identifier.https://claude.ai/code/session_01PBTGaPCSnnt6u3pjXpbLwY
Summary by CodeRabbit
Note: This release contains internal documentation updates only. No user-facing features or functionality have been modified.