Skip to content

docs(chit): PMOVESCHIT VISUAL_TOUR — interactive code-walkthrough - #2343

Closed
POWERFULMOVES wants to merge 1 commit into
mainfrom
docs/pmoveschit-visual-tour
Closed

POWERFULMOVES wants to merge 1 commit into
mainfrom
docs/pmoveschit-visual-tour

Conversation

@POWERFULMOVES

Copy link
Copy Markdown
Owner

What

Adds pmoves/docs/PMOVESCHIT/VISUAL_TOUR.md — an interactive, code-grounded walkthrough of CHIT (Cymatic-Holographic Information Transfer) as it actually exists in the codebase, and wires it into the PMOVESCHIT README.

Why

Part of the CHIT tour — turns the CHIT thesis into a runnable, code-anchored tour (CGP packet structure, encoding flow, terminal viz, gateway API, HMAC/anchor security, geometry bus, cross-service map). Reviewer-friendly on-ramp for the CHIT story spine.

Scope

  • pmoves/docs/PMOVESCHIT/VISUAL_TOUR.md (+1044) — the walkthrough
  • pmoves/docs/PMOVESCHIT/README.md (+6/-1) — link/wire-in

Docs-only. 3-dot diff vs main is exactly these 2 files. No secrets — passphrase="your_secret" occurrences are documentation placeholders, not real credentials.

🤖 Generated with Claude Code

…to README

Preserves a 1044-line CHIT visual-tour doc that was sitting untracked in the
working tree (authored 2026-05-20, never committed). Walks CHIT
(Cymatic-Holographic Information Transfer) as it exists in the codebase — runnable,
validate-against-source — rather than as theory. Wires it into the PMOVESCHIT
README doc table + the "Use it" and a new "Video rendering" (Remotion + Pretext)
navigation paths.

Draft: surfaced during working-tree cleanup; opening as draft for owner review
before publish.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@POWERFULMOVES, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 15 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 4511dc45-1deb-462d-9bce-a20a83ac7d13

📥 Commits

Reviewing files that changed from the base of the PR and between 2f72861 and dd3d0ff.

📒 Files selected for processing (2)
  • pmoves/docs/PMOVESCHIT/README.md
  • pmoves/docs/PMOVESCHIT/VISUAL_TOUR.md

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

Comment @coderabbitai help to get the list of available commands.

@github-actions github-actions Bot added the docs Documentation label Aug 2, 2026

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: dd3d0ff32a

ℹ️ 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".

Comment on lines +176 to +179
def build_cgp_from_docx(docx_path: str,
units_mode="paragraphs",
K=8, iters=30, beta=12.0, bins=8, tau=5.0, seed=42,
S=3):

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Describe the encoder that actually exists

Replace this copied legacy implementation with the current backend flow: pmoves/tools/chit_backend.py has no build_cgp_from_docx function and does not run CHR; it reads consciousness-chunks JSONL, embeds it, and clusters with KMeans. Consequently, the advertised encoding walkthrough is not code-grounded, and the later yourfile.docx --out ... --S 3 command also fails because the real CLI requires --input and --output and has no --S option.

Useful? React with 👍 / 👎.

From `pmoves/services/graph-linker/chit_signer.py`:

