Use Cases

See how different kinds of teams and individuals could use aDNA to organize their work. Each scenario follows an illustrative persona through a concrete deployment.

Illustrative, not case studies

The distinction is load-bearing and we would rather lose the persuasive version of this page than blur it. A case study reports what someone did; a scenario shows what a deployment looks like. Only one of those is evidence, and pages that quietly present the second as the first are the reason the first is worth anything.

How to read one

Each scenario names a starting situation, the vaults the persona ends up with, and the decisions that got them there. The useful part is usually the shape — how many vaults, where the boundaries fall, what stays local — because that is the part that transfers. The specific tools and counts will not match your situation and are not meant to.

If none of them fits, that is a legitimate outcome rather than a gap in your understanding: aDNA is a structure for organising context, and plenty of real deployments look like none of these four.

The scenarios