Contract Graph Dev Kit

Why Dev Kit

It keeps the code aligned with your intent and minimises the drift.

What does drift look like?

Drift can show up in the structure of the code and its behaviour.

Code structure drift

  • New code takes on work an existing component already owns.
  • Related functionality gets scattered across distant modules or components.
  • Circular dependencies form between components, making changes harder to isolate.
  • Small changes require edits across many unrelated files.
  • Components grow to handle several unrelated responsibilities.

Behaviour and logic drift

  • The same behaviour gets implemented twice in different parts.
  • Similar features behave differently across the application.
  • Special cases accumulate, making the original logic harder to follow.
  • Old and new implementations coexist without a clear replacement.
  • Changes add new code because the right place isn’t clear.

Why does drift happen?

Agent behaviours and session conditions can both contribute to drift.

Coding agent problems

  • Repeated fixes can reinforce a mistaken assumption instead of correcting it.
  • Agents can stop at a working solution before checking architectural fit.
  • Agents can follow nearby patterns without checking their wider consequences.
  • Agents can expand the scope beyond what the change requires.
  • Existing workarounds can become patterns the agent copies and spreads.

Coding session problems

  • Undocumented design decisions can leave agents guessing where changes belong.
  • Earlier constraints can be overlooked or lost as sessions grow.
  • Keyword searches can find relevant code while missing wider context.
  • Outdated documentation can steer agents towards structures that no longer exist.
  • Passing tests can hide changes that weaken the existing architecture.

Beside the code

How does Contract Graph Dev Kit help?

Record the shape the next session should follow. The Dev Kit keeps project intent, responsibilities, and dependencies in the repository, with a workflow that guides agents through agreed changes.

Shared project context

Carry project intent and agreed decisions between sessions, so agents can start from the direction already established.

Contracts and dependencies

Record each part’s responsibilities, public promises, and relationships, helping agents locate the right place for a change and assess affected parts.

Guided delivery workflow

Guide agents through planning, implementation, review, and verification, with agreed scope and completion checks.

When a change alters a responsibility or promise, the bundled skills update the affected contracts with the code. The kit’s tools check the recorded graph’s structure. The next session can start from that recorded shape. How the two ways of working use that graph.

How to use Get started