Supplied material
CVs, profiles, projects, links, notes, goals, and constraints selected by the person.
System architecture
VitaeContext sits between selected career material and the agents or systems that use it. Context stays portable; task execution stays downstream.
Product model
VitaeContext maintains the grounded input. Downstream systems own the task method and final output.
CVs, profiles, projects, links, notes, goals, and constraints selected by the person.
A maintained Markdown file stores reusable facts, intent, evidence boundaries, and claims to avoid.
A bounded summary, direct file, or stateless MCP server exposes only the context needed for the task.
Career agents and tools apply their own methods to produce CVs, applications, profiles, and other work.
Canonical project facts
VitaeContext is the current project identity. The public implementation is open source under the MIT license, and the website mirrors the package rather than defining separate runtime behavior.
vitaecontext · version 2.3.0Progressive disclosure
Most tasks need the compact Career Context file or a bounded summary. VitaeGraph adds selected deep records only when a task needs more detail.
request
└── Career Context
├── bounded task summary
└── selected VitaeGraph records
└── downstream workflowEvidence vocabulary
Shared labels stop inference, goals, and inaccessible material from being presented as verified experience.
VitaeContext does not authenticate every real-world claim or guarantee rankings, recruiter attention, visibility, or career outcomes. Generated work still requires human review.