mutability (living / frozen / sealed)
id
mutability
title
mutability (living / frozen / sealed)
type
definition
requires
- artifact-type-registry
related
- state memory (Kamae 6)
entry_points
- mutability
summary
The scale of how much an artifact may change over its life — living (revised freely), frozen (changed only by override), or sealed (never again).
depth
1
2
3
· plain
The scale of how much an artifact may change over its life — living (revised freely), frozen (changed only by override), or sealed (never again).
· definition
The axis naming how an artifact changes over its
life living — revised in place (, overview, by dated revision, the Basis of
Design) frozen — not edited in place, changed only by a superseding addendum (system
); thaw-able through the addendum mechanism, still governs the build
· usage
sealed —
final, the text never changes (closed hos, sidequests, addenda, findings,
devlogs/, executed ATs, propagation-ledger commits, sealed decisions); reopening carries
gravity — a sealed record is history (a future document may respond, nothing it in
force), a sealed decision's force yields only to a deliberate, recorded supersession Forward-only governs frozen and sealed; living is the declared exception — and the state
memory ( 6) is living and non-canonical: the posture.
related
state memory (Kamae 6)
referenced by (derived)
forward-only
defining documents: artifact-type-registry §6