How the scenarios were generated, what got filtered out, and what the audit does not do.
The contract text was parsed into addressable units — labeled L1–L5 for Contract 1 and L1′–L5′ for Contract 2 — and each unit was run through the seven-question diagnostic battery: internal contradiction, vague operative term, definitional boundary, standardless discretion, gap or silence, cross-clause tension, and term consistency.
Each confirmed defect was then developed into a dispute scenario with a concrete fact pattern, two steel-manned positions, the precise textual flaw, a predicted outcome with the doctrine driving it, and proposed replacement language. The quality bar for retaining a scenario is that a competent tribunal could decide it either way; scenarios where one side obviously prevails were sharpened or dropped.
The contract profile applies no canon gauntlet. Unlike the statute and regulation profiles, where an apparent ambiguity that the canons of construction would dispatch in a paragraph is treated as a false positive, contract ambiguity is resolved by recovering the parties' bargain — and four-corners resolution is an acceptable answer rather than a reason to discard the scenario.
Every operative line drew at least one finding except L2, whose weight bands are the only genuinely unambiguous specification in the instrument. That precision is itself the tell: a drafter who specified weight to the half-pound and the wrapping to the brand of plastic did not specify the class of bird.
Profile A — Contracts. The competing interpreters are fixed and binary: Buyer (Frigaliment Importing Co.) against Seller (B.N.S. International Sales Corp.). The resolving doctrines are harmonization, specific-governs-general, contra proferentem, the implied covenant of good faith and fair dealing, the prevention doctrine, course of dealing and usage of trade, and the four-corners and parol evidence rules.
The scan was run against the contract as though before performance. Scenario S-1 is the dispute that actually arose, which allows its predicted outcome to be checked against Judge Friendly's actual holding rather than merely trusted. The other five did not become litigation but are live on the face of the document.
This audit detects interpretive ambiguity, not validity or enforceability. A contract can be perfectly clear and wholly unenforceable; nothing here assesses whether either confirmation is valid, whether the statute of frauds is satisfied, or whether any remedy would be available.
Six defects were developed into full scenarios and eight further absences are recorded in the coverage list. Because the instrument is short, this is closer to a complete audit than a sample.
Items the scan surfaced that were not developed into full scenarios.
Contract 1 is quoted verbatim as it appears in the opinion at 190 F. Supp. 117. Contract 2 is NOT quoted in the opinion; it is reconstructed from the court's statement that the second contract was identical except in three respects, and the price for the 2½–3 lb. class in that document is not in the record. Any reading of it as $33.00 is inference, not fact.
One fragment could not be confirmed. The L3 description line is confirmed through "secured fiber cartons." It is commonly rendered as continuing "…or wooden boxes, suitable for export," but that continuation was not verified verbatim from an authoritative reporter text in this run and is therefore excluded from the source text above and from the scan. If the tail is genuine, it adds a second export-suitability seam alongside S-4.
Predicted outcomes are predictions, not pronouncements. Only S-1 has been tested against a real judgment.
Generated by interpretive-ambiguity-stress-test (Profile A — Contracts) and rendered by ambiguity-report. Source: Frigaliment Importing Co. v. B.N.S. International Sales Corp., 190 F. Supp. 116 (S.D.N.Y. 1960) (Friendly, J., sitting by designation).