Danijel Martinek
449a4aedf5
User pushback: 'I already need mock data for dev and for testing at runtime' — i.e., the dual role of the mock is obvious, not surprising. Earlier framing was condescending. Reframe around 'runtime reach': - Section blurb leads with 'three artifacts at different distances from runtime' - Three-roles card intro: same neighborhood, different reach. Mock is reached by runtime; contract + factory only by tests. - 'The mock has two jobs' → 'The mock is reached from two directions — both legitimate, neither is the test version'. - Contract framing now leads with its real purpose: it tests the mock alongside the real impl so you can trust the mock as a runtime artifact.