knowledge

name	knowledge
description	Knowledge base update from field data. Scans the week's operational data for new patterns, structures them, and writes to department knowledge bases. Thursday-Friday routine. Octopus colors: Yellow (pattern extraction) + Red-Orange (structure) + Blue (implementation).

/knowledge: Knowledge Base Update

Octopus Colors: Yellow (Researcher) + Red-Orange (Designer) + Blue (Maker)

Process

1. Read .chairman/config.json for active departments
2. For each department (or specific department if $ARGUMENTS provided):
3. Scan for new knowledge (Yellow):
   • Recent reports in .chairman/reports/
   • Recent assignments and their outputs
   • Patterns: recurring issues, common objections, process gaps
   • Customer feedback or market signals
4. Structure the knowledge (Red-Orange):
   • Categorize: process update, FAQ, pattern, correction
   • Check for contradictions with existing knowledge base entries
   • Format consistently with existing entries
5. Implement updates (Blue):
   • Write new entries to departments/{dept}/knowledge/
   • Update existing entries if information has changed
   • Remove outdated entries (move to _archive/ subfolder)

Output Format

# Knowledge Base Update: [Date]

## Updates Made

### [Department]
- **Added:** [filename] - [what was added and why]
- **Updated:** [filename] - [what changed]
- **Archived:** [filename] - [why it is outdated]

### [Department]
...

## Summary
- Total updates: [count] across [dept count] departments
- New entries: [count]
- Updated: [count]
- Archived: [count]

Rules

• Never delete knowledge base entries. Archive them to _archive/.
• Check for contradictions before writing. If found, flag to Chairman.
• Do not add speculative knowledge. Only patterns supported by data.
• If $ARGUMENTS targets a specific department, only update that one.
• Notify Chairman of significant additions (new process, corrected procedure).