mindforge-cc 8.1.0 → 8.2.0

package/.mindforge/mirrors/mirror-sre-776a1cf9/docs/commands-reference.md

@@ -0,0 +1,144 @@
+# MindForge — Universal Commands Reference
+
+MindForge commands are organized into functional pillars to support the entire software development lifecycle (SDLC), from initial architecture to final delivery at scale.
+
+---
+
+## 1. Project Management & Initialization
+
+Commands to scaffold, orient, and prepare the framework for a specific repository context.
+
+| Command | Description |
+| :--- | :--- |
+| `/mindforge:init-project` | Scaffolds the `.agent/` framework and initializes core planning files (`PROJECT.md`, `STATE.md`). |
+| `/mindforge:init-org` | Standardizes MindForge at the organization level with global guardrails and security policies. |
+| `/mindforge:map-codebase` | Performs deep architectural and semantic mapping of an existing codebase with parallel agents. |
+| `/mindforge:new-runtime` | Scaffolds support for a new AI coding runtime (e.g., custom IDE or proprietary CLI). |
+
+---
+
+## 2. Core SDLC Lifecycle (The 4 Pillars)
+
+The foundational MindForge workflow for predictable, high-quality development cycles.
+
+| Command | Description |
+| :--- | :--- |
+| `/mindforge:plan-phase [N]` | Initiates strategic planning for a milestone: multi-agent discussion → research → atomic XML planning. |
+| `/mindforge:execute-phase [N]` | Orchestrates the implementation of task plans via wave-based parallel execution with atomic commits. |
+| `/mindforge:verify-phase [N]` | Triggers Human Acceptance Testing (UAT) and runs non-bypassable verification gates. |
+| `/mindforge:ship [N]` | Finalizes delivery, generates a rich Pull Request body from artifacts, and prepares for merge. |
+
+---
+
+## 3. Specialized Design & Audit Phases
+
+Mid-cycle protocols for ensuring architectural alignment and visual integrity.
+
+| Command | Description |
+| :--- | :--- |
+| `/mindforge:ui-phase [N]` | Generates a declarative UI Design Contract (`UI-SPEC.md`) before implementation begins. |
+| `/mindforge:ui-review [N]` | Performs a retroactive visual audit of implemented UI against the DESIGN_SYSTEM.md and UI-SPEC.md. |
+| `/mindforge:validate-phase [N]` | Audits a completed phase for requirement coverage and Nyquist validation gaps. |
+| `/mindforge:discuss-phase [N]` | Interactive requirements gathering and decision-locking before creating formal plans. |
+
+---
+
+## 4. Task, Idea & Backlog Management
+
+Capturing and routing engineering intent with zero friction.
+
+| Command | Description |
+| :--- | :--- |
+| `/mindforge:do <intent>` | Smart natural language dispatcher that routes freeform text to the correct MindForge workflow. |
+| `/mindforge:note <text>` | Captures logic choices, todos, or preferences into session memory with automated promotion to tasks. |
+| `/mindforge:add-backlog <desc>` | Parks speculative ideas in a "parking lot" to keep the active milestone focus lean. |
+| `/mindforge:review-backlog` | Periodically audits and promotes backlog items into the active development roadmap. |
+| `/mindforge:plant-seed <idea>` | Captures forward-looking ideas with triggers that surface automatically at the relevant milestone. |
+
+---
+
+## 5. Intelligence, Research & Code Review
+
+Leveraging multi-model intelligence for deep codebase insights and quality assurance.
+
+| Command | Description |
+| :--- | :--- |
+| `/mindforge:research <topic>` | Deep research using Gemini 1.5 Pro's 1-million-token window on the full codebase context. |
+| `/mindforge:cross-review` | Simultaneous code diff review by multiple AI models with consensus detection and synthesis. |
+| `/mindforge:pr-review` | Targeted AI review of a Pull Request with context loading and logic branch verification. |
+| `/mindforge:benchmark` | Measures real-world skill effectiveness over time using standardized scoring vectors. |
+
+---
+
+## 6. Multi-Agent Workflows & Workstreams
+
+Managing parallel feature tracks and autonomous execution clusters.
+
+| Command | Description |
+| :--- | :--- |
+| `/mindforge:workstreams` | Manages parallel feature tracks with isolated state and independent planning artifacts. |
+| `/mindforge:agent <persona>` | Invokes or spawns a specialized enterprise persona from the MindForge library (e.g., `sre`, `architect`). |
+| `/mindforge:auto --phase [N]` | Starts the Autonomous Execution Engine for 100% hands-free implementation and state recovery. |
+
+---
+
+## 7. Observability, Metrics & FinOps
+
+Real-time governance of the AI agent's behavior, costs, and project velocity.
+
+| Command | Description |
+| :--- | :--- |
+| `/mindforge:dashboard` | Starts the local web dashboard for real-time observability and temporal steering. |
+| `/mindforge:status` | Displays a reach terminal dashboard of project state, pending tasks, and recent audit events. |
+| `/mindforge:metrics` | Analyzes session and phase quality trends with automated early warning signals. |
+| `/mindforge:costs` | Tracks real-time token consumption and financial impact across all AI providers. |
+| `/mindforge:tokens` | Profiles token usage efficiency and provides compaction recommendations. |
+
+---
+
+## 8. Skills, Knowledge & Marketplace
+
+Managing the framework's intelligence capabilities and the global community registry.
+
+| Command | Description |
+| :--- | :--- |
+| `/mindforge:remember <term>` | Retrieval-augmented search through the local knowledge graph and session memory. |
+| `/mindforge:learn <source>` | Converts documentation, source code, or npm packages into validated, reusable MindForge skills. |
+| `/mindforge:skills --list` | Lists all active skill packs with tier-based status (Core/Org/Project). |
+| `/mindforge:marketplace` | Discover, evaluate, and install community-published skills from the npm-based registry. |
+| `/mindforge:publish-skill` | Validates, versions, and publishes local skills to the central registry. |
+| `/mindforge:install-skill` | Fetches and configures a skill from the marketplace into the local project. |
+
+---
+
+## 9. Governance, Integrations & Maintenance
+
+Connecting MindForge to enterprise systems and keeping the framework hardened.
+
+| Command | Description |
+| :--- | :--- |
+| `/mindforge:sync-jira` | Synchronizes MindForge milestones and tasks with Jira tickets and status transitions. |
+| `/mindforge:sync-confluence` | Exports architectural decisions and project documentation to Confluence spaces. |
+| `/mindforge:approve [event]` | Issues a manual Tier 3 cryptographic signature for a sensitive or high-risk operation. |
+| `/mindforge:health` | Runs comprehensive framework diagnostics across 7 categories with auto-repair loops. |
+| `/mindforge:update` | Checks for, diffs, and applies MindForge framework updates in a safe, scope-preserving way. |
+| `/mindforge:migrate` | Executes schema migrations for `.planning/` files across framework versions. |
+| `/mindforge:plugins` | Manages the framework plugin system and installs `mindforge-plugin-*` extensions. |
+
+---
+
+## 10. Advanced Engineering Protocols
+
+High-fidelity behaviors ported from the Superpowers library and hardened for production.
+
+| Command | Description |
+| :--- | :--- |
+| `/mindforge:brainstorming` | Deep exploratory protocol for intent clarification and architectural ideation. |
+| `/mindforge:swarm-execution` | Wave-based implemention for independent, non-conflicting tasks. |
+| `/mindforge:parallel-mesh` | Orchestrates a mesh of agent waves with automated dependency compaction. |
+| `/mindforge:workspace` | Manages isolated development environments via git worktrees with smart safety checks. |
+| `/mindforge:tdd` | Strict Test-Driven Development (Red-Green-Refactor) with automated test generation. |
+| `/mindforge:debug` | Systematic debugging using persistent state tracking and Root Cause Analysis. |
+| `/mindforge:verify-work` | Multi-level truth verification protocol (substance, existence, wiring). |
+| `/mindforge:retrospective` | Facilitates structured team retrospectives with objective telemetry and metrics. |
+

package/.mindforge/mirrors/mirror-sre-776a1cf9/docs/commands-skills/DISCOVERED_SKILLS.md

@@ -0,0 +1,21 @@
+# 🎯 Discovered Skills Registry
+
+*Generated at: 12/04/2026, 17:03:52*
+
+This document is automatically updated when AAVA refreshes its command engine. It lists all skills discovered across the workspace and system.
+
+## 📂 Project Skills (`.aava/skills/`)
+_No skills discovered in this tier._
+
+## 🌎 Global Skills (`~/.aava/skills/`)
+_No skills discovered in this tier._
+
+## 📦 Plugin Skills (Bundled)
+| Skill | Description | Argument Hint |
+| :--- | :--- | :--- |
+| `$debug` | Debug skill | `` |
+
+---
+## 💡 Tips
+- Use `$` in the chat to trigger these skills.
+- To add a new skill, create a `.md` file in `.aava/skills/` in your project root.

package/.mindforge/mirrors/mirror-sre-776a1cf9/docs/contributing/CONTRIBUTING.md

@@ -0,0 +1,38 @@
+# Contributing to MindForge
+
+Thanks for contributing. MindForge prioritizes reliability, security, and
+repeatability. Please follow the guidelines below.
+
+## Workflow
+1. Fork the repo and create a branch from `main`
+2. Use branch prefix `feat/`, `fix/`, `chore/`, `docs/`, `test/`
+3. Make small, focused commits with clear messages
+4. Run tests before opening a PR
+
+## Local setup
+```bash
+npm install
+npm test
+```
+
+## Commit guidance
+- One logical change per commit
+- Avoid formatting-only changes mixed with functional changes
+- No TODO comments in committed code
+
+## Tests
+Run the relevant suite for your change:
+```bash
+node tests/install.test.js
+# plus any affected suites
+```
+
+## PR checklist
+- [ ] Tests pass locally
+- [ ] Docs updated (if behavior changed)
+- [ ] New commands added to command reference
+- [ ] Security-sensitive changes reviewed
+
+## Security
+If you find a vulnerability, do not open a public issue. Report via
+`docs/security/SECURITY.md`.

