review

To audit a TypeScript project for architecture conformance, the review workflow reads your architecture docs, derives concrete rules, and generates an immutable checklist. It coordinates a subagent to validate each item against your repository files and produces a final audit report.

Architecture drift detection works by generating a verifiable checklist from your architecture docs and validating each item against repository files using a subagent. It appends an immutable, versioned review record to tseng/reviews to preserve history and ensure traceability across architecture revisions.

Yes, you can trace TypeScript architecture reviews across multiple revisions because each audit appends a new immutable entry to the tseng/reviews directory. This structured record preserves history and enables traceability across architecture revisions.

The best way to generate an architecture review checklist from documentation is using a two-phase workflow that first retrieves the current architecture revision and then derives concrete, verifiable rules from the docs to create a structured checklist.

Yes, you need architecture documentation to perform a TypeScript architecture audit because the workflow reads these docs to derive concrete rules and generate the verifiable checklist used to validate repository files.

A limitation of validating repository files against a fixed architecture ruleset is that the audit relies on a subagent to check each checklist item, meaning the review scope and accuracy are bounded by the derived rules from your architecture docs and the subagent's file validation capabilities.