Two lifecycle models built independently, three months apart. One describes what a legal AI practice does. The other computes what a firm should do next. They agree on the shape. They disagree on three things, and the disagreements are the interesting part.
AESOP runs on seven stages. Harbor's service framework runs on three bands. Put them side by side and the stages sort themselves into the bands with almost no arguing.
Two stages land in Advise. Two land in Implement. Three land in Manage. The line between Design and Build is the same line Harbor draws between advising and doing.
Seven stages against three bands. The correspondence is close enough to be meaningful and loose enough to be real.
Harbor names five capabilities in its Enterprise AI Operating Model. Every one of them already has a home in AESOP. The two lists were written without reference to each other.
| Harbor's capability | AESOP equivalent |
|---|---|
| AI Strategy: define outcomes before buying | Metrics before build; problems before solutions |
| Measure what matters | Certification bands, deterministic scoring, eval harness |
| Invest with intention | Portfolio prioritization with a weighted score and a veto rule |
| Change behavior, not just technology | Working agreement, adoption plan with its own metrics |
| Build trust at the speed of innovation | Human-edit feedback loop, drift monitoring, go/no-go gates |
Also pre-contact. Two independent alignments is a pattern, not a coincidence.
Harbor publishes a list of what an Advise engagement delivers. The roadmap generator produces some of those items from scratch and reads the rest as inputs. The split is clean.
| Harbor's Advise deliverable | Generator |
|---|---|
| Readiness assessment | Consumed as input |
| Use-case identification and prioritization | Generated |
| Workflow and process analysis | Consumed as input |
| Technology and model evaluation | Generated, with per-claim provenance tiers |
| Governance and risk frameworks | Generated, from advisory GOVERN verdicts |
| Deployment roadmap | Generated |
| Business case and success measures | Generated, via the AI Profit Paradox |
| Operating model design | Generated, as the roadmap's Manage band |
Items two, four, six and seven are generated. The rest are consumed. The taxonomy is Harbor's, not invented.
A perfect match would be suspicious. These two models were built by different people for different jobs, and the seams show in three places.
Harbor's model is three bands, sized for a service organization to describe itself. AESOP's is seven stages with gates between them.
Seven stages means seven places to stop and check. The gates are the product, not the stages.
Harbor's Advise → Implement → Manage reads sequential. AESOP's Evaluate → Repair → Track is a loop, and the Fault-Line Radar instruments the market half of it. Harbor sells model and platform evaluation as an episode, appearing once in Advise and again in Manage.
Nothing in the published framework says when to re-evaluate. The Radar does.
Harbor's framework describes what good practitioners do. The generator computes what should happen. Complementary, not competing.
Harbor does not need a machine that replaces consultants. It needs one that makes their judgment explicit, replayable, and inheritable.
The machine exists. The knowledge does not have a home.
Harbor's enablement teams have run AI adoption, training and change management inside law firms, including Magic Circle firms. The knowledge is real and it is the asset. What it lacks is a structured place to live and a way to be deployed against a specific client's facts.
The generator has the opposite problem: a working machine with generic knowledge and no proprietary base to draw on.
Neither is a product alone.
The timeline matters, because it separates two different claims. One is that the thinking converged on its own. The other is that some of it was built to match.
| Date | Event |
|---|---|
| 2026-05-17 or earlier | AESOP lifecycle exists. Earliest repo history is a merge commit; the lifecycle predates it |
| 2026-08 | Harbor Deploy launches |
| 2026-08-25 | Harbor's Operationalizing AI report published |
| 2026-09-01 | Eudia / Harbor partnership announced |
| 2026-09-05 | Fault-Line Radar lands in legal-os |
| 2026-09-07 | radar/advisory.py, the four-effect-order model |
| 2026-09-11 | The roadmap generator design begins |
The AESOP lifecycle predates Harbor's published framework by roughly three months. Same arc, arrived at independently.
The Radar and advisory.py postdate Harbor Deploy. The roadmap generator is explicitly shaped to Harbor's Advise deliverable list.
Do not blur those. The first is evidence of thinking. The second is evidence of listening.