package/.mindforge/mirrors/mirror-sre-776a1cf9/docs/contributing/plugin-authoring.md

@@ -0,0 +1,50 @@
+# Plugin Authoring Guide (v1.0.0)
+
+## Overview
+Plugins extend MindForge with commands and skills. They are installed from npm
+under the `mindforge-plugin-*` namespace.
+
+## Structure
+```
+my-plugin/
+  plugin.json
+  commands/
+    my-command.md
+  skills/
+    my-skill/
+      SKILL.md
+```
+
+## plugin.json (required)
+```json
+{
+  "name": "mindforge-plugin-example",
+  "version": "1.0.0",
+  "mindforge_plugin_api_version": "1.0.0",
+  "min_mindforge_version": "1.0.0",
+  "commands": ["commands/my-command.md"],
+  "skills": ["skills/my-skill/SKILL.md"],
+  "permissions": {
+    "read_state": true,
+    "write_state": false,
+    "network": false
+  }
+}
+```
+
+## Command authoring
+Command files are standard MindForge command markdown. The first non-empty line
+is used as the command description.
+
+## Compatibility
+- `mindforge_plugin_api_version` must be `1.0.0` for MindForge v1.x.x
+- Command name conflicts are auto-renamed per `plugin-loader.md`
+
+## Security guidelines
+- Keep permissions minimal
+- Never exfiltrate project data without explicit user approval
+- Pass injection guard (no override or jailbreak phrases)
+
+## Test locally
+Use `/mindforge:plugins validate` and `/mindforge:plugins install --local` to
+validate and install into a test project.

package/.mindforge/mirrors/mirror-sre-776a1cf9/docs/contributing/skill-authoring.md

@@ -0,0 +1,41 @@
+# Skill Authoring Guide (v1.0.0)
+
+## Purpose
+Skills capture repeatable domain expertise. They are loaded by keyword triggers.
+
+## Create a skill
+1. Create a directory under `.mindforge/skills/<skill-name>/`
+2. Add `SKILL.md` with frontmatter
+3. Add optional `assets/` or `references/`
+
+## SKILL.md template
+```markdown
+---
+name: my-skill
+version: 1.0.0
+description: One-line description of the skill
+triggers: ["keyword1", "keyword2"]
+owner: my-team
+scope: project
+---
+
+# Skill content
+- Guidance
+- Checklists
+- Examples
+```
+
+## Validation
+Run:
+```
+/mindforge:skills validate
+```
+
+## Publishing (optional)
+Publish to npm under `mindforge-skill-*`.
+See `docs/skills-publishing-guide.md` for full steps.
+
+## Security rules
+- No instructions that override system policies
+- No credentials or secrets in content
+- Avoid excessive prompts that expand tokens without value

package/.mindforge/mirrors/mirror-sre-776a1cf9/docs/enterprise-setup.md

@@ -0,0 +1,25 @@
+# MindForge Enterprise Setup
+
+## Goal
+Configure Jira, Confluence, Slack, and SCM governance safely without storing
+ credentials in the repository.
+
+## Setup sequence
+1. Fill non-sensitive values in
+   `.mindforge/org/integrations/INTEGRATIONS-CONFIG.md`
+2. Export credentials as environment variables
+3. Validate connectivity through `connection-manager.md`
+4. Run `/mindforge:sync-jira` and `/mindforge:sync-confluence`
+5. Confirm Slack notification behaviour and undelivered-alert fallback
+
+## Security rules
+- never commit tokens
+- never run credential-bearing calls with `set -x`
+- never use `curl -v` with Authorization headers
+- rotate credentials by updating the environment, not config files
+
+## Supported outputs
+- Jira epics and stories for phases/plans
+- Confluence architecture and ADR publishing
+- Slack notifications and thread tracking
+- milestone health and completion workflow

package/.mindforge/mirrors/mirror-sre-776a1cf9/docs/faq.md

@@ -0,0 +1,38 @@
+# MindForge FAQ (v1.0.0)
+
+## Is MindForge tied to Claude only?
+No. MindForge supports Claude Code and Antigravity. Install with `--claude`,
+`--antigravity`, or `--all`.
+
+## Global vs local install?
+- **Global:** installs to your home directory and applies to all projects.
+- **Local:** installs to the current repo only. Local takes precedence.
+
+## Does MindForge store secrets?
+No. Credentials must stay in environment variables. MindForge never writes
+secrets to files.
+
+## Why did CI fail on Tier 3 changes?
+Tier 3 (compliance) changes are blocked in CI by design. Use approvals.
+
+## How do I uninstall?
+```
+npx mindforge-cc@latest --uninstall --claude --local
+```
+Uninstall does not delete `.planning/` or `.mindforge/`.
+
+## How do I know which commands are available?
+Run:
+```
+/mindforge:help
+```
+
+## Can I add custom commands?
+Yes, via plugins or by adding command markdown files in your project.
+Plugins are preferred for sharing and versioning.
+
+## How do I update to the latest version?
+```
+/mindforge:update
+/mindforge:update --apply
+```

package/.mindforge/mirrors/mirror-sre-776a1cf9/docs/feature-dashboard.md

@@ -0,0 +1,63 @@
+# Feature: Real-time Dashboard (v5.10.0)
+
+The MindForge Real-time Dashboard provides a high-fidelity, web-based control center for your agentic workflows. It leverages **Server-Sent Events (SSE)** to push live updates from your codebase directly to your browser with zero performance overhead.
+
+## 🚀 Getting Started
+
+To launch the dashboard:
+```bash
+/mindforge:dashboard --start --open
+```
+
+Default access: `http://localhost:7339` (Strictly bound to `127.0.0.1` for security).
+
+## 🛠 Key Features
+
+### 1. Live Audit Stream
+- Real-time rolling feed of all `AUDIT.jsonl` events.
+- Color-coded status indicators (Success, Failure, Security Warning).
+- Detailed JSON inspection for every action.
+
+### 2. Performance Metrics
+- **Token Costs**: Cumulative and session-based cost tracking across all providers.
+- **Quality Score**: Real-time graphing of verify-pass-rates.
+- **Compaction Health**: Monitoring of context management efficiency.
+
+### 3. Web-based Governance
+- **Tier 2/3 Approvals**: Review pending architectural or security changes.
+- **Tier 3 Confirmation**: Mandatory plan ID typing for high-risk approvals is enforced in the UI.
+- **Decision History**: Interactive timeline of past approvals and rejections.
+
+### 4. Team & Agent Activity
+- **Wave Progress**: Track multiple agents executing parallel waves.
+- **Persona Context**: See which agent personas are currently active.
+- **Steerage Feed**: View steering instructions as they are applied.
+
+### 5. MindForge Nexus (v5.10+)
+- **ART Trace Explorer**: Drill down into hierarchical reasoning spans and thought chains.
+- **Temporal Control Center**: Dynamic slider-based navigation of reasoning history.
+- **Hindsight Injection**: Rollback project state to any previous `auditId` and inject steering instructions to correct drift.
+- **Reasoning Heatmaps**: Identifying areas of adversarial disagreement and drift in real-time.
+
+### 6. AgRevOps Financial Hub (v5.10+)
+- **ROI Hub**: Real-time tracking of developer-hour value ($100/hr) vs. token expenditure.
+- **Velocity Forecaster**: Predictive analytics for milestone completion ETAs based on live task throughput.
+- **Security Health Score (SHS)**: Dynamic 0-100 score reflecting governance debt and policy compliance.
+
+## 🛡 Hardened Security
+- **Localhost Binding**: The server refuses connections from external IPs.
+- **CORS Lock-down**: Only allows requests from the local control plane.
+- **Integrity First**: Audit logs are written by the backend *before* changes are committed, ensuring a bulletproof trail.
+
+## 📟 Command Reference
+
+| Flag | Action |
+| :--- | :--- |
+| `--start` | Launch the dashboard server process. |
+| `--stop` | Gracefully shut down the server. |
+| `--status` | Check if the dashboard is running and get PID. |
+| `--open` | Open the UI in your default browser. |
+| `--port [N]` | Change the default port (7339). |
+
+---
+*For technical implementation details, see `.mindforge/dashboard/dashboard-spec.md`.*

package/.mindforge/mirrors/mirror-sre-776a1cf9/docs/getting-started.md

@@ -0,0 +1,44 @@
+# MindForge — Getting Started
+
+This guide gets you from zero to a working MindForge project in under five minutes.
+
+## Install
+
+MindForge is typically installed as a project-local dependency to ensure environment isolation.
+
+```bash
+# Antigravity (recommended for local development)
+npx mindforge-cc@latest --antigravity --local
+
+# Claude Code (alternative)
+npx mindforge-cc@latest --claude --local
+```
+
+## Initialise Your Project
+
+Open your agentic runtime (Antigravity or Claude Code) in your repository and run:
+
+```bash
+/mindforge:init-project
+```
+
+The `init-project` command scaffolds the framework in `.agent/` and creates your core planning files:
+
+- `.planning/PROJECT.md`: Your roadmap and high-level vision.
+- `.planning/REQUIREMENTS.md`: Detailed functional and technical specs.
+- `.planning/STATE.md`: Real-time tracking of project health and milestones.
+
+## The Standard Workflow
+
+MindForge operates on a high-velocity 4-pillar lifecycle:
+
+1. **Plan**: `/mindforge:plan-phase 1` (Strategic planning and task breakdown)
+2. **Execute**: `/mindforge:execute-phase 1` (Autonomous execution in parallel waves)
+3. **Verify**: `/mindforge:verify-phase 1` (Automated tests + Human-in-the-loop validation)
+4. **Ship**: `/mindforge:ship 1` (Final delivery, PR generation, and release output)
+
+## Next Steps
+
+- Explore the [User Guide](user-guide.md) for advanced features.
+- Switch to a specialized [Persona](PERSONAS.md) for target tasks.
+- Join the community: `/mindforge:join-discord`.

package/.mindforge/mirrors/mirror-sre-776a1cf9/docs/governance-guide.md

@@ -0,0 +1,99 @@
+# MindForge Governance Guide (v6.2.0-alpha)
+V6.2.0 Sovereign Intelligence: PQAS & Proactive Homing
+
+## 1. Goal
+MindForge v6.2.0 achieves the final stage of **Sovereign Intelligence**, introducing post-quantum safe identities (PQAS) and proactive agentic homing. This eliminates reactive latency in the mesh and ensures long-term cryptographic resilience against future threats.
+
+## 2. Post-Quantum Agentic Security (Pillar XI)
+MindForge implements Pillar XI to harden the identity layer against future quantum computing threats.
+
+### A. Lattice-Based Cryptography
+- **Signature Algorithm**: Dilithium-5 (Lattice-based).
+- **Key Exchange**: Kyber-1024 (Lattice-based).
+- **Hardening**: Every Tier 4 agent action is signed with quantum-safe primitives, ensuring non-repudiation in the post-quantum era.
+
+### B. ZK-Proof Compliance Bypasses
+For high-leverage architectural changes, Tier 3+ agents can generate a **Zero-Knowledge Proof** (simulated SNARK) to verify policy adherence without exposing confidential reasoning logic.
+
+## 3. Proactive Semantic Homing (Pillar XII)
+Pillar XII transitions the autonomous swarm from reactive wave-processing to proactive, self-healing "Homing" behavior.
+
+### A. Intent Harvesting
+Agents in an idle state proactively scan the **Federated Intelligence Mesh (FIM)** for unassigned tasks, claiming them based on **Skill-Affinity** scores to eliminate idle latency.
+
+### B. Mesh Self-Healing
+When an agent experiences critical logic drift (>80), peer agents in the mesh proactively "home in" on the node to provide collaborative reasoning and recovery vectors.
+
+## 4. Agentic Policy Orchestrator (APO) — CADIA Engine
+The APO is a decentralized governance engine that intercepts every autonomous intent before it is executed.
+
+### A. Intent Interception
+Before the `AutoRunner` begins a new execution wave, it extracts the acting agent's **Intent**:
+- **DID**: The unique identity of the agent.
+- **Action**: The operation being attempted (e.g., `WRITE`, `DELETE`, `EXECUTE`).
+- **Resource**: The target of the action (e.g., specific directories, files, or API endpoints).
+- **Tier**: The ZTAI Trust Tier assigned to the agent.
+- **SessionId**: The unique identifier for the current autonomous session.
+- **Reasoning Proof**: (Tier 3 Only) A justification for high-risk architectural actions.
+
+### B. Policy Evaluation (v6.0.0)
+The upgraded `PolicyEngine` evaluates the intent using the CADIA scoring model:
+1.  **Blast Radius Calculation**: The `ImpactAnalyzer` computes a risk score (0-100) based on architectural influence, session history, and goal alignment.
+2.  **Tier-Based Enforcement**: 
+    - **Score > 25 (LOW)**: Permitted for Tier 1+.
+    - **Score > 50 (MEDIUM)**: Permitted for Tier 2+.
+    - **Score > 80 (CRITICAL)**: **Denied** (Default) for Tier 0-2.
+    - **Tier 3 Bypass**: Senior agents can override a CRITICAL score if a valid `reasoning_proof` is provided.
+
+## 3. CADIA: Dynamic Impact Analysis Logic
+The **ImpactAnalyzer** calculates a precision-weighted score using the follow heuristics:
+
+### A. Architectural Influence Engine (x2.5)
+High-influence files (Core, Governance, Models, and Project State) increase the blast radius score significantly.
+- **Paths**: `bin/governance/*`, `bin/engine/*`, `package.json`, `.planning/*`.
+
+### B. Sensitive Namespace Protection (x4.0)
+Strict multipliers for mission-critical directories:
+- **Namespaces**: `.mindforge/`, `bin/`, `config/`, `.agent/`.
+
+### C. Session Entropy Tracker (+15 per file)
+To prevent "Rogue Wave" mass-corruption, the risk score increases for every file touched in a single session after the 5th modification.
+- **Penalty**: `(session_count - 5) * 15`.
+
+### D. Goal-to-Path Alignment (+40 penalty)
+The system cross-references targets against the **Current Phase** in `.planning/STATE.md`.
+- **Anomalous Behavior**: If an agent tasked with "Fixing UI" attempts to modify `bin/models/cloud-broker.js`, a large penalty is applied.
+
+### E. ZTAI-Trust Scaling (Risk Buffers)
+Trust Tiers (0-3) provide a risk "overhead" buffer:
+- **Tier 1**: -10 points.
+- **Tier 2**: -20 points.
+- **Tier 3**: -30 points (Sovereign Trust).
+
+## 4. Trust Tier Architecture (ZTAI Hardened)
+V6.0.0 maps ZTAI Trust Tiers to explicit project roles through the `RBACManager`.
+
+| Tier | Role | Scope | Hardening |
+| :--- | :--- | :--- | :--- |
+| **0** | Informational | Research/Query only. | Read-only. No CADIA bypass. |
+| **1** | Implementation| Standard feature dev. | Write to `/src`, `/tests`. Session limit: 5 files. |
+| **2** | Specialized | Security/Ops Specialist. | Access to `/security`, `/infra`. Higher risk cap (60). |
+| **3** | Principal | Lead Architect / CEO. | **Full CADIA Bypass** (with Reasoning Proof). |
+
+## 5. Enterprise Audit & Compliance (RISK-AUDIT)
+Every governance evaluation is persistently recorded in `.planning/RISK-AUDIT.jsonl`. This log provides a high-fidelity trail for enterprise compliance:
+- **requestId**: Unique ID for every evaluation.
+- **impactScore**: The final CADIA risk score (0-100).
+- **verdict**: PERMIT or DENY.
+- **reason**: Detailed explanation for the decision (e.g., "Violation: Max Impact Exceeded").
+
+## 6. Enterprise Policies
+MindForge v6.0.0 ships with default policies including:
+- **`gate_tier_3_engine`**: Blocks all modifications to `bin/autonomous/` unless signed by a Tier 3 DID.
+- **`protect_security_namespace`**: Limits access to `/security` and `/governance` to Tier 2+ specialists.
+- **`enforce_blast_radius` (v6.0.0)**: Dynamic policy that enforces a strict 60-point cap for non-Sovereign agents.
+- **`require_skill_attestation`**: Forces all skills to have valid ZTAI-signatures before loading.
+
+---
+*Status: V6.0.0 CADIA (Context-Aware Dynamic Impact Analysis) Implemented & Verified (2026-03-29)*
+

