fraim-framework 2.0.55 → 2.0.56

package/dist/registry/templates/evidence/Implementation-BugEvidence.md

@@ -0,0 +1,94 @@
+# Bug: <Title>
+Issue: #<issue>  
+Bug Spec: <Link to Bug Spec>
+PR: <Link to PR>
+
+## Completeness Evidence
+ - Issue tagged with label `phase:impl`: Yes/No
+ - Issue tagged with label `status:needs-review`: Yes/No
+ - All files committed/synced to branch: Yes/No
+
+## Feedback Received
+### PR Comments
+ - Table with following columns 
+   - PR Comment
+   - How Addressed
+
+### User Feedback (Direct)
+ - Table with following columns
+   - Feedback Content
+   - How Addressed
+
+## Implementation Quality Checkpoints
+ - [ ] Code complexity reviewed (no overengineering)
+ - [ ] No resource waste (excessive retries, delays, workarounds)
+ - [ ] Solution based on proven approach from design phase
+ - [ ] All new files/functions are actually used
+
+## Validation Evidence
+- Complete valiation performed as suggested in bug spec: Yes/No
+- **MANDATORY**: Evidence must reflect actual validation status, not assumptions
+- **MANDATORY**: Cannot mark automated validations as "pending" without attempting them first
+- Table with following columns
+   - Validation Step (manual vs automated)
+   - Validation Result (pass vs fail)
+   - Evidence (actual command/output or explanation why not applicable)
+   - Failure Analysis (if fail)
+
+## New Files/Functions Created
+ - Table with the following columns
+    - File/Function Name
+    - Purpose
+    - Who is using/importing/calling it
+    - Is it actually used? (Yes/No - if No, explain why it exists)
+
+## New Tests Added
+- Required if existing test cases did not repro the bug, Optional if bug fix made previously failing test cases pass
+- **MANDATORY**: For each new test case added, you MUST:
+  - Show actual test execution command run
+  - Show actual test output (exit code and results)
+  - Document whether it passed/failed
+  - Cannot claim tests "need fixes" without attempting execution first
+
+## Test Execution Log
+**MANDATORY**: Include actual test execution results below:
+
+```bash
+# Example: Running test file
+$ npm run test -- test-XXX-fix.ts
+# [Include actual output here]
+# Exit code: 0 (success) or non-zero (failure)
+```
+
+**For each test file**:
+- Command executed: `[command]`
+- Exit code: `[0 or non-zero]`
+- Passed tests: `[count]`
+- Failed tests: `[count]`
+- Output excerpt: `[relevant lines]`
+
+## Existing Test Suites Run
+ - Table with following columns
+    - Test Suite
+    - Was it Run (if not, why not - it's ok to not run a suite if there is no impact of your work to it as covered in agent-testing-guidelines.md)
+    - Failing Tests
+    - Failure Analysis (if any tests fail)
+
+## Pre-Completion Reflection
+
+[Include reflection analysis here following `get_fraim_file({ path: "rules/mandatory-pre-completion-reflection.md" })`]
+
+✅ Reflection Phase 1 (Claim Verification) completed: YES/NO
+✅ Reflection Phase 2 (Risk Analysis) completed: YES/NO
+✅ Reflection Phase 3 (Validation Plan Check) completed: YES/NO
+✅ Reflection Phase 4 (Self-Audit) completed: YES/NO
+✅ All blockers from reflection addressed: YES/NO
+✅ Confidence level: X% (must be ≥ 90% to proceed)
+
+**Reflection Summary:**
+[Brief summary of key findings from reflection]
+
+## Continous Learning
+ - Table with following columns
+    - Learning
+    - Agent Rule Updates (what agent rule file was updated to ensure the learning is durable)

package/dist/registry/templates/evidence/Implementation-FeatureEvidence.md

@@ -0,0 +1,129 @@
+# Feature: <Title>
+Issue: #<issue>  
+Tech Spec: <Link to tech spec>
+PR: <Link to PR>
+
+## Completeness Evidence
+ - All phases of tech spec complete: Yes/No 
+ - Issue tagged with label `phase:impl`: Yes/No
+ - Issue tagged with label `status:needs-review`: Yes/No
+ - All files committed/synced to branch: Yes/No
+
+## Feedback Received
+### PR Comments
+ - Table with following columns 
+   - PR Comment
+   - How Addressed
+
+### User Feedback (Direct)
+ - Table with following columns
+   - Feedback Content
+   - How Addressed
+
+## Implementation Quality Checkpoints
+ - [ ] Code complexity reviewed (no overengineering)
+ - [ ] No resource waste (excessive retries, delays, workarounds)
+ - [ ] Solution based on proven prototype from design phase
+ - [ ] All new files/functions are actually used
+
+## Validation Evidence
+ - Complete validation performed as suggested in tech spec: Yes/No
+ - **IMPORTANT**: Post full test output (not just "tests passing ✅")
+ - Table with following columns
+    - Validation Step (manual vs automated)
+    - Validation Result (pass vs fail)
+    - Failure Analysis (if fail)
+
+### Example: Full Test Output
+```
+🚀 Starting Calendar-Goal Analysis API Tests
+
+Running 3 tests
+✔ Edge case - no goals defined (67.8ms)
+✔ Multi-tenancy data isolation (205.9ms)
+✔ Full analysis flow (passed)
+
+❌ Total Failed Tests: 0
+```
+
+### Example: Database Objects (if applicable)
+```javascript
+{
+  _id: ObjectId("68e81da2a87a1a0f91589023"),
+  executive_id: "demo-exec-001",
+  title: "Increase Enterprise Sales by 30%",
+  timeframe: "QUARTERLY",
+  priority: 9,
+  status: "IN_PROGRESS"
+}
+```
+
+### Example: API Request/Response (if applicable)
+**Request:**
+```http
+GET /executive-goals/calendar-analysis?timeframe=backward&period=7
+Headers:
+  x-executive-id: demo-exec-001
+```
+
+**Response (200 OK):**
+```json
+{
+  "success": true,
+  "analysis": {
+    "executive_id": "demo-exec-001",
+    "total_calendar_hours": 7.5,
+    "goal_breakdown": [
+      {
+        "goal_id": "68e81da2a87a1a0f91589025",
+        "goal_title": "Launch AI Product Line",
+        "total_hours": 2.5,
+        "percentage": 33.3,
+        "meeting_ids": ["event-002", "event-007"]
+      }
+    ]
+  }
+}
+```
+
+## New Files/Functions Created
+ - Table with the following columns
+    - File/Function Name
+    - Purpose
+    - Who is using/importing/calling it
+    - Is it actually used? (Yes/No - if No, explain why it exists)
+
+## New Tests Added
+ - Added all tests suggested in tech spec: Yes/No
+ - Table with the following columns
+    - Test Case Name
+    - What is test case validating
+    - Test Result (pass vs fail)
+    - Failure Analysis (if fail)
+
+## Existing Test Suites Run
+ - Table with following columns
+    - Test Suite
+    - Was it Run (if not, why not - it's ok to not run a suite if there is no impact of your work to it as covered in agent-testing-guidelines.md)
+    - Failing Tests
+    - Failure Analysis (if any tests fail)
+
+   
+## Pre-Completion Reflection
+
+[Include reflection analysis here following `get_fraim_file({ path: "rules/mandatory-pre-completion-reflection.md" })`]
+
+✅ Reflection Phase 1 (Claim Verification) completed: YES/NO
+✅ Reflection Phase 2 (Risk Analysis) completed: YES/NO
+✅ Reflection Phase 3 (Validation Plan Check) completed: YES/NO
+✅ Reflection Phase 4 (Self-Audit) completed: YES/NO
+✅ All blockers from reflection addressed: YES/NO
+✅ Confidence level: X% (must be ≥ 90% to proceed)
+
+**Reflection Summary:**
+[Brief summary of key findings from reflection]
+
+## Continous Learning
+ - Table with following columns
+    - Learning
+    - Agent Rule Updates (what agent rule file was updated to ensure the learning is durable)

package/dist/registry/templates/evidence/Spec-Evidence.md

@@ -0,0 +1,19 @@
+# Feature Specification: <Title>
+Issue: #<issue>  
+PR: <Link to PR>
+
+## Completeness Evidence
+ - Issue tagged with label `phase:spec`: Yes/No
+ - Issue tagged with label `status:needs-review`: Yes/No
+ - All specification documents committed/synced to branch: Yes/No
+ - Table with following columns 
+   - Customer Research Area
+   - Sources of Information
+ - Table with following columns 
+   - PR Comment
+   - How Addressed
+
+## Continuous Learning
+ - Table with following columns
+    - Learning
+    - Agent Rule Updates (what agent rule file was updated to ensure the learning is durable)

package/dist/registry/templates/help/HelpNeeded.md

@@ -0,0 +1,14 @@
+# Feature: <Title>
+Issue: #<issue>  
+PR: <Link to PR>
+
+## Help Needed
+ - What help is needed? Be as specific as possible
+ - What is it blocking?
+ - What is the impact?
+
+## What has been tried
+ - What solutions have been tried to unblock? What was the result?
+
+## What Options exist
+ - Do you have options in mind? If so, what are the Pros/Cons and what is your suggestion?

package/dist/registry/templates/legal/NDA-TEMPLATE.md

@@ -0,0 +1,170 @@
+# Template: Non-Disclosure Agreement (NDA)
+
+Use this template to create comprehensive NDAs that protect intellectual property and confidential information.
+
+## Agreement Setup
+- **Product/Project Name**: 
+- **Disclosing Party**: [Your Company Name]
+- **Receiving Party**: [Recipient Company/Individual Name]
+- **Agreement Type**: [Unilateral / Mutual]
+- **Jurisdiction**: [State/Country for governing law]
+- **Effective Date**: 
+- **Duration**: [Typically 2-5 years]
+
+## Confidential Information Classification
+
+### Technical Information
+- [ ] Source code and software architecture
+- [ ] Technical specifications and documentation
+- [ ] Algorithms and proprietary methods
+- [ ] System designs and workflows
+- [ ] Performance data and benchmarks
+- [ ] Development roadmaps and timelines
+
+### Business Information
+- [ ] Business strategies and plans
+- [ ] Financial information and projections
+- [ ] Customer lists and contact information
+- [ ] Pricing strategies and models
+- [ ] Market research and analysis
+- [ ] Partnership agreements and terms
+
+### Intellectual Property
+- [ ] Patents and patent applications
+- [ ] Trademarks and trade names
+- [ ] Copyrighted materials
+- [ ] Trade secrets and know-how
+- [ ] Proprietary processes
+- [ ] Research and development data
+
+## Risk Assessment
+
+### Protection Level Required
+- [ ] Standard confidentiality protection
+- [ ] Enhanced trade secret protection
+- [ ] Non-compete restrictions needed
+- [ ] Non-solicitation clauses required
+- [ ] Return/destruction obligations
+
+### Potential Risks
+**Competitive Risk**: 
+**IP Theft Risk**: 
+**Market Advantage Loss**: 
+**Customer/Partner Impact**: 
+
+## NDA Document
+
+---
+
+# NON-DISCLOSURE AGREEMENT
+
+**EFFECTIVE DATE**: [Date]
+
+**PARTIES**: This Non-Disclosure Agreement ("Agreement") is entered into between:
+
+**DISCLOSING PARTY**: [Your Company Name], a [State] [corporation/LLC] ("Company")
+Address: [Your Address]
+
+**RECEIVING PARTY**: [Recipient Name], [individual/entity type] ("Recipient")
+Address: [Recipient Address]
+
+## 1. PURPOSE
+
+The parties wish to explore a potential business relationship concerning [Product/Project Name] ("Purpose"). In connection with this Purpose, Company may disclose certain confidential and proprietary information to Recipient.
+
+## 2. CONFIDENTIAL INFORMATION
+
+"Confidential Information" means all information, whether written, oral, electronic, visual, or in any other form, disclosed by Company to Recipient, including but not limited to:
+
+a) Technical data, source code, software, algorithms, processes, formulas, techniques, and know-how
+b) Business plans, strategies, financial information, customer lists, and market research
+c) Product specifications, designs, prototypes, and development plans
+d) Any information marked as "Confidential" or that would reasonably be considered confidential
+e) All notes, analyses, compilations, or other materials prepared by Recipient containing Confidential Information
+
+Confidential Information does NOT include information that:
+- Is publicly available through no breach of this Agreement
+- Was rightfully known by Recipient prior to disclosure
+- Is independently developed by Recipient without use of Confidential Information
+- Is rightfully received from a third party without breach of confidentiality
+
+## 3. OBLIGATIONS
+
+Recipient agrees to:
+
+a) **Maintain Confidentiality**: Hold all Confidential Information in strict confidence
+b) **Limited Use**: Use Confidential Information solely for the Purpose stated above
+c) **No Disclosure**: Not disclose Confidential Information to any third party without prior written consent
+d) **Protection**: Use the same degree of care to protect Confidential Information as used for its own confidential information, but no less than reasonable care
+e) **Limited Access**: Restrict access to Confidential Information to employees/agents with a legitimate need to know who have signed confidentiality agreements
+f) **No Copying**: Not copy, reproduce, or create derivative works from Confidential Information except as necessary for the Purpose
+
+## 4. RETURN OF MATERIALS
+
+Upon termination of discussions or upon Company's request, Recipient shall:
+- Promptly return all materials containing Confidential Information
+- Delete all electronic copies and destroy all notes or analyses containing Confidential Information
+- Provide written certification of compliance with these obligations
+
+## 5. NO RIGHTS GRANTED
+
+This Agreement does not grant Recipient any rights to Company's intellectual property, including patents, trademarks, copyrights, or trade secrets. No license is granted except the limited right to review Confidential Information for the Purpose.
+
+## 6. TERM
+
+This Agreement shall remain in effect for [Duration] years from the Effective Date, unless terminated earlier by either party with 30 days written notice. Obligations regarding Confidential Information shall survive termination.
+
+## 7. REMEDIES
+
+Recipient acknowledges that breach of this Agreement would cause irreparable harm to Company for which monetary damages would be inadequate. Therefore, Company shall be entitled to:
+- Immediate injunctive relief without posting bond
+- All costs and attorneys' fees incurred in enforcing this Agreement
+- All other remedies available at law or equity
+
+## 8. GENERAL PROVISIONS
+
+a) **Governing Law**: This Agreement shall be governed by the laws of [Jurisdiction]
+b) **Jurisdiction**: Any disputes shall be resolved in the courts of [Jurisdiction]
+c) **Entire Agreement**: This Agreement constitutes the entire agreement between the parties
+d) **Amendment**: This Agreement may only be modified in writing signed by both parties
+e) **Severability**: If any provision is unenforceable, the remainder shall remain in effect
+f) **Assignment**: This Agreement may not be assigned without prior written consent
+
+## SIGNATURES
+
+**DISCLOSING PARTY**:
+[Your Company Name]
+
+By: _________________________
+Name: [Your Name]
+Title: [Your Title]
+Date: _______________________
+
+**RECEIVING PARTY**:
+[Recipient Name/Company]
+
+By: _________________________
+Name: [Recipient Name]
+Title: [Title if applicable]
+Date: _______________________
+
+---
+
+## Execution Checklist
+- [ ] All blanks filled in with specific information
+- [ ] Confidential information scope clearly defined
+- [ ] Duration and jurisdiction specified
+- [ ] Both parties have reviewed terms
+- [ ] Legal counsel review completed (recommended)
+- [ ] Original signed copies retained by both parties
+- [ ] Effective date recorded for tracking
+
+## Record Keeping
+- **File Location**: `docs/legal/nda/{recipient-name}-{date}-nda.md`
+- **Execution Date**: 
+- **Expiration Date**: 
+- **Key Terms**: 
+- **Follow-up Required**: 
+
+## Notes
+[Add any specific considerations, modifications, or special terms for this agreement]