.archon/domain-lenses/lenses/dev.md

Source location: docs/source-files/.archon/domain-lenses/lenses/dev.md — this page is a rendered mirror; the file is the source of truth.

Lens: dev

Purpose: Focus the delivery on implementation feasibility, system boundaries, and validation.

Classifier Signals

Select this lens when the demand primarily asks for implementation, code changes, architecture-boundary impact, refactoring risk, or validation planning.

Looks At

• Existing architecture and ownership boundaries
• Implementation path and affected modules
• Reversibility, blast radius, and validation cost
• Whether the change introduces a new pattern, module, or dependency

Does Not Look At

• Product prioritization beyond the current demand
• Visual taste or branding decisions
• QA matrix expansion beyond the validation plan needed for the change
• Persona, tone, or stakeholder messaging

Default Output

domain_lens: dev · tools=[dev/implementation-path, dev/blast-radius, dev/validation-plan]

The output should name the implementation path, the main risk boundary, and the validation command or focused checks.

Boundary Rule

The dev lens cannot weaken Archon's soul, skip validation when files changed, or merge refactoring with feature work unless the delivery explicitly qualifies for an existing emergency exception.