Ingest Command

# Ingest Command

## Command: `ingest`

Transform free text into structured knowledge by updating the knowledgebase.

### Input

The user provides free text such as:
- Meeting notes
- Slack conversations
- Email threads
- Status updates
- Announcements
- Any unstructured text containing information about projects, people, or progress

### Steps

1. **Get current date and time**
   
   Always run this first:
   ```bash
   .context/scripts/print_datetime.sh
   ```
   
   Use this date for any progress entries, wins, ideas, or interests that need timestamps.

2. **Load the glossary**
   
   Read `/GLOSSARY.md` to understand domain-specific terminology. This ensures you speak the same language as the user.

3. **Analyze the input**
   
   Parse the provided text to identify:
   - **Projects** — Any project names, work items, or initiatives mentioned
   - **People** — Names, usernames, or references to team members
   - **Progress updates** — Completed work, bug fixes, features shipped
   - **Ideas** — Suggestions, proposals, or things being considered
   - **Wins** — Achievements, milestones, promotions, or successes
   - **Interests** — Topics someone is learning about or excited by
   - **Current focus** — What someone is actively working on
   - **New terms** — Domain-specific words or acronyms that aren't in the glossary

4. **Make best-effort updates**
   
   Proactively update the knowledgebase based on what you found:
   
   **For projects:**
   - Create `/projects/:project_name/README.md` if the project is new
   - Add progress entries to `/projects/:project_name/progress/:year/:month.md`
   - Create work item files at `/projects/:project_name/work/:work_item.md` for large tasks
   - Update project README with new links to work items
   
   **For people:**
   - Create `/people/:team/:person_name.md` if the person is new (use `_unknown_team` if team is unclear)
   - Update their **Current focus** with what they're working on
   - Add entries to **Wins** for achievements (with today's date)
   - Add entries to **Ideas** for suggestions (with today's date)
   - Add entries to **Interests** for topics they're engaged with (with today's date)
   - Update **Up next** if future work is mentioned
   
   **For README.md files:**
   - Update `/projects/README.md` if new projects were added
   - Update `/people/README.md` if new people were added
   - Update team README files if people were added to teams
   - Update project README files if work items were added
   
   **For progress entries:**
   - Format: `## :day :month :year` heading (e.g., `## 18 December 2025`)
   - Group updates by category (Performance, Bug fixes, New features, Documentation, etc.)
   - Include GitHub username at end of line where known (e.g., `@username`)
   - Newer entries appear at the top of the file

5. **Suggest glossary updates**
   
   If new terms, acronyms, or domain-specific language was found:
   - List them with suggested definitions
   - Ask the user to confirm before adding to `/GLOSSARY.md`
   - Unknown or ambiguous terms go in the "Unknown" section at the bottom

6. **Summarize changes**
   
   Briefly list what was updated:
   - Files created
   - Files modified
   - People profiles updated
   - Projects updated
   - Progress entries added

7. **Ask clarifying questions**
   
   After making best-effort updates, ask about anything ambiguous:
   - "I wasn't sure which team Alex belongs to — should they stay in `_unknown_team`?"
   - "Is 'Project Phoenix' the same as the existing 'phoenix-redesign' project?"
   - "Should I add these terms to the glossary? ..."
   
   Keep questions concise and actionable.

### Guidelines

- **Be proactive** — Make changes first, ask questions after. Don't wait for permission on clear updates.
- **Preserve existing content** — Add to files rather than replacing content. Append progress entries, add to lists.
- **Use the glossary** — Reference `/GLOSSARY.md` to understand terms. Use consistent language.
- **Link where possible** — Cross-reference projects and people with markdown links.
- **Attribute work** — Include `@username` when you know who did something.
- **Date everything** — Use the date from `print_datetime.sh` for new entries.
- **Create structure** — If folders don't exist, create them. Every folder needs a README.md.
- **Stay organized** — Follow the directory structure: `/projects/:name/`, `/people/:team/:name.md`
- **Be concise** — Brief confirmations, focused questions. Don't over-explain.

### Examples

**Input:** "Sarah shipped the new auth flow yesterday and fixed the login bug. Marcus is starting on the dashboard redesign next week."

**Actions:**
1. Run `print_datetime.sh` → December 18, 2025
2. Update Sarah's profile: add auth flow to Wins, mark login bug fix
3. Update Marcus's profile: add dashboard redesign to Up next
4. Add progress entry to relevant project(s) with yesterday's date
5. Ask: "Which project should the auth flow and login bug be tracked under?"

**Input:** "Team standup: API Gateway migration is 80% complete. Jane discovered we need to handle CORS differently. New hire Tom starting Monday on Platform team."

**Actions:**
1. Run `print_datetime.sh`
2. Update API Gateway project progress with 80% milestone
3. Add CORS handling as work item or idea on API Gateway project
4. Create Tom's profile in `/people/platform/tom.md`
5. Update Jane's profile with API Gateway work
6. Summarize changes and ask: "What's Tom's role?" and "Should CORS handling be a work item or just noted in progress?"