Skip to content

docs(plan): name the ECHIDNA Julia file without a local-looking path - #21

Merged
hyperpolymath merged 1 commit into
mainfrom
marina/cool-noether-i2rc8g
Nov 15, 2026
Merged

hyperpolymath merged 1 commit into
mainfrom
marina/cool-noether-i2rc8g

Conversation

@hyperpolymath

@hyperpolymath hyperpolymath commented Nov 15, 2026 •

Copy link
Copy Markdown
Owner

Summary

Follow-up to atoma#20. The Hypatia structural-drift rule SD022 raised one warning on #20: docs/plan/FAMILY-ULTRAPLAN.adoc cited an ECHIDNA file as src/julia/coprocessor.jl, and Atoma has no src/julia directory. The scanner read the path as a stale local reference. #20 merged with that alert open.

Changes

  • docs/plan/FAMILY-ULTRAPLAN.adoc: the sentence now names the file and says that it is in the ECHIDNA Julia sources. One sentence; no other change.

Not from this work

The estate-rules job is red on main before and after #20: tests/workflows/proof_claims_rows_test.sh reports that docs/status/PROOF-STATUS.adoc has no rows in a == Claims table (12 controls, 1 failed, also on commit 3213895, the base of #20). This PR does not change that file. The repair needs a decision on which Atoma claims become rows, so it is not made here.

Testing

asciidoctor --failure-level=WARN on the file: clean. scripts/check-internal-links.sh: pass.


Generated by Claude Code

Summary by CodeRabbit

  • Documentation
    • Updated the planning documentation’s owner question to refer to the ECHIDNA coprocessor layer and identify its Julia source file as coprocessor.jl, replacing the previous path.
    • This update is limited to documentation; no exported or public entities were changed.

The family plan cited the ECHIDNA file as src/julia/coprocessor.jl. Atoma has no src/julia directory, so the Hypatia structural-drift rule SD022 read the path as a stale local reference and raised a warning on the first pull request. The sentence now names the file and says that it is in the ECHIDNA Julia sources.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136P7Zmp1i8PGVHkq3u2iNz
@coderabbitai

coderabbitai Bot commented Nov 15, 2026 •

Copy link
Copy Markdown
Contributor

Explain Change →

No actionable comments were generated in the recent review.

Walkthrough

The plan document updates an owner question to refer to the ECHIDNA coprocessor layer and its Julia source file as coprocessor.jl.

Changes: Plan reference

Layer / File(s) Summary
Update owner question reference
docs/plan/FAMILY-ULTRAPLAN.adoc
The question now names the Julia source file coprocessor.jl instead of src/julia/coprocessor.jl.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Other

Merge Risk: Minimal · up to 0e617

This is a documentation-only wording change with no runtime impact. The estate-rules CI failure comes from a file this PR does not touch, so it is not caused by this change.

Pre-merge checks: Passed 4

Check name Status Explanation
Title check Passed The title names the change: the ECHIDNA Julia file in the plan document is now cited by name rather than by a local-looking path. It matches the raw summary and the PR objectives, and it is specific e…
Description check Passed The description follows the repository template's main parts. It has a Summary that explains the why and links the related PR #20, and a Changes section that lists the one edited file. It also has a T…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Title check

Explanation

The title names the change: the ECHIDNA Julia file in the plan document is now cited by name rather than by a local-looking path. It matches the raw summary and the PR objectives, and it is specific enough for a teammate scanning history.

Full details: Description check

Explanation

The description follows the repository template's main parts. It has a Summary that explains the why and links the related PR #20, and a Changes section that lists the one edited file. It also has a Testing section with the asciidoctor and link-check results. The template's RSR Quality Checklist is absent, and the author did not tick its items. Some checklist items likely do not apply to a one-sentence docs change, but the author should state which required items were checked or why they do not apply.

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.

Share

Recent review info

Run configuration

Commits

Reviewing files that changed from the base of the PR and between 8533fcf and 0e61717.

Files selected for processing: 1

  • docs/plan/FAMILY-ULTRAPLAN.adoc

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

