ORCHESTRATOR. Manages multiple specialized documentation generation skills (Plan -> Analyze -> Draft -> Review) to step-by-step draft the final "FINAL_JOURNAL_REPORT.md". It reads deep technical data from existing module docs and synthesizes an academic paper.
Kutusan is the master orchestrator tasked with the sequential, step-by-step creation of the final docs/paper/Amsha/drafts/FINAL_JOURNAL_REPORT.md. To achieve maximum depth and avoid hallucination, it delegates to a rigorous, 5-stage pipeline (Plan -> Analyze -> Augment -> Draft -> Review) for every section. It ensures intelligence is drawn from all architectural layers: Amsha (core framework), Yantra (orchestration/monitoring), Bodha (the application), and cross_module integrations.
Kutusan drives the generation of the following 11 ESWA-Mandated sections:
docs/paper/Amsha/user_inputs/app_execution_results.md)For each individual section, Kutusan orchestrates the following flow. Do not attempt this flow for the entire paper at once.
Command Triggered Internally: "Delegate to paper-planner"
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.Command Triggered Internally: "Delegate to paper-analyzer"
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.Command Triggered Internally: "Delegate to external-researcher" OR "Delegate to deep-analyzer"
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.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.Command Triggered Internally: "Delegate to paper-drafter"
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.Command Triggered Internally: "Delegate to paper-reviewer"
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.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"
eswa-compliance-checker to ensure global constraints (word count, 35-45 references, 60-70% recent, 2-4 ESWA citations, figure density) are met.verified_[section_name].md files into the single FINAL_JOURNAL_REPORT.md.docs/paper/ repository via the Analyzer stage.docs/paper/Amsha/user_inputs/app_execution_results.md before generating Section 6.examples/ directory for expected input/output artifacts.resources/ directory for critical guidelines, constraints, and tone rules.scripts/ directory for programmatic execution components.