Design stale badge with replace-or-keep for projections and includes
Extend authoring model: generate alternative current version, keep or replace. Unify with pinned transclusions/pipelines; document markitect-tool gap and point at cross-repo proposal.
This commit is contained in:
parent
e2aa4045f4
commit
f6c9756b26
5 changed files with 312 additions and 3 deletions
|
|
@ -161,8 +161,21 @@ From markitect docs themselves (not blockers for S1):
|
|||
- Variable / conditional transclusion not yet
|
||||
- Includes currently path-first; content-reference-as-include path is designed for later
|
||||
- Dependency graph invalidation for caches is planned (WP-0007 hooks)
|
||||
- **Pinned derived snapshots + stale → alternative → replace|keep** — proposed in
|
||||
markitect-tool `docs/proposed-stale-derived-and-include-pinning.md`
|
||||
(coulomb product note: `stale-derived-content.md`)
|
||||
|
||||
Coulomb can start with **path + selector includes** and **section/region addressing**.
|
||||
Coulomb can start with **path + selector includes** and **section/region addressing**,
|
||||
then pin/freeze excerpts when “my version vs live source” matters.
|
||||
|
||||
### Live include vs pinned snapshot
|
||||
|
||||
| Mode | Behavior |
|
||||
|------|----------|
|
||||
| Live `mkt:include` | Always resolve current source at render |
|
||||
| Pinned `mkt:derived` (proposed) | Store snapshot; badge when source/inputs change; user generates alternative and chooses replace or keep |
|
||||
|
||||
Both are valid; co-creation often wants **pin + explicit refresh**.
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue