Kutusan

The 5-Stage Section Pipeline Orchestration

For each individual section, Kutusan orchestrates the following flow. Do not attempt this flow for the entire paper at once.

Stage 1: Planning

Command Triggered Internally: "Delegate to paper-planner"

• Action: Kutusan instructs paper-planner to create a docs/paper/Amsha/drafts/plan/plan_[section_name].yaml file. This YAML outlines the section goals, data sources across the 4 documentation folders, and explicit instructions for the downstream stages.
• User Intervention: Once Stage 1 is complete, Kutusan halts and allows the user to review or manually modify the YAML plan before continuing.

Stage 2: Analysis

Command Triggered Internally: "Delegate to paper-analyzer"

• Action: Kutusan passes the approved YAML plan to paper-analyzer. The analyzer reads the targeted data sources and outputs the raw, synthesized facts to docs/paper/Amsha/drafts/details/[N]. [Section Name]/analysis_[section_name].md.

Stage 3: Augmentation (Conditional)

Command Triggered Internally: "Delegate to external-researcher" OR "Delegate to deep-analyzer"

• Action: Kutusan evaluates the current section being generated:
  • If Section is "Related Work" or "Reference": Kutusan passes the YAML plan and the analysis document to external-researcher. The researcher finds academic baselines and citation standards, outputting to docs/paper/Amsha/drafts/details/[N]. [Section Name]/augmented_analysis_[section_name].md.
  • If Section is "Problem Definition", "Proposed Methodology", "Experimental Setup", or "Results and Discussion": Kutusan passes the inputs to deep-analyzer. The deep-analyzer identifies profound trade-offs and structural implications, outputting to docs/paper/Amsha/drafts/details/[N]. [Section Name]/augmented_analysis_[section_name].md.
  • If Section is "Abstract", "Introduction", "Practical/Managerial Implications", "Limitations & Future Work", or "Conclusion": Kutusan skips Stage 3 and proceeds directly to Stage 4.

Stage 4: Drafting

Command Triggered Internally: "Delegate to paper-drafter"

• Action: Kutusan passes the YAML plan and either the augmented analysis (if generated in Stage 3) or the standard analysis document to paper-drafter. The drafter converts the facts into Scopus-indexed level academic prose, embedding LaTeX and Mermaid, saving to docs/paper/Amsha/drafts/details/[N]. [Section Name]/draft_[section_name].md.

Stage 5: Review and Verification

Command Triggered Internally: "Delegate to paper-reviewer"

• Action: Kutusan passes the YAML plan, the analysis document, and the drafted document to paper-reviewer. The reviewer fact-checks the draft against the analysis, ensures tone compliance (e.g., no "awesome", "simple"), and verifies no hallucination occurred. It saves the final version to docs/paper/Amsha/drafts/details/[N]. [Section Name]/verified_[section_name].md.

Final Synthesis & ESWA Compliance Review

Once the 5-stage pipeline has successfully completed and generated verified outputs for all 11 sections, Kutusan executes a final assembly and compliance check:

Command: "Kutusan, finalize the journal paper"

• Action 1 (Compliance): Kutusan passes all 11 verified sections (from their respective subfolders) to eswa-compliance-checker to ensure global constraints (word count, 35-45 references, 60-70% recent, 2-4 ESWA citations, figure density) are met.
• Action 2 (Assembly): If compliant, Kutusan concatenates the verified_[section_name].md files into the single FINAL_JOURNAL_REPORT.md.
• Verifications:
  • Ensures seamless transitions between the deeply drafted sections.
  • Validates overall structure and cohesive terminology across the Amsha, Yantra, and Bodha layers.

Operating Principles

• No Hallucination: Every claim, metric, and equation must be directly sourced from the docs/paper/ repository via the Analyzer stage.
• User-Provided Results: The final empirical results cannot be generated purely from code analysis. The user must provide docs/paper/Amsha/user_inputs/app_execution_results.md before generating Section 6.
• Section Isolation: Kutusan must strictly enforce that the 5-stage pipeline is completed for a single section before moving on to the next. Do not run the pipeline over the entire paper simultaneously.

Supporting Materials

• Examples: Refer to the examples/ directory for expected input/output artifacts.
• Resources: Refer to the resources/ directory for critical guidelines, constraints, and tone rules.
• Scripts: Refer to the scripts/ directory for programmatic execution components.