- 5 days ago
- 2 min read
Last week we described the diagnostic pipeline. This week, the part that makes it usable in a deal process — and the part that still doesn't work.
An unconstrained prompt produces fluent, generic output because the model is drawing from a broad probability distribution across everything it has read. Ask "which rural Altnets are financially stressed?" and you get a competent summary of trade-press coverage. It reads authoritatively. It is not diligence, because you cannot audit a single claim in it.
Constraint engineering is the discipline of narrowing that distribution until the output becomes checkable. Three levers do most of the work:
1. Anchoring every claim to a document
The most effective constraint is the simplest: require the model to cite a specific filing, regulatory publication, or dataset for each assertion, and to state explicitly where data is unavailable rather than estimating. This single rule converts a persuasive narrative into a list of claims a human can verify or reject in an afternoon.
2. Bounding the question to a defined universe
"Rural UK Altnets" is not a universe — it is a vibe. Ofcom's Area 3 classification, active Project Gigabit contracts, and Companies House filing status are universes. Prompts that reference a defined population produce output whose gaps are visible; prompts that don't produce output whose gaps are invisible.
3. Forbidding the inferential leap
Models are strongest at exactly the thing diligence punishes: constructing a plausible causal chain across weakly related facts. An explicit negative constraint — do not infer commercial consequence from a regulatory term without a contractual anchor — removes a whole category of confident, unfounded conclusions.
Here is the honest limitation, and it is the reason we do not describe this as a solved problem.
Constraints reduce variance. They do not eliminate it. Run the same constrained prompt twice against the same dataset and you will not always get the same shortlist back — same facts, different confident conclusions.
That instability is tolerable when the output is treated as a list of things to check. It is disqualifying when treated as a conclusion. The distinction is not academic: an unstable shortlist presented as a finding is how a deal team ends up spending real hours investigating a risk that was never there, or missing one that was.
What actually closes the gap is not a better prompt. It is ground truth — site visits, contract review, conversations with operators and their customers — fed back into the process as evidence that either confirms or kills each generated hypothesis. That feedback loop is the part we are building now. We are not claiming to have finished it.
The prompt architecture decides what gets asked. Evidence from the ground decides what turns out to be true.
One question we genuinely want answered: if you are running AI inside a diligence or research process today, what is your actual sign-off gate — a named human, a score threshold, or something else?
Sources: Ofcom, Telecoms Access Review 2026–31; Companies House; INCA, State of the Altnets 2026. Methodology description is GreySynth's own.
Next: what an AI-native telecom operating model actually looks like in practice.