What problem does it solve? Architecture documentation often drifts from what the code actually does, and locally reasonable decisions can compose into a system that is structurally wrong for its purpose. This Skill pressure-tests an existing system's architecture against the running code, exposing doc-to-code gaps, mis-invested effort, and deferred existential risks. ## Core Features & Use Cases - Reality Audit: Verifies every Accepted ADR in the source and confirms Proposed items are genuinely unbuilt, distinguishing substance from stubs with line counts and test counts. - Adversarial Theses: Develops 2-4 code-cited theses on whether a system of this nature should be designed this way, each with inherent limitations, concrete better-decision sketches, and steelmans. - Structured Report: Writes a point-in-time assessment to .gener8v/reviews/<system-slug>-architecture-assessment.md with verdict, limitations, recommendations, and open questions. - Use Case: Before adopting a workflow engine, run the review on your pipeline system; it may reveal that most persistence code is irreducible domain logic, while the real finding is an over-built DAG engine running a strictly linear pipeline. ## Quick Start Run the architecture review on the ingestion system with focus on the tenancy model and job queue, and write the assessment report.
