architecture-audit

Detect architecture drift in a TypeScript monorepo by analyzing package topology and kernel internals to identify layer violations, dead systems, and over-abstraction. This generates file-level findings with fix directions and risk estimates to establish a prioritized baseline before refactoring.

Prioritize technical debt before a monorepo refactor by running coordinated parallel inspections to categorize fixes as immediate, planning, or escalation. This triage appends actionable entries to an architecture debt register, identifying top simplification opportunities for stakeholder planning.

Check for documentation drift by running parallel agent analysis that inspects documentation accuracy against high-churn kernel internals. This produces file-level findings that expose mismatches between authoritative docs and the actual implementation during release readiness reviews.

Yes, you can audit package topology and provider adapters across a 22-package monorepo. The analysis scopes to inspect structural dependencies and layer violations, producing an architecture snapshot that guides targeted fixes and escalations for complex cleanup scenarios.

Identify dead or disabled systems during post-feature cleanup by analyzing the monorepo for scaffolding, flags, and under-abstraction. The audit produces file-level findings with specific fix directions and effort estimates to safely remove obsolete structural debt.

The primary limitation is that the architecture audit is scoped specifically to the reactive-agents-ts 22-package TypeScript monorepo topology. It targets pre-refactor or cleanup scenarios, meaning its package-level dependency analysis and documentation drift detection are tailored to that specific environment.