Same Page Count, Different Problem A 300-page contract packet and 300 one-page invoices can have the same page count. They do not have the same engineering problem. The contract packet fails because context gets messy. Definitions appear 80 pages before the clause that depends on them. Amendments override earlier terms. Tables lose meaning when separated from section headings. A reviewer needs to know which page supports a value, not just whether a value exists. The invoice batch fails because operations get messy. One file is corrupt. Twelve need review. Forty belong to a different vendor. A retry loop runs twice. A spreadsheet export hides partial failures. Cost attribution gets murky because one upload created hundreds of independent workflow records. If both workflows are treated as "300 pages of documents," the design will be wrong for at least one of them. Page count is a weak abstraction. Length and count create different failure modes. Long documents need context boundaries.…