```python
from pmoves.services.graph-linker.chit_signer import sign_neo4j_node, verify_neo4j_node

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Use an importable graph-linker module path

Change this import to the service's actual loading pattern: graph-linker contains a hyphen, so Python parses this statement as invalid syntax and it can never run. The repository adds pmoves/services/graph-linker to sys.path and imports chit_signer directly, as shown by neo4j_client.py and the signer tests.

Useful? React with 👍 / 👎.

Comment on lines +747 to +749
curl -X POST http://localhost:8086/geometry/decode/text \
-H "Content-Type: application/json" \
-d '{"constellation_ids": ["urban_farming"], "per_constellation": 5}'

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Match the decoder request to the service on port 8086

Use the Hi-RAG v2 request schema here, or point the example at the separate gateway service. Port 8086 is Hi-RAG v2, whose /geometry/decode/text handler reads constellation_id and k; it ignores constellation_ids and per_constellation, so this supposedly runnable command performs no lookup and returns an empty selection rather than decoding urban_farming.

Useful? React with 👍 / 👎.

Comment on lines +1020 to +1022
curl -X POST http://localhost:8105/render \
-H "Authorization: Bearer $JWT" \
-d '{"a2ui_spec": {...}, "format": "mp4", "quality": "high"}'

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Send the raw A2UI spec to the render endpoint

Correct this request to send the A2UI document itself as the body. The /render handler assigns spec = req.body and requires top-level version, animation, and scenes, so the documented {a2ui_spec: ...} wrapper always receives HTTP 400. The handler also reads format from the ?format= query parameter and does not consume quality, making those body fields ineffective.

Useful? React with 👍 / 👎.

"text_layout": {
"engine": "pretext", // ← Pretext engine
"maxWidth": 720,
"lineHeight": 1.4,

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Use a pixel line height in the Pretext example

Replace 1.4 with an appropriate pixel value. resolveTextLayout passes a numeric text_layout.lineHeight directly to Pretext as pixels rather than interpreting it as a CSS multiplier; with the default 36px font, copying this example lays lines only 1.4px apart and produces severely overlapping text.

Useful? React with 👍 / 👎.

Comment on lines +1041 to +1042
| `a2ui.render.started.v1` | job_id, spec_hash, format |
| `a2ui.render.completed.v1` | job_id, url, duration_ms, layout_summary |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Document only the renderer's actual NATS contract

Remove the nonexistent started event and describe the registered completed payload accurately. A repo-wide search finds no producer or contract for a2ui.render.started.v1, while a2ui.render.completed.v1 is registered with required fields such as render_key, scenes, composition_id, and timestamp; it does not publish the documented job_id or presigned url. Consumers built from this table would wait forever for the first event and parse the second incorrectly.

Useful? React with 👍 / 👎.

@POWERFULMOVES

Copy link
Copy Markdown
Owner Author

Closing as duplicate - pmoves/docs/PMOVESCHIT/VISUAL_TOUR.md is already on main via #1847 (squash b36ca9002). The CHIT visual tour work that this PR was attempting landed through the B850 chit-tour refresh lane (#2340) plus the existing #1847. No new content here - this branch is empty against origin/main. Reopen if the original #1847 needs a re-skin to match the current canonical PMOVESCHIT/README.md structure, but that's the lane gated on visual sign-off (PR #2076 DRAFT), not a duplicate merge.

POWERFULMOVES added a commit that referenced this pull request Aug 3, 2026
… findings from #2343)

Re-does the closed #2343 with every command/API verified against the actual code:
- encoder: re-attributes the docx/CHR walkthrough to the CHR prototype
  (Constellation-Harvest-Regularization/app.py) and documents the real production
  auto-mapper chit_backend.py (JSONL→KMeans→CGP) + its real CLI (--input/--output,
  no --S/docx positional).
- graph-linker import: hyphenated path is invalid Python → sys.path.insert + import chit_signer.
- Hi-RAG /geometry/decode/text: body is {constellation_id, k}, not {constellation_ids, per_constellation}.
- A2UI /render: body IS the spec (version/animation/scenes); format via ?format= query; no quality; port 8107 (not 8105).
- Pretext lineHeight is PIXELS (44), not a 1.4 multiplier.
- NATS: a2ui.render.started.v1 does not exist; a2ui.render.completed.v1 payload = render_key/format/duration_ms/scenes/composition_id/layout_summary/timestamp (no job_id/url).

All corrections verified against the live code (chit_backend.py, graph-linker/chit_signer.py,
hi-rag-gateway-v2/routes/geometry.py, a2ui-renderer/src/index.ts + pretextLayout.ts,
contracts/topics.json). Docs-only.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
POWERFULMOVES added a commit that referenced this pull request Aug 3, 2026
… findings from #2343) (#2352)

Re-does the closed #2343 with every command/API verified against the actual code:
- encoder: re-attributes the docx/CHR walkthrough to the CHR prototype
  (Constellation-Harvest-Regularization/app.py) and documents the real production
  auto-mapper chit_backend.py (JSONL→KMeans→CGP) + its real CLI (--input/--output,
  no --S/docx positional).
- graph-linker import: hyphenated path is invalid Python → sys.path.insert + import chit_signer.
- Hi-RAG /geometry/decode/text: body is {constellation_id, k}, not {constellation_ids, per_constellation}.
- A2UI /render: body IS the spec (version/animation/scenes); format via ?format= query; no quality; port 8107 (not 8105).
- Pretext lineHeight is PIXELS (44), not a 1.4 multiplier.
- NATS: a2ui.render.started.v1 does not exist; a2ui.render.completed.v1 payload = render_key/format/duration_ms/scenes/composition_id/layout_summary/timestamp (no job_id/url).

All corrections verified against the live code (chit_backend.py, graph-linker/chit_signer.py,
hi-rag-gateway-v2/routes/geometry.py, a2ui-renderer/src/index.ts + pretextLayout.ts,
contracts/topics.json). Docs-only.

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
POWERFULMOVES added a commit that referenced this pull request Aug 3, 2026
…SHIPPED + 3-PR triage batch (#2354)

The 2026-08-02 closeout (PR #2345) left Lane 5 as a forward-looking RELEASE
("squash pending — PR #2344 open") and Lane 2228 as a forward-looking CLAIM
("this CLAIM becomes a RELEASE on admin-merge"). Both are now actually
shipped. Plus a 3-PR triage batch that was DIRTY/BEHIND on main `a5320d7e3a`.

What lands in the AGNOTE:
  - Lane 5 RELEASE: confirms squash 2cba394 (PR #2344) with full validation
    + the 2 follow-up items still open (village-gate wire-in + TOKENISM_ATTRIBUTION
    interest→limits migration).
  - Lane 2228 RELEASE: promotes the PR #2349 CLAIM to RELEASE, names the actual
    squash 8a377b3, references Issue #2228 closure.
  - 3-PR triage batch: PR #2352 (chit-visual-tour-codegrounded, the real answer
    to #2343 I closed yesterday), PR #2346 (yt-cookies fresh key), PR #2353
    (monitoring mount paths — the VHDX-fill root cause).

Refs: #2228
Squashes referenced: 2cba394, 8a377b3, 6178bda, 1bf7ed6, 2dcbf25

Co-authored-by: Shaela Bello <slbello@uncg.edu>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant