feat(flows): stack and group DFD stores - #37
Merged
Conversation
A process no longer gets one store box and one column chip per table. Its reads and writes render as stacked store boxes with one connector each, tables group into clusters (author-declared in clusters/<slug>.md and referenced as cluster:<slug>, or derived from basetype/subtype families and ERD groups), and every flow entry can carry a prose label: that shows on the chip. The flow view has a per-process view (default) and a connected view with stores/clusters/groups collapse levels, a stack dialog listing members, and a contract dialog listing which columns come from which tables. Five flow.cluster_* validation rules cover unknown or empty clusters, unknown members, and overlap. The modeling skill now authors a label on every flow entry and a cluster for stores a process treats as one thing, in every mode that writes flows, and verifies stack legibility. The key-inherited demo's Collect Payment writes a settlement cluster and is the worked example the skill and the flows guide quote. Non-breaking: existing models render unchanged; db: entries, hash routes, and the export format keep their meaning. New hash params flowview= and collapse= are additive. Design: docs/design/dfd-store-clusters.md Spec: docs/spec/dfd-store-clusters.md
damusix
force-pushed
the
worktree-dfd-store-stacks
branch
from
September 8, 2026 15:36
dadcc43 to
02c37c0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
clusters/<slug>.md,cluster:<slug>), basetype/subtype families, or ERD groups, and every flow entry can carry a proselabel:shown on the chip.flow.cluster_*validation rules.What this solves
Real models (a dozen processes, dozens of stores, hundreds of edges) drew one box and one column chip per table and were unreadable. Grouping and labelling keep each process at a handful of stacked rows with prose on the connectors.