lens-topology-design

Invoke the topology design workflow with your project context, and it reads existing ledgers, feature archives, and prior decision reports to produce a proposed hierarchy. The output is a topology decision report with stable IDs, parent references, and a migration plan.

A topology decision report documents scope, sources, assumptions, current and proposed topology, a stable ID table, blocking inconsistencies, and a scaffold plan. It carries a status of PROPOSED, APPROVED, APPLIED, or BLOCKED plus a machine-readable JSON summary block.

No, ledger scaffolds are only created or updated when the user explicitly approves in interactive mode or passes an explicit apply/scaffold argument in headless mode. Otherwise the workflow writes a report only and never edits source documents.

The workflow surfaces the conflict instead of collapsing boundaries to fit the folder layout. It explains which authored evidence supports each side and records the inconsistency as blocking or advisory in the decision report.

Yes, headless mode writes a decision report from available context and marks unresolved choices explicitly instead of asking questions. It never modifies ledger files in headless runs unless an explicit apply argument is present.