cv/docs/AGENTS.md

<!-- Parent: ../AGENTS.md -->
<!-- Generated: 2026-06-25 | Updated: 2026-06-30 -->

# docs

## Purpose
Structured YAML source material for the résumés — the canonical, role-agnostic record of Prad's career. The `src/*.tex` variants are hand-curated *from* this data; nothing here is generated and nothing generates the `.tex`. Treat these files as the single source of truth: when a fact changes (a date, a metric, a new project), update it here first, then reflect it in the relevant templates.

## Subdirectories
Each subdirectory holds one flat collection of like-shaped YAML files (no nesting). Each has its own AGENTS.md describing its schema.

| Directory | Purpose |
|-----------|---------|
| `experience/` | One file per employer — `sonr`, `leidos`, `britetwist`, `hobsons`, `unissant` (see `experience/AGENTS.md`). |
| `projects/` | One file per project, 16 total (see `projects/AGENTS.md`). Sonr-era projects carry the strongest material. |
| `skills/` | `languages.yml`, `frameworks.yml`, `methodology.yml` — feed the Skills column (see `skills/AGENTS.md`). |
| `about/` | `profile.yml`, `education.yml`, `honors.yml`, `organizations.yml` — identity, contact, and the Honors/Organizations blocks (see `about/AGENTS.md`). |

## For AI Agents

### Working In This Directory
- Cross-references use relative paths (e.g. `associated-with: ../experience/sonr.yml`). Keep them valid when renaming/moving files.
- `description` blocks are YAML block scalars (`|`) of Markdown-style `- ` bullets. These bullets are the raw pool the templates draw from — condensed, not copied verbatim, to fit one page.
- This is **data, not a build input.** Editing YAML does not change any PDF until a human/agent edits the corresponding `src/*.tex`.

### Testing Requirements
No build step. Validate that edited files still parse:
```bash
python3 -c "import yaml; yaml.safe_load(open('<file>.yml'))"
```

### Common Patterns
- Skill names are kept consistent across files (e.g. "Decentralized Identifiers (DIDs)", "WebAssembly (WASM)") so they can be matched and deduplicated.
- Dates are ISO `YYYY-MM-DD`; templates render them as year ranges.

## Dependencies

### Internal
- Consumed by `../src/*.tex` (by hand) and indirectly by `../CLAUDE.md` guidance.

### External
- None — plain YAML, no schema/validation tooling configured.

<!-- MANUAL: Any manually added notes below this line are preserved on regeneration -->