Context Kits now. Context Inbox next.

Start with downloadable structure. Add app visibility when the work earns it.

dovetell Context Kits help AI-assisted teams keep decisions, tasks, handoffs, and alignment controls close to the repo. Context Inbox is the app workflow for ongoing visibility, review, drift, and write-back.

Context Kits

From a small starter loop to Team HQ governance.

The kit paths are not about more files for their own sake. Each level adds only the structure needed to keep context reusable, reviewable, and aligned with the work.

Project HQ

docs
Gated preview

For active projects that need governed docs, document lineage, and cleanup paths.

Adds
  • Document registry and stable doc pointers
  • Docs-as-code lanes for core, dev, user, UX, and business context
  • Promotion triggers for when informal memory should become a document
See the framework

For projects with repeated explanation, drift, or cleanup pressure.

Team HQ

team
Research preview

For teams coordinating across roles, repos, active work lanes, and governance checkpoints.

Adds
  • Centerlines, centerline items, triggers, and events
  • Required docs as alignment controls
  • Cross-repo alignment locks and operational provenance
Check fit first

Useful when coordination cost is already real.

Not sure yet? Try the sample set first.

The free sample set spans the same basic idea: repo-owned context that a human or coding agent can read, resume from, and improve without starting cold.

View free samples
Plain language

What is a centerline?

A centerline is an active lane of work with a clear objective and a small set of control documents. It helps a team notice when useful work is still aligned, when a tangent should be parked, and when the lane itself needs to change.

Centerline

The active lane: what we are trying to keep straight while work is moving.

Required docs

The alignment controls: the docs that define what straight and true means for that lane.

Docs-as-code keeps the lane inspectable.

Required docs live with the repo as stable document pointers, so a centerline can point to the decisions, plans, UX notes, and governance choices that keep the work honest. When one of those docs is missing, the team has a clear signal to create it before treating the lane as governed.

Next workflow

Context Inbox is the app layer for teams that want help maintaining context.

Context Kits work on their own. Context Inbox is the next workflow for teams that want guided review, drift, and write-back around repo-owned files.

Context Inbox areas
connect reposource
detect driftsignal
review changehuman
write backapproved