This directory is prisma-next's home for project-context Drive memory — the team's accumulated lessons, calibrations, and conventions overlaid onto the canonical Drive skill bodies.
Per the protocol-as-memory architecture, the methodology has two memory homes:
- Canonical skill bodies (in
.agents/skills/drive-*/SKILL.md, eventually pulled from upstreamprisma/ignite). Portable methodology — the protocol every team adopts. - Project context (here). Team-specific protocol — the calibration the team has accumulated, plus the operational conventions for integrating Drive with the team's tracker, branch conventions, and tooling.
Both are loaded by drive-* skills at workflow entry. Both are human-readable and human-runnable (workflow vs atomic skill tiers — operators can run steps manually without invoking skills). A team member who hasn't invoked a single drive-* skill can read these directly to consult the team's protocol.
calibration/ is the single home for the team's accumulated calibration — sizing anchors, model-tier routing, DoR / DoD overlays at every scope, the failure-mode catalogue, the grep library, and the patterns the team has learnt to recognise. Calibration is cross-cutting (one failure mode informs multiple categories' overlays), so it lives in one place rather than smeared across the category READMEs.
Every category README links out to the relevant calibration files; skills load both.
Each category README documents how this team operates the matching skill — the per-team conventions that don't shift with retro accretion the way calibration does.
Lessons accumulate in calibration/ from drive-run-retro invocations. When a lesson generalises across teams, it gets promoted to canonical via drive-update-skills. When a canonical body changes upstream, drive-reconcile-skills flags overlays that may now be redundant or contradictory.
The split between canonical (portable) and project-context (team-specific) is the load-bearing protocol-as-memory architecture. Don't move team-specific things into canonical; don't keep cross-team things only in project-context.