Review-shaped questions require artifacts before Council spend.
When a filing asks VectorCourt to adversarially review a microservice, audit an architecture, assess operational risk, or surface unknown unknowns, the Clerk must first verify that the system under review exists in the filing. If the artifact is missing, deliberation stops before Council spend.
Minimum Contract
- Provide an artifact link or a concrete system description.
- For architecture and adversarial reviews, provide API/schema evidence.
- Provide deployment or topology evidence.
- Provide dependency evidence.
- Provide operational context: owners, traffic, external dependencies, and support capacity.
This is refusal to manufacture confidence. A review without the artifact turns the Council into plausible failure modes for the wrong system.
The Clerk is allowed to say: attach the artifact, then ask again.