knowzcode 0.4.0 → 0.6.0

package/knowzcode/knowzcode_orchestration.md

@@ -1,66 +1,66 @@
-# KnowzCode Orchestration Configuration
-
-**Purpose:** Project-level defaults for team sizing and agent orchestration. Read by `/kc:work` and `/kc:audit` at startup. Per-invocation flags override these settings.
-
----
-
-## Builder Configuration
-
-```yaml
-# Maximum concurrent builders in Parallel Teams mode (default: 5, range: 1-5)
-# Lower values reduce token usage and complexity; higher values increase parallelism.
-# If the dependency map produces fewer partitions, fewer builders spawn regardless.
-max_builders: 5
-```
-
----
-
-## Scout Configuration
-
-```yaml
-# Scout mode controls context-scout spawning at Stage 0 (default: full)
-#   full    — 3 scouts: specs, workgroups, backlog (default)
-#   minimal — 1 scout: combined scan of all local context
-#   none    — skip scouts entirely (lead loads context inline)
-scout_mode: full
-```
-
----
-
-## Specialist Defaults
-
-```yaml
-# Specialists enabled by default for this project (default: none)
-# These activate without needing --specialists on every invocation.
-# Per-invocation --no-specialists overrides this setting.
-# Values: security-officer, test-advisor, project-advisor
-default_specialists: []
-
-# Examples:
-# default_specialists: [security-officer]
-# default_specialists: [security-officer, test-advisor]
-# default_specialists: [security-officer, test-advisor, project-advisor]
-```
-
----
-
-## MCP Agent Configuration
-
-```yaml
-# Enable MCP agents (knowz-scout, knowz-scribe) when vaults are configured (default: true)
-# Set to false to skip vault agents even when vaults exist — reduces agent count.
-mcp_agents_enabled: true
-```
-
----
-
-## Override Precedence
-
-| Setting | Config Default | Flag Override |
-|---------|---------------|--------------|
-| max_builders | `max_builders:` | `--max-builders=N` |
-| scout_mode | `scout_mode:` | `--no-scouts` |
-| default_specialists | `default_specialists:` | `--specialists`, `--no-specialists` |
-| mcp_agents_enabled | `mcp_agents_enabled:` | `--no-mcp` |
-
-Per-invocation flags always win. `--specialists` adds to defaults; `--no-specialists` clears all.
+# KnowzCode Orchestration Configuration
+
+**Purpose:** Project-level defaults for team sizing and agent orchestration. Read by `/kc:work` and `/kc:audit` at startup. Per-invocation flags override these settings.
+
+---
+
+## Builder Configuration
+
+```yaml
+# Maximum concurrent builders in Parallel Teams mode (default: 5, range: 1-5)
+# Lower values reduce token usage and complexity; higher values increase parallelism.
+# If the dependency map produces fewer partitions, fewer builders spawn regardless.
+max_builders: 5
+```
+
+---
+
+## Scout Configuration
+
+```yaml
+# Scout mode controls context-scout spawning at Stage 0 (default: full)
+#   full    — 3 scouts: specs, workgroups, backlog (default)
+#   minimal — 1 scout: combined scan of all local context
+#   none    — skip scouts entirely (lead loads context inline)
+scout_mode: full
+```
+
+---
+
+## Specialist Defaults
+
+```yaml
+# Specialists enabled by default for this project (default: none)
+# These activate without needing --specialists on every invocation.
+# Per-invocation --no-specialists overrides this setting.
+# Values: security-officer, test-advisor, project-advisor
+default_specialists: []
+
+# Examples:
+# default_specialists: [security-officer]
+# default_specialists: [security-officer, test-advisor]
+# default_specialists: [security-officer, test-advisor, project-advisor]
+```
+
+---
+
+## MCP Agent Configuration
+
+```yaml
+# Enable MCP agents (knowz-scout, knowz-scribe) when vaults are configured (default: true)
+# Set to false to skip vault agents even when vaults exist — reduces agent count.
+mcp_agents_enabled: true
+```
+
+---
+
+## Override Precedence
+
+| Setting | Config Default | Flag Override |
+|---------|---------------|--------------|
+| max_builders | `max_builders:` | `--max-builders=N` |
+| scout_mode | `scout_mode:` | `--no-scouts` |
+| default_specialists | `default_specialists:` | `--specialists`, `--no-specialists` |
+| mcp_agents_enabled | `mcp_agents_enabled:` | `--no-mcp` |
+
+Per-invocation flags always win. `--specialists` adds to defaults; `--no-specialists` clears all.

package/knowzcode/knowzcode_project.md

