Skip to content

docs: acknowledge Pane-A in core docs and rule files#21

Merged
hyperpolymath merged 2 commits intomainfrom
claude/issue-20-four-pane-drift
Apr 30, 2026
Merged

docs: acknowledge Pane-A in core docs and rule files#21
hyperpolymath merged 2 commits intomainfrom
claude/issue-20-four-pane-drift

Conversation

@hyperpolymath
Copy link
Copy Markdown
Owner

@hyperpolymath hyperpolymath commented Apr 30, 2026

Summary

Closes #20.

src/View.res renders four panes (Pane-A, Pane-L, Pane-N, Pane-W) and the README table at README.adoc:99-110 enumerates all four, but several adjacent docs and rule files still framed the layout as three panes (no Pane-A). This PR reconciles the most direct "three panel(s)/pane(s)" claims with the implementation, including the user-visible Help panel.

Changes

Doc + rule-file drift (commit 1)

  • README.adoc:92 — section heading "Three-Pane Parallel Layout" → "Four-Pane Parallel Layout".
  • .claude/CLAUDE.md:51 — "106 panels across three panes …" → four panes, with Panel-A added and a one-line note on the Binary Star core (L + N orbiting W) plus Panel-A's ambient role.
  • .machine_readable/6a2/META.a2ml — Binary Star decision (line 24) now enumerates four panels (three orbital + one ambient); the three-pane-layout key (line 108) is renamed four-pane-layout, with position called out as design intuition rather than architectural fact.
  • .machine_readable/6a2/ECOSYSTEM.a2ml:76-77 — VeriSimDB mapping reframed as a mapping to the L/N/W panes of PanLL's four-pane layout (Panel-A is ambient substrate, not part of the VCL-DT mapping).
  • Six rule files — binary-star Decision (line 161) extended to four panel types with Panel-A added; the Why line distinguishes the Binary Star orbital core (L + N around W) from Panel-A's ambient role:
    • .cursorrules
    • .clinerules
    • .github/copilot-instructions.md
    • .junie/guidelines.md
    • .q/rules/coordination.md
    • .claude/CLAUDE.generated.md

User-visible help content (commit 2)

  • src/core/HelpContent.res:
    • "welcome" entry body — unified three-panel workspaceunified four-panel workspace (Panel-A ambient substrate, Panel-L logic/symbolic, Panel-N neural, Panel-W world/barycentre).
    • "three-panel-layout" entry — id and title renamed to four-panel-layout; body rewritten to introduce Panel-A as ambient substrate, clarify Panel-L's letter as "Logic" rather than "left", and replace the (left)/(centre)/(right) position framing with flow-and-perspective framing per the architectural model.
    • Keywords extended — keep three-panel for backward search, add four-panel, panel-a, ambient, binary star.

The renamed three-panel-layout help-anchor id has no inbound references elsewhere in the repo (verified via grep) — safe rename.

Out of scope (deliberately)

  • Rule file lines 101 and 196 — these are descriptions of the Binary Star architecture, which is genuinely a three-pane metaphor (L + N orbiting W). Correct as written.
  • Rule file lines 103 and 186 — also Binary Star claims, accurate when read as referring to Binary Star types specifically. Reframing them so they remain accurate in the presence of Panel-A requires more nuance than this PR aims for; left for a follow-up.
  • README.adoc:287 (v0.2.0 component enumeration) — snapshot of v0.2.0 status; PaneA may not have been functional at that release, so left unmodified.

Test plan

  • No code changes; doc-only.
  • three-panel-layout help-anchor id has no inbound references elsewhere in the repo.
  • three-pane-layout key (renamed in META.a2ml) has no other consumers across the hyperpolymath org (org-wide code search returns only the file itself).
  • Help content rebuild reflects the new "Understanding the Four-Panel Layout" entry (run npx rescript build + the help indexer if there is one).

src/View.res renders four panes (Pane-A, Pane-L, Pane-N, Pane-W)
and the README table at lines 99-110 enumerates all four, but
several adjacent docs and rule files still framed the layout as
three panes (no Pane-A). This commit reconciles the most direct
"three panel(s)/pane(s)" claims with the implementation.

Touched:

- README.adoc: section heading "Three-Pane Parallel Layout"
  -> "Four-Pane Parallel Layout" (the table immediately below it
  already lists four).
- .claude/CLAUDE.md: "106 panels across three panes ..."
  -> four panes, with Panel-A added and a one-line note on the
  Binary Star core (L + N orbiting W) plus Panel-A's ambient role.
- .machine_readable/6a2/META.a2ml: Binary Star decision now
  enumerates four panels (three orbital + one ambient); the
  three-pane-layout key is renamed four-pane-layout, with
  position called out as design intuition rather than
  architectural fact (architectural relationship is by flow +
  viewing perspective).
- .machine_readable/6a2/ECOSYSTEM.a2ml: VeriSimDB mapping
  reframed as a mapping to the L/N/W panes of PanLL's four-pane
  layout (with Panel-A as ambient substrate, not part of the
  VCL-DT mapping).
- Six rule files (.cursorrules, .clinerules,
  .github/copilot-instructions.md, .junie/guidelines.md,
  .q/rules/coordination.md, .claude/CLAUDE.generated.md):
  binary-star "Decision: Three panel types ..." -> "Four panel
  types" with Panel-A added; the Why line now distinguishes
  the Binary Star orbital core (L + N around W) from Panel-A's
  ambient role.

Out of scope for this PR (Binary Star descriptions left intact):

- Lines 101 and 196 in the rule files are descriptions of the
  Binary Star architecture, which is genuinely a three-pane
  metaphor (L + N orbiting W). They are correct as written.
- Line 103 ("The three panel types serve fundamentally different
  roles") and line 186 ("Binary Star model has exactly three
  types") are also Binary Star claims; they are accurate when
  read as referring to Binary Star types specifically. Reframing
  them so they remain accurate in the presence of Panel-A
  requires more nuance than this PR aims to land — left for a
  follow-up.
- README.adoc:287 (v0.2.0 component enumeration) is a snapshot
  of v0.2.0 status; PaneA may not have been functional at that
  release, so left unmodified.

Refs: #20

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@chatgpt-codex-connector
Copy link
Copy Markdown

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

HelpContent.res had two stale entries that surfaced "three-panel"
framing to operators in the Help panel:

- "welcome" entry body (line 44): "...unified three-panel workspace"
  -> "...unified four-panel workspace (Panel-A ambient substrate,
  Panel-L logic/symbolic, Panel-N neural, Panel-W world/barycentre)".
- "three-panel-layout" entry (lines 56-64): renamed id and title to
  four-panel-layout, body rewritten to introduce Panel-A as ambient
  substrate, Panel-L's letter clarified as "Logic" rather than "left",
  and the "(left)/(centre)/(right)" position framing replaced with
  flow-and-perspective framing per the architectural model.
- Keywords on the layout entry extended: keep "three-panel" for
  backward search, add "four-panel", "panel-a", "ambient",
  "binary star".

The "three-panel-layout" id is referenced in only this file — no
inbound help-anchor links break.

Refs: #20
@sonarqubecloud
Copy link
Copy Markdown

@hyperpolymath hyperpolymath merged commit 37129cb into main Apr 30, 2026
16 of 27 checks passed
@hyperpolymath hyperpolymath deleted the claude/issue-20-four-pane-drift branch April 30, 2026 06:41
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.

Rule files and README still describe a three-pane layout; impl has four (Pane-A added)

1 participant