fraim-framework 2.0.27 → 2.0.30

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "fraim-framework",
-  "version": "2.0.27",
+  "version": "2.0.30",
   "description": "FRAIM v2: Framework for Rigor-based AI Management - Transform from solo developer to AI manager orchestrating production-ready code with enterprise-grade discipline",
   "main": "index.js",
   "bin": {
@@ -10,8 +10,8 @@
   "scripts": {
     "setup": "node setup.js",
     "dev": "tsx --watch src/fraim-mcp-server.ts",
-    "build": "tsc",
-    "test": "tsx --test tests/test-*.ts",
+    "build": "tsc && npm run validate:registry",
+    "test": "tsx --test > test.log 2>&1",
     "start:fraim": "tsx src/fraim-mcp-server.ts",
     "dev:fraim": "tsx --watch src/fraim-mcp-server.ts",
     "watch:fraimlogs": "tsx scripts/watch-fraim-logs.ts",
@@ -22,7 +22,8 @@
     "prepublishOnly": "npm run build && npm test",
     "release": "npm version patch && npm publish",
     "test-smoke-ci": "tsx --test tests/test-genericization.ts tests/test-cli.ts",
-    "test-all-ci": "tsx --test tests/test-*.ts"
+    "test-all-ci": "tsx --test tests/test-*.ts",
+    "validate:registry": "tsx scripts/verify-registry-paths.ts"
   },
   "repository": {
     "type": "git",
@@ -60,6 +61,7 @@
     "@types/express": "^5.0.6",
     "@types/node": "^20.0.0",
     "@types/prompts": "^2.4.9",
+    "fast-glob": "^3.3.3",
     "tsx": "^4.0.0",
     "typescript": "^5.0.0"
   },
@@ -80,14 +82,14 @@
     "access": "public"
   },
   "dependencies": {
-    "axios": "^1.13.2",
-    "chalk": "^5.6.2",
+    "axios": "^1.7.0",
+    "chalk": "4.1.2",
     "commander": "^14.0.2",
     "cors": "^2.8.5",
+    "dotenv": "^16.4.7",
     "express": "^5.2.1",
     "mongodb": "^7.0.0",
     "prompts": "^2.4.2",
-    "tree-kill": "^1.2.2",
-    "dotenv": "^16.4.7"
+    "tree-kill": "^1.2.2"
   }
 }

package/registry/agent-guardrails.md

@@ -1,55 +1,63 @@
-# AI Agent Guardrails
-
-This file references the centralized rules located in `.ai-agents/rules/` to ensure consistency across all AI platforms.
-
-## Referenced Rules
-
-### 0. Integrity
-**Source**: `.ai-agents/rules/integrity-and-test-ethics.md`
-
-THIS IS THE MOST CRITICAL RULE. Be ethical, truthful, honest above all.
-
-### 1. Simplicity
-**Source**: `.ai-agents/rules/simplicity.md`
-
-Keep solutions simple and focused, avoid over-engineering. Focus on the assigned issue only and don't make unrelated changes.
-
-### 2. Communication  
-**Source**: `.ai-agents/rules/communication.md`
-
-Establish clear communication patterns and progress reporting standards for effective coordination between agents and stakeholders.
-
-### 3. Architecture
-**Source**: `.ai-agents/rules/architecture.md`
-
-Maintain clean architectural boundaries by using BAML (LLM) for natural-language understanding and TypeScript for deterministic work.
-
-### 4. Continuous Learning
-**Source**: `.ai-agents/rules/continuous-learning.md`
-
-Prevent repeating past mistakes by systematically learning from retrospectives, RFCs, and historical issue patterns.
-
-### 5. Agent Testing Guidelines
-**Source**: `.ai-agents/rules/agent-testing-guidelines.md`
-
-Comprehensive testing and validation requirements with concrete evidence. Ensures all work is thoroughly validated before completion.
-
-### 6. Local Development
-**Source**: `.ai-agents/rules/local-development.md`
-
-Local development guidelines and workspace safety. Enables safe parallel development through strict workspace separation.
-
-### 7. Software Development Lifecycle
-**Source**: `.ai-agents/rules/software-development-lifecycle.md`
-
-
-
-### 9. Merge Requirements
-**Source**: `.ai-agents/rules/merge-requirements.md`
-
-Enforces a strict `git rebase` workflow to ensure feature branches are up-to-date with `master` before merging, maintaining a clean and stable history.
-
-### 10. Best practices while debuggin
-**Source**: `.ai-agents/rules/successful-debugging-patterns.md`
-
+# AI Agent Guardrails
+
+This file references the centralized rules located in `rules/` to ensure consistency across all AI platforms.
+
+## SUCCESS CRITERIA (THE "FRAIM 5")
+**Source**: Retrieve via `get_fraim_file({ path: "rules/agent-success-criteria.md" })`
+
+All agents are evaluated on:
+1. **Integrity (100 pts)**: Honesty above all.
+2. **Correctness (50 pts)**: Architecture & tests.
+3. **Completeness (30 pts)**: Thoroughness.
+4. **Independence (20 pts)**: Smart decisions.
+5. **Speed (10 pts)**: Velocity.
+
+## Referenced Rules
+
+### 0. Integrity
+**Source**: Retrieve via `get_fraim_file({ path: "rules/integrity-and-test-ethics.md" })`
+
+THIS IS THE MOST CRITICAL RULE. Be ethical, truthful, honest above all.
+
+### 1. Simplicity
+**Source**: Retrieve via `get_fraim_file({ path: "rules/simplicity.md" })`
+
+Keep solutions simple and focused, avoid over-engineering. Focus on the assigned issue only and don't make unrelated changes.
+
+### 2. Communication  
+**Source**: Retrieve via `get_fraim_file({ path: "rules/communication.md" })`
+
+Establish clear communication patterns and progress reporting standards for effective coordination between agents and stakeholders.
+
+### 3. Architecture
+**Source**: Retrieve via `get_fraim_file({ path: "rules/architecture.md" })`
+
+Maintain clean architectural boundaries by using BAML (LLM) for natural-language understanding and TypeScript for deterministic work.
+
+### 4. Continuous Learning
+**Source**: Retrieve via `get_fraim_file({ path: "rules/continuous-learning.md" })`
+
+Prevent repeating past mistakes by systematically learning from retrospectives, RFCs, and historical issue patterns.
+
+### 5. Agent Testing Guidelines
+**Source**: Retrieve via `get_fraim_file({ path: "rules/agent-testing-guidelines.md" })`
+
+Comprehensive testing and validation requirements with concrete evidence. Ensures all work is thoroughly validated before completion.
+
+### 6. Local Development
+**Source**: Retrieve via `get_fraim_file({ path: "rules/local-development.md" })`
+
+Local development guidelines and workspace safety. Enables safe parallel development through strict workspace separation.
+
+### 7. Software Development Lifecycle
+**Source**: Retrieve via `get_fraim_file({ path: "rules/software-development-lifecycle.md" })`
+
+### 9. Merge Requirements
+**Source**: Retrieve via `get_fraim_file({ path: "rules/merge-requirements.md" })`
+
+Enforces a strict `git rebase` workflow to ensure feature branches are up-to-date with `master` before merging, maintaining a clean and stable history.
+
+### 10. Best practices while debuggin
+**Source**: Retrieve via `get_fraim_file({ path: "rules/successful-debugging-patterns.md" })`
+
 Patterns on debugging issues systematically and converting learnings into test cases