@@ -1,48 +1,48 @@
-# Project Overview
-
-## Goal
-*   **Goal:** [concise project objective — 1-2 sentences]
-*   **Core Problem:** [specific user problem this solves — 1-2 sentences]
-
-## Stack
-
-| Category | Technology | Version |
-|:---------|:-----------|:--------|
-| Language | | |
-| Backend Framework | | |
-| Frontend Framework | | |
-| Database | | |
-| ORM/ODM | | |
-| Testing (Unit) | | |
-| Testing (E2E) | | |
-| Key Libraries | | |
-
-## Architecture
-*   **Style:** [e.g., Monolithic, Microservices, Serverless]
-*   **Key Components:** [2-3 sentence description of main components and interactions]
-
-## Standards
-*   **Formatter:** [e.g., Prettier, Black]
-*   **Linter:** [e.g., ESLint, Flake8]
-*   **Test Framework:** [e.g., Jest, PyTest]
-*   **Commit Convention:** [e.g., Conventional Commits]
-*   **File Naming:** [e.g., kebab-case.js, PascalCase.tsx]
-
-### Component Classification
-* **Standard**: Simple components, clear inputs/outputs, minimal business logic
-* **Complex**: Significant business logic, multiple dependencies, state management
-* **Critical**: Security, payments, user data, system stability
-
-## Testing
-*   **Unit Tests:** Required for core business logic and utilities
-*   **Integration Tests:** Required for API endpoints and service interactions
-*   **E2E Tests:** [Optional for MVP — describe scope if applicable]
-*   **Coverage Target:** [e.g., >70% for core logic]
-*   **Test Location:** [e.g., adjacent `*.test.js` or `tests/` directory]
-
-## Security Priorities
-*   **Authentication:** [method — session-based, JWT, etc. Passwords MUST be hashed]
-*   **Authorization:** [approach — RBAC, ownership checks, etc.]
-*   **Input Validation:** All user inputs validated server-side
-*   **Secrets:** Environment variables only, never hardcoded
-*   **Dependencies:** Regular `npm audit` / `pip-audit` checks
+# Project Overview
+
+## Goal
+*   **Goal:** [concise project objective — 1-2 sentences]
+*   **Core Problem:** [specific user problem this solves — 1-2 sentences]
+
+## Stack
+
+| Category | Technology | Version |
+|:---------|:-----------|:--------|
+| Language | | |
+| Backend Framework | | |
+| Frontend Framework | | |
+| Database | | |
+| ORM/ODM | | |
+| Testing (Unit) | | |
+| Testing (E2E) | | |
+| Key Libraries | | |
+
+## Architecture
+*   **Style:** [e.g., Monolithic, Microservices, Serverless]
+*   **Key Components:** [2-3 sentence description of main components and interactions]
+
+## Standards
+*   **Formatter:** [e.g., Prettier, Black]
+*   **Linter:** [e.g., ESLint, Flake8]
+*   **Test Framework:** [e.g., Jest, PyTest]
+*   **Commit Convention:** [e.g., Conventional Commits]
+*   **File Naming:** [e.g., kebab-case.js, PascalCase.tsx]
+
+### Component Classification
+* **Standard**: Simple components, clear inputs/outputs, minimal business logic
+* **Complex**: Significant business logic, multiple dependencies, state management
+* **Critical**: Security, payments, user data, system stability
+
+## Testing
+*   **Unit Tests:** Required for core business logic and utilities
+*   **Integration Tests:** Required for API endpoints and service interactions
+*   **E2E Tests:** [Optional for MVP — describe scope if applicable]
+*   **Coverage Target:** [e.g., >70% for core logic]
+*   **Test Location:** [e.g., adjacent `*.test.js` or `tests/` directory]
+
+## Security Priorities
+*   **Authentication:** [method — session-based, JWT, etc. Passwords MUST be hashed]
+*   **Authorization:** [approach — RBAC, ownership checks, etc.]
+*   **Input Validation:** All user inputs validated server-side
+*   **Secrets:** Environment variables only, never hardcoded
+*   **Dependencies:** Regular `npm audit` / `pip-audit` checks

package/knowzcode/knowzcode_tracker.md

