Principles
Eight rules the product will not break.
A code intelligence tool is only useful if you can trust what it says, and know when not to. These are the design rules every feature is checked against.
Every claim cites its source.
A route, a rule or a dependency in the twin points at the repository, commit, file and line that support it.
In practiceClick any fact and you land on the code it came from, at the version it was read.
Gaps stay visible.
Skipped files, unresolved calls, unread repositories and missing traces are part of the answer, not footnotes.
In practiceCoverage is shown next to every result. Unread code never looks understood.
Never “no impact” while the map has holes.
The most dangerous sentence in a review is “this change affects nothing else”. The twin only says it when it can prove it.
In practiceImpact reports end with the map stops here, naming what could not be followed.
Kinds of truth do not promote each other.
Read from code, inferred by AI, intended by the team and verified by a test are four different things. Repetition does not turn one into another.
In practiceAn inference stays an inference until someone checks it. A requirement is not evidence that code exists.
AI drafts. People decide.
Models read, summarise, propose and write. Approving a requirement, a plan, a test result or a merge is a human decision.
In practiceNo agent can approve, accept or merge its own work, and every decision records who made it.
Approvals belong to exact inputs.
An approval is a judgement about specific code and specific requirements. When either changes, the judgement may no longer hold.
In practiceA push that changes the inputs flags the approval for review. The old decision stays readable in history.
History is kept, not rewritten.
Corrections, decisions and earlier readings are versioned. A later scan never silently overwrites what a person said.
In practiceYou can always see what the team knew, and when it knew it.
Your code is read, never run.
The twin analyses source as text. It does not execute customer code to understand it.
In practiceEach company uses its own AI provider key, and platform operators cannot browse customer source.