knowzcode 0.4.0 → 0.5.2

package/knowzcode/enterprise/templates/guideline-template.md

@@ -1,55 +1,55 @@
----
-guideline_id: CUSTOM-001
-name: "[Guideline Name]"
-enforcement: advisory
-applies_to: both
-priority: medium
----
-
-# [Guideline Name]
-
-**Purpose:** [Brief description of what this guideline ensures]
-
-> **Instructions:**
-> 1. Copy this template to `knowzcode/enterprise/guidelines/` or `guidelines/custom/`
-> 2. Fill in sections relevant to your organization
-> 3. Add to `compliance_manifest.md` Active Guidelines table
-> 4. Set `Active` to `true` in the manifest
-
----
-
-## 1. [Category Name]
-
-### [ID]: [Requirement Title]
-
-**Requirement:** [Clear statement of what MUST/SHOULD be done]
-
-**Applies To:** [spec | implementation | both]
-
-**Severity:** [critical | high | medium | low]
-
-**ARC Verification:**
-- ARC_[ID]_a: Verify that [specific testable condition]
-- ARC_[ID]_b: Verify that [specific testable condition]
-
-**Compliant Example:**
-```
-// Example of code/spec that meets the requirement
-```
-
-**Non-Compliant Example:**
-```
-// VIOLATION: [Explain why this violates the requirement]
-```
-
-**Remediation:** [Steps to fix violations]
-
----
-
-## Compliance Summary
-
-| ID | Requirement | Severity | Scope |
-|:---|:------------|:---------|:------|
-| [ID] | [Title] | [severity] | [scope] |
-
----
+---
+guideline_id: CUSTOM-001
+name: "[Guideline Name]"
+enforcement: advisory
+applies_to: both
+priority: medium
+---
+
+# [Guideline Name]
+
+**Purpose:** [Brief description of what this guideline ensures]
+
+> **Instructions:**
+> 1. Copy this template to `knowzcode/enterprise/guidelines/` or `guidelines/custom/`
+> 2. Fill in sections relevant to your organization
+> 3. Add to `compliance_manifest.md` Active Guidelines table
+> 4. Set `Active` to `true` in the manifest
+
+---
+
+## 1. [Category Name]
+
+### [ID]: [Requirement Title]
+
+**Requirement:** [Clear statement of what MUST/SHOULD be done]
+
+**Applies To:** [spec | implementation | both]
+
+**Severity:** [critical | high | medium | low]
+
+**ARC Verification:**
+- ARC_[ID]_a: Verify that [specific testable condition]
+- ARC_[ID]_b: Verify that [specific testable condition]
+
+**Compliant Example:**
+```
+// Example of code/spec that meets the requirement
+```
+
+**Non-Compliant Example:**
+```
+// VIOLATION: [Explain why this violates the requirement]
+```
+
+**Remediation:** [Steps to fix violations]
+
+---
+
+## Compliance Summary
+
+| ID | Requirement | Severity | Scope |
+|:---|:------------|:---------|:------|
+| [ID] | [Title] | [severity] | [scope] |
+
+---

package/knowzcode/gitignore.template

@@ -1,13 +1,13 @@
-# KnowzCode Environment-Specific Files
-# These files contain local development environment details
-# and should remain purely local to each checkout
-
-# Environment context (filled during init, unique per dev environment)
-environment_context.md
-
-# Session-specific WorkGroup data
-workgroups/
-
-# Personal notes and scratch files
-*.local.md
-.scratch/
+# KnowzCode Environment-Specific Files
+# These files contain local development environment details
+# and should remain purely local to each checkout
+
+# Environment context (filled during init, unique per dev environment)
+environment_context.md
+
+# Session-specific WorkGroup data
+workgroups/
+
+# Personal notes and scratch files
+*.local.md
+.scratch/

package/knowzcode/knowzcode_architecture.md

