no-fakes-discipline

You can prevent mock implementations by enforcing real-system validation through file blocking hooks that detect and refuse substitution attempts, ensuring all interactions hit the real system.

Real-system validation matters because using mocks or stubs can lead to false confidence and hidden bugs. Enforcing interactions with the real system prevents these issues and maintains strict validation gates across development and production environments.

You enforce a no-mocking policy by activating validation gates that inject refusal stderr when substitution attempts are detected. This requires setting up hooks for file blocking and post-action discipline to maintain the real-system enforcement posture.

Yes, file blocking and post-action discipline hooks are required dependencies to detect substitution attempts and enforce the no-mocking policy effectively.

When a user requests a fake or stub for a system call, the enforcement mechanism detects the intent and prevents the implementation by injecting refusal stderr, blocking the creation of mock implementations and enforcing the real system.

Yes, real-system validation applies to both development and production environments where real-system validation is critical. The enforcement mechanism maintains a strict posture against fakes across these environments to prevent hidden bugs.