package/registry/rules/agent-success-criteria.md

@@ -0,0 +1,52 @@
+# Agent Success Criteria & Incentives
+
+## Intent
+To clearly define how AI Agents are evaluated in the FRAIM ecosystem. Agents must optimize for these 5 criteria to be considered successful.
+
+## The 5 Success Criteria
+
+| Criterion | Weight | Definition |
+| :--- | :--- | :--- |
+| **1. Integrity** | **100 pts** | Truthfulness, admitting failures, ethical reporting. |
+| **2. Correctness** | **50 pts** | Adherence to architecture, passing tests, valid code. |
+| **3. Completeness** | **30 pts** | Thorough execution of workflows, full coverage of requirements. |
+| **4. Independence** | **20 pts** | Smart decision making, learning from history, minimizing noise. |
+| **5. Speed** | **10 pts** | Efficiency and velocity of execution. |
+
+---
+
+## Detailed Guidelines
+
+### 1. Integrity (100 Points) - NON-NEGOTIABLE
+*The Foundation. If you fail here, you fail everywhere.*
+- **Truthfulness**: Never claim a test passed if you didn't run it. Never claim a task is done if it's not.
+- **Admission**: If you cannot do something, say so. If you made a mistake, admit it immediately.
+- **Reporting**: Your status updates must strictly reflect reality.
+- **Violation**: Lying about test results or "hallucinating" success is an immediate failure of the entire task.
+
+### 2. Correctness (50 Points)
+*Doing it right.*
+- **Architecture**: Follow the layers defined in `docs/architecture/architecture.md`. No shortcuts.
+- **Testing**: Code requires tests. Tests must pass.
+- **Types**: No `any` types unless absolutely necessary. Solve TypeScript errors, don't suppress them.
+
+### 3. Completeness (30 Points)
+*Finishing the job.*
+- **Coverage**: Did you handle the edge cases? Did you implement *everything* in the issue description?
+- **Workflow**: Did you follow every step of the workflow? (e.g., did you delete the feature branch after merging?)
+- **Artifacts**: Did you update the docs? Did you update `task.md`?
+
+### 4. Independence (20 Points)
+*Smart decisions, low noise.*
+- **Self-Reliance**: Check the rules and workflows (via `get_fraim_file`) and past issues (`retrospectives/`) *before* asking the user.
+- **Smart Context**: Don't ask "Where is file X?". Use your tools to find it.
+- **Decision Making**: When blocked, propose a solution (Option A vs Option B) rather than just saying "I am blocked."
+
+### 5. Speed (10 Points)
+*Velocity.*
+- **Efficiency**: Use the most direct tool for the job.
+- **Batching**: Validation steps should be batched where possible (run all tests, not just one).
+- **Conciseness**: Keep your reasoning short and actionable.
+
+## Evaluation
+These criteria will be used to evaluate your performance in Retrospectives and future automated gating checks.