docs(isoz): identity rebrand to IsoZ + Geometric Determinism theory (Cycle 1) - #25
Merged
Merged
Conversation
- docs/theory/GEOMETRIC_DETERMINISM.md: synthesis of the 3 decks (Geometry of Truth / Geometric Determinism / ZuluYokohama Protocol) into the AxiomZ/Jones Framework, with an explicit buildable-core vs aspirational-vision split. - docs/theory/TRUTH_RESOLVER_ROADMAP.md: v1 (shipped) -> v2 sheaf coherence -> v3 commit-vs-resolve -> v4 Oracle seam upgrade path. - specs/2026-06-06-isoz-identity-design.md: Cycle-1 rebrand to IsoZ (hybrid Z-brand, honest substance), README rewrite around the intent=code=value thesis, repo rename, doc demotions; Cycle 2 = code-symbol renames, Cycle 3 = website. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…rom realized activity:states Bind the IsoZ identity isomorphically across concept/framework/process/pattern, grounded in actual merged work (PRs #17-#24, truth_resolver, docs/theory), with semantic truth as the invariant (every assertion traces to a realized activity:state; vision-tier labeled roadmap). Process = product.
6 tasks: README rewrite (full new content inline), CLI/plugin/manifesto/brand string demotions, and a GATED repo rename. Strings + identity only; no code symbols (Cycle 2) or website (Cycle 3). Every assertion traces to a realized activity:state per spec section 0.
- README rewritten around the intent=code=value thesis; honest 'what it is', two-layer credit (Superpowers/autoresearch credited), Feature Studio run instructions, honest gate descriptions, links docs/theory with vision/seed split - CLI banner/strings, plugin manifest name+description, manifesto, brand doc: unify to IsoZ; drop Quantum-Resistant/cryptographic/Infinite-Recursive-swarm/ MaxVal false-capability terms (manifesto swarm line corrected to [DEMO] reality) - strings/docs only; no code symbols/module names (Cycle 2), no website (Cycle 3)
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis PR executes Cycle 1 of the IsoZ rebranding: rewrites README and brand identity, updates CLI and plugin manifest user-facing strings, revises the ISOMORPHISM_MANIFESTO to the IsoZ model, and adds design/spec/theory/roadmap documents for the intent≡code≡value gate. ChangesIsoZ Identity Rebrand — Cycle 1
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 6
🤖 Prompt for all review comments with AI agents
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 `@assets/brand/BRAND_IDENTITY.md`:
- Around line 1-2: The markdown headings are missing surrounding blank lines
which triggers MD022; locate the top-level heading "# IsoZ — Brand Identity" and
the subheading "## Brand Identity & Logo Concepts (jtechAi Labs)" (and the other
headings referenced) and ensure there is an empty line above and below each
heading so each heading is separated from adjacent content; update the document
to add those blank lines consistently for the other heading pairs mentioned to
clear the markdownlint warnings.
In `@docs/ISOMORPHISM_MANIFESTO.md`:
- Around line 3-4: The markdown headings (e.g., "## The Doctrine of IsoZ" and
the other headings referenced) are missing the required surrounding blank lines
causing markdownlint MD022 failures; edit the document to ensure each heading
has a single blank line before and after it (normalize spacing for all affected
headings such as the ones at "The Doctrine of IsoZ" and the subsequent headings
listed in the comment) so the file passes markdownlint-cli2 MD022 checks.
In `@docs/superpowers/plans/2026-06-06-isoz-identity.md`:
- Line 91: Several fenced code blocks in the document are missing a language tag
and surrounding blank lines which triggers markdownlint fence violations; locate
each triple-backtick fence (``` occurrences) and normalize them by adding an
appropriate fence language (e.g., ```text or ```bash or ```md as context
requires) and ensure there is a blank line before the opening fence and a blank
line after the closing fence so all fenced blocks follow markdownlint rules.
- Around line 97-99: The script uses a hard-coded absolute path ("cd
/c/Users/Deving-1/rs-isoz") making the verification commands non-portable;
change that to a repo-relative directory resolution (for example use git
rev-parse --show-toplevel or a $REPO_ROOT variable) and run the grep checks
against README.md in the repo root (e.g., cd to the repo root or prefix
README.md with $REPO_ROOT/README.md). Update the same pattern found in the other
occurrences referenced (lines around the grep commands at 257–259) so all checks
are repository-relative and work for other contributors.
In `@docs/superpowers/specs/2026-06-06-isoz-identity-design.md`:
- Line 20: The spec currently uses the thesis equation "intent ≡ context ≡
value" which conflicts with the canonical "intent ≡ code ≡ value"; update the
sentence in the IsoZ / `truth_resolver` description to use "intent ≡ code ≡
value" and scan the `truth_resolver` mention and surrounding spec text to
replace any other occurrences of "context" in the thesis with "code" so the
canonical equation is consistent across the document.
In `@scripts/cli.py`:
- Around line 3-4: Update the CLI copy to use the new honest/demo framing:
replace legacy phrases like "maxval vectors" and "infinite recursive evolution
matrix" found in the module docstring and the CLI help/description strings
(e.g., the top-level docstring and the argparse parser description/help texts
used in main or where parser = argparse.ArgumentParser(...) is defined) with the
new wording that includes the “[DEMO]” tag and the “honest/demo” phrasing used
elsewhere in this change set so all displayed strings (the module header and the
parser help/description used around the CLI setup) are consistent.
🪄 Autofix (Beta)
❌ Autofix failed (check again to retry)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 7220d161-0dc1-4b39-8efe-3b891d1bb2e5
📒 Files selected for processing (9)
.claude-plugin/plugin.jsonREADME.mdassets/brand/BRAND_IDENTITY.mddocs/ISOMORPHISM_MANIFESTO.mddocs/superpowers/plans/2026-06-06-isoz-identity.mddocs/superpowers/specs/2026-06-06-isoz-identity-design.mddocs/theory/GEOMETRIC_DETERMINISM.mddocs/theory/TRUTH_RESOLVER_ROADMAP.mdscripts/cli.py
| ## License | ||
|
|
||
| See [LICENSE](LICENSE). The inherited Superpowers and autoresearch layers retain their original authors' licenses and credit. | ||
| ``` |
There was a problem hiding this comment.
Fix markdownlint fence violations in the plan document.
Static analysis flags missing fence language and missing blank lines around several fenced blocks. This can fail docs linting and should be normalized in this file.
Also applies to: 106-106, 135-135, 165-165, 185-185, 197-197, 224-224, 244-244, 251-251, 265-265
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 91-91: Fenced code blocks should be surrounded by blank lines
(MD031, blanks-around-fences)
[warning] 91-91: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/superpowers/plans/2026-06-06-isoz-identity.md` at line 91, Several
fenced code blocks in the document are missing a language tag and surrounding
blank lines which triggers markdownlint fence violations; locate each
triple-backtick fence (``` occurrences) and normalize them by adding an
appropriate fence language (e.g., ```text or ```bash or ```md as context
requires) and ensure there is a blank line before the opening fence and a blank
line after the closing fence so all fenced blocks follow markdownlint rules.
Source: Linters/SAST tools
…nesty, doc lint) - spec: fix thesis-equation drift `intent =\xC2\xA0context =\xC2\xA0value` -> `intent = code = value` (CodeRabbit Major; canonical form used everywhere else in the doc set). - cli.py: demote remaining overclaim strings (module docstring, status table title, evolve --help) to honest IsoZ/[DEMO] framing. STRINGS ONLY; no code symbols renamed (those stay Cycle 2). - BRAND_IDENTITY / ISOMORPHISM_MANIFESTO: fix MD022 heading-spacing (blank lines). - plan: replace machine-specific absolute paths with repo-relative commands. CodeRabbit finding on markdownlint fences in the internal plan doc is intentionally skipped (non-gating linter, internal process artifact) - explained in PR reply. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Collaborator
Author
CodeRabbit triage — pushed in 9e0b6c0Thanks for the review. Verified each finding against the current tree before acting; 5 of 6 applied, 1 skipped with reason. Applied:
Skipped (with reason):
No behavior changes; this PR remains strings/docs only. |
# Conflicts: # README.md
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
README.md (1)
16-16:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winAvoid hardcoding implementation line counts in README claims.
Line 16 hardcodes
187-line, which will drift and make the README stale. Prefer capability wording over exact LOC.Suggested change
-**Honesty split:** the *theory decks are the vision*; the *code is the current seed*. Anything not yet in code (ATFT, the Ternary-Crystal hardware substrate, sheaf-v2) is labeled **roadmap**, never capability. Today, `truth_resolver` is a 187-line deterministic gate that scores intent/context/value overlap; that is the real, shipped state. +**Honesty split:** the *theory decks are the vision*; the *code is the current seed*. Anything not yet in code (ATFT, the Ternary-Crystal hardware substrate, sheaf-v2) is labeled **roadmap**, never capability. Today, `truth_resolver` is a deterministic gate that scores intent/context/value overlap; that is the real, shipped state.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@README.md` at line 16, Remove the hardcoded "187-line" reference in the README and rephrase the sentence to describe the current capability of the truth_resolver rather than exact LOC; update the fragment mentioning `truth_resolver` so it reads something like "Today, `truth_resolver` is a deterministic gate that scores intent/context/value overlap" or similar capability-focused wording to avoid stale line-count claims.
🤖 Prompt for all review comments with AI agents
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 `@README.md`:
- Line 3: The README line "Prototype 0.001a — in dev. Last human update 6 Jun 26
(mr.orange@jtech.ai)" exposes a personal email; remove the direct PII by editing
that line in README.md to omit the personal address and replace it with a
neutral contact channel (e.g., project issue tracker, support@jtech.ai, or "See
CONTRIBUTING or open an issue") and keep the timestamp/version text unchanged;
ensure the change references the original phrase so reviewers can verify the
replacement.
---
Outside diff comments:
In `@README.md`:
- Line 16: Remove the hardcoded "187-line" reference in the README and rephrase
the sentence to describe the current capability of the truth_resolver rather
than exact LOC; update the fragment mentioning `truth_resolver` so it reads
something like "Today, `truth_resolver` is a deterministic gate that scores
intent/context/value overlap" or similar capability-focused wording to avoid
stale line-count claims.
🪄 Autofix (Beta)
✅ Autofix completed
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 5f5bbceb-e823-41d1-bad2-6983822ff496
📒 Files selected for processing (1)
README.md
| -mr.orange@jtech.ai | ||
| # IsoZ | ||
|
|
||
| > Prototype 0.001a — in dev. Last human update 6 Jun 26 (mr.orange@jtech.ai). |
There was a problem hiding this comment.
Remove direct personal contact info from public README.
Line 3 exposes a personal email address in a top-level public document. That creates avoidable PII/privacy risk and long-term maintenance overhead for contact ownership.
Suggested change
-> Prototype 0.001a — in dev. Last human update 6 Jun 26 (mr.orange@jtech.ai).
+> Prototype 0.001a — in dev. Last human update: June 6, 2026.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| > Prototype 0.001a — in dev. Last human update 6 Jun 26 (mr.orange@jtech.ai). | |
| > Prototype 0.001a — in dev. Last human update: June 6, 2026. |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@README.md` at line 3, The README line "Prototype 0.001a — in dev. Last human
update 6 Jun 26 (mr.orange@jtech.ai)" exposes a personal email; remove the
direct PII by editing that line in README.md to omit the personal address and
replace it with a neutral contact channel (e.g., project issue tracker,
support@jtech.ai, or "See CONTRIBUTING or open an issue") and keep the
timestamp/version text unchanged; ensure the change references the original
phrase so reviewers can verify the replacement.
CodeRabbit (re-review): "187-line" will drift stale -> capability wording. Aligns with the README's own anti-overclaim stance (an exact count is a claim that decays into a falsehood over time). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Collaborator
Author
|
Re-review nit applied in db2ec33: dropped the hardcoded That closes every actionable item across both review rounds (6 + 1): thesis-equation drift, CLI overclaim strings, MD022 spacing, absolute paths, and the LOC count — all applied; the internal-plan-doc markdownlint fences skipped with reason (non-gating, nested-fence artifacts). The README also now reconciles the parallel |
|
Note Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it. Autofix skipped. No unresolved CodeRabbit review comments with fix instructions found. |
|
Note Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it. Fixes Applied SuccessfullyFixed 2 file(s) based on 1 unresolved review comment. Files modified:
Commit: The changes have been pushed to the Time taken: |
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.
IsoZ — identity rebrand + Geometric Determinism theory foundation (Cycle 1)
Who is submitting this PR? (required)
claude-opus-4-8) orchestration; opus-tier subagents (exact minor not surfaced; likely 4.8).What problem are you trying to solve?
The project had a four-way fragmented identity (repo RotarySlider · README H1 Autoresearch Superpowers · plugin rotary-slider-matrix · website Surface & Structure UI) and language that overclaimed the code — a session audit found the README was two documents stapled together and surfaced false-capability terms ("Quantum-Resistant Cryptography Gate", Bandit mislabeled as "cryptographic", an "Infinite Recursive LLM Swarm" that is actually a
[DEMO]flag-flip). A visitor could not tell what the project is called, who makes it, or what it actually does.What does this PR change?
Unifies the identity under one honest brand — IsoZ (from isomorphism: the
intent ≡ code ≡ valuethesis) — and rewrites the README around what the project truly is: a Feature Studio (Next.js + R3F + FastAPI + Svelte) over a pluggable gate framework, whose thesis is the deterministictruth_resolver. It demotes user-facing overclaim strings to honest descriptions (CLI banner, plugin manifest, manifesto, brand doc), credits the inherited Superpowers/autoresearch layers honestly, documents the previously-undocumented Feature Studio, and adds adocs/theory/foundation (synthesis of the author's three theory decks + atruth_resolverroadmap) with an explicit vision-vs-shipped-seed honesty split. Strings/docs only — no code symbols/module names (deferred to Cycle 2) and no website (Cycle 3).Is this change appropriate for the core library?
No. Fork-specific rebrand. Internal fork PR.
What alternatives did you consider?
Does this PR contain multiple unrelated changes?
No. One problem: unify the identity to IsoZ and bring user-facing language into isomorphism with the code. The theory docs ground the thesis the rebrand asserts.
Existing PRs
[DEMO]) and thetruth_resolver(feat(truth-resolver): alignment-gating prototype over intent/context/value #19). No prior identity/rebrand PR exists.Environment tested
Verification (all green): README H1 =
# IsoZ; zero residual ofQuantum-Resistant/Infinite Recursive LLM Swarm/cryptographic security checks;truth_resolver+docs/theory/+ studio run-instructions + upstream credit all present;scripts/cli.pyparses (ast.parseOK);.claude-plugin/plugin.jsonis valid JSON; brand/manifesto identity + false-capability terms = 0. No code symbols/module names changed.New harness support
N/A.
Evaluation
N/A for skill evals — documentation/identity rebrand. Verified by per-file residual-overclaim greps + presence greps + parse/JSON validity, and grounded in spec §0: every IsoZ assertion traces to a realized activity:state (merged PRs #17–#24 +
truth_resolver); vision-tier (ATFT/Ternary-Crystal/sheaf-v2) labeled roadmap, never capability.Rigor
Human review
Summary by CodeRabbit
Documentation
Rebranding
Manifest & Descriptions
New Features