Architecture decision records (ADRs) as AI training data: what fractional CTOs should know

What is an architecture decision record, and why do AI buyers care?

An architecture decision record (ADR) is a short document that captures one technical decision: the context, the options considered, the choice made and its consequences. Teams keep them in a repository folder, a wiki or a ticketing system. Next to code history, ADRs supply the reasoning that commits and diffs leave out, which makes them useful for training and evaluating AI agents that need to make or review engineering choices, not just write code. See what AI training data is for the broader picture.

For a fractional CTO, ADRs are also a quick maturity signal. A client that writes them has a documented engineering culture, and that is the profile that may qualify for a licensing introduction.

What does a good ADR contain?

The strongest sets are the ones that link to pull requests and later incident reviews, so a decision can be traced to its outcome.

Where do ADRs live in a client company?

• A docs or adr folder in the main repositories, versioned with the code.
• A wiki space owned by platform or architecture teams.
• Request-for-comments documents in a shared drive.
• Design review threads in Slack or Teams.
• Issue tracker epics that carry decision notes.

Because many of these are versioned, the history of how a decision changed can be as informative as the final text. Git history is part of the same story. Companies that moved wikis or repositories recently may have lost edit history, so ask about archives.

How does a fractional CTO spot a company worth introducing?

Use the ADR depth check during a normal engagement:

• At least a few years of numbered ADRs, not a single template file.
• Status fields show superseded or deprecated decisions.
• Decisions link to tickets, pull requests or incident reports.
• Records are mostly in English and written by engineers, not copied from vendors.
• The business has 50+ full-time employees at peak (contractors excluded), operating for several years.
• Source code and records are owned by the company, not a client or a contract developer who retained rights.
• An owner, CEO, CFO or authorized representative could act as sponsor.

If you are still evaluating, the fractional CTO partner overview explains how this fits alongside client work.

What rights and confidentiality limits apply?

ADRs often mention customers, vendors, security weaknesses and credentials. Those references are the first thing to review.

You do not need to resolve any of this. You flag the question and the company works it out with SourceX before anything moves.

What should you say to the CTO or founder?

Related decision-and-outcome records appear in support escalation records, freight claims files and dispatcher decisions.

When should you not raise it?

Do not raise it when the client is under 50 full-time employees at peak, when its repositories belong to a customer or a prior owner, when a trustee or assignee controls the assets, or when the founders will not consider an exclusive license for an agreed term. Also leave it alone if the ADRs were written recently in bulk, for example by an AI tool, only to create an asset. Genuine decisions made over years are the point.

How does the introduction work?

1. You introduce the company through the referral form or your referral link, with basic fit information.
2. SourceX qualifies it on size, history, data breadth and rights.
3. The company completes a data inventory of its systems and repositories.
4. Redaction and exclusions are agreed before work begins.
5. Price and terms are agreed, buyers review, and the company signs only if it chooses.
6. Data is delivered after an executed agreement, and the company is paid.
7. Your reward is paid after SourceX receives payment.

You never export, upload or describe code, ADRs or other confidential records.

How do rewards work for a fractional CTO?

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. The reward is paid only after the buyer pays and SourceX receives its fee; an introduction, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed. Check your own client contracts for conflict-of-interest or disclosure expectations before you register.

Next step

If a client keeps a long ADR trail and meets the baseline, register as a partner and make the introduction. The data inventory builder helps them list repositories and wikis, and who qualifies covers the baseline in full.