specs/Ornamentation.md: what a game is besides its rules
Some checks failed
ci / check (push) Failing after 4s
Some checks failed
ci / check (push) Failing after 4s
Draws one boundary — between what the rules can see and everything else a player experiences — and says which repository each belongs to as the simulator grows. "Ritual" becomes ornamentation: half the category is material rather than ceremonial, and "decoration" is already spoken for in this repo (a control that cannot fail). The test is not "does it have a decision in it" — choosing who deals is a decision and is ornamental. The test is whether the state hash moves, which reuses the instrument that already binds a trial note to a position. The part that earns its place in clay-borg rather than in a renderer's stylesheet: calling something ornamentation is a CLAIM THAT IT DOES NOT MATTER, and this project's register is a list of times that claim was wrong — quantity in Tokens.csv, F18's four unread files, SOLVE offered where it could not act. So a declaration carries a falsifier, and "provisional" is a state it must say out loud. Downstream may read, may not decide — ADR-0007 D5 restated at the repository boundary. The port to clay-animate is deliberately NOT designed: no consumer exists, and an interface built against an imagined client is the same defect as a gate that cannot go red. Five invariants, four checkable today. I3 — same seed and decisions produce a byte-identical recording at any pace through any renderer — is the falsifier for the whole split. CB-WP-0036 re-declared from L to M accordingly: the animation architecture that made it L has moved to clay-animate. No code had been written and the tier-L review had not been run, which is the only reason it could be re-scoped rather than unwound. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
34370d1076
commit
31ae160043
5 changed files with 353 additions and 173 deletions
|
|
@ -5,6 +5,9 @@ the stable structural decisions: layers, component planes, capability ports,
|
|||
data flows, and repository layout. For motivation and product intent see
|
||||
[`../INTENT.md`](../INTENT.md); for the full originating exploration see
|
||||
[`../history/260730-InitialExploration.md`](../history/260730-InitialExploration.md).
|
||||
For the boundary between what the rules can see and everything else a
|
||||
player experiences — and which repository each belongs to as the simulator
|
||||
grows — see [`Ornamentation.md`](Ornamentation.md).
|
||||
|
||||
Status: **draft** — this blueprint is normative for new work but still
|
||||
malleable (Clay). Changes go through a decision record in `decisions/`.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue