Write the pattern landscape table (system-model step 6) #1480
Labels
No labels
P0
P1
P2
P3
bug
category/code-change
category/cross-repo
category/eval-run
category/investigation
category/no-test-target
category/owner-ruling
category/prose-artifact
category/recurring-chore
category/structure
category/umbrella
crc-refactor
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
rule-proposal
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#1480
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
README section 6 step 6 asks for a pattern landscape table. Without it we cannot show which patterns the signals reveal, and which patterns have no extracted signal. The goal "complete signal-to-pattern mapping" (README, "Goal, vision and approach") needs this table before the fact spike.
Reproduce
n/a: new research document.
Approach
Write
docs/system-design-format/pattern-landscape.md. A short research task picks the sources first: GoF (refactoring.guru catalog), Fowler PoEAA, POSA, Enterprise Integration Patterns, DDD tactical patterns, and one modern system-design source. One row per pattern, with these columns: pattern, source, scale group, revealing signals and facts, extracted now?, extraction cost, preference (blank until Jared rules). Add a reverse index: signal → candidate patterns. Put each pattern in one bin: expressible now, needs fact X, or not detectable statically. Drop no row as outdated. Use the fact families and scale groups of pattern-matching.md sections 2 and 5.Required work:
Reverse indexindocs/system-design-format/pattern-landscape.mdAcceptance criteria
Non-goals
Extracting new facts (step 9). Ruling on preference.
Origin
1b4ea2d5)VERDICT: CREATE
Resolution
Done: Pattern landscape table: 172 rows, bins, scale groups, reverse index
Evidence:
6bcff837Follow-ups: #1487