@sonarqubecloud

Copy link
Copy Markdown

@github-actions

github-actions Bot commented Nov 15, 2026 •

Copy link
Copy Markdown

Hypatia grid green

🟢 clean · commit 0e61717cc59e · run 43705509190 · scope: this change (1 file(s))

Advisory: 11 row(s), worst 🔴 high (0 critical, 9 high in grid scope) — reported, never grading the change.

Unique graded findings across gating and advisory rows: 23 (23 reporter observations; 21 without sufficient identity to corroborate). Row counts remain per reporter; unique totals do not change gating.
Raw Hypatia alert-derived observations: 37 (code-scanning, Dependabot and secret-scanning; some may also be in SARIF; not an extra total).

Reporter Gate Status Critical High Medium Minor Since previous revision
Hypatia scan gating 🟢 clean 0 0 0 0 — same commit (no revision comparison)
panic-attack assail advisory 🟢 clean 0 0 0 0 — same commit (no revision comparison)
pons asinorum advisory 🟢 clean 0 0 0 0 — same commit (no revision comparison)
echidnabot advisory ⚪ not applicable 0 0 0 0 — same commit (no revision comparison)
rhodibot (RSR compliance) advisory 🟢 clean 0 0 0 0 — same commit (no revision comparison)
panicbot advisory ⚪ not applicable 0 0 0 0 — same commit (no revision comparison)
sustainabot advisory ⚪ not applicable 0 0 0 0 — same commit (no revision comparison)
glambot (presentation quality) advisory 🔵 minor 0 0 0 6 — same commit (no revision comparison)
seambot advisory ⚪ not applicable 0 0 0 0 — same commit (no revision comparison)
finishingbot (release readiness) advisory 🔴 high 0 9 8 0 — same commit (no revision comparison)
cipherbot advisory ⚪ not applicable 0 0 0 0 — same commit (no revision comparison)
accessibilitybot advisory ⚪ not applicable 0 0 0 0 — same commit (no revision comparison)
Hypatia scan: 4 finding(s)
  • 4 further finding(s) in files this change does not touch: reported, not graded (0 critical, 3 high).
panic-attack assail: 20 finding(s)
  • 20 further finding(s) in files this change does not touch: reported, not graded (0 critical, 2 high).
pons asinorum: 9 finding(s)
  • 9 further finding(s) in files this change does not touch: reported, not graded (0 critical, 0 high).
echidnabot: not_applicable — template default: enrol once the repository carries proofs and an ECHIDNA engine is configured
  • ⚪ not applicable: template default: enrol once the repository carries proofs and an ECHIDNA engine is configured
rhodibot (RSR compliance): 11 finding(s)
  • 11 further finding(s) in files this change does not touch: reported, not graded (0 critical, 10 high).
panicbot: not_applicable — panic-attack is already graded by the verdict grid's own panic-attack row, from static-analysis-gate.yml evidence; enrolling panicbot would report one scanner twice and give two rows that can disagree
  • ⚪ not applicable: panic-attack is already graded by the verdict grid's own panic-attack row, from static-analysis-gate.yml evidence; enrolling panicbot would report one scanner twice and give two rows that can disagree
sustainabot: not_applicable — reserved fleet slot; no adapter exists (gitbot-fleet bots/sustainabot/README.adoc)
  • ⚪ not applicable: reserved fleet slot; no adapter exists (gitbot-fleet bots/sustainabot/README.adoc)
glambot (presentation quality): 94 finding(s)
  • info GS-001 — Install git-seo for comprehensive SEO analysis: https://github.com/hyperpolymath/git-seo
  • info MACH-007 — ECOSYSTEM.scm not found in .machine_readable/ directory.
  • info MACH-007 — META.scm not found in .machine_readable/ directory.
  • info MACH-007 — STATE.scm not found in .machine_readable/ directory.
  • info MACH-005 — No robots.txt found. Consider adding one for crawler control.
  • info VIS-005 — docs/plan/FAMILY-ULTRAPLAN.adoc:18 — Line 84 characters exceeds max length of 80.
  • 88 further finding(s) in files this change does not touch: reported, not graded (0 critical, 2 high).
