Contracts before improvisation
Model the interface and its behavior before asking a model to guess what the world looks like.
Our worldview
Deterministic systems must exist before prompt and context optimization can mean anything.
Why DotMock exists
Agent-driven development makes software loops faster and more autonomous. It also makes every unstable dependency, irreversible side effect, and missing trace more expensive.
We believe agents need a controlled environment in which they can integrate, fail, retry, recover, and produce evidence. That environment should speak the real protocol, preserve state, emit the real kind of outbound event, and make every material change inspectable.
DotMock is that environment around the backend. It is not a replacement for the backend, a prettier fake response, or a claim that prompts can compensate for nondeterministic systems.
Principles
Safe loops over impressive demos
A complete, reproducible failure-and-recovery path matters more than a polished happy-path response.
Evidence over confidence
Traffic, state changes, deliveries, drafts, and approvals should be visible and attributable.
Native behavior over lowest-common-denominator mocks
REST, GraphQL, SOAP, gRPC, LLM APIs, and webhooks deserve their own contracts and runtime semantics.