cv/docs/AGENTS.md

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, no per-file AGENTS.md — they share a schema described below).

Directory	Purpose
experience/	One file per employer (sonr, leidos, britetwist, hobsons, unissant). Fields: title, company, start/end, location, description (bullets), skills, projects (refs).
projects/	One file per project (16). Fields: title, start/end, project-url, associated-with, skills, description (bullets). Sonr-era projects (appchain, beam-chat, cryptography-library, client-sdk, token-economics, decentralized-airdrop, ecosystem-devrel) carry the strongest material.
skills/	languages.yml (expert/strong/familiar tiers), frameworks.yml (grouped flat list), methodology.yml (flat list). These feed the Skills column in the templates.
recognition/	honors.yml (e.g. MIT Sloan guest lecture) and organizations.yml (W3C, DIF working groups). Feed the Honors/Organizations blocks.
information/	profile.yml (name, contact, role summaries) and education.yml (VCU, Applied Math).

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:

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.