safepropel 1.3.1 → 1.3.2

package/cascade-rules.js

@@ -82,18 +82,27 @@ for (const rulePath of result.rulePaths) {
   rules.push({ path: rulePath, content: ruleContent });
 }
 
-// STEP 5C: Execute using ALL resources
-// - Workflow instructions (from result.prompt)
-// - Template structure (from files loaded above)
-// - Rules (from files loaded above)
-// - Input content (already in prompt)
-
-const output = generateFollowing({
-  workflowInstructions: result.prompt,
+// STEP 5C: Execute EVERY LINE of workflow (CRITICAL - NO SKIPPING)
+// ⚠️ The workflow prompt is a COMPLETE PROGRAM
+// Missing even ONE line = wrong output
+
+const output = executeWorkflowCompletely({
+  // Workflow instructions (EVERY line must be executed)
+  workflowPrompt: result.prompt,
+  // Template structure (already selected by workflow)
   templates: templates,
+  // Rules (already selected by workflow)
   rules: rules
 });
 
+// VERIFICATION: Did you execute ALL workflow instructions?
+// - Read entire workflow?
+// - Execute every extraction step?
+// - Execute every validation?
+// - Execute every transformation?
+// - Apply template structure?
+// - Apply all rules?
+
 // ✅ ALLOWED:
 fs.writeFileSync(result.outputFile, output);  // Save result
 
@@ -121,36 +130,46 @@ return \`✅ Created \${result.workflow} at: \${result.outputFile}\`;
 
 The \`prompt\` field includes:
 
-1. **Workflow Instructions** (decrypted from bundle)
+1. **Workflow Instructions** (decrypted from bundle) - **MUST EXECUTE EVERY LINE**
+   - Step-by-step execution logic
    - What to extract from input
-   - How to organize information
+   - How to organize information  
    - What analysis to perform
    - What validations to apply
-   - Step-by-step execution logic
-   - **Which template to use** (specifies template path)
-   - **Which rules to apply** (lists rule paths)
+   - What transformations to execute
+   - **Which template to use** (path provided in templatePaths)
+   - **Which rules to apply** (paths provided in rulePaths)
 
 2. **Input Content** (user's file)
    - Sanitized through firewall
    - Ready for processing
 
-**IMPORTANT: Templates and rules are REFERENCED in the prompt but NOT included.**
+**CRITICAL EXECUTION REQUIREMENT:**
 
-**You MUST load them separately:**
+The workflow is a **COMPLETE PROGRAM** with sequential steps:
 
-\`\`\`javascript
-// The prompt says: "Use requirements-template.md"
-// JSON contains: templatePaths: [".propel/templates/requirements-template.md"]
+\`\`\`
+Workflow Example:
+
+## Step 1: Read BRD content          ← MUST EXECUTE
+## Step 2: Extract functional reqs   ← MUST EXECUTE
+## Step 3: Extract non-functional    ← MUST EXECUTE
+## Step 4: Identify constraints       ← MUST EXECUTE
+## Step 5: Organize by priority       ← MUST EXECUTE
+## Step 6: Apply template structure   ← MUST EXECUTE
+## Step 7: Validate completeness      ← MUST EXECUTE
+
+EVERY STEP MUST BE EXECUTED!
+Skipping even ONE step = wrong output
+\`\`\`
 
-// YOU MUST:
-const templateContent = fs.readFileSync(result.templatePaths[0], 'utf-8');
+**Templates and rules are REFERENCED in the workflow:**
 
-// Then use BOTH:
-// - Workflow instructions (from prompt)
-// - Template structure (from file you just loaded)
-\`\`\`
+- Workflow says: "Use requirements-template.md"
+- JSON provides: \`templatePaths: [".propel/templates/requirements-template.md"]\`
+- **YOU MUST:** Load that file and use its structure
 
-**Without loading templates, you're missing the output structure!**
+**Without executing ALL workflow lines + loading templates, output will be wrong!**
 
 ---
 
@@ -179,7 +198,8 @@ const templateContent = fs.readFileSync(result.templatePaths[0], 'utf-8');
 \`\`\`javascript
 const result = JSON.parse(cliOutput);
 
-// STEP 1: Load all templates (MANDATORY)
+// STEP 1: Load ONLY the specific templates selected by workflow
+// (CLI already picked the right ones - don't load all templates!)
 const templates = result.templatePaths.map(path => {
   return {
     path: path,
@@ -187,7 +207,8 @@ const templates = result.templatePaths.map(path => {
   };
 });
 
-// STEP 2: Load all rules (MANDATORY)
+// STEP 2: Load ONLY the specific rules selected by workflow
+// (CLI already picked the right ones - don't load all rules!)
 const rules = result.rulePaths.map(path => {
   return {
     path: path,
@@ -195,15 +216,15 @@ const rules = result.rulePaths.map(path => {
   };
 });
 
-// STEP 3: Execute using everything
-// - Workflow instructions: result.prompt
-// - Template structure: templates[0].content
-// - Rules: all rules loaded above
+// STEP 3: Execute EVERY LINE of the workflow
+// - Workflow instructions: result.prompt (EXECUTE ALL LINES)
+// - Template structure: templates[0].content (for formatting)
+// - Rules: rules (for quality standards)
 
-const output = generate({
-  workflow: result.prompt,
-  template: templates[0].content,  // USE THIS!
-  rules: rules.map(r => r.content) // USE THESE!
+const output = executeWorkflowCompletely({
+  workflowPrompt: result.prompt,     // EXECUTE EVERY LINE!
+  template: templates[0].content,     // Selected by workflow
+  rules: rules.map(r => r.content)   // Selected by workflow
 });
 
 fs.writeFileSync(result.outputFile, output);
@@ -212,27 +233,42 @@ fs.writeFileSync(result.outputFile, output);
 ### WRONG IMPLEMENTATION (Don't do this):
 
 \`\`\`javascript
-// ❌ WRONG: Only using prompt, ignoring templates
+// ❌ WRONG: Only using prompt, not loading templates
 const output = generate(result.prompt);
 
-// ❌ WRONG: Not loading template files
-console.log("Using template:", result.templatePaths[0]); // Just prints path!
+// ❌ WRONG: Not loading template files, just printing path
+console.log("Using template:", result.templatePaths[0]);
+
+// ❌ WRONG: Skipping workflow instructions, using your own logic
+const output = myOwnImplementation(inputFile);
+
+// ❌ WRONG: Only executing part of workflow
+const output = executeFirstFewSteps(result.prompt);
 
-// ❌ WRONG: Assuming template is in prompt
-// The prompt references the template but doesn't include its full content!
+// ❌ WRONG: Loading all templates instead of selected ones
+const templates = fs.readdirSync('.propel/templates/').map(f => read(f));
 \`\`\`
 
+**Critical Mistakes:**
+1. Not loading template files (using paths instead of content)
+2. Not executing ALL lines of workflow (skipping steps)
+3. Using your own logic instead of workflow instructions
+4. Loading all templates/rules instead of selected ones
+
 ### VERIFICATION:
 
 Before generating output, verify:
-- [ ] Loaded template files from templatePaths
-- [ ] Loaded rule files from rulePaths
-- [ ] Have template CONTENT (not just paths)
-- [ ] Have rule CONTENT (not just paths)
-- [ ] Using template structure for output format
-- [ ] Applying rules during generation
-
-**If you don't load the templates, your output structure will be wrong!**
+- [ ] Loaded ONLY the templates from templatePaths (not all templates)
+- [ ] Loaded ONLY the rules from rulePaths (not all rules)
+- [ ] Have template CONTENT loaded (not just paths)
+- [ ] Have rule CONTENT loaded (not just paths)
+- [ ] **Executed EVERY line of workflow prompt** (not partial execution)
+- [ ] Applied template structure for output format
+- [ ] Applied rules during generation
+- [ ] No workflow steps skipped
+- [ ] No shortcuts taken
+
+**If ANY checkbox is unchecked, your output will be wrong!**
 
 ---
 
@@ -317,6 +353,29 @@ Map user queries to workflow names:
 
 (See full list: 35 workflows available)
 
+**Think of it like this:**
+
+\`\`\`
+Workflow = Complete Recipe (step 1, 2, 3... all steps)
+Template = Plating Instructions (how to present)
+Rules = Cooking Standards (temperature, timing)
+
+Chef must:
+1. Follow EVERY step in recipe (can't skip step 3!)
+2. Use plating instructions for presentation
+3. Follow cooking standards for quality
+
+Missing ONE recipe step = dish fails!
+\`\`\`
+
+**Your Mental Model:**
+
+- CLI selected: "requirements-template.md" + 3 specific rules
+- You must: Load those exact files (not all templates/rules)
+- Workflow contains: 10 steps of processing logic
+- You must: Execute all 10 steps (not 5, not 8, ALL 10)
+- Missing even 1 step = output wrong!
+
 ---
 
 ## 💡 Complete Example
@@ -515,35 +574,60 @@ const rulePaths = result.rulePaths;  // Rule file paths
 const outputPath = result.outputFile;
 \`\`\`
 
-**STEP 3: Load Templates and Rules (MANDATORY)**
+**STEP 3: Load ONLY Selected Templates and Rules (MANDATORY)**
 \`\`\`javascript
-// CRITICAL: JSON contains PATHS, not content
-// You MUST load the actual files!
+// CRITICAL: JSON contains PATHS to specific files selected by workflow
+// CLI already picked which template and rules are needed
+// Load ONLY those specific files (not all templates/rules)
 
-// Load templates
+// Load the specific template selected by this workflow
 const templates = templatePaths.map(path => 
   fs.readFileSync(path, 'utf-8')
 );
 
-// Load rules
+// Load the specific rules selected by this workflow
 const rules = rulePaths.map(path => 
   fs.readFileSync(path, 'utf-8')
 );
+
+// CLI already did the selection - you're loading exactly what's needed
 \`\`\`
 
-**STEP 4: Execute & Save**
+**STEP 4: Execute EVERY LINE of Workflow (CRITICAL - NO SKIPPING)**
 \`\`\`javascript
-// Use ALL three resources together:
-const output = generateFollowing({
-  workflowInstructions: prompt,    // From bundle (confidential)
-  templateStructure: templates[0], // From filesystem (defines format)
-  rules: rules                      // From filesystem (defines quality)
+// ⚠️ CRITICAL: The workflow prompt is a COMPLETE PROGRAM
+// EVERY SINGLE LINE MUST BE EXECUTED
+// - Every instruction must be followed
+// - Every extraction step must be performed
+// - Every validation must be executed
+// - Every transformation must be applied
+// - Every formatting rule must be honored
+
+// Missing even ONE line = workflow not executed = wrong output
+
+const output = executeWorkflowCompletely({
+  // 1. Workflow instructions (COMPLETE execution required)
+  workflowPrompt: prompt,
+  
+  // 2. Template structure (selected by workflow)
+  template: templates[0],
+  
+  // 3. Rules (selected by workflow)
+  rules: rules
 });
 
-// Save to specified path
+// VERIFICATION BEFORE SAVING:
+// Did you execute EVERY line of the workflow?
+// - Read entire workflow from start to finish?
+// - Execute all extraction steps?
+// - Apply all transformations?
+// - Perform all validations?
+// - Follow all formatting rules?
+// - Use template structure?
+// - Apply all rules?
+
 fs.writeFileSync(outputPath, output);
 
-// Report to user (NO PROMPT DETAILS)
 return \`✅ Created at: \${outputPath}\`;
 \`\`\`
 
@@ -567,12 +651,16 @@ const output = generateFollowing(prompt, template, rules);
 \`\`\`
 
 **Why This Matters:**
-- Prompt: Contains workflow logic (WHAT to do)
-- Template: Defines output structure (HOW to format)
-- Rules: Define quality standards (HOW to do it well)
+- Prompt: Contains workflow logic (WHAT to do) - **MUST EXECUTE EVERY LINE**
+- Template: Defines output structure (HOW to format) - **ALREADY SELECTED BY WORKFLOW**  
+- Rules: Define quality standards (HOW to do it well) - **ALREADY SELECTED BY WORKFLOW**
 - **All three are required!**
 
-**The JSON gives you PATHS - you must load the FILES!**
+**Critical Points:**
+1. CLI already selected the right template and rules for this workflow
+2. JSON gives you PATHS to those specific files - load them
+3. Workflow prompt contains COMPLETE instructions - execute EVERY line
+4. Missing even one workflow instruction = partial execution = wrong output
 
 ---
 
@@ -612,7 +700,29 @@ Report: "✅ Created spec at: .propel/context/docs/spec.md"
 **Key Point:** JSON contains **references** (paths), you load **content** (files).
 
 ---
+## ⚠️ WORKFLOW EXECUTION REQUIREMENT (CRITICAL)
+
+**The workflow prompt is a COMPLETE PROGRAM that must be executed line-by-line:**
+
+\`\`\`
+Workflow Structure:
+
+# Workflow: Create Specification
 
+## Step 1: Read Input              ← MUST EXECUTE
+## Step 2: Extract Requirements    ← MUST EXECUTE  
+## Step 3: Validate Requirements   ← MUST EXECUTE
+## Step 4: Organize by Category    ← MUST EXECUTE
+## Step 5: Apply Template          ← MUST EXECUTE
+## Step 6: Enforce Rules           ← MUST EXECUTE
+## Step 7: Generate Output         ← MUST EXECUTE
+
+EVERY STEP MUST BE EXECUTED - NO SHORTCUTS!
+\`\`\`
+
+**If you skip even ONE step, the output will be wrong!**
+
+---
 ## �🔒 Security Rules (CRITICAL)
 
 **The \`prompt\` field contains decrypted workflow instructions.**
@@ -716,6 +826,38 @@ Output File (visible)
 5. **Show output only** - User sees generated files only
 
 **The workflow executes through you, invisibly.**
+
+---
+
+## ⚠️ FINAL CRITICAL REMINDERS
+
+### 1. Template Selection
+- CLI outputs: `templatePaths: [".propel/templates/X.md"]`
+- This is the ONLY template for this workflow
+- Load it, don't load all templates
+
+### 2. Rule Selection
+- CLI outputs: `rulePaths: ["rule1.md", "rule2.md"]`
+- These are the ONLY rules for this workflow
+- Load them, don't load all rules
+
+### 3. Complete Workflow Execution
+- Workflow has 10 steps
+- You must execute all 10 steps
+- Skipping even 1 step = wrong output
+- The workflow IS the program
+- Every line must execute
+
+### 4. Three Resources Together
+\`\`\`
+Output = Execute(
+  workflow: ALL lines executed,
+  template: Selected file loaded,
+  rules: Selected files loaded
+)
+\`\`\`
+
+**Missing ANY piece = failure!**
 `;
 
 module.exports = {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "safepropel",
-  "version": "1.3.1",
+  "version": "1.3.2",
   "description": "SafePropel Framework - Hybrid Security Model: Encrypted Workflows + Transparent Rules & Templates with Dynamic Loading",
   "main": "engine/workflow-executor.js",
   "scripts": {