One folder, one bounded contextLLM view

alcohol.zinc's real contexts

25 modules become 8 bounded contexts, and no loop of calls is left. Today 23 of the 25 sit in loops (the largest holds 21). MEASURED (the links) + REASONED (the lines).

ContextWhat it means
habitwhat a person committed to, and whether each day was kept
proofthe ways a day is proven: tap, NFC, Strava
planwhat a person pays for and what it allows
donationa missed stake becomes money that reaches a charity
paymentthe card and its mandates
friendfriends, and telling them when you miss
notificationmessages to a person
accountthe person's identity and its deletion
Link between contextsCountBecomes
a real question to another context14a contract call
"this happened"8an event through the outbox
accidental9deleted
Map, replayed on 50 real changesChanges inside one contextAlso touching nothing shared
today, 25 modules40%26%
finer, 1446%28%
proposed, 854%32%
coarser, 458%34%
  • These are not the 24% from the answer: 54% touch one context but may also touch shared files; 24% touch one folder and nothing else.
  • Two counts, both right: the .NET scan merges three Habit modules into one (23 modules, a loop of 19). The map keeps them apart (25, a loop of 21).
  • The coarser map scores a little better (2 changes of 50). I keep 8: its "money" would mix three meanings of "charge". REASONED
  • The 8 names are product words. They are yours to rename when zinc moves; nothing here waits for that.
  • A folder does not fix a wrong boundary. In zinc 46% of changes would still cross contexts with the best of these names. The map and the contracts matter as much as the layout.

The eight

Explorer
  • what a person committed to
  • how a day is proven
  • what a person pays for
  • a missed stake becomes a donation
  • the card
  • friends
  • messages to a person
  • identity