Career context
A maintained Markdown file stores reusable facts, goals, evidence, constraints, and claims to avoid.
Project design
How the pieces fit together
VitaeContext keeps career facts, task methods, maintained knowledge, and provider packaging in separate layers.
Product model
Facts and methods stay separate.
Career context describes the person. Skills describe how an agent should approach one type of work.
Focused skills
One runtime module handles the current task instead of loading every method and reference.
Versioned knowledge
Each module can load maintained wiki entries and references when the task needs deeper platform detail.
Provider adapters
One canonical skill source is exported into each supported provider's required layout.
Progressive loading
Load one module, then only needed detail.
The root skill routes a request. The selected module decides which wiki entries or references are relevant. This keeps unrelated platform material out of the current agent context.
request
└── root skill
└── one focused skill
├── required workflow
└── relevant wiki or referenceEvidence vocabulary
Make certainty visible.
Shared labels stop inference, goals, and inaccessible material from being presented as verified experience.
- Verified
- Observed in supplied or inspected material.
- From context
- Taken from the supplied career context file.
- From source
- Taken from another supplied source.
- Inference
- Reasoned from evidence but not directly observed.
- Inaccessible
- Could not be inspected.
- Needs evidence
- Should not become a public claim yet.
What the system does not guarantee
VitaeContext does not guarantee rankings, recruiter attention, citations, visibility, or career outcomes. Audit scorecards order work internally; they are not platform scores. Generated advice still requires review.