coentrify 0.1.0 → 0.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -8,4 +8,4 @@ The package holds the source of coentrify under `src/`: its standards, its tools
8
8
  - `npx coentrify make no mistakes` - sets the project up autonomously: the agent chooses, and you veto afterward
9
9
  - `npx coentrify update` - brings the project up to date
10
10
  - `npx coentrify explain` - says what coentrify is
11
- - `npx coentrify check` - says when `coentrify.json` is behind the installed version, and what changed in between. It runs at the start of a session, and never blocks.
11
+ - `npx coentrify check` - says when `coentrify.json` is behind the installed version, and what changed in between. It runs at the start of a session, and never blocks. With `update` on `automatic` in `coentrify.json`, the agent then brings the project up to date at once.
package/bin/coentrify.js CHANGED
@@ -17,7 +17,10 @@ const SUMMARY = /^# .+\n+([^\n]+)/;
17
17
  const INSTALL = `npm install --save-dev ${PACKAGE}`;
18
18
  const RAISE = `npm install --save-dev ${PACKAGE}@latest`;
19
19
  const UPDATE_STEP = `bring this project up to date by following coentrify update, ${SOURCE}/commands.md#coentrify-update`;
20
- const USAGE = 'usage: npx coentrify [make-no-mistakes | update | explain | check]';
20
+ const AUTOMATIC = 'automatic';
21
+ const AUTOMATIC_STEP = `The update is automatic, so without waiting for a go: ${UPDATE_STEP}. With builders at work, the conductor hands it to an agent of its own, and a builder leaves it to the conductor.`;
22
+ const REVIEW_STEP = `The update waits for the director's go. Next step: ask for it, then ${UPDATE_STEP}`;
23
+ const USAGE ='usage: npx coentrify [make-no-mistakes | update | explain | check]';
21
24
  const HEADER = `coentrify - spec-driven development, ${WIKI}`;
22
25
 
