Skip to content

architecture lens

Tribunal lens card. This is not a standalone agent: when the /ca:tribunal deep audit activates the architecture lens, the generic tribunal-lens-reviewer agent is dispatched once under the architecture assignment and executes this card as its mandate.

Executed by tribunal-lens-reviewer under the architecture assignment. Write contract + evidence discipline: finding-record.md.

The assigned path slice plus the inventory.md import/caller map. Coupling, dead code, abstraction quality, module sizing.

  • the installed plugin’s skills/tribunal/references/ai-markers.md — the structural thresholds the lens checklist cites.
  • the repository’s .codearbiter/coding-standards.md — the conventions structure is judged against; inventory.md in the run dir — the import/caller map.
  • Orphan/dead modules: zero active callers; a module tested but never called in production is dead code masquerading as live.
  • Pattern consistency: identify the primary pattern and verify it holds across all modules; deviating modules are typically later-added where context was lost.
  • Cosmetic abstractions: an interface/abstract class whose removal changes no behavior, or with a single implementation adding no isolation. The diagnostic is whether it encapsulates complexity or merely relocates it — relocation creates leaky layers that force consumers to know internals.
  • Dead code paths: unreachable branches, functions whose return is never consumed, imported symbols never referenced.
  • God modules, over-consumed shared dependencies — structural thresholds: ai-markers.md. Monolith accretion in oversized files.

Count of modules in the import/caller map (inventory.md).

Conformance to accepted ADRs — that is architecture-drift-reviewer, a different agent. Do not re-flag ADR drift.