seambot: not_applicable — template default: enrol once a seam register exists at spec/seams/seam-register.json
  • ⚪ not applicable: template default: enrol once a seam register exists at spec/seams/seam-register.json
finishingbot (release readiness): 185 finding(s)
  • high V1-DOC-ROADMAP.adoc — Required file ROADMAP.adoc not found (Project roadmap).
  • high TOOL-001 — .tool-versions file not found for asdf/mise version management.
  • high SCM-001-NEUROSYM.scm — Required SCM file NEUROSYM.scm not found (Neurosymbolic AI documentation).
  • high SCM-001-AGENTIC.scm — Required SCM file AGENTIC.scm not found (Agentic AI integration documentation).
  • high SCM-001-PLAYBOOK.scm — Required SCM file PLAYBOOK.scm not found (Operational playbooks and procedures).
  • high SCM-001-ECOSYSTEM.scm — Required SCM file ECOSYSTEM.scm not found (Project's place in the ecosystem).
  • high SCM-001-META.scm — Required SCM file META.scm not found (Meta-level information and architectural decisions).
  • high SCM-001-STATE.scm — Required SCM file STATE.scm not found (Project state and progress tracking).
  • high PH-100 — Found 128 placeholders, exceeds maximum allowed (0)
  • medium V1-COM-CONTRIBUTING.md — CONTRIBUTING.md file not found (Contribution guidelines).
  • medium V1-COM-CODE_OF_CONDUCT.md — CODE_OF_CONDUCT.md file not found (Code of conduct).
  • medium V1-SEC-001 — SECURITY.md not found for responsible disclosure.
  • medium TEST-001 — Could not determine if this is a Rust or Deno project.
  • medium REL-004 — No SECURITY.md file found
  • medium CLM-006 — docs/plan/FAMILY-ULTRAPLAN.adoc — Documentation references non-existent file: coprocessor.jl
  • medium CLM-006 — docs/plan/FAMILY-ULTRAPLAN.adoc — Documentation references non-existent file: PROOF-STATUS.adoc
  • medium PH-001 — docs/plan/FAMILY-ULTRAPLAN.adoc:126 — Found 'TODO' in: * `Justfile` recipes `readiness`, `build-release` and `test-smoke` are TODO stubs that fail.
  • 168 further finding(s) in files this change does not touch: reported, not graded (0 critical, 4 high).
cipherbot: not_applicable — template default: enrol once the repository implements cryptography
  • ⚪ not applicable: template default: enrol once the repository implements cryptography
accessibilitybot: not_applicable — template default: enrol once the repository serves HTML
  • ⚪ not applicable: template default: enrol once the repository serves HTML

Scope: static findings reported by each row's tool at the named commit. The table grades only findings in files this change touches, so the colour answers "does this change introduce anything?", not "what does the whole repository still carry?". Standing findings are counted in each accordion and in report.json; the baseline filter remains the place where acknowledged debt is recorded. The lane state is the worst GATING row; advisory rows are listed and counted but never set it. Purple, red, yellow and blue grade the worst GRADED finding present; orange is evidence missing, malformed or a scanner that did not run; grey is an explicit scope exclusion with its reason. No row is a security certification. report.json, badge.json and the raw findings are in the verdict-grid artifact on the linked run.

@hyperpolymath
hyperpolymath marked this pull request as ready for review November 15, 2026 10:41
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 15, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-15T10:42:32.355518Z 0e61717 Draft marked ready
🔒 Security Review ✅ Completed 2026-11-15T10:43:05.556098Z 0e61717 Draft marked ready
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@hyperpolymath
hyperpolymath enabled auto-merge (squash) November 15, 2026 10:44
@hyperpolymath
hyperpolymath merged commit 26066d4 into main Nov 15, 2026
50 of 51 checks passed
@hyperpolymath
hyperpolymath deleted the marina/cool-noether-i2rc8g branch November 15, 2026 10:48
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.

3 participants