Project design

How the pieces fit together

VitaeContext keeps career facts, task methods, maintained knowledge, and provider packaging in separate layers.

Read the source design Browse skills

Product model

Facts and methods stay separate.

Career context describes the person. Skills describe how an agent should approach one type of work.

Career context

A maintained Markdown file stores reusable facts, goals, evidence, constraints, and claims to avoid.

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.

Canonical project facts

One project, package, and source.

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.

Project and package: VitaeContext · vitaecontext · version 2.1.0
Canonical source: github.com/vitaecontext/vitaecontext
License: MIT License
Creators and maintainers: Renato Mignone and Elia Innocenti

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 reference

Evidence vocabulary

Make certainty visible.

Shared labels stop inference, goals, and inaccessible material from being presented as verified experience.

Project fact: Confirmed by current package source or maintained project documentation.
Supplied career fact: Taken from user-provided or inspected material; not independently authenticated by VitaeContext.
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.