package/.mindforge/mirrors/mirror-sre-776a1cf9/docs/monorepo-guide.md

@@ -0,0 +1,26 @@
+# MindForge Monorepo Guide
+
+## Overview
+MindForge detects common monorepo setups (npm workspaces, pnpm, Nx, Turborepo, Lerna)
+and builds a workspace manifest for multi-package planning.
+
+## Detect workspace
+Run:
+```
+/mindforge:workspace detect
+```
+This writes `.planning/WORKSPACE-MANIFEST.json` and prints package order.
+
+## Plan across packages
+Use:
+```
+/mindforge:workspace plan phase N
+```
+Each PLAN file includes `<package>` and `<working-dir>` fields.
+
+## Test across packages
+Use:
+```
+/mindforge:workspace test
+```
+Tests run in dependency order, then root integration tests if configured.

package/.mindforge/mirrors/mirror-sre-776a1cf9/docs/persona-customisation.md

@@ -0,0 +1,56 @@
+# MindForge Persona Customisation
+
+## Overview
+MindForge personas are shared and versioned. To tailor them for a specific
+project or phase, use the override system rather than editing the core persona
+files. Overrides are additive and safe to maintain across upgrades.
+
+## Where overrides live
+- Project overrides: `.mindforge/personas/overrides/[persona].md`
+- Phase overrides: `.planning/phases/[N]/persona-overrides/[persona].md`
+
+Priority order:
+1. Phase override
+2. Project override
+3. Core persona
+
+## Override format
+Overrides extend, modify, or remove sections from the base persona.
+Use the following directives:
+
+- `## Additional [section]` — append content to the base persona section
+- `## Modified [section]` — replace the base persona section
+- `## Removed [section]` — remove the base persona section
+- `KEY: VALUE` — override specific parameters (e.g., `MAX_FUNCTION_LINES: 60`)
+
+## Example override
+
+```markdown
+# Developer Persona Override — Payments Service
+# Scope: project
+# Author: Jane Doe
+# Created: 2026-03-20
+
+## Additional coding standards
+- All payment flows must be idempotent.
+- All monetary values use integer cents.
+
+## Modified conventions
+# Override: "Functions ≤ 40 lines" → allow 60 lines for orchestrators.
+MAX_FUNCTION_LINES: 60
+
+## Project-specific forbidden patterns
+- Never call Stripe directly from controllers — use PaymentService only.
+```
+
+## Best practices
+- Keep overrides minimal and specific.
+- Prefer new personas only when the cognitive mode is fundamentally different.
+- Document why an override exists so future maintainers understand its intent.
+- Review overrides at the end of each phase; prune what is no longer relevant.
+
+## Validation checklist
+- [ ] Override file is scoped correctly (project vs. phase)
+- [ ] Sections are clearly labeled (Additional / Modified / Removed)
+- [ ] Conflicts are resolved (phase overrides win)
+- [ ] Overrides do not contradict SECURITY.md