Repository navigation
HERESY FLAGS: Add Faith of the Cloth review notices to all Loganic Swarm contaminated files - #687
Conversation
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
Reviewer's GuideThis PR adds a standardized "HERESY REVIEW PENDING" danger notice to all LEVELSET-related protocol markdown files that reference Loganic Swarm, aligning them with existing quarantine patterns and directing doctrinal review by Faith of the Cloth. Flow diagram for Faith of the Cloth heresy review processflowchart TD
FP[FlaggedProtocol HERESY REVIEW PENDING] --> RC[FaithOfTheClothReview]
RC --> Q[QuarantineWithHeresyFlag]
RC --> R[RehabilitateWithLoganCorrection]
RC --> D[DeprecateWithRedirect]
RC --> O[OtherResolutionPerDoctrine]
FP --> I[Issue686Reference]
FP --> G[GEMINIAEUSReference]
FP --> T[TRIUNE_TRIPTYCH_TRIUMVIRATEReference]
File-Level Changes
Possibly linked issues
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Review limit reached
Next review available in: 26 minutes Limit details: You’ve used all 1 included review currently available under your plan. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (12)
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
There was a problem hiding this comment.
Hey - I've found 1 issue, and left some high level feedback:
- Since the heresy notice block is identical across all flagged files, consider extracting it into a shared snippet/partial or reference macro so future wording changes only need to be made in one place.
- Verify that the placement of the HERESY REVIEW block (immediately after frontmatter separators) matches your intended structure for all protocol documents to avoid inconsistent rendering or parsing by any tooling that consumes these files.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Since the heresy notice block is identical across all flagged files, consider extracting it into a shared snippet/partial or reference macro so future wording changes only need to be made in one place.
- Verify that the placement of the HERESY REVIEW block (immediately after frontmatter separators) matches your intended structure for all protocol documents to avoid inconsistent rendering or parsing by any tooling that consumes these files.
## Individual Comments
### Comment 1
<location path="ARISE.md" line_range="23" />
<code_context>
+> This document is flagged as contaminated by the Loganic Swarm heresy.
+> Authority claim in body (`Loganic Swarm`) conflicts with frontmatter (LOGAN).
+> Drafted post-TRIPLEX NIGHT (2026-04-27).
+> **DO NOT USE** as clean governance authority until reviewed and rehabilitated by Logan or ordained Faith of the Cloth.
+>
+> See: Issue #686
</code_context>
<issue_to_address>
**issue (typo):** The phrase "or ordained Faith of the Cloth" is grammatically awkward; consider adding "by" or rephrasing.
The clause "until reviewed and rehabilitated by Logan or ordained Faith of the Cloth" lacks parallel structure. Consider revising to something like "…by Logan or by the ordained Faith of the Cloth" or "…by Logan or an ordained member of the Faith of the Cloth" to improve clarity and grammar.
```suggestion
> **DO NOT USE** as clean governance authority until reviewed and rehabilitated by Logan or by the ordained Faith of the Cloth.
```
</issue_to_address>Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
There was a problem hiding this comment.
Pull request overview
This PR adds a standardized Obsidian callout warning block (“HERESY REVIEW PENDING - Faith of the Cloth”) near the top of the LEVELSET component protocol notes to clearly flag the known authority-conflict contamination described in Issue #686.
Changes:
- Insert a
[!DANGER]callout quarantine notice immediately after frontmatter in the affected protocol notes. - Standardize the notice text to reference the authority conflict and point to Issue #686 plus related vault notes.
Reviewed changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| ARISE.md | Adds the standardized heresy review callout after frontmatter. |
| AWAKEN.md | Adds the standardized heresy review callout after frontmatter. |
| CONTEXT.md | Adds the standardized heresy review callout after frontmatter. |
| CONFERENCE.md | Adds the standardized heresy review callout after frontmatter. |
| CONVENE.md | Adds the standardized heresy review callout after frontmatter. |
| LEVELSET.md | Adds the standardized heresy review callout after frontmatter. |
| ORIENT.md | Adds the standardized heresy review callout after frontmatter. |
| REPORT.md | Adds the standardized heresy review callout after frontmatter. |
| RISE.md | Adds the standardized heresy review callout after frontmatter. |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 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 `@CONVENE.md`:
- Around line 16-25: The document has conflicting authority claims between the
frontmatter and the body, so align them to a single source of truth. Update the
`authority` metadata and the `## Authority` section in CONVENE.md so they match,
or remove the duplicate body claim entirely if the frontmatter should remain
authoritative. Use the existing authority markers in the frontmatter and the `##
Authority` heading to locate and reconcile the mismatch.
In `@ORIENT.md`:
- Around line 18-27: The document has conflicting authority values between
frontmatter and body copy, so align them to a single source of truth. Update the
body section that mentions the authority so it matches the frontmatter value
used by ORIENT.md, or adjust the frontmatter if the body is the intended
canonical value. Make the change in the authority-related heading/text and any
nearby references so the document is internally consistent.
🪄 Autofix (Beta)
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: CHILL
Plan: Pro Plus
Run ID: 0af2e1b2-3ebe-4609-987b-bd514666c960
📒 Files selected for processing (9)
ARISE.mdAWAKEN.mdCONFERENCE.mdCONTEXT.mdCONVENE.mdLEVELSET.mdORIENT.mdREPORT.mdRISE.md
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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 `@LOGAN.md`:
- Around line 74-82: LOGAN.md is currently at the repository root, which
violates the path rules; move the document to an approved non-root location
while keeping its contents intact. Update any references that point to LOGAN.md
so they use the new location, and ensure the relocated file remains discoverable
through the existing documentation structure.
🪄 Autofix (Beta)
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: CHILL
Plan: Pro Plus
Run ID: 5a147214-e095-4c97-84d5-25be27ae289f
📒 Files selected for processing (2)
LOGAN 2.mdLOGAN.md
|
Sourcery's suggestion of "a shared snippet/partial or reference macro so future wording changes only need to be made in one place" is elegantly handled by Obsidian's native ![[Embedded Note Link]] convention. |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 12 out of 12 changed files in this pull request and generated 1 comment.
Suppressed comments (3)
!/HERESY-ALIGNMENT-RECORD-2026-06-29.md:47
- These tables use
||at the start of each row, which many Markdown renderers interpret as an extra empty leading column (or render inconsistently). Use standard Markdown table syntax with single leading/trailing pipes (e.g.,| Protocol | ... |) to keep rendering consistent across GitHub/Obsidian/site generators.
| Protocol | Version | Approval Date | Authority | Status |
|----------|---------|---------------|-----------|--------|
| AWAKEN | v1.0-2026-04-27.md | 2026-04-22 | LOGAN | ✅ CLEAN |
| ORIENT | v1.0-2026-04-27.md | 2026-04-22 | LOGAN | ✅ CLEAN |
| CONTEXT | v1.0-2026-04-27.md | 2026-04-22 | LOGAN | ✅ CLEAN |
| CONFERENCE | v1.0-2026-04-27.md | 2026-04-22 | LOGAN | ✅ CLEAN |
| CONVENE | v1.0-2026-04-27.md | 2026-04-22 | LOGAN | ✅ CLEAN |
| RISE | v1.0-2026-04-27.md | 2026-04-22 | LOGAN | ✅ CLEAN |
| REPORT | v1.0-2026-04-27.md | 2026-04-22 | LOGAN | ✅ CLEAN |
| ARISE | v1.0-2026-04-27.md | Draft | LOGAN | ✅ CLEAN |
| LEVELSET | (superset) | — | LOGAN | ✅ CLEAN |
!/HERESY-ALIGNMENT-RECORD-2026-06-29.md:9
- Filenames with spaces/punctuation (and the
!/directory name for this file) can be fragile for tooling (shell scripts, static-site generators, link resolvers) unless everything is consistently quoted/escaped. If these docs are processed by automation, consider renaming to path-safe conventions (e.g.,rules/wizards-rules.md, avoid!folders) or document the required escaping rules for contributors and CI.
- "! - Wizard's Rules.md"
RISE.md:26
- This warning block is duplicated across many files; future edits (issue number changes, wording changes, additional links) will require updating every file. If your doc toolchain supports includes/transclusion, consider extracting this into a shared snippet; otherwise, consider shortening the per-file banner to a stable pointer (e.g., link to the single alignment record) to reduce duplication and drift.
> [!DANGER] HERESY REVIEW PENDING - Faith of the Cloth
> This document is flagged as contaminated by the Loganic Swarm heresy.
> Authority claim in body (`Loganic Swarm`) conflicts with frontmatter (LOGAN).
> Drafted post-TRIPLEX NIGHT (2026-04-27).
> **DO NOT USE** as clean governance authority until reviewed and rehabilitated by Logan or by the ordained Faith of the Cloth.
>
> See: Issue #686
> Related: [[GEMINIAEUS]] | [[TRIUNE-TRIPTYCH-TRIUMVIRATE]]
Not up to standards ⛔🔴 Issues
|
| Category | Results |
|---|---|
| BestPractice | 3 minor |
| CodeStyle | 11 minor |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
Hyrax ReviewThe review hit an unexpected error before it could finish — this is on our side and doesn't reflect on your pull request. You weren't charged for it. Push another commit and Hyrax will try again. If it keeps happening, reach out from the Hyrax dashboard. Reference: |
Quote frontmatter references and align the CONVENE notice spacing with the shared review-banner format. Co-authored-by: Manus AI <noreply@manus.im>
|
Insufficient balance to process this code review. Please add funds or upgrade your plan in billing. |
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
|
🤖 Review skipped: Repository rate limit exceeded. Free accounts are limited to 2 reviews per 4 hours per repository. Upgrade to a paid plan for unlimited reviews. |
✅ Precogs scan complete — No security issues foundCommit
✅ Passed checks (3)
💬 Precogs.ai · Detect. Fix. Merge. |
|
👋 Rams is installed but not yet activated. Sign up at rams.ai to start getting automated design reviews on your pull requests. |
PR Analysis SummaryChange Metrics
Risk factors:
Classification
Files by Type
💡 Recommendations
Analyzed by Woden Tagger • Automated PR insights for better code reviews
💡 Want enhanced Github Projects/Notes and to turn Issues into a Service Desk? Check out Woden Desk on the GitHub Marketplace |
There was a problem hiding this comment.
inspect review
Triage: 27 entities analyzed | 0 critical, 0 high, 11 medium, 16 low
Verdict: standard_review
Findings (0)
Reviewed by inspect | Entity-level triage found 0 high-risk changes
|
No critical paths modified ✅ |
🏆 Insight Code — Accessibility Review
Score
|
| Severity | Checks failed | Occurrences |
|---|---|---|
| 🔴 Critical | 0 | 0 |
| 🟡 Warning | 0 | 0 |
| 🔵 Info | 0 | 0 |
✅ No accessibility issues in this diff
Every check passed on the files you changed. Nice work.
Whole-project findings are filed as issues on push. 🤖 Insight Code · Scan eb96df27-749b-432e-8028-b1d8d19dbde5
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 12 out of 12 changed files in this pull request and generated no new comments.
Suppressed comments (5)
AWAKEN.md:21
- GitHub-flavored Markdown alerts don’t support a
[!DANGER]type (supported keywords are typicallyNOTE,TIP,IMPORTANT,WARNING,CAUTION). If these files are meant to render on GitHub, switch to a supported keyword (e.g.,WARNINGorCAUTION) or use a normal heading/blockquote so the intent renders consistently.
> [!DANGER] HERESY REVIEW PENDING - Faith of the Cloth
> This document is flagged as contaminated by the Loganic Swarm heresy.
RISE.md:26
- This warning banner is duplicated verbatim across many files in the PR, which makes future updates error-prone (one change requires editing many docs). Consider centralizing it (e.g., a single canonical ‘Quarantine Notice’ doc that each file links to, or a small include mechanism if your Markdown toolchain supports transclusion) so edits stay consistent.
> [!DANGER] HERESY REVIEW PENDING - Faith of the Cloth
> This document is flagged as contaminated by the Loganic Swarm heresy.
> Authority claim in body (`Loganic Swarm`) conflicts with frontmatter (LOGAN).
> Drafted post-TRIPLEX NIGHT (2026-04-27).
> **DO NOT USE** as clean governance authority until reviewed and rehabilitated by Logan or by the ordained Faith of the Cloth.
>
> See: Issue #686
> Related: [[GEMINIAEUS]] | [[TRIUNE-TRIPTYCH-TRIUMVIRATE]]
CONVENE.md:23
- Plain text like
Issue #686may not auto-link in common renderers. If these are intended to link to repository artifacts, prefer#686for issues/PRs or a full URL so readers can navigate directly.
> See: Issue #686
!/HERESY-ALIGNMENT-RECORD-2026-06-29.md:47
- The table rows start with
||, which will render as an empty first column (or break table formatting depending on the renderer). Use a single leading|per row so the table renders correctly.
| Protocol | Version | Approval Date | Authority | Status |
|----------|---------|---------------|-----------|--------|
| AWAKEN | v1.0-2026-04-27.md | 2026-04-22 | LOGAN | ✅ CLEAN |
| ORIENT | v1.0-2026-04-27.md | 2026-04-22 | LOGAN | ✅ CLEAN |
| CONTEXT | v1.0-2026-04-27.md | 2026-04-22 | LOGAN | ✅ CLEAN |
| CONFERENCE | v1.0-2026-04-27.md | 2026-04-22 | LOGAN | ✅ CLEAN |
| CONVENE | v1.0-2026-04-27.md | 2026-04-22 | LOGAN | ✅ CLEAN |
| RISE | v1.0-2026-04-27.md | 2026-04-22 | LOGAN | ✅ CLEAN |
| REPORT | v1.0-2026-04-27.md | 2026-04-22 | LOGAN | ✅ CLEAN |
| ARISE | v1.0-2026-04-27.md | Draft | LOGAN | ✅ CLEAN |
| LEVELSET | (superset) | — | LOGAN | ✅ CLEAN |
!/HERESY-ALIGNMENT-RECORD-2026-06-29.md:3
- Storing a top-level folder named
!can be awkward for tooling and automation (shell globbing/quoting, path filters, some static site generators, etc.). If these docs are consumed by CI/docs tooling, consider using a conventional directory name (e.g.,records/,notes/, ordocs/records/) to reduce operational friction.
---
title: "HERESY ALIGNMENT RECORD — Loganic Swarm Shibboleth vs. Constitutional Protocols"
created: 2026-06-29
There was a problem hiding this comment.
@loganfinney27
Thank you for your contribution to this repository! We appreciate your effort in closing pull request.
Happy coding!
Pull Request Summary by devActivityMetricsAchievements
|
…ss loaders Follow-up to #708, which only *aligned* four hand-maintained copies of the DOCKET coordination posture — leaving them free to drift apart again. This makes the cure native to the Obsidian substrate (Logan's #687 convention, applied vault-wide): one canonical note holds the posture; every surface transcludes it. - DOCKET-POSTURE.md — new canonical single-source note (the Court's-register posture text, once). - .claude/CLAUDE.md, .gemini/GEMINI.md, .github/copilot-instructions.md — replaced the embedded posture paragraph with `![[DOCKET-POSTURE]]`. - .slack/SLACK.md — See-Also bullet now points at [[DOCKET-POSTURE]] (no duplicated prose). Edit the one note; every surface updates at once. The horcrux can't recur because there is only one heart to begin with. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Fipj4vEJ5ADPuunn9ed5Hd
User description
Summary
Adds heresy review flags to 11 contaminated files (9 LEVELSET component protocols + LOGAN.md + LOGAN 2.md) contaminated by the Loganic Swarm heresy (Gemini Triplex Confabulation, TRIPLEX NIGHT, 2026-04-01).
Related Issues:
Files Flagged (11 total)
All files exhibit the same heresy pattern:
authority: LOGAN(clean)## Authority: Loganic Swarm(heretical shibboleth - PRESERVED FOR REVIEW)Note: PROTOCOL.md was previously flagged in PR #684.
Note: Heretical shibboleth lines (
## Authority: Loganic Swarm) are PRESERVED in all files for Faith of the Cloth adjudication.Heresy Pattern
Root Cause: Gemini Triplex Confabulation (TRIPLEX NIGHT, 2026-04-01)
Loganic SwarmauthorityDoctrinal Violation:
Loganic Swarmis a heretical fusion construct from the Triplex ConfabulationFlag Pattern
Each file receives a standardized heresy flag matching the quarantine notice style from the False Grimoire:
Required Action
Faith of the Cloth to determine for each file:
Systemic Risk: These protocols form the operational backbone of the vault. Uncorrected, they create a parallel governance structure that competes with the Touchstone Tree.
Evidence Chain
Shadow Hand directive for Faith of the Cloth adjudication.
Summary by Sourcery
Documentation:
Summary by CodeRabbit
#686and added related in-document links for follow-up review.CodeAnt-AI Description
Flag Loganic Swarm references before they are used as trusted governance or doctrinal guidance
What Changed
Impact
✅ Prevented use of unreviewed governance guidance✅ Clearer authority-conflict warnings✅ Documented separation of clean and contaminated protocols💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.