Engineering Quality Gate — choose the correct procedure

Routing page for engineering review workflows. Choose architecture boundary review or standards-backed implementation review.

Run the architecture boundary review

Choose this when the main problem is system shape, ownership, layering, or boundary correctness.

Jump to Option 1 →

Run the standards-backed implementation review

Choose this when the main problem is whether code or configuration is correct according to official guidance.

Jump to Option 2 →

System shape

Choose Architecture Boundary Review

Use this when the main question is: “Is the system shape or boundary correct?”

This path is for architecture classification and structural diagnosis.

Implementation correctness

Choose Standards-Backed Implementation Review

Use this when the main question is: “Is this implementation correct according to official guidance?”

This path is for source-backed implementation findings and remediation.

When both are needed

Run them separately and in order

If both review types are needed, do not merge them into one run.

Order: 1) Architecture Boundary Review → 2) Standards-Backed Implementation Review.

Option 1

Run the architecture boundary review

Choose this procedure when the task is about architecture classification, layering, dependency direction, boundary leakage, interface ownership, state ownership, or minimal structural remediation.

Use this path when the dominant problem is architectural structure rather than source-backed implementation correctness.

Open procedure

Policy

Option 2

Run the standards-backed implementation review

Choose this procedure when the task is about code or configuration changes versus official docs, framework or runtime guidance, API misuse, version-sensitive implementation issues, or source-backed remediation steps.

Use this path when the dominant problem is implementation correctness and applicability of official guidance.

Open procedure

Policy

Mixed review contract

Mixing architecture diagnosis and implementation-guidance checks into one run.

This reduces boundary clarity and usually weakens the output.

Thin evidence for architecture

Expecting architecture classification from thin file excerpts.

Architecture review needs enough structural evidence.

No source path for implementation review

Expecting source-backed implementation recommendations without authoritative sources or browsing permission.

The implementation review fails closed when the source boundary is missing.

Using the router as the procedure

Treating this routing page as the runnable procedure instead of opening one of the two procedures above.

This page is for choosing the path, not executing it.