Commands And Refactoring

Intentions include adding, moving, renaming, rebinding, replacing, removing, wrapping, unwrapping, and resolving semantic obligations.

Textual intentions have Begin and End boundaries and generate one or more typed regions. Structural operations with no fragment can compile and end immediately. Multiple completed intentions form one session and one later semantic commit.

Both textual and structural auto-intentions must name capabilities advertised by the current projection. A stale or unavailable capability cannot create a session or mutate the candidate. Optional syntax uses the generic clear action, advertised only for a facet whose removal produces a valid semantic candidate.

The Refactoring Catalog is a roadmap, not a collection of text rewrites. Each refactoring must preserve or deliberately replace semantic identities and compile as one atomic command batch.