feat(v2-arch): strip local dispute tables, add cc_node_leases, align docs #130
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,4 @@ | ||
| name: chittysecrets Rotation Audit | ||
|
Contributor
There was a problem hiding this comment. 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win Complete or explicitly document the legacy naming migration.
📍 Affects 3 files
🤖 Prompt for AI Agents |
||
|
|
||
| on: | ||
| workflow_dispatch: | ||
|
|
@@ -23,8 +23,8 @@ | |
| set -euo pipefail | ||
| [[ -n "${GH_TOKEN:-}" ]] || { echo "Missing ORG_AUTOMATION_TOKEN"; exit 1; } | ||
| [[ -n "${OP_SERVICE_ACCOUNT_TOKEN:-}" ]] || { echo "Missing OP_SERVICE_ACCOUNT_TOKEN"; exit 1; } | ||
| - name: Install chittysecrets CLI | ||
| uses: chittysecrets/install-cli-action@v1 | ||
Check warningCode scanning / CodeQL Unpinned tag for a non-immutable Action in workflow or composite action Medium |
||
|
Comment on lines
+26
to
+27
Contributor
There was a problem hiding this comment. 🔒 Security & Privacy | 🟠 Major | ⚡ Quick win 🧩 Analysis chain🏁 Script executed: #!/bin/bash
set -euo pipefail
echo "== workflow files =="
fd -a 'onepassword-rotation-audit\.ya?ml$' . | sed 's#^\./##'
echo
echo "== relevant lines =="
for f in $(fd 'onepassword-rotation-audit\.ya?ml$' .); do
echo "--- $f"
sed -n '1,60p' "$f" | cat -n
done
echo
echo "== all chittysecrets action refs in repo =="
rg -n "chittysecrets/install-cli-action|uses: .*`@v`[0-9]|uses: [^@]+@[0-9a-fA-F]{40}" . || trueRepository: chittyos/chittycommand Length of output: 248 🌐 Web query:
💡 Result: There is no GitHub repository named chittysecrets/install-cli-action. It appears you may be confusing this with 1Password/install-cli-action, an official GitHub Action for installing the 1Password CLI [1][2]. While searching for the term chittysecrets, results indicate it is associated with the organization chittyos (e.g., chittyconnect, chittymcp, chittychronicle) [3][4][5]. Within the repositories of the chittyos organization, there are instances where they utilize 1Password/install-cli-action, but they do not maintain an install-cli-action of their own [4][6]. If you are looking for the releases for the 1Password/install-cli-action repository, they are available on the official GitHub repository page [2]. As of July 26, 2026, the latest release for 1Password/install-cli-action is v4.0.0, which was released on June 11, 2026 [1][2]. Citations:
Pin the installed Action to a verified immutable commit. 🧰 Tools🪛 GitHub Check: CodeQL[warning] 27-27: Unpinned tag for a non-immutable Action in workflow or composite action 📍 Affects 2 files
🤖 Prompt for AI AgentsSource: Linters/SAST tools |
||
| - name: Run rotation audit | ||
| id: rotation | ||
| shell: bash | ||
|
|
@@ -46,7 +46,7 @@ | |
| shell: bash | ||
| run: | | ||
| set -euo pipefail | ||
| title="[Security] chittysecrets rotation policy violations" | ||
| body="$(cat reports/secret-rotation/latest.md)" | ||
| existing="$(gh issue list --state open --search "\"${title}\" in:title" --json number,title --jq '.[] | select(.title=="'"${title}"'") | .number' | head -n1 || true)" | ||
| if [[ -n "${existing}" ]]; then | ||
|
|
||
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
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
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,127 @@ | ||
| # ChittyCommand v2: Principled Refactor Spec | ||
|
|
||
| ## 1. Product Concept | ||
| ChittyCommand v2 shifts from being a "better dashboard" or standalone application into the **canonical orchestration cockpit for ChittyOS**. It is the shell through which the user interacts with the entire suite of distributed truth-producing engines. | ||
|
|
||
| ChittyCommand **does not own truth**. It is a visualization, routing, and orchestration layer. It exposes the litigation, life, and asset command modes, acting as the unified interface where the Ch1tty pilot layer, the ChittyClaw legal brain, and the underlying bedrock services converge to empower human decision-making. | ||
|
|
||
| ## 2. Canonical Service Responsibility Matrix | ||
| The engines generate truth; the cockpit visualizes it. | ||
|
|
||
| | Domain | Owning Engine | Cockpit Role (ChittyCommand) | | ||
| | :--- | :--- | :--- | | ||
| | **Matters & Strategy** | `ChittyCases` / `ChittyClaw` | Visualizes matter posture, synthesizes legal elements, queues strategy | | ||
| | **Evidence & Facts** | `ChittyEvidence` / `ChittyStorage` | Reconstructs timeline, maps source files, highlights audit gaps | | ||
| | **Proof & Discovery** | `ChittyProof` / `ChittyPro` | Displays contradiction hotspots, assembles proof packets, gates readiness | | ||
| | **Finance & Runway** | `ChittyFinance` | Projects cashflow, stages damages, monitors burn rate | | ||
| | **Assets & Value** | `ChittyAssets` | Surfaces valuations, tracks encumbrances, maps entities | | ||
| | **Immutable Truth** | `ChittyLedger` | Reads chronological event custody and DRL (Reputation) reckoning | | ||
| | **Orchestration** | `Ch1tty` | Routes intents, launches workflows, handles agent handoffs | | ||
|
|
||
| ## 3. Refactored Navigation | ||
| Navigation moves away from generic views to highly opinionated, purpose-driven **Command Modes**. | ||
|
|
||
| * **[Default] Case Command**: Litigation + Life Operations Cockpit | ||
| * **Evidence Command**: Timeline reconstruction and gap analysis | ||
| * **Finance Command**: Damages staging and runway protection | ||
| * **Asset Command**: Entity map and encumbrance tracking | ||
| * **Proof Command**: Citation completeness and packet assembly | ||
| * **Contradiction Command**: ChittyPro conflict detection and impeachment logic | ||
| * **Life Ops Command**: Daily non-litigation operations | ||
| * **Ch1tty Orchestration Command**: Agent routing, workflow supervision | ||
| * **Export / Filing Command**: Court-ready document sequencing | ||
| * **System Health Command**: Ecosystem readiness and canonical compliance | ||
|
|
||
| ## 4. Data Ownership Map | ||
| To prevent ChittyCommand from becoming a shadow source of truth, all data flows adhere strictly to canonical pipelines: | ||
|
|
||
| * **Source-gated data:** `ChittyStorage` → `ChittyEvidence` → `ChittyProof` → `ChittyLedger` → `ChittyCases` | ||
| * **Financial data:** `ChittyFinance` → `ChittyLedger` → `ChittyCases` | ||
| * **Asset/Value data:** `ChittyAssets` → `ChittyFinance` → `ChittyCases` | ||
| * **Contradictions:** `ChittyEvidence` + `ChittyContextual` → `ChittyPro Contradiction Engine` → `ChittyCases` | ||
| * **Legal Strategy:** `ChittyClaw` → `ChittyCases` → **Attorney Review Queue** | ||
|
|
||
| ## 5. Workflow Orchestration Map | ||
| Ch1tty serves as the pilot layer. Workflows are launched from ChittyCommand, executed by Ch1tty, processed by the bedrock services, and returned to ChittyCommand for approval. | ||
|
|
||
| ```mermaid | ||
| graph TD | ||
| A[Human Action / Goal] --> B(ChittyCommand UI) | ||
| B --> C{Ch1tty Router} | ||
| C --> D[ChittyClaw] | ||
| C --> E[ChittyPro] | ||
| C --> F[ChittyFinance] | ||
|
|
||
| D --> G(ChittyCases) | ||
| E --> G | ||
| F --> G | ||
|
|
||
| G --> H[Attorney Review Queue] | ||
| H --> I((Human Approval Gate)) | ||
| ``` | ||
|
|
||
| ## 6. UI Component Plan | ||
| Every card, timeline item, task, and recommendation must be a strict projection of the bedrock. They must explicitly declare their provenance. | ||
|
|
||
| **Standardized Component Anatomy:** | ||
| * **Visual Data:** The projection of the data (e.g., a timeline event). | ||
| * **Metadata Ribbon (Bottom/Side):** | ||
| * `Owning Service`: (e.g., `ChittyEvidence`) | ||
| * `Source Table`: (e.g., `ev_facts`) | ||
| * `Canonical ID`: (e.g., `FCT-9A2B`) | ||
| * **State Indicators (Top Right):** | ||
| * `Readiness Status`: (e.g., `Sourced`, `Unverified`) | ||
| * `Blocker State`: (e.g., `Awaiting Deposition`) | ||
| * **Action Row:** | ||
| * `Next Action`: Auto-computed by ChittyClaw | ||
| * `Approval Gate`: Explicit human/attorney sign-off button | ||
|
|
||
| ## 7. Readiness Scoring Model | ||
| Readiness is computed, not asserted. | ||
| * **Fact Readiness:** (Sourced + Hashed in Ledger) = 1.0 | ||
| * **Element Readiness:** (All required facts for a legal element reach 1.0) = Ready | ||
| * **Filing Readiness:** (All elements Ready + Attorney Approval Gate cleared) = Ready for Export | ||
|
|
||
| ## 8. Evidence Governance Rules | ||
| * **No Raw Storage:** ChittyCommand cannot accept file uploads directly to its own DB. It must use the `ChittyStorage` canonical pipeline. | ||
| * **No Unattributed Facts:** A fact without a valid `canonical ID` pointing to `ChittyEvidence` renders with a red `[UNSOURCED]` warning and prevents filing export. | ||
| * **Immutability:** ChittyCommand cannot edit a ledger event. It can only dispatch a workflow to append a correction to `ChittyLedger`. | ||
|
|
||
| ## 9. Context-Aware Matter Implementation (Example: Arias v. Bianchi) | ||
| ChittyCommand dynamically configures its default mode based on the active matter injected by `ChittyContextual`. It does not hardcode cases. | ||
|
|
||
| **Example Homepage layout for an active litigation matter (e.g., Arias v. Bianchi):** | ||
| 1. **Ch1tty Command Bar:** Global intent routing. | ||
| 2. **Case Readiness Thermometers:** Visualizing elements of the claim (e.g., Breach of Fiduciary Duty, Fraud). | ||
| 3. **Strategic Objective Cards:** Sourced from `ChittyContextual` / `ChittyCases` for this specific matter. | ||
| 4. **Evidence Reconstruction Timeline:** Intersecting `ChittyFinance` anomalies with `ChittyEvidence` emails. | ||
| 5. **Strategy Execution Timeline:** Forward-looking roadmap. | ||
| 6. **Filing Sequencer:** Document assembly for the next court deadline. | ||
| 7. **Attorney Decision Queue:** Items requiring explicit human approval. | ||
| 8. **Financial Runway:** Current cash flow vs projected litigation costs. | ||
| 9. **Contradiction Hotspots:** Highlighting where counterparty statements conflict with `ChittyPro`. | ||
| 10. **Ecosystem Health Rail:** (Governance is shifted here, not the homepage). | ||
|
|
||
| ## 10. Migration Plan from Current ChittyCommand | ||
| 1. **Audit:** Map all current ChittyCommand local states to their canonical bedrock owners. | ||
| 2. **Strip:** Remove all truth-owning database tables from ChittyCommand. | ||
| 3. **Rewire:** Rebuild data fetching to query `ChittyCases`, `ChittyFinance`, etc. | ||
| 4. **Componentize:** Implement the Standardized Component Anatomy for all UI elements. | ||
| 5. **Launch:** Default the router to Case Command. | ||
|
|
||
| ## 11. CHARTER.md Update Proposal | ||
| **Add to Core Principles:** | ||
| > "ChittyCommand is the cockpit, not the engine. It shall never act as a source of truth for facts, finances, assets, or legal conclusions. Its sole mandate is to visualize, route, and orchestrate the truth produced by the canonical ChittyOS ecosystem." | ||
|
|
||
| ## 12. CHITTY.md Update Proposal | ||
| **Add to Architecture Constraints:** | ||
| > "All ChittyCommand UI components must explicitly render their canonical provenance, including the Owning Service, Source Table, and Canonical ID. Any data mutation must be routed through the Ch1tty pilot layer to the appropriate bedrock service." | ||
|
|
||
| ## 13. AGENTS.md Update Proposal | ||
| **Add to Agent Routing Rules:** | ||
| > "Agents interfacing with ChittyCommand must respect the Attorney Decision Queue. Agents may assemble packets, detect contradictions (ChittyPro), and propose strategies (ChittyClaw), but cannot bypass the human approval gate for filings, strategy shifts, or irreversible ecosystem mutations." | ||
|
|
||
| ## 14. Open Questions / Integration Blockers | ||
| * **Latency:** Does rendering the Standardized Component Anatomy across hundreds of timeline events introduce query bloat? (Requires aggressive caching and materialized views in the bedrock). | ||
| * **Authentication:** How does ChittyAuth map user roles to the "Attorney Review Queue"? | ||
| * **Contextual Sync:** Ensuring `ChittyContextual` accurately maintains the "active context" as the user switches between Command Modes. |
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: chittyos/chittycommand
Length of output: 50379
🏁 Script executed:
Repository: chittyos/chittycommand
Length of output: 34277
🏁 Script executed:
Repository: chittyos/chittycommand
Length of output: 7713
🏁 Script executed:
Repository: chittyos/chittycommand
Length of output: 1677
🌐 Web query:
1Password CLI op run chittysecrets command chittysecrets run💡 Result:
The command sequence you provided, op run chittysecrets command chittysecrets run, is not a standard or documented 1Password CLI command [1][2][3]. In the context of the 1Password CLI, the
op runcommand is used to securely inject secrets from 1Password into the environment of a subprocess [1][4]. The standard syntax forop runis [1]: op run -- For example, to run a script or application, you would use [5][4]: op run --./your-script.sh The term "chittysecrets" appears to be specific to a private project or organization-specific utility rather than a native part of the 1Password CLI [6][7]. Based on public code repositories, "chittysecrets" is referenced in custom commit messages and internal service configuration files (such as those forchittyconnect), suggesting it is a custom wrapper or tool used within that specific environment [6][7]. If you are trying to use 1Password CLI to run an application that relies on this custom "chittysecrets" tool, you would likely use the 1Password CLI to provide the necessary credentials to that tool, for instance: op run -- chittysecrets run This would execute thechittysecrets runcommand as a subprocess, with any secret references defined in your environment or configuration files automatically resolved and injected by 1Password [1][4].Citations:
Define the canonical chittysecrets invocation style. The docs and scripts use
chittysecrets run, standaloneop run/op read, and directop item getwithout documenting whether these are equivalent, wrapper-specific, or environment-specific flows. Align this consistently..github/copilot-instructions.md#L110,AGENTS.md#L94,CLAUDE.md#L121: declare whetherop run -- chittysecrets runor directop runis the canonical local command.docs/registration/SUBMISSION_RUNBOOK.md#L37-L55: keep thechittysecretscold-source →op runruntime handoff explicit if it remains a two-step flow.scripts/onepassword-rotation-audit.sh#L7-L9and template: either remove the confusing “chittysecrets CLI (op)” label or document thatchittysecretsis provided through 1Password CLI.📍 Affects 6 files
.github/copilot-instructions.md#L110-L110(this comment)AGENTS.md#L94-L94CLAUDE.md#L121-L121docs/registration/SUBMISSION_RUNBOOK.md#L37-L37scripts/onepassword-rotation-audit.sh#L8-L8templates/governance-baseline/scripts/onepassword-rotation-audit.sh#L8-L8🤖 Prompt for AI Agents