Attach the artifact, then ask for the review.
A review-shaped filing without the system artifact is not a review. It forces the Council to invent architecture, then charge you for arguing with that invention. VectorCourt stops here and asks for the minimum manifest first.
Required fields
A link to the service artifact bundle, or a concrete inline description of the system being reviewed.
A review-shaped filing without a review target forces the Council to invent architecture.
OpenAPI/AsyncAPI, schema, protobuf, migration, or data-contract reference.
Adversarial and architecture reviews depend on named input, output, and state boundaries.
Runtime, topology, infrastructure-as-code, rollout, or deployment configuration reference.
Operational failure modes differ radically by runtime, topology, rollout, and rollback path.
Lockfile, package manifest, vendor inventory, or external dependency list.
Integration and supply-chain risk cannot be grounded without dependency evidence.
Team size, traffic class, external dependencies, ownership, SRE capacity, and support model.
Socio-technical and on-call risks depend on who must operate the scaffold after launch.