liveBook · Manning

Ambiguity

As explained in Vibe Engineering

Ambiguity is a lack of sufficient clarity that permits multiple interpretations of a requirement, rule, or design choice.

Ambiguity is insufficient clarity that permits multiple interpretations. In multi-agent systems, it changes from a minor inefficiency into a structural risk: each missing constraint can produce many divergent implementations. section 10.8.1

Ambiguity becomes dangerous when:

  • Conventions rely on context or experience instead of explicit constraints. section 10.8.1
  • Many agents interpret the same instruction differently, creating plausible but inconsistent code. section 10.8.1
  • Individual inconsistencies compound across commits into architectural drift that nobody fully understands. section 10.8.1

The 90-percent-clear convention

A convention that is 90% clear may work for one developer, who infers the missing 10% from experience. Given to a hundred agents, it can yield ten subtly different implementations that compile, pass tests, and still move the architecture toward an unintended shape. section 10.8.1

How Vibe Engineering covers it

How deep it goes
Explains how ambiguity scales into architectural drift, but stops short of prescribing a detailed remediation process.
Examples
Uses a 90%-clear convention, one developer, one hundred agents, plausible code, passing tests, and accumulated architectural drift.
What you can do after
Evaluate whether specifications provide enough explicit constraints for consistent multi-agent implementation.
How it connects
Connects ambiguity with multi-agent systems, software architecture, implicit conventions, and codebase organization.

Also explained in

Compare how 6 books explain ambiguity →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Vibe Engineering. The section links point to the parts of the book it draws on.