@@ -1,40 +1,40 @@
-# ◆ KnowzCode - Status Map
-
-**Purpose:** This document tracks the development status of all implementable components (NodeIDs) defined in `knowzcode_architecture.md`. It guides task selection, groups related work via `WorkGroupID`, and provides a quick overview of project progress. It is updated by the KnowzCode AI Agent as per `knowzcode_loop.md`.
-
-**Note:** All paths are relative to the project root where the knowzcode files reside. The specs/ directory is within your project directory alongside other knowzcode files.
-
----
-**Progress: 0%**
----
-
-| Status | WorkGroupID | Node ID | Label | Dependencies | Logical Grouping | Spec Link | Classification | Notes / Issues |
-| :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- |
-| ⚪️ `[TODO]` | | `[ExampleNodeID]` | `[Example Node Label]` | `[DepNodeID1]` | `[Example Group]` | `[Spec](knowzcode/specs/ExampleNodeID.md)` | `[Standard]` | |
-| | | | | | | | | |
-| | | | | | | | | |
-
----
-### ◆ KnowzCode Status Legend:
-
-*   ⚪️ **`[TODO]`**: Task is defined and ready to be picked up if dependencies are met. This status also applies to `REFACTOR_` tasks created from technical debt.
-*   📝 **`[NEEDS_SPEC]`**: Node has been identified in the architecture but requires a detailed specification to be drafted.
-*   ◆ **`[WIP]`**: ◆ **KnowzCode Working** - Work In Progress. The KnowzCode AI Agent is currently working on this node as part of the specified `WorkGroupID`.
-*   🟢 **`[VERIFIED]`**: The primary completion state. The node has been implemented, all ARC Verification Criteria are met, the spec is finalized to "as-built", and all outcomes are logged.
-*   ❗ **`[ISSUE]`**: A significant issue or blocker has been identified, preventing progress. Details should be in `knowzcode_log.md` or linked in the "Notes / Issues" column.
-
----
-### Notes on Columns:
-
-*   **Status**: The current state of the NodeID (see Legend above).
-*   **WorkGroupID**: A unique ID assigned to a "Change Set" of nodes being worked on together. This is blank unless the `Status` is `[WIP]`.
-*   **Node ID**: The unique identifier for the component, matching the ID used in `knowzcode/knowzcode_architecture.md`.
-*   **Label**: A concise, human-readable name for the NodeID.
-*   **Dependencies**: A comma-separated list of `NodeID`s that must be `[VERIFIED]` before work on this node can begin. Only reference NodeIDs that exist in the architecture diagram. If a dependency's spec doesn't exist, that dependency must be `[NEEDS_SPEC]` status.
-*   **Logical Grouping**: An optional tag to categorize nodes by feature, module, or layer (e.g., "Authentication", "UserAPI").
-*   **Spec Link**: A relative Markdown link to the corresponding specification file in the `knowzcode/specs/` directory.
-*   **Classification**: Optional tag (e.g., `Critical`, `Complex`, `Standard`) to influence planning and review intensity.
-*   **Notes / Issues**: Brief comments, or a reference to a more detailed issue in `knowzcode/knowzcode_log.md`.
-
----
-*(This table will be populated based on `knowzcode_architecture.md`. The AI Agent will then update the `Status` and `WorkGroupID` columns as it processes each Change Set according to `knowzcode_loop.md`.)*
+# ◆ KnowzCode - Status Map
+
+**Purpose:** This document tracks the development status of all implementable components (NodeIDs) defined in `knowzcode_architecture.md`. It guides task selection, groups related work via `WorkGroupID`, and provides a quick overview of project progress. It is updated by the KnowzCode AI Agent as per `knowzcode_loop.md`.
+
+**Note:** All paths are relative to the project root where the knowzcode files reside. The specs/ directory is within your project directory alongside other knowzcode files.
+
+---
+**Progress: 0%**
+---
+
+| Status | WorkGroupID | Node ID | Label | Dependencies | Logical Grouping | Spec Link | Classification | Notes / Issues |
+| :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- |
+| ⚪️ `[TODO]` | | `[ExampleNodeID]` | `[Example Node Label]` | `[DepNodeID1]` | `[Example Group]` | `[Spec](knowzcode/specs/ExampleNodeID.md)` | `[Standard]` | |
+| | | | | | | | | |
+| | | | | | | | | |
+
+---
+### ◆ KnowzCode Status Legend:
+
+*   ⚪️ **`[TODO]`**: Task is defined and ready to be picked up if dependencies are met. This status also applies to `REFACTOR_` tasks created from technical debt.
+*   📝 **`[NEEDS_SPEC]`**: Node has been identified in the architecture but requires a detailed specification to be drafted.
+*   ◆ **`[WIP]`**: ◆ **KnowzCode Working** - Work In Progress. The KnowzCode AI Agent is currently working on this node as part of the specified `WorkGroupID`.
+*   🟢 **`[VERIFIED]`**: The primary completion state. The node has been implemented, all ARC Verification Criteria are met, the spec is finalized to "as-built", and all outcomes are logged.
+*   ❗ **`[ISSUE]`**: A significant issue or blocker has been identified, preventing progress. Details should be in `knowzcode_log.md` or linked in the "Notes / Issues" column.
+
+---
+### Notes on Columns:
+
+*   **Status**: The current state of the NodeID (see Legend above).
+*   **WorkGroupID**: A unique ID assigned to a "Change Set" of nodes being worked on together. This is blank unless the `Status` is `[WIP]`.
+*   **Node ID**: The unique identifier for the component, matching the ID used in `knowzcode/knowzcode_architecture.md`.
+*   **Label**: A concise, human-readable name for the NodeID.
+*   **Dependencies**: A comma-separated list of `NodeID`s that must be `[VERIFIED]` before work on this node can begin. Only reference NodeIDs that exist in the architecture diagram. If a dependency's spec doesn't exist, that dependency must be `[NEEDS_SPEC]` status.
+*   **Logical Grouping**: An optional tag to categorize nodes by feature, module, or layer (e.g., "Authentication", "UserAPI").
+*   **Spec Link**: A relative Markdown link to the corresponding specification file in the `knowzcode/specs/` directory.
+*   **Classification**: Optional tag (e.g., `Critical`, `Complex`, `Standard`) to influence planning and review intensity.
+*   **Notes / Issues**: Brief comments, or a reference to a more detailed issue in `knowzcode/knowzcode_log.md`.
+
+---
+*(This table will be populated based on `knowzcode_architecture.md`. The AI Agent will then update the `Status` and `WorkGroupID` columns as it processes each Change Set according to `knowzcode_loop.md`.)*