coulomb/coulomb-social
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Record architecture decisions: thin git plane, live default, upgrades

Browse source 
D1 thin dir+git with shard-wiki then kontextual upgrade path; D2 defer
asset-store; D3 NetKingdom authz consolidation; D4 outline explode/implode
and live-by-default includes with pin as exception.
This commit is contained in:
tegwick 2026-08-13 00:48:33 +02:00
parent c27a50e6d3
commit d953aed4dd
5 changed files with 232 additions and 210 deletions
Download patch file Download diff file Expand all files Collapse all files

16
docs/architecture/stale-derived-content.md
View file

@ -118,20 +118,22 @@ Same for abstractor and visual (visual compare: two images or image vs placehold
Two legitimate modes (both needed):
### A. Live resolve (dynamic)
### A. Live resolve (dynamic) — **product default**
```markdown
<!-- mkt:include path="src.md" selector="sections[heading=API]" -->
```
At render/export, markitect resolves from **current** `src.md`.
“Stale” is less about the marker and more about **viewer cache**.
Still useful: badge if **last rendered snapshot** ≠ current resolve hash
(for offline cards that show a cached excerpt).
At render/export, markitect resolves from **current** `src.md`
(**spreadsheet-like**: formula results stay up to date).
### B. Pinned / materialised include (snapshot in host page)
“Stale” for pure live includes is mostly **viewer/cache** (optional badge if
a cached card excerpt lags live resolve). No replace/keep needed unless the
host cached a display snapshot.
For “user owns a frozen copy but can refresh”:
### B. Pinned / materialised include (snapshot in host page) — **exception**
For “freeze this excerpt / paste values” (explicit pin):
```markdown
<!-- mkt:derived id="api-excerpt"