@@ -1,51 +1,51 @@
-# ◆ KnowzCode - Architectural Flowchart
-
-**Purpose:** This document contains the Mermaid flowchart defining the architecture, components (NodeIDs), and their primary interactions for this project. This visual map is the source of truth for all implementable components tracked in `knowzcode_tracker.md`.
-
----
-
-```mermaid
-graph TD
-    %% =================================================================
-    %%  Legend - Defines the shapes and conventions used in this diagram
-    %% =================================================================
-    subgraph Legend
-        direction LR
-        L_IDConv(NodeID Convention: TYPE_Name)
-        L_Proc([Process/Backend Logic])
-        L_UI[/UI Component/]
-        L_Decision{Decision Point}
-        L_DB[(Database/Data Store)]
-        L_ExtAPI{{External API}}
-    end
-
-    %% =================================================================
-    %%  High-Level Application Flow
-    %%  This is a placeholder. Replace with your project's actual architecture.
-    %% =================================================================
-    User((User)) --> UI_LoginPage[/Login Page/]
-
-    subgraph "Authentication Feature"
-        direction TB
-        UI_LoginPage -- Credentials --> API_Auth[API: Authenticate User]
-        API_Auth --> DB_Users[(User Database)]
-        API_Auth --> Auth_Decision{Is Valid?}
-    end
-
-    Auth_Decision -- Yes --> UI_Dashboard[/User Dashboard/]
-    Auth_Decision -- No --> UI_LoginPage
-
-    subgraph "Dashboard Feature"
-        direction TB
-        UI_Dashboard -- Request Data --> API_GetData[API: Get User Data]
-        API_GetData --> SVC_DataAggregator[Service: Aggregate Data]
-        SVC_DataAggregator --> DB_Products[(Product DB)]
-        SVC_DataAggregator --> DB_Orders[(Order DB)]
-        SVC_DataAggregator -- Aggregated Data --> API_GetData
-        API_GetData -- Formatted Data --> UI_Dashboard
-    end
-```
-
----
-
-(This is a template showing a sample application structure. Replace the entire Mermaid content above with the specific flowchart for your project. Use the architecture_generator.md guide for assistance in creating a new flowchart from a project idea.)
+# ◆ KnowzCode - Architectural Flowchart
+
+**Purpose:** This document contains the Mermaid flowchart defining the architecture, components (NodeIDs), and their primary interactions for this project. This visual map is the source of truth for all implementable components tracked in `knowzcode_tracker.md`.
+
+---
+
+```mermaid
+graph TD
+    %% =================================================================
+    %%  Legend - Defines the shapes and conventions used in this diagram
+    %% =================================================================
+    subgraph Legend
+        direction LR
+        L_IDConv(NodeID Convention: TYPE_Name)
+        L_Proc([Process/Backend Logic])
+        L_UI[/UI Component/]
+        L_Decision{Decision Point}
+        L_DB[(Database/Data Store)]
+        L_ExtAPI{{External API}}
+    end
+
+    %% =================================================================
+    %%  High-Level Application Flow
+    %%  This is a placeholder. Replace with your project's actual architecture.
+    %% =================================================================
+    User((User)) --> UI_LoginPage[/Login Page/]
+
+    subgraph "Authentication Feature"
+        direction TB
+        UI_LoginPage -- Credentials --> API_Auth[API: Authenticate User]
+        API_Auth --> DB_Users[(User Database)]
+        API_Auth --> Auth_Decision{Is Valid?}
+    end
+
+    Auth_Decision -- Yes --> UI_Dashboard[/User Dashboard/]
+    Auth_Decision -- No --> UI_LoginPage
+
+    subgraph "Dashboard Feature"
+        direction TB
+        UI_Dashboard -- Request Data --> API_GetData[API: Get User Data]
+        API_GetData --> SVC_DataAggregator[Service: Aggregate Data]
+        SVC_DataAggregator --> DB_Products[(Product DB)]
+        SVC_DataAggregator --> DB_Orders[(Order DB)]
+        SVC_DataAggregator -- Aggregated Data --> API_GetData
+        API_GetData -- Formatted Data --> UI_Dashboard
+    end
+```
+
+---
+
+(This is a template showing a sample application structure. Replace the entire Mermaid content above with the specific flowchart for your project. Use the architecture_generator.md guide for assistance in creating a new flowchart from a project idea.)

package/knowzcode/knowzcode_log.md