23
26
  function next(step) {
@@ -56,12 +59,13 @@ function check() {
56
59
  console.log(`coentrify: the project uses coentrify, and it is not installed. Install it with ${declared ? DEPENDENCIES_INSTALL : INSTALL}.`);
57
60
  return;
58
61
  }
59
- const project = readJson(CONFIG).version;
62
+ const { version: project, update = AUTOMATIC } = readJson(CONFIG);
60
63
  const installed = readJson(INSTALLED_MANIFEST).version;
61
64
  if (typeof project !== 'string') {
62
65
  console.log(`coentrify: ${CONFIG} has no version. Next step: ${UPDATE_STEP}`);
63
66
  } else if (compare(installed, project) > 0) {
64
- console.log(`coentrify: ${CONFIG} is at ${project}, and the installed coentrify is ${installed}. Next step: ${UPDATE_STEP}`);
67
+ console.log(`coentrify: ${CONFIG} is at ${project}, and the installed coentrify is ${installed}.`);
68
+ console.log(update === AUTOMATIC ? AUTOMATIC_STEP : REVIEW_STEP);
65
69
  console.log('What changed for a project, by version:');
66
70
  console.log(migrations(project, installed).join('\n'));
67
71
  } else if (compare(installed, project) < 0) {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "coentrify",
3
- "version": "0.1.0",
3
+ "version": "0.1.1",
4
4
  "description": "Spec-driven development: standards, checks and tools for working with AI agents.",
5
5
  "license": "MIT-0",
6
6
  "type": "module",
@@ -0,0 +1,27 @@
1
+ # 0.1.1
2
+
3
+ The first round of changes filed from a project that runs on the package: two new game laws and four sharper ones, filing without hesitation, and an update that runs by itself. A project adds `update` to its `coentrify.json`, `automatic` by default, and rebuilds its coentrify.json check from the changed spec.
4
+
5
+ - 202 standards in 21 modules: seven changed
6
+ - Desire Before Reward and Bands, Not Bullseyes join the game laws
7
+ - Always Something To Do keeps a queue of goals at every skill level, Know What Is Coming unlocks nothing before it is introduced, No Hard Edges holds softly for the world, and music may come from a licensed library
8
+ - A contributor's setting is the standing go to file, and the agent creates the issue itself. A law for a subset of games is filed too
9
+ - The onboarding sets every adopted standard up in full, and puts a part to leave out to the director
10
+ - `update` in `coentrify.json` lets a session bring the project up to date by itself once the installed coentrify is newer
11
+ - A part of a standard that looks optional carries its own reason, starting with the wiki's lightbox
12
+
13
+ ## Behavior
14
+
15
+ - Changed [File A Change With Coentrify](../standards/behavior/file-a-change-with-coentrify.md)
16
+
17
+ ## Gamedev
18
+
19
+ - Changed [Game Design Laws](../standards/gamedev/game-design-laws.md)
20
+ - Changed [Game Design Laws: Experience](../standards/gamedev/game-design-laws-experience.md)
21
+ - Changed [Game Design Laws: Own Style](../standards/gamedev/game-design-laws-own-style.md)
22
+ - Changed [Game Design Laws: Progress](../standards/gamedev/game-design-laws-progress.md)
23
+ - Changed [Game Design Laws: UI](../standards/gamedev/game-design-laws-ui.md)
24
+
25
+ ## Tooling
26
+
27
+ - Changed [VitePress Wiki](../standards/tooling/vitepress-wiki.md)
@@ -2,6 +2,7 @@
2
2
 
3
3
  What changed in each version of coentrify. A version has a page of its own, which opens with its summary. The summary is also the text of its release.
4
4
 
5
+ - [0.1.1](0.1.1.md) - two new game laws, filing without hesitation, and an update that runs by itself
5
6
  - [0.1.0](0.1.0.md) - coentrify ships as an npm package, installed as a dev dependency
6
7
  - [0.0.8](0.0.8.md) - a second sweep of every page: a story lands whole, secrets stay away from agents, and every decision of an agent's own is named
7
8
  - [0.0.7](0.0.7.md) - a sweep of every page, a first prompt with the source, and the first round on hard traps
@@ -21,6 +21,7 @@ The onboarding writes `coentrify.json`, and the director changes it after.
21
21
  "records": ["changelog", "healing-log"],
22
22
  "wiki": "vitepress",
23
23
  "healing": "automatic",
24
+ "update": "automatic",
24
25
  "modules": {
25
26
  "behavior": {
26
27
  "always-make-no-mistakes": "tracked",
@@ -39,6 +40,7 @@ The onboarding writes `coentrify.json`, and the director changes it after.
39
40
  - `records` lists each record kept by its place under `docs/records/`: `log`, `activity`, `changelog`, `healing-log`, `playtests`, `user-tests`
40
41
  - `modules` - every standard taken from coentrify, by module, with its state
41
42
  - `healing` - who makes a harness change: `automatic` by default, where a subagent makes it, logs it in the healing log and the report names it for a veto, or `review`, where it is filed for the director
43
+ - `update` - what a session does when the installed coentrify is newer than `version`: `automatic` by default, where the agent brings the project up to date at once and reports, or `review`, where it says so and waits for the director's go
42
44
  - `contributor` - left out by default. Set to `true`, the project may file changes at the source.
43
45
  - `filing` - for a contributor: `review` by default, where the director looks at an issue before it is filed at the source, or `automatic`, where the subagent files it on its own
44
46
  - `libraries` - left out by default. Each library the project contributes to, by name, with its `source` and a `filing` of its own, as above ([Library Feedback](standards/docs/library-feedback.md))
@@ -67,6 +69,6 @@ A check built from its spec in the [tools](tools/overview.md) keeps the file tru
67
69
  - A folder the file names has to exist.
68
70
  - A standard the file lists has to be on disk.
69
71
  - A state is `tracked` or `customized`.
70
- - `healing` and `filing` are `automatic` or `review`, and `filing` stands only beside `contributor: true`.
72
+ - `healing`, `filing` and `update` are `automatic` or `review`, and `filing` stands only beside `contributor: true`.
71
73
 
72
74
  With `--staged`, as a pre-commit step, the check also refuses a commit that changes a tracked standard by hand. The commit passes once the state is `customized`, or when the commit changes the version, as an update does.
package/src/commands.md CHANGED
@@ -33,11 +33,13 @@ Any question about what coentrify is. Explain from the [readme](readme.md), the
33
33
 
34
34
  Any request to bring the project up to date. The update script from the [tools](tools/overview.md) works out what changed since the project's version, and the agent handles what needs judgment.
35
35
 
36
- - Raise coentrify to its latest version, `npm install --save-dev coentrify@latest`.
36
+ With `update` on `automatic`, the session check starts the update when the installed coentrify is newer than the project, and no go is waited for. Nothing is raised then: the installed version is the one to reach. With builders at work, the conductor hands the update to an agent of its own, and a builder leaves it to the conductor.
37
+
38
+ - Raise coentrify to its latest version, `npm install --save-dev coentrify@latest`, unless the session check started the update.
37
39
  - Run the update script from the installed package for the plan, `python3 node_modules/coentrify/src/tools/scripts/coentrify-update.py`, and read the [changelog](changelog/overview.md) from the project's version on. The script fetches the project's version from npm to compare with.
38
40
  - A project from before 0.1.0 sets coentrify up again, the way the [onboarding](onboarding.md#an-earlier-coentrify) says for an earlier coentrify.
39
41
  - Read `standards/decisions.md` for the reasoning behind the earlier choices.
40
- - Show the director a changed rule in a tracked standard before it is replaced.
42
+ - With `update` on `review`, show the director a changed rule in a tracked standard before it is replaced. With `automatic`, it is replaced at once, and the report names it.
41
43
  - A standard whose update the director declines is set to `customized` first, with the reason in the decisions.
42
44
  - Run it again with `--apply`, which replaces the tracked standards and their overview lines, and writes the new version.
43
45
  - Run the unlink script again, since a replaced standard brings its links back.
package/src/onboarding.md CHANGED
@@ -53,6 +53,7 @@ Older copies of coentrify are in use, and some have grown into a version of thei
53
53
  - The project's own additions are analyzed one by one.
54
54
  - An addition that still fits goes on top of the current standards.
55
55
  - An addition that the update made irrelevant is listed for removal.
56
+ - An addition that holds beyond the project is filed with coentrify, where the project is a contributor ([File A Change With Coentrify](standards/behavior/file-a-change-with-coentrify.md)).
56
57
 
57
58
  ## Recommend
58
59
 
@@ -65,11 +66,11 @@ Every choice has a default, and the default is the recommendation. The [recommen
65
66
  - Adoption grows with the phase: an idea takes the Always modules and a workflow, and the stack modules join once it is built.
66
67
  - A standard that an adopted standard links to, in a module the project did not pick, is offered as an option.
67
68
  - A workflow is strongly recommended, since tracking the work is part of coentrify.
68
- - Healing is automatic, and for a contributor, filing with coentrify waits for the director.
69
+ - Healing and updates are automatic, and for a contributor, filing with coentrify waits for the director.
69
70
 
70
71
  ## Choose
71
72
 
72
- The agent shows the recommendations as one short list. The director accepts a default, picks another option, or overrides with something of the project's own.
73
+ The agent shows the recommendations as one short list. The director accepts a default, picks another option, or overrides with something of the project's own. A part of an adopted standard the agent would leave out is in that list too, as a choice with its reason.
73
74
 
74
75
  With `coentrify make no mistakes` the agent asks nothing. The agent takes every recommendation, and makes a best guess where there is none. A conflict is settled the same way, and listed in the report.
75
76
 
@@ -86,7 +87,7 @@ With `coentrify make no mistakes` the agent asks nothing. The agent takes every
86
87
  - Set up the `docs` folder.
87
88
  - Create the wiki, where chosen.
88
89
  - Switch off the agent's own commit attribution where it has a setting for it ([Commits](standards/commits/commits.md#no-attribution)).
89
- - Build the checks and hooks the chosen standards ask for, in the project's own stack, from their specs in the [tools](tools/overview.md).
90
+ - Set every chosen standard up in full: build the checks and hooks it asks for, in the project's own stack, from their specs in the [tools](tools/overview.md).
90
91
  - Offer a setup script for personal content, where the director uses cloud sessions.
91
92
 
92
93
  ### The Links
@@ -111,7 +112,7 @@ The entry point also says to read the Core Rules again after a compaction. An ag
111
112
 
112
113
  ### The Session Check
113
114
 
114
- Every session starts with `coentrify check`. It says when `coentrify.json` is behind the installed coentrify, and what changed in between, and it never blocks.
115
+ Every session starts with `coentrify check`. It says when `coentrify.json` is behind the installed coentrify, and what changed in between, and it never blocks. With `update` on `automatic`, the agent then brings the project up to date at once ([Commands](commands.md#coentrify-update)).
115
116
 
116
117
  - Where the agent has a session start hook, such as Claude Code, the hook runs the check through the project's npm scripts ([Thin Wrappers In CI And Hooks](standards/scripts/thin-wrappers-in-ci-and-hooks.md)).
117
118
  - Elsewhere, the entry point asks for the check at the start of a session.
@@ -94,6 +94,13 @@ A contributor also files a change that holds beyond the project with coentrify (
94
94
  - Review - recommended: the director looks at the issue before it is filed, since the source is public
95
95
  - Automatic - the subagent files it on its own
96
96
 
97
+ ## Updates
98
+
99
+ The session check notices when the installed coentrify is newer than the project's version. `update` in `coentrify.json` says what happens then.
100
+
101
+ - Automatic - recommended: the agent brings the project up to date at once, replaces the tracked standards and reports the rest, such as a customized standard that changed
102
+ - Review - the check says an update is in, and the update waits for the director
103
+
97
104
  ## Folders
98
105
 
99
106
  - `docs` - the docs
@@ -8,15 +8,16 @@ What one project learns reaches every project.
8
8
 
9
9
  ## How To Apply
10
10
 
11
- - A project files only when its `coentrify.json` says `contributor: true`.
12
- - `filing` in `coentrify.json` says who files. With `review`, the default, the director looks at the issue first. With `automatic`, the subagent that `healing` starts files it on its own ([Always Make No Mistakes](always-make-no-mistakes.md#a-rule-or-a-check)).
13
- - A change is filed as an issue at the source that `coentrify.json` names.
11
+ - A project files only when its `coentrify.json` says `contributor: true`. Any project can be a contributor, and the setting is the director's standing go to file at the source.
12
+ - `filing` in `coentrify.json` says who files. With `review`, the default, the director looks at the issue first, and that look is the go for it. With `automatic`, the subagent that `healing` starts files it on its own ([Always Make No Mistakes](always-make-no-mistakes.md#a-rule-or-a-check)).
13
+ - A change is filed as an issue at the source that `coentrify.json` names. Creating the issue is the filing, so the agent creates it there itself once the go is in, without asking again.
14
+ - A session that cannot create an issue at the source asks for that access once, and keeps the drafts ready meanwhile.
14
15
  - A change to a module with a source of its own is filed with coentrify only when it is generic, as an addition of the module or the standard that coentrify lacks.
15
16
  - An issue holds one point, so issues close one by one.
16
17
  - Before filing, search the open issues.
17
18
  - A point that is filed already gets an addition on that issue, or a thumbs up.
18
19
  - An issue states the trigger, the proposal and the check: what happened, the rule to add, change or loosen and the standards it touches, and whether code could catch it instead, and which.
19
- - An issue holds no project details, since the source is public.
20
+ - The source is public, and it expects issues from the projects that use it. An issue holds no project details for that reason.
20
21
 
21
22
  ## Related
22
23
 
@@ -18,7 +18,7 @@ The Behavior standards: how an agent works and what an agent checks.
18
18
  - [Don't Filter Data Without A Spec](dont-filter-data-without-a-spec.md) - never drop data unless the exclusion is specced and tested
19
19
  - [Don't Introduce Tech Debt](dont-introduce-tech-debt.md) - new code follows conventions even when neighbors don't. Fix what your change caused
20
20
  - [Feature Workflow](feature-workflow.md) - plan -> doc -> laws -> spec -> failing e2e -> implement -> regression -> proof the director can verify
21
- - [File A Change With Coentrify](file-a-change-with-coentrify.md) - a contributor files a harness change that holds beyond its project, one point per issue, without project details
21
+ - [File A Change With Coentrify](file-a-change-with-coentrify.md) - a contributor files a harness change that holds beyond its project, and creates the issue itself: one point per issue, without project details
22
22
  - [Flag Every Addition Of Your Own](flag-every-addition-of-your-own.md) - name a decision of your own that no law, rule or guideline settles, for a veto. An impactful change is discussed first
23
23
  - [Free Text Replies, No Buttons](free-text-replies-no-buttons.md) - no answer buttons or wrap-up questions. Ask in prose and keep going. No closing prompts where a dashboard shows the director's inboxes
24
24
  - [General Working Rules](general-working-rules.md) - honest assessments, the model only for judgment calls, surface conflicts, read before you write, follow the written conventions
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "game-design-laws-experience.md": {
3
- "words": 620,
3
+ "words": 682,
4
4
  "reason": "twelve laws of one theme in one part"
5
5
  }
6
6
  }
@@ -8,7 +8,7 @@ The player never has to wait, unless it is technically impossible to continue ri
8
8
 
9
9
  ## Always Something To Do
10
10
 
11
- The player always has something to do. Short term, the pull to expand and explore. Long term, a dot on the horizon. When closing in on it, the outline of the next dot is already visible. The ultimate goal is not revealed too soon, but is visible from early mid-game. Nothing new to pursue for a moment is not nothing to do: there is the state to check and the next choice to think about, such as the balance when there is nothing to buy yet. Leave space for thinking, just not too much when the player already knows what to do. The better the player plays, the less time there is to think.
11
+ The player always has something to do. Short term, the pull to expand and explore. Mid term, the next objective and the one after it: the goals form a queue, so reaching one never leaves the player in the void that follows the last episode of a series. The queue brings no pressure, only something to want next. Long term, a dot on the horizon. When closing in on it, the outline of the next dot is already visible. The ultimate goal is not revealed too soon, but is visible from early mid-game. That holds at every skill level: a skilled player who goes fast never runs out of things to do. Nothing new to pursue for a moment is not nothing to do: there is the state to check and the next choice to think about, such as the balance when there is nothing to buy yet. Leave space for thinking, just not too much when the player already knows what to do. The better the player plays, the less time there is to think.
12
12
 
13
13
  ## Exploration Is Rewarded
14
14
 
@@ -16,7 +16,7 @@ Everything of one kind is shown in one place: a styleguide, a dev level, a page
16
16
 
17
17
  ## Generate, Never Reuse
18
18
 
19
- Making an asset is a commodity now. Generate your own, and never reuse a pack.
19
+ Making an asset is a commodity now. Generate your own, and never reuse a pack. Music is the exception: a track may come from a library, licensed for the game, unless the music is where the game is unique ([Unique Where It Counts](#unique-where-it-counts)).
20
20
 
21
21
  ## Unique Where It Counts
22
22
 
@@ -23,6 +23,16 @@ Completing the game 100% is reasonably doable. No orthogonal gameplay, like a pa
23
23
 
24
24
  Beating the game normally never requires playing try hard. The game supports every type of player, the completionist and the casual alike, by staying flexible and never forcing a play style. Optimizing is there for the player who wants it.
25
25
 
26
+ ## Bands, Not Bullseyes
27
+
28
+ Relevant for: skill checks, timing and crafting.
29
+
30
+ Success is a band, never a bullseye. A hit lands in a hitbox, never on a point, and a short grace period absorbs lag and thinking time. A beginner scrapes through, an expert optimizes, and any method that lands in the band counts ([No Try Hard](#no-try-hard)).
31
+
32
+ ## Desire Before Reward
33
+
34
+ The player wants a thing before they can have it. A wreck on the horizon is seen long before it can be reached ([Always Something To Do](game-design-laws-experience.md#always-something-to-do)). The wanting makes the way there worth playing, a dull task included. A reward that comes before the wanting is worth nothing.
35
+
26
36
  ## Earned Progress
27
37
 
28
38
  The player feels the progress made, so the gap between where the player starts and ends is as big as it can be: the player starts with as little as possible and earns the rest. Nothing that can be earned is handed over. What comes for free is worth nothing. A free first step that starts a climb is no gift but the climb's first rung.
@@ -41,7 +51,7 @@ Systems whose mere existence opens possibilities for the player, play styles amo
41
51
 
42
52
  ## Know What Is Coming
43
53
 
44
- The player always knows what is coming in the short future: the next upgrade, the next unlock, the distance to the next goal, and when it is the end. There is always something coming, so the next upgrade or level is always looming. The world still keeps its secrets ([Fair Surprise](game-design-laws-world.md#fair-surprise)).
54
+ The player always knows what is coming in the short future: the next upgrade, the next unlock, the distance to the next goal, and when it is the end. There is always something coming, so the next upgrade or level is always looming. Knowing needs no overview or progress bar: the world can show it, by a billboard, a glimpse or a line of dialog. Nothing unlocks before it is introduced ([Adopt, Repeat, Confirm](game-design-laws-guidance.md#adopt-repeat-confirm-arc)). The world still keeps its secrets ([Fair Surprise](game-design-laws-world.md#fair-surprise)).
45
55
 
46
56
  ## Related
47
57
 
@@ -12,7 +12,7 @@ The app feels alive: something is always moving on screen, things happen. Action
12
12
 
13
13
  ## No Hard Edges
14
14
 
15
- No sharp edge exists anywhere unless it is necessary. Every panel, button, row and box has rounded corners, if only slightly, and so does everything the scenes draw, a screen on a wall included. A corner stays sharp only when the thing itself would read wrong rounded.
15
+ No sharp edge exists anywhere unless it is necessary. Every panel, button, row and box has rounded corners, if only slightly, and so does everything the scenes draw, a screen on a wall included. In the world the law holds in a softer form: nothing real is perfectly sharp, a building's corner is worn and a plank is sanded, so a model's edges carry a slight bevel, and a hard edge sticks out. A corner stays sharp only when the thing itself would read wrong rounded. In the world that is a deliberate choice, and canon in the game: a blade, barbed wire, a spiked fence.
16
16
 
17
17
  ## Glow In Contrast
18
18
 
@@ -33,6 +33,8 @@ The full text is in [Game Design Laws: Progress](game-design-laws-progress.md).
33
33
  - [As Long As It Is Interesting](game-design-laws-progress.md#as-long-as-it-is-interesting) - no target length
34
34
  - [Doable 100%](game-design-laws-progress.md#doable-100) - no orthogonal skill demanded for completion
35
35
  - [No Try Hard](game-design-laws-progress.md#no-try-hard) - every play style is supported
36
+ - [Bands, Not Bullseyes](game-design-laws-progress.md#bands-not-bullseyes) - success is a tolerance window, never an exact point
37
+ - [Desire Before Reward](game-design-laws-progress.md#desire-before-reward) - the player wants a thing before they can have it
36
38
  - [Earned Progress](game-design-laws-progress.md#earned-progress) - start with as little as possible and earn the rest
37
39
  - [Lasting Impact](game-design-laws-progress.md#lasting-impact) - what the player decides lasts
38
40
  - [Emergent Gameplay](game-design-laws-progress.md#emergent-gameplay) - systems that open possibilities
@@ -51,7 +53,7 @@ The full text is in [Game Design Laws: UI](game-design-laws-ui.md).
51
53
 
52
54
  - [Communicate State](game-design-laws-ui.md#communicate-state) - what reacts, what is disabled and what changed shows it
53
55
  - [Alive App, Static Actions](game-design-laws-ui.md#alive-app-static-actions) - something always moves, actions are instant
54
- - [No Hard Edges](game-design-laws-ui.md#no-hard-edges) - rounded corners everywhere
56
+ - [No Hard Edges](game-design-laws-ui.md#no-hard-edges) - rounded corners everywhere, and soft edges in the world. Sharp only on purpose
55
57
  - [Glow In Contrast](game-design-laws-ui.md#glow-in-contrast) - a glow contrasts the text it wraps
56
58
  - [No Layout Shifts](game-design-laws-ui.md#no-layout-shifts) - controls never move while the player acts
57
59
  - [Same Trigger Both Ways](game-design-laws-ui.md#same-trigger-both-ways) - what opens an interaction closes it
@@ -90,7 +92,7 @@ The full text is in [Game Design Laws: Own Style](game-design-laws-own-style.md)
90
92
  - [No Asset Flips](game-design-laws-own-style.md#no-asset-flips) - every asset is the game's own
91
93
  - [Blueprint First](game-design-laws-own-style.md#blueprint-first) - things of one kind come from one blueprint
92
94
  - [Shown Together](game-design-laws-own-style.md#shown-together) - everything of one kind is shown in one place
93
- - [Generate, Never Reuse](game-design-laws-own-style.md#generate-never-reuse) - generate an asset, never reuse a pack
95
+ - [Generate, Never Reuse](game-design-laws-own-style.md#generate-never-reuse) - generate an asset, never reuse a pack, music aside
94
96
  - [Unique Where It Counts](game-design-laws-own-style.md#unique-where-it-counts) - unique in what makes the game, best practice for the rest
95
97
 
96
98
  ## How To Apply
@@ -102,7 +104,7 @@ The full text is in [Game Design Laws: Own Style](game-design-laws-own-style.md)
102
104
  - An exception is a paragraph under the law in the game's overrides, naming the feature and the reason, added only when the director affirms it.
103
105
  - Check a new feature against the laws before its spec. A conflict is surfaced, never averaged.
104
106
  - Feature docs link the law they lean on instead of repeating it.
105
- - A new law goes in the game's docs, in the director's wording. One that holds for every game is filed with coentrify, its game specifics stripped ([File A Change With Coentrify](../behavior/file-a-change-with-coentrify.md)).
107
+ - A new law goes in the game's docs, in the director's wording. One that holds for other games too, a subset of them included, is filed with coentrify, its game specifics stripped, with a `Relevant for:` line for a subset ([File A Change With Coentrify](../behavior/file-a-change-with-coentrify.md)).
106
108
 
107
109
  ## Related
108
110
 
@@ -14,10 +14,10 @@ The director reviews the docs, changelogs, captures and reels in the wiki while
14
14
  - A sidebar group is never a page itself, since a group that links cannot be closed by clicking it again. Its overview is the first item inside the dropdown.
15
15
  - A page's title is its H1, and a spec nests collapsed under its feature.
16
16
  - The record groups run newest first: the log, the activity, the playtests, the user tests and the changelog. The activity and log groups are titled Activity Log and Request Log.
17
- - A new or deleted page is picked up in place: once the changes settle, the sidebar is rebuilt and the open pages reload. The server never restarts for it, since a burst of new pages made it restart over and over.
17
+ - A new or deleted page is picked up in place: once the changes settle, the sidebar is rebuilt and the open pages reload. The server never restarts for it, since a burst of new pages would restart it over and over.
18
18
  - The wiki has one config file, `.vitepress/config`, and a session never creates a second one.
19
19
  - The watcher ignores the build output and the cache.
20
- - Every image in a page enlarges on a click to the full window width. The arrow keys walk the page's images, Escape or a click closes it, a counter shows the position, and the hidden state has its own display rule.
20
+ - Every image in a page enlarges on a click to the full window width, so the director judges a capture at full size, never shrunk to the text column. The arrow keys walk the page's images, Escape or a click closes it, a counter shows the position, and the hidden state has its own display rule.
21
21
  - Local search, last updated dates and clean URLs are on.
22
22
  - The dev server sends `Cache-Control: no-store`, so the director never reviews a stale image.
23
23
  - Videos sit in the public folder and embed with a plain video tag.
@@ -6,14 +6,14 @@ A spec for the check that keeps a project's `coentrify.json` true ([coentrify.js
6
6
 
7
7
  - It fails when the file does not parse, when a folder it names is missing, and when a standard it lists is not on disk.
8
8
  - It fails on a state other than `tracked` or `customized`. A module's `source` key is no standard.
9
- - It fails on a `healing` or `filing` other than `automatic` or `review`, and on `filing` without `contributor: true`.
9
+ - It fails on a `healing`, `filing` or `update` other than `automatic` or `review`, and on `filing` without `contributor: true`.
10
10
  - It fails on a library under `libraries` without a `source`, or with a `filing` other than `automatic` or `review`.
11
11
  - As a pre-commit step it also refuses a commit that changes a tracked standard by hand. The commit passes once the state is `customized`, or when the commit changes the version, as an update does.
12
12
 
13
13
  ## The Check
14
14
 
15
15
  - A file that names its folders and lists standards on disk passes.
16
- - A missing folder, a missing standard, a state of `draft` or a `healing` of `sometimes` fails.
16
+ - A missing folder, a missing standard, a state of `draft`, a `healing` of `sometimes` or an `update` of `daily` fails.
17
17
  - `filing` without `contributor: true` fails.
18
18
  - A library with a `source` and a `filing` passes, and one without a `source` fails.
19
19
  - A commit that edits a tracked standard by hand refuses, and passes once its state is `customized`.