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
Decouple a concept page's size from the size of the store by removing the Integration Points
section from the page body entirely — touches: frontmatter stays as the grep surface, and the
nature of each interaction is described once, per edge, outside the page.
Meta
feature: docs/features/concept-store-capacity
estimate: M
candidate stories: Each interaction is described once, for both directions; A page declares
its neighbours without carrying their prose; The reciprocity fan-out retires; Blast-radius
retrieval still answers from one read
This is the structural answer to the problem #220 relieves. #220 re-cuts what the word cap
measures, which stops the cap from blocking a real edge; it does not stop a neighbour list from
growing with the store. This does — a page's size stops being a function of how many other pages
exist, permanently, and the reciprocity fan-out is deleted rather than adjusted.
It is deferred because it costs a store-wide migration (rewrite every active page, one new edge
artifact per edge, plus the append-only Decision Log entry each changed page owes) and it carries
a real retrieval regression: a page would no longer describe its own neighbourhood in a single
read, which is the primary retrieval path. #220 buys the headroom to make that call deliberately
rather than under pressure.
Promotion trigger
#220's schema amendment states a measurable store-level threshold at which this is revisited —
the candidate at analysis time was any page passing ~15 edges, or store-wide Integration Points
prose passing ~25% of all capped body text (16.2% when measured on 2026-08-03). Re-measure before
planning; the threshold as filed in the amendment wins over the number here.
Measured basis at filing
47 active pages · 198 directed touches edges · Integration Points is 16.2% of all capped body
text · mean bullet 13.7 words · highest degree 15.
Decouple a concept page's size from the size of the store by removing the Integration Points
section from the page body entirely —
touches:frontmatter stays as the grep surface, and thenature of each interaction is described once, per edge, outside the page.
Meta
its neighbours without carrying their prose; The reciprocity fan-out retires; Blast-radius
retrieval still answers from one read
Why this is deferred, not rejected
This is the structural answer to the problem #220 relieves. #220 re-cuts what the word cap
measures, which stops the cap from blocking a real edge; it does not stop a neighbour list from
growing with the store. This does — a page's size stops being a function of how many other pages
exist, permanently, and the reciprocity fan-out is deleted rather than adjusted.
It is deferred because it costs a store-wide migration (rewrite every active page, one new edge
artifact per edge, plus the append-only Decision Log entry each changed page owes) and it carries
a real retrieval regression: a page would no longer describe its own neighbourhood in a single
read, which is the primary retrieval path. #220 buys the headroom to make that call deliberately
rather than under pressure.
Promotion trigger
#220's schema amendment states a measurable store-level threshold at which this is revisited —
the candidate at analysis time was any page passing ~15 edges, or store-wide Integration Points
prose passing ~25% of all capped body text (16.2% when measured on 2026-08-03). Re-measure before
planning; the threshold as filed in the amendment wins over the number here.
Measured basis at filing
47 active pages · 198 directed
touchesedges · Integration Points is 16.2% of all capped bodytext · mean bullet 13.7 words · highest degree 15.