scip-architecture-review

SCIP Architecture and Maintainability Review

Load $scip-query for mechanics. Use ordinary file tools for implementation reads and scip-query for the relationships and findings that guide the investigation. This workflow covers first-use assessment, later design reassessment, and the structural consequences of changes. Use $scip-integrity-audit when the issue is whether a feature fulfills its promise.

Choose from the shared guide's architecture and dependency commands, simplification and cleanup commands, or framework investigations when a concrete concern calls for that analysis. Each row explains its question, index requirement and limits.

A module assigns responsibility to a group of code, such as storing documents or calculating eligibility. Its interface is the operations and rules consumers must understand: inputs, results, errors, effects, and ordering. A dependency exists when one implementation relies on another's behavior or representation.

Maintainability is the ability to change required behavior correctly without unnecessary discovery, duplicated decisions, or coordinated edits. Evaluate mistakes the structure would invite an agent to make and the facts it must discover to avoid them. File size, folder names, interface counts, and clean dependency rules do not establish design quality.

Orient without inventing owners

Run scip-query system --source for current TS/JS module groups and imports, including groups without findings. It needs no index or architecture configuration. Group IDs distinguish declared boundaries from provisional directories. Read coverage and missing configuration before claiming whole-repository visibility.

Use a printed group selector to investigate its files, dependencies, consumers, source interface evidence, findings, and limits. Use health for ranked cleanup candidates when useful and architecture for declared policy. Neither substitutes for behavior.