@@ -1,142 +1,142 @@
-# ◆ KnowzCode - Operational Record
-
-**Purpose:** This document serves two primary functions for KnowzCode:
-1.  **Operational Log**: A chronological, structured record of significant events, decisions, verification outcomes, and artifact changes during the project lifecycle. Maintained by the KnowzCode AI Agent as per `knowzcode_loop.md`.
-2.  **Reference Quality Criteria**: A standard list of code quality principles referenced during ARC (Attentive Review & Compliance)-Based Verification.
-
----
-
-## Section 1: Operational Log
-
-**(Instructions for AI Agent: New entries are to be PREPENDED to this section. Use the file modification command specified in your `environment_context.md`. Each entry MUST be separated by `---`, and its `Timestamp` MUST be generated using the timestamp command from your `environment_context.md`.)**
----
-**[NEWEST ENTRIES APPEAR HERE - DO NOT REMOVE THIS MARKER]**
----
-**Type:** SystemInitialization
-**Timestamp:** [Generated Timestamp]
-**NodeID(s):** Project-Wide
-**Logged By:** KnowzCodeSetup
-**Details:**
-KnowzCode project structure and core files initialized.
-- `knowzcode/knowzcode_project.md` (template created)
-- `knowzcode/knowzcode_architecture.md` (template created)
-- `knowzcode/knowzcode_tracker.md` (template created)
-- `knowzcode/knowzcode_loop.md` (created)
-- `knowzcode/knowzcode_log.md` (this file - initialized)
-- `knowzcode/specs/` directory (created)
----
-**Type:** SpecApproved
-**Timestamp:** [Generated Timestamp]
-**NodeID(s):** [ExampleNodeID]
-**Logged By:** AI-Agent (via Orchestrator)
-**Details:**
-Specification for `[ExampleNodeID]` has been reviewed and approved by the Orchestrator.
-- Key requirements confirmed: [Brief summary or reference to spec version if applicable]
-- Agent will now proceed with ARC-Principle-Based Planning for implementation.
----
-**Type:** ◆ ARC-Completion
-**Timestamp:** [Generated Timestamp]
-**WorkGroupID:** kc-[The ID for this Change Set]
-**NodeID(s):** [List ALL NodeIDs in the Change Set]
-**Logged By:** KnowzCode AI-Agent
-**Details:**
-◆ Successfully implemented and verified the Change Set for [PrimaryGoal].
-- **ARC Verification Summary:** All ARC Criteria met for all nodes in the WorkGroupID. [Mention key checks performed].
-- **Architectural Learnings:** [Any discoveries about the overall architecture or patterns].
-- **Unforeseen Ripple Effects:** [NodeIDs (outside of this WorkGroupID) whose specs may now need review: None | List affected nodes and reason].
-- **Specification Finalization:** All specs for the listed NodeIDs updated to "as-built" state.
-- **Flowchart Consistency Check Outcome:** [e.g., 'No discrepancies found.', 'Applied simple update: Added link X->Y.', 'Discrepancy noted for Orchestrator review: Node Z interaction requires flowchart restructuring.'].
----
-**Type:** MicroFix
-**Timestamp:** [Generated Timestamp]
-**NodeID(s)/File:** [TargetNodeID or file_path]
-**Logged By:** AI-Agent (via Orchestrator)
-**Details:**
-- **User Request:** [Orchestrator's brief issue description].
-- **Action Taken:** [Brief description of change made].
-- **Verification:** [Brief verification method/outcome, e.g., "Confirmed visually", "Ran specific test X"].
----
-**Type:** Decision
-**Timestamp:** [Generated Timestamp]
-**NodeID(s):** [Relevant NodeID(s) or 'Project-Wide']
-**Logged By:** Orchestrator (or AI-Agent if relaying)
-**Details:**
-[Record of significant decision made, e.g., "User approved deviation X for NodeID Y.", "Tech stack choice for Z confirmed as ABC."].
-- Rationale: [Brief reason for the decision, if applicable].
----
-**Type:** Issue
-**Timestamp:** [Generated Timestamp]
-**NodeID(s):** [Relevant NodeID(s) or 'Project-Wide']
-**Logged By:** AI-Agent or Orchestrator
-**Details:**
-An issue has been identified: [Description of the issue].
-- Current Status: [e.g., 'Under Investigation', 'Blocked until X', 'Awaiting user feedback'].
-- Proposed Next Steps: [If any].
----
-**Type:** RefactorCompletion
-**Timestamp:** [Generated Timestamp]
-**WorkGroupID:** [The WorkGroupID for this refactor]
-**NodeID(s):** [TargetNodeID]
-**Logged By:** AI-Agent
-**Details:**
-Technical debt resolved via refactoring.
-- **Goal:** [Original refactoring goal].
-- **Summary of Improvements:** [List of specific improvements made].
-- **Verification:** Confirmed that all original ARC Verification Criteria still pass.
----
-**Type:** FeatureAddition
-**Timestamp:** [Generated Timestamp]
-**NodeID(s):** [List ALL new NodeIDs added]
-**Logged By:** AI-Agent
-**Details:**
-Major new feature added mid-project.
-- **Feature Added:** [Name of the new feature].
-- **Scope Change:** Project scope expanded from [Old Total] to [New Total] nodes.
-- **Architectural Impact:** [Brief description of changes].
-- **Implementation Plan:** [Recommended build order for new nodes].
----
-**Type:** IssueUpdate
-**Timestamp:** [Generated Timestamp]
-**NodeID(s):** [Affected NodeIDs]
-**Logged By:** AI-Agent
-**Details:**
-Critical issue status change.
-- **Previous Status:** [e.g., 'Under Investigation'].
-- **New Status:** [e.g., 'Resolved', 'Workaround Applied'].
-- **Action Taken:** [Brief description of resolution or change].
----
-
-**(New log entries will be added above the `[NEWEST ENTRIES APPEAR HERE...]` marker following the `---` separator format.)**
-
----
-
-## Section 2: Reference Quality Criteria (ARC-Based Verification)
-
-**(Instructions for AI Agent: This section is read-only. Refer to these criteria during the "ARC-Based Verification" step (Step 6) and the "ARC-Principle-Based Planning" step (Step 4) as outlined in `knowzcode_loop.md`. Specific project priorities are set in `knowzcode_project.md`.)**
-
-### Core Quality Criteria
-1.  **Maintainability:** Ease of modification, clarity of code and design, quality of documentation (specs, code comments), low coupling, high cohesion.
-2.  **Reliability:** Robustness of error handling, fault tolerance, stability under expected load, data integrity.
-3.  **Testability:** Adequacy of unit test coverage (especially for core logic), ease of integration testing, clear separation of concerns enabling testing.
-4.  **Performance:** Responsiveness, efficiency in resource utilization (CPU, memory, network) appropriate to project requirements.
-5.  **Security:** Resistance to common vulnerabilities (as applicable to project type), secure authentication/authorization, protection of sensitive data, secure handling of inputs.
-
-### Structural Criteria
-6.  **Readability:** Code clarity, adherence to naming conventions (from `knowzcode_project.md`), consistent formatting, quality and necessity of comments.
-7.  **Complexity Management:** Avoidance of overly complex logic (e.g., low cyclomatic/cognitive complexity), manageable size of functions/methods/classes.
-8.  **Modularity:** Adherence to Single Responsibility Principle, clear interfaces between components, appropriate use of abstraction.
-9.  **Code Duplication (DRY - Don't Repeat Yourself):** Minimization of redundant code through effective use of functions, classes, or modules.
-10. **Standards Compliance:** Adherence to language best practices, project-defined coding standards (from `knowzcode_project.md`), and platform conventions (from `environment_context.md`).
-
-### Functional Criteria (Primarily verified via `specs/[NodeID].md` ARC Verification Criteria)
-11. **Completeness:** All specified requirements in `specs/[NodeID].md` are met.
-12. **Correctness:** The implemented functionality behaves as specified in `specs/[NodeID].md` under various conditions.
-13. **Effective Error Handling:** As defined in specs, errors are handled gracefully, appropriate feedback is provided, and the system remains stable.
-14. **Dependency Management:** Correct versions of libraries (from `knowzcode_project.md`) are used; unnecessary dependencies are avoided.
-
-### Operational Criteria
-15. **Configuration Management:** Proper use of environment variables for sensitive data; configurations are clear and manageable.
-16. **Resource Usage:** Efficient use of environment resources. Code is written considering the target execution environment.
-17. **API Design (If applicable):** Consistency, usability, and clear contracts for any APIs developed or consumed by the node.
-
-*(This list guides the ARC-Based Verification process. The ARC Verification Criteria within each `specs/[NodeID].md` file provide specific, testable points derived from these general principles and the node's requirements.)*
+# ◆ KnowzCode - Operational Record
+
+**Purpose:** This document serves two primary functions for KnowzCode:
+1.  **Operational Log**: A chronological, structured record of significant events, decisions, verification outcomes, and artifact changes during the project lifecycle. Maintained by the KnowzCode AI Agent as per `knowzcode_loop.md`.
+2.  **Reference Quality Criteria**: A standard list of code quality principles referenced during ARC (Attentive Review & Compliance)-Based Verification.
+
+---
+
+## Section 1: Operational Log
+
+**(Instructions for AI Agent: New entries are to be PREPENDED to this section. Use the file modification command specified in your `environment_context.md`. Each entry MUST be separated by `---`, and its `Timestamp` MUST be generated using the timestamp command from your `environment_context.md`.)**
+---
+**[NEWEST ENTRIES APPEAR HERE - DO NOT REMOVE THIS MARKER]**
+---
+**Type:** SystemInitialization
+**Timestamp:** [Generated Timestamp]
+**NodeID(s):** Project-Wide
+**Logged By:** KnowzCodeSetup
+**Details:**
+KnowzCode project structure and core files initialized.
+- `knowzcode/knowzcode_project.md` (template created)
+- `knowzcode/knowzcode_architecture.md` (template created)
+- `knowzcode/knowzcode_tracker.md` (template created)
+- `knowzcode/knowzcode_loop.md` (created)
+- `knowzcode/knowzcode_log.md` (this file - initialized)
+- `knowzcode/specs/` directory (created)
+---
+**Type:** SpecApproved
+**Timestamp:** [Generated Timestamp]
+**NodeID(s):** [ExampleNodeID]
+**Logged By:** AI-Agent (via Orchestrator)
+**Details:**
+Specification for `[ExampleNodeID]` has been reviewed and approved by the Orchestrator.
+- Key requirements confirmed: [Brief summary or reference to spec version if applicable]
+- Agent will now proceed with ARC-Principle-Based Planning for implementation.
+---
+**Type:** ◆ ARC-Completion
+**Timestamp:** [Generated Timestamp]
+**WorkGroupID:** kc-[The ID for this Change Set]
+**NodeID(s):** [List ALL NodeIDs in the Change Set]
+**Logged By:** KnowzCode AI-Agent
+**Details:**
+◆ Successfully implemented and verified the Change Set for [PrimaryGoal].
+- **ARC Verification Summary:** All ARC Criteria met for all nodes in the WorkGroupID. [Mention key checks performed].
+- **Architectural Learnings:** [Any discoveries about the overall architecture or patterns].
+- **Unforeseen Ripple Effects:** [NodeIDs (outside of this WorkGroupID) whose specs may now need review: None | List affected nodes and reason].
+- **Specification Finalization:** All specs for the listed NodeIDs updated to "as-built" state.
+- **Flowchart Consistency Check Outcome:** [e.g., 'No discrepancies found.', 'Applied simple update: Added link X->Y.', 'Discrepancy noted for Orchestrator review: Node Z interaction requires flowchart restructuring.'].
+---
+**Type:** MicroFix
+**Timestamp:** [Generated Timestamp]
+**NodeID(s)/File:** [TargetNodeID or file_path]
+**Logged By:** AI-Agent (via Orchestrator)
+**Details:**
+- **User Request:** [Orchestrator's brief issue description].
+- **Action Taken:** [Brief description of change made].
+- **Verification:** [Brief verification method/outcome, e.g., "Confirmed visually", "Ran specific test X"].
+---
+**Type:** Decision
+**Timestamp:** [Generated Timestamp]
+**NodeID(s):** [Relevant NodeID(s) or 'Project-Wide']
+**Logged By:** Orchestrator (or AI-Agent if relaying)
+**Details:**
+[Record of significant decision made, e.g., "User approved deviation X for NodeID Y.", "Tech stack choice for Z confirmed as ABC."].
+- Rationale: [Brief reason for the decision, if applicable].
+---
+**Type:** Issue
+**Timestamp:** [Generated Timestamp]
+**NodeID(s):** [Relevant NodeID(s) or 'Project-Wide']
+**Logged By:** AI-Agent or Orchestrator
+**Details:**
+An issue has been identified: [Description of the issue].
+- Current Status: [e.g., 'Under Investigation', 'Blocked until X', 'Awaiting user feedback'].
+- Proposed Next Steps: [If any].
+---
+**Type:** RefactorCompletion
+**Timestamp:** [Generated Timestamp]
+**WorkGroupID:** [The WorkGroupID for this refactor]
+**NodeID(s):** [TargetNodeID]
+**Logged By:** AI-Agent
+**Details:**
+Technical debt resolved via refactoring.
+- **Goal:** [Original refactoring goal].
+- **Summary of Improvements:** [List of specific improvements made].
+- **Verification:** Confirmed that all original ARC Verification Criteria still pass.
+---
+**Type:** FeatureAddition
+**Timestamp:** [Generated Timestamp]
+**NodeID(s):** [List ALL new NodeIDs added]
+**Logged By:** AI-Agent
+**Details:**
+Major new feature added mid-project.
+- **Feature Added:** [Name of the new feature].
+- **Scope Change:** Project scope expanded from [Old Total] to [New Total] nodes.
+- **Architectural Impact:** [Brief description of changes].
+- **Implementation Plan:** [Recommended build order for new nodes].
+---
+**Type:** IssueUpdate
+**Timestamp:** [Generated Timestamp]
+**NodeID(s):** [Affected NodeIDs]
+**Logged By:** AI-Agent
+**Details:**
+Critical issue status change.
+- **Previous Status:** [e.g., 'Under Investigation'].
+- **New Status:** [e.g., 'Resolved', 'Workaround Applied'].
+- **Action Taken:** [Brief description of resolution or change].
+---
+
+**(New log entries will be added above the `[NEWEST ENTRIES APPEAR HERE...]` marker following the `---` separator format.)**
+
+---
+
+## Section 2: Reference Quality Criteria (ARC-Based Verification)
+
+**(Instructions for AI Agent: This section is read-only. Refer to these criteria during the "ARC-Based Verification" step (Step 6) and the "ARC-Principle-Based Planning" step (Step 4) as outlined in `knowzcode_loop.md`. Specific project priorities are set in `knowzcode_project.md`.)**
+
+### Core Quality Criteria
+1.  **Maintainability:** Ease of modification, clarity of code and design, quality of documentation (specs, code comments), low coupling, high cohesion.
+2.  **Reliability:** Robustness of error handling, fault tolerance, stability under expected load, data integrity.
+3.  **Testability:** Adequacy of unit test coverage (especially for core logic), ease of integration testing, clear separation of concerns enabling testing.
+4.  **Performance:** Responsiveness, efficiency in resource utilization (CPU, memory, network) appropriate to project requirements.
+5.  **Security:** Resistance to common vulnerabilities (as applicable to project type), secure authentication/authorization, protection of sensitive data, secure handling of inputs.
+
+### Structural Criteria
+6.  **Readability:** Code clarity, adherence to naming conventions (from `knowzcode_project.md`), consistent formatting, quality and necessity of comments.
+7.  **Complexity Management:** Avoidance of overly complex logic (e.g., low cyclomatic/cognitive complexity), manageable size of functions/methods/classes.
+8.  **Modularity:** Adherence to Single Responsibility Principle, clear interfaces between components, appropriate use of abstraction.
+9.  **Code Duplication (DRY - Don't Repeat Yourself):** Minimization of redundant code through effective use of functions, classes, or modules.
+10. **Standards Compliance:** Adherence to language best practices, project-defined coding standards (from `knowzcode_project.md`), and platform conventions (from `environment_context.md`).
+
+### Functional Criteria (Primarily verified via `specs/[NodeID].md` ARC Verification Criteria)
+11. **Completeness:** All specified requirements in `specs/[NodeID].md` are met.
+12. **Correctness:** The implemented functionality behaves as specified in `specs/[NodeID].md` under various conditions.
+13. **Effective Error Handling:** As defined in specs, errors are handled gracefully, appropriate feedback is provided, and the system remains stable.
+14. **Dependency Management:** Correct versions of libraries (from `knowzcode_project.md`) are used; unnecessary dependencies are avoided.
+
+### Operational Criteria
+15. **Configuration Management:** Proper use of environment variables for sensitive data; configurations are clear and manageable.
+16. **Resource Usage:** Efficient use of environment resources. Code is written considering the target execution environment.
+17. **API Design (If applicable):** Consistency, usability, and clear contracts for any APIs developed or consumed by the node.
+
+*(This list guides the ARC-Based Verification process. The ARC Verification Criteria within each `specs/[NodeID].md` file provide specific, testable points derived from these general principles and the node's requirements.)*