{"id":"requirement-interpretation","type":"concept","title":"Requirement interpretation","created":"2026-07-24","status":"Hypothesis defined","authors":["Upstream Zero"],"edges":[{"rel":"observes","to":"requirements"}],"summary":"How an evaluator reads a buyer's stated need and turns it into the criteria it screens vendors against.","question":"When a buyer states a requirement, how does the evaluator interpret it, and does that interpretation stay stable across runs?","pubState":"published","body":"Requirement interpretation studies the step before elimination: how an\nevaluator reads a buyer's stated need and converts it into the specific\ncriteria it then screens vendors against. Two evaluators, or two runs, can\ninterpret the same words differently.\n\nThe core question is how a stated requirement is interpreted and whether that\ninterpretation is stable. This component has a defined hypothesis but no\npublished run of its own yet; the requirement steps inside the survivability\nruns touch it indirectly.","url":"/concepts/requirement-interpretation","machineUrl":"/objects/requirement-interpretation","referencedBy":[{"from":"E-002","rel":"part-of"}],"_meta":{"site":"Upstream Zero · Commercial Intelligence for AI-Mediated Commercial Evaluation","version":"0.1","note":"Claims are presented at their evidence tier; Narrated is the lowest. Verify by walking edges, not by trusting us."}}