What belongs in Career Context
- Identity, current direction, and target roles.
- Selected experience, projects, education, and skills.
- Proof links and the source of important claims.
- Constraints, preferred tone, and claims to avoid.
Context Builder
Turn career material into reusable context.
The Context Builder organizes supplied material into a private Markdown source of truth. It preserves evidence boundaries and prepares a clean handoff for downstream agents and career systems.
Method
Build it in six deliberate passes.
The goal is not to copy every document into one large file. The goal is a compact, inspectable interface to the career context that repeated tasks actually need.
- 01
Choose the material
Start with documents, profile text, project notes, public links, and goals you are comfortable supplying.
- 02
Resolve direction
Record current focus, target roles, priorities, tone, constraints, and claims the agent must avoid.
- 03
Separate claim states
Keep supplied facts, evidence, inference, inaccessible material, and needs-evidence claims visibly distinct.
- 04
Build the compact file
Create stable Markdown sections that support fast retrieval without loading every career detail.
- 05
Review before use
Validate the structure, read the result, and correct omissions or overstatements before handing context downstream.
- 06
Maintain it
Update the file when roles, projects, goals, or proof change. Use VitaeGraph only when richer records are useful.
What stays outside
- Private material that is not needed for agent work.
- Guesses rewritten as professional facts.
- Platform-specific formatting rules and workflow logic.
- Detailed records better kept in optional VitaeGraph nodes.
Invoke the builder
Give the agent a destination and selected sources.
Keep the file outside public repositories and review the proposed context before treating it as the source of truth.
Use vitaecontext-build to create my Career Context file.
Save it at ~/.vitaecontext/name-surname-career-context.md.
I will choose the CV, profile text, project notes, and links to inspect.
Keep unsupported claims visible instead of polishing them into facts.