You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
.specify/memory/constitution.md (the supreme governance doc — CLAUDE.md defers to it) has two factual status statements that are now wrong, plus one overstated claim:
L67 — Principle VI:SMS 2DM: Secondary; read support mandatory, write support future
Wrong._write_2dm ships (src/chilmesh/CHILmesh.py:2508) and save(".2dm") dispatches to it (:2472). Write support is shipped, and as of this rotation tested (tests/test_2dm_roundtrip.py, 12 round-trip cases, development158c018).
L26 — Mutation API:Topology changes (split, merge, insert_vertex) are explicitly opt-in via future Phase 5: Mutation API
Wrong (status).src/chilmesh/mutations.py ships the full API (split_triangle, swap_edge, merge_elements, remove_vertex, collapse_edge, move_boundary_node, split_triangles, smooth_topology) — Phase 5: Mesh mutation API (split, merge, swap, insert) #94 closed/shipped, also reflected in the README roadmap. The read-only-default semantics may still hold, but "future Phase 5" is stale.
Overstated claim (surfaced by the new round-trip test): the constitution describes .2dm roundtrip as lossless, but _write_2dm serializes only node coords + element connectivity — not boundary-segment metadata. Lossless for geometry/topology; boundary records are dropped. The wording should qualify this.
Why this is filed, not fixed
Per the per-repo operator directive, autonomous routine sessions do not unilaterally rewrite governance docs (the constitution outranks CLAUDE.md). The sanctioned fix is an operator pass or speckit-constitution update that keeps dependent templates in sync. First flagged for the 2dm half on #201 (2026-06-09); still present, hence this focused record.
Problem
.specify/memory/constitution.md(the supreme governance doc — CLAUDE.md defers to it) has two factual status statements that are now wrong, plus one overstated claim:L67 — Principle VI:
SMS 2DM: Secondary; read support mandatory, write support future_write_2dmships (src/chilmesh/CHILmesh.py:2508) andsave(".2dm")dispatches to it (:2472). Write support is shipped, and as of this rotation tested (tests/test_2dm_roundtrip.py, 12 round-trip cases,development158c018).L26 — Mutation API:
Topology changes (split, merge, insert_vertex) are explicitly opt-in via future Phase 5: Mutation APIsrc/chilmesh/mutations.pyships the full API (split_triangle,swap_edge,merge_elements,remove_vertex,collapse_edge,move_boundary_node,split_triangles,smooth_topology) — Phase 5: Mesh mutation API (split, merge, swap, insert) #94 closed/shipped, also reflected in the README roadmap. The read-only-default semantics may still hold, but "future Phase 5" is stale.Overstated claim (surfaced by the new round-trip test): the constitution describes
.2dmroundtrip as lossless, but_write_2dmserializes only node coords + element connectivity — not boundary-segment metadata. Lossless for geometry/topology; boundary records are dropped. The wording should qualify this.Why this is filed, not fixed
Per the per-repo operator directive, autonomous routine sessions do not unilaterally rewrite governance docs (the constitution outranks CLAUDE.md). The sanctioned fix is an operator pass or
speckit-constitutionupdate that keeps dependent templates in sync. First flagged for the 2dm half on #201 (2026-06-09); still present, hence this focused record.Suggested edits (for the operator/speckit pass)
SMS 2DM: Secondary; read + write support shipped (write drops boundary metadata).Filed by the CHILmesh hour-10 rotation (maintenance track). Not auto-fixable — governance-doc edit.
[model: claude-opus-4-8, repo: CHILmesh, session: 2026-06-22T10Z-rotation, refs: #94, #201]