Improving Architecture

Boundary

Return read-only ranked candidates. Do not edit code, design a final interface, write an implementation plan, select a candidate for the user, or invoke another skill.

Read CONTEXT.md and relevant ADRs if they exist, using them only as vocabulary and constraint evidence. Never create or update those files.

Vocabulary

• Depth — behavior hidden behind a smaller interface.
• Shallow module — callers must understand nearly as much complexity as the implementation.
• Seam — a bounded interface where behavior can vary without editing callers.
• Locality — related knowledge, change, and failure are concentrated.
• Leverage — multiple callers stop repeating knowledge or coordination.

See reference/deep-modules.md for examples and reference/deletion-test.md for the deletion test.

Process