Skip to content

Concepts guide ("How CodePlans Thinks") + layers-and-boundaries spec - #51

Merged
SylonZero merged 1 commit into
masterfrom
claude/roadmap-plans-review-8t8gri
Aug 5, 2026
Merged

Concepts guide ("How CodePlans Thinks") + layers-and-boundaries spec#51
SylonZero merged 1 commit into
masterfrom
claude/roadmap-plans-review-8t8gri

Conversation

@SylonZero

Copy link
Copy Markdown
Owner

Docs-only PR ahead of the v0.4.6 implementation.

New guide — docs/guides/concepts.md

"How CodePlans Thinks": the conceptual map for developers —

  • what each object is for (not just what it's called), with the object model in one pass;
  • the load-bearing product boundary (access, plans, and releases all hang off it — which is why "each subsystem = a product" breaks coordinated releases);
  • the normative rule: products ship, assets change — with worked examples (single SaaS = one product with many assets; portfolio = several products; monorepos are orthogonal; internal platforms with their own contract are products);
  • the layer axis as the second dimension inside a product;
  • the five design principles: derived not maintained, reality not intent, shipping is a human act, agents are first-class users, models are refinable.

New spec — docs/specs/layers-and-boundaries-spec.md (proposed, v0.4.6)

  • assets.layer: free text with a conventional taxonomy (edge · frontend · backend · domain · data · infra · shared) and display-time defaults from asset type — existing instances get a layered map with zero migration; defaults are never written to rows.
  • Atlas layer columns: a "Columns: Product | Layer" toggle, auto-switching to layers when a single product is in scope (fixing the single-column degenerate case); taxonomy-ordered columns so edges mostly point one way.
  • move_asset with defined semantics: blocked by draft/active plans (listed for retargeting), work items follow the asset, history is history (stamps, completed-plan links, capabilities, lineage all preserved).
  • MCP: layer on create/update_asset, new move_asset tool (→42), a Boundaries section in get_modeling_guide, and one-line boundary heuristics in create_product/create_asset descriptions.
  • Explicit non-goals: layers never carry permissions (that would make them products with extra steps); no heuristic auto-writes of layers.

Also

  • Reconciliation phases renumbered to v0.4.7/v0.4.8 across the record spec, README roadmap, app-spec, and docs site.
  • Doc cards for both new documents; the Atlas spec cross-references the layer axis.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Y7FhGxYjnJHJ7m9MpH2dgJ


Generated by Claude Code

- docs/guides/concepts.md ('How CodePlans Thinks'): the conceptual map —
  what each object is for, the load-bearing product boundary (access,
  plans, releases), the normative rule (products ship, assets change),
  worked examples (single SaaS, portfolio, monorepo, internal platform),
  the layer axis, and the five design principles (derived not
  maintained; reality not intent; shipping is a human act; agents are
  first-class users; models are refinable)
- docs/specs/layers-and-boundaries-spec.md (proposed, v0.4.6): assets
  .layer (free text + conventional taxonomy, display-time defaults from
  type), Atlas layer columns with single-product auto-switch, moveAsset
  semantics (blocked by open plans, work items follow, history is
  history), MCP changes (layer params, move_asset tool -> 42, modeling-
  guide Boundaries section, boundary heuristics in tool descriptions)
- Reconciliation phases shifted to v0.4.7/v0.4.8 across the record
  spec, README roadmap, app-spec, and site; doc cards added for both
  new documents; atlas spec cross-references the layer axis

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Y7FhGxYjnJHJ7m9MpH2dgJ
@SylonZero
SylonZero merged commit 4a88e01 into master Aug 5, 2026
1 check passed
@SylonZero
SylonZero deleted the claude/roadmap-plans-review-8t8gri branch August 5, 2026 19:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants