v0.4.6 — Layers & model boundaries

Between a product and its assets there is room for interpretation — and a well-modeled single-product instance (one product, 40 assets) got a one-column Atlas and no way to refactor its model. v0.4.6 fixes that with a rule, a field, and a tool.

The rule (now in the concepts guide and inside the MCP modeling guide): a product is something you ship, version, and grant access to as a unit; an asset is something you change. When in doubt, fewer products with more assets — assets are movable, products are commitments.

Highlights

• Asset layers — a layer field describing where an asset sits inside its product (taxonomy: edge / frontend / backend / domain / data / infra / shared). Unset layers display a sensible default from asset type — no migration, no backfill
• Atlas layer columns — a Columns: Product | Layer toggle on the map, auto-switching to layers when a single product is in scope. Deep single-SaaS systems now get a real architecture map instead of one tall column
• move_asset — model refactoring with honest semantics: blocked while open plans target the asset (the error lists them), work items follow the asset, and history — release stamps, completed-plan links, capabilities — is preserved untouched
• MCP guidance — get_modeling_guide now carries the boundary rule, worked examples, the layer taxonomy, and a model-refining recipe; boundary heuristics live in the create_product / create_asset descriptions. 42 tools total
• Layer surfaced in the asset edit panel, detail header, Atlas grid cards, and a sortable table column; demo seed ships explicit layers
• 5 new tests (206 total)

Also since v0.4.5: the concepts guide ("How CodePlans Thinks") and the Asset Atlas + layers-and-boundaries specs joined the docs site.

Next (v0.4.7): agent-driven reconciliation proposals — the asset record verified against the code it describes.