coentrify 0.0.2 → 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.
Files changed (262) hide show
  1. package/LICENSE +18 -0
  2. package/README.md +2 -1
  3. package/bin/coentrify.js +83 -12
  4. package/package.json +3 -2
  5. package/src/changelog/0.0.1.md +259 -0
  6. package/src/changelog/0.0.2.md +219 -0
  7. package/src/changelog/0.0.3.md +81 -0
  8. package/src/changelog/0.0.4.md +198 -0
  9. package/src/changelog/0.0.5.md +160 -0
  10. package/src/changelog/0.0.6.md +282 -0
  11. package/src/changelog/0.0.7.md +113 -0
  12. package/src/changelog/0.0.8.md +212 -0
  13. package/src/changelog/0.1.0.md +9 -0
  14. package/src/changelog/0.1.1.md +27 -0
  15. package/src/changelog/overview.md +14 -0
  16. package/src/coentrify-json.md +74 -0
  17. package/src/commands.md +50 -0
  18. package/src/glossary.md +132 -0
  19. package/src/how-it-works.md +51 -0
  20. package/src/onboarding.md +141 -0
  21. package/src/origin.md +19 -0
  22. package/src/philosophy.md +99 -0
  23. package/src/proof.md +596 -0
  24. package/src/readme.md +76 -0
  25. package/src/recommendations.md +107 -0
  26. package/src/standards/ai/match-known-commands-deterministically-classify-the-rest.md +22 -0
  27. package/src/standards/ai/overview.md +6 -0
  28. package/src/standards/ai/prompt-small-models-differently.md +21 -0
  29. package/src/standards/angular/canmatch-wildcard-for-route-access.md +22 -0
  30. package/src/standards/angular/interface-not-abstract-class-for-mock-swap.md +37 -0
  31. package/src/standards/angular/no-any-in-templates.md +25 -0
  32. package/src/standards/angular/no-inline-templates.md +14 -0
  33. package/src/standards/angular/one-component-per-folder-flat.md +12 -0
  34. package/src/standards/angular/one-projected-node-per-control-flow-block.md +19 -0
  35. package/src/standards/angular/overview.md +16 -0
  36. package/src/standards/angular/prefer-content-projection-over-props-angular.md +17 -0
  37. package/src/standards/angular/projected-content-is-never-styled-by-the-host.md +23 -0
  38. package/src/standards/angular/static-attribute-not-literal-binding.md +23 -0
  39. package/src/standards/angular/track-timed-items-by-an-id.md +17 -0
  40. package/src/standards/angular/ui-copy-in-template.md +26 -0
  41. package/src/standards/angular/use-modern-angular-template-apis.md +20 -0
  42. package/src/standards/architecture/adopt-configure-override.md +25 -0
  43. package/src/standards/architecture/app-shield.md +57 -0
  44. package/src/standards/architecture/converge-only-once-proven.md +22 -0
  45. package/src/standards/architecture/folder-concerns.md +28 -0
  46. package/src/standards/architecture/overview.md +11 -0
  47. package/src/standards/architecture/per-application-split-over-shared-branching.md +25 -0
  48. package/src/standards/architecture/separation-before-layer-standards.md +17 -0
  49. package/src/standards/architecture/unique-where-it-counts.md +19 -0
  50. package/src/standards/behavior/a-go-before-work-elsewhere.md +17 -0
  51. package/src/standards/behavior/a-maybe-is-a-trigger-to-investigate.md +20 -0
  52. package/src/standards/behavior/a-name-describes-its-unit.md +19 -0
  53. package/src/standards/behavior/a-quiet-tree-while-a-suite-runs.md +19 -0
  54. package/src/standards/behavior/always-make-no-mistakes.md +45 -0
  55. package/src/standards/behavior/always-verify-before-reporting-done.md +18 -0
  56. package/src/standards/behavior/always-work-from-a-plan.md +29 -0
  57. package/src/standards/behavior/anchor-edits-after-formatting.md +17 -0
  58. package/src/standards/behavior/backward-trace-missing-prerequisites.md +20 -0
  59. package/src/standards/behavior/code-review-compounds-into-patterns-and-sweeps.md +21 -0
  60. package/src/standards/behavior/communication-boundary.md +18 -0
  61. package/src/standards/behavior/dev-tiers.md +25 -0
  62. package/src/standards/behavior/docs-hold-only-what-the-director-decided.md +23 -0
  63. package/src/standards/behavior/dont-filter-data-without-a-spec.md +20 -0
  64. package/src/standards/behavior/dont-introduce-tech-debt.md +25 -0
  65. package/src/standards/behavior/feature-workflow.md +31 -0
  66. package/src/standards/behavior/file-a-change-with-coentrify.md +25 -0
  67. package/src/standards/behavior/flag-every-addition-of-your-own.md +22 -0
  68. package/src/standards/behavior/free-text-replies-no-buttons.md +20 -0
  69. package/src/standards/behavior/general-working-rules.md +37 -0
  70. package/src/standards/behavior/non-destructive-documenting-and-test-automation.md +20 -0
  71. package/src/standards/behavior/normal-dashes.md +15 -0
  72. package/src/standards/behavior/note-issues.md +26 -0
  73. package/src/standards/behavior/overview.md +46 -0
  74. package/src/standards/behavior/own-ports-own-processes.md +37 -0
  75. package/src/standards/behavior/project-lifecycle.md +21 -0
  76. package/src/standards/behavior/propagate-renames-and-convention-changes-everywhere.md +16 -0
  77. package/src/standards/behavior/prose-style.md +24 -0
  78. package/src/standards/behavior/prototype-mode-is-speed-first.md +20 -0
  79. package/src/standards/behavior/regular-layered-gap-analysis.md +20 -0
  80. package/src/standards/behavior/reload-the-standards-after-compacting.md +16 -0
  81. package/src/standards/behavior/review-changes-before-reporting-done.md +17 -0
  82. package/src/standards/behavior/review-every-capture-before-reporting.md +21 -0
  83. package/src/standards/behavior/standards-maintenance.md +65 -0
  84. package/src/standards/behavior/standards-over-skills.md +17 -0
  85. package/src/standards/behavior/sweeps-enumerate-into-tech-debt-first.md +20 -0
  86. package/src/standards/behavior/sync-the-docs-after-every-change.md +20 -0
  87. package/src/standards/behavior/the-quality-of-the-question.md +17 -0
  88. package/src/standards/behavior/things-of-one-kind-are-consistent.md +20 -0
  89. package/src/standards/behavior/understand-the-need.md +69 -0
  90. package/src/standards/behavior/use-us-english-everywhere.md +17 -0
  91. package/src/standards/behavior/verify-apis-against-docs-and-the-installed-artifact.md +17 -0
  92. package/src/standards/behavior/verify-control-before-rename.md +11 -0
  93. package/src/standards/code/code-principles.md +32 -0
  94. package/src/standards/code/escape-hatch-comments.md +20 -0
  95. package/src/standards/code/name-by-concept-not-copy.md +20 -0
  96. package/src/standards/code/no-abbreviated-names.md +20 -0
  97. package/src/standards/code/no-describe-what-comments.md +26 -0
  98. package/src/standards/code/overview.md +10 -0
  99. package/src/standards/code/pre-empt-recurring-code-review-nits.md +31 -0
  100. package/src/standards/commits/commits.md +44 -0
  101. package/src/standards/commits/gate-commits-on-exit-codes.md +22 -0
  102. package/src/standards/commits/main-stays-green-work-stays-clean.md +23 -0
  103. package/src/standards/commits/overview.md +8 -0
  104. package/src/standards/commits/verify-staging-before-committing.md +29 -0
  105. package/src/standards/docs/application-template.md +89 -0
  106. package/src/standards/docs/docs-are-hierarchical-explicit-and-short.md +48 -0
  107. package/src/standards/docs/docs-describe-behavior-not-wiring.md +24 -0
  108. package/src/standards/docs/docs-folder-structure.md +38 -0
  109. package/src/standards/docs/docs-state-knowledge.md +23 -0
  110. package/src/standards/docs/documentation-philosophy.md +62 -0
  111. package/src/standards/docs/feature-spec-template.md +89 -0
  112. package/src/standards/docs/feature-template.md +62 -0
  113. package/src/standards/docs/file-names.md +20 -0
  114. package/src/standards/docs/glossary.md +18 -0
  115. package/src/standards/docs/library-feedback.md +20 -0
  116. package/src/standards/docs/no-faux-headers-in-lists.md +18 -0
  117. package/src/standards/docs/overview.md +20 -0
  118. package/src/standards/docs/ui-vocabulary.md +31 -0
  119. package/src/standards/docs/workspace-levels.md +24 -0
  120. package/src/standards/docs/workspace-suite.md +24 -0
  121. package/src/standards/docs/workspace-template.md +41 -0
  122. package/src/standards/e2e/e2e-assert-before-interacting.md +21 -0
  123. package/src/standards/e2e/e2e-mock-contract.md +20 -0
  124. package/src/standards/e2e/e2e-runs-on-the-development-build.md +18 -0
  125. package/src/standards/e2e/e2e-test-conventions.md +61 -0
  126. package/src/standards/e2e/e2e-tests-must-demonstrate-behavior.md +28 -0
  127. package/src/standards/e2e/one-check-for-many-canvas-clicks.md +17 -0
  128. package/src/standards/e2e/overview.md +14 -0
  129. package/src/standards/e2e/per-feature-overview-test.md +30 -0
  130. package/src/standards/e2e/real-input-for-frame-races.md +25 -0
  131. package/src/standards/e2e/substring-locator-collisions.md +23 -0
  132. package/src/standards/e2e/use-the-e2e-pipeline-for-browser-probing.md +18 -0
  133. package/src/standards/electron/electron-packaging-and-suite.md +22 -0
  134. package/src/standards/electron/electron-shell-shape.md +21 -0
  135. package/src/standards/electron/overview.md +6 -0
  136. package/src/standards/gamedev/2d-visual-design.md +22 -0
  137. package/src/standards/gamedev/budget-exceptions.json +6 -0
  138. package/src/standards/gamedev/captures-and-reels.md +39 -0
  139. package/src/standards/gamedev/devbox.md +21 -0
  140. package/src/standards/gamedev/game-design-laws-experience.md +68 -0
  141. package/src/standards/gamedev/game-design-laws-guidance.md +43 -0
  142. package/src/standards/gamedev/game-design-laws-own-style.md +33 -0
  143. package/src/standards/gamedev/game-design-laws-progress.md +64 -0
  144. package/src/standards/gamedev/game-design-laws-quality.md +30 -0
  145. package/src/standards/gamedev/game-design-laws-story.md +45 -0
  146. package/src/standards/gamedev/game-design-laws-ui.md +52 -0
  147. package/src/standards/gamedev/game-design-laws-world.md +38 -0
  148. package/src/standards/gamedev/game-design-laws.md +114 -0
  149. package/src/standards/gamedev/game-phases-concept.md +29 -0
  150. package/src/standards/gamedev/game-phases-design.md +39 -0
  151. package/src/standards/gamedev/game-phases-development.md +30 -0
  152. package/src/standards/gamedev/game-phases-live.md +19 -0
  153. package/src/standards/gamedev/game-phases.md +52 -0
  154. package/src/standards/gamedev/game-work-workflow.md +47 -0
  155. package/src/standards/gamedev/gamedev-working-cadence.md +52 -0
  156. package/src/standards/gamedev/incremental-pacing.md +22 -0
  157. package/src/standards/gamedev/launch-strategy.md +50 -0
  158. package/src/standards/gamedev/measure-sound-never-guess.md +24 -0
  159. package/src/standards/gamedev/overview.md +29 -0
  160. package/src/standards/gamedev/own-icons.md +19 -0
  161. package/src/standards/gamedev/silent-runs.md +26 -0
  162. package/src/standards/gamedev/sprite-sheet-frames.md +23 -0
  163. package/src/standards/overview.md +43 -0
  164. package/src/standards/records/activity-log.md +33 -0
  165. package/src/standards/records/changelog-per-version.md +43 -0
  166. package/src/standards/records/healing-log.md +23 -0
  167. package/src/standards/records/overview.md +10 -0
  168. package/src/standards/records/playtest-files.md +38 -0
  169. package/src/standards/records/request-log.md +30 -0
  170. package/src/standards/records/user-test-files.md +21 -0
  171. package/src/standards/reporting/change-report.md +43 -0
  172. package/src/standards/reporting/overview.md +6 -0
  173. package/src/standards/reporting/reels-and-video-proof.md +32 -0
  174. package/src/standards/scripts/no-npx-in-scripts.md +20 -0
  175. package/src/standards/scripts/npm-script-naming.md +43 -0
  176. package/src/standards/scripts/overview.md +7 -0
  177. package/src/standards/scripts/thin-wrappers-in-ci-and-hooks.md +25 -0
  178. package/src/standards/security/keep-personal-data-out-of-requests.md +16 -0
  179. package/src/standards/security/keep-secrets-away-from-agents.md +21 -0
  180. package/src/standards/security/never-access-the-keychain.md +16 -0
  181. package/src/standards/security/overview.md +7 -0
  182. package/src/standards/simple-workflow/bugs-template.md +38 -0
  183. package/src/standards/simple-workflow/overview.md +12 -0
  184. package/src/standards/simple-workflow/plan-template.md +50 -0
  185. package/src/standards/simple-workflow/plans-vs-persistent-files.md +31 -0
  186. package/src/standards/simple-workflow/remove-completed-items-from-docs.md +19 -0
  187. package/src/standards/simple-workflow/roadmap-template.md +41 -0
  188. package/src/standards/simple-workflow/technical-debt-template.md +44 -0
  189. package/src/standards/simple-workflow/the-simple-workflow.md +48 -0
  190. package/src/standards/simple-workflow/todo-template.md +31 -0
  191. package/src/standards/tests/a-bugs-test-reproduces-with-real-input.md +18 -0
  192. package/src/standards/tests/bracket-state-changes-with-contrast-assertions.md +37 -0
  193. package/src/standards/tests/gestures-in-tests.md +35 -0
  194. package/src/standards/tests/implementation-agnostic-assertions.md +20 -0
  195. package/src/standards/tests/implementation-agnostic-locators.md +18 -0
  196. package/src/standards/tests/overview.md +13 -0
  197. package/src/standards/tests/realistic-test-data-variance.md +24 -0
  198. package/src/standards/tests/seed-surfaces-every-state-on-page-1.md +17 -0
  199. package/src/standards/tests/test-design.md +47 -0
  200. package/src/standards/tests/test-the-system-behind-a-mock.md +21 -0
  201. package/src/standards/tickets-workflow/agent-roles.md +54 -0
  202. package/src/standards/tickets-workflow/budget-exceptions.json +6 -0
  203. package/src/standards/tickets-workflow/building-a-ticket.md +47 -0
  204. package/src/standards/tickets-workflow/overview.md +15 -0
  205. package/src/standards/tickets-workflow/stabilize-before-adding.md +18 -0
  206. package/src/standards/tickets-workflow/the-builder.md +28 -0
  207. package/src/standards/tickets-workflow/the-conductor.md +44 -0
  208. package/src/standards/tickets-workflow/the-done-part.md +23 -0
  209. package/src/standards/tickets-workflow/ticket-template.md +96 -0
  210. package/src/standards/tickets-workflow/work-item-names.md +30 -0
  211. package/src/standards/tickets-workflow/work-tracking.md +177 -0
  212. package/src/standards/tickets-workflow/work-workflow.md +123 -0
  213. package/src/standards/tickets-workflow/writing-a-ticket.md +50 -0
  214. package/src/standards/tooling/browser-captures-go-to-disk.md +20 -0
  215. package/src/standards/tooling/check-where-a-pane-click-landed.md +19 -0
  216. package/src/standards/tooling/defer-tooling-until-the-cost-shows-up.md +19 -0
  217. package/src/standards/tooling/develop-against-mocks.md +19 -0
  218. package/src/standards/tooling/hygiene-tests-run-on-their-own-runner.md +18 -0
  219. package/src/standards/tooling/lightweight-test-reporting-only.md +16 -0
  220. package/src/standards/tooling/node-versions.md +24 -0
  221. package/src/standards/tooling/overview.md +17 -0
  222. package/src/standards/tooling/parallel-agents.md +45 -0
  223. package/src/standards/tooling/playwright-parallel-runs.md +30 -0
  224. package/src/standards/tooling/playwright-video-recording.md +32 -0
  225. package/src/standards/tooling/read-before-you-truncate.md +19 -0
  226. package/src/standards/tooling/start-playwright-on-a-clean-port.md +22 -0
  227. package/src/standards/tooling/vitepress-wiki.md +38 -0
  228. package/src/standards/typescript/always-add-explicit-types.md +32 -0
  229. package/src/standards/typescript/barrel-imports.md +21 -0
  230. package/src/standards/typescript/no-magic-values.md +52 -0
  231. package/src/standards/typescript/one-artifact-per-file.md +19 -0
  232. package/src/standards/typescript/overview.md +8 -0
  233. package/src/standards/ui/communicate-state.md +21 -0
  234. package/src/standards/ui/never-obscure-information-the-user-needs.md +26 -0
  235. package/src/standards/ui/overview.md +16 -0
  236. package/src/standards/ui/pixel-perfect-design-check.md +22 -0
  237. package/src/standards/ui/ui-component-design.md +34 -0
  238. package/src/standards/ui/ui-components-first.md +25 -0
  239. package/src/standards/ui/ui-layout-via-slot-composition.md +33 -0
  240. package/src/standards/ui/ui-library-is-domain-agnostic.md +20 -0
  241. package/src/standards/ui/ui-refactor-preserve-dont-redesign.md +25 -0
  242. package/src/standards/ui/ui-styleguide.md +30 -0
  243. package/src/standards/ui/ui-variants-by-function-not-by-color.md +23 -0
  244. package/src/standards/ui/validation-errors-fire-on-submit.md +20 -0
  245. package/src/standards/ui/walk-the-users-journey.md +29 -0
  246. package/src/standards/web/always-use-design-tokens-for-colors.md +24 -0
  247. package/src/standards/web/dark-mode-through-tokens.md +19 -0
  248. package/src/standards/web/hidden-attribute-loses-to-display.md +22 -0
  249. package/src/standards/web/overview.md +9 -0
  250. package/src/standards/web/scss-shared-partial-imports.md +16 -0
  251. package/src/standards/web/transitions-only-on-user-toggle.md +19 -0
  252. package/src/standards.md +66 -0
  253. package/src/tools/overview.md +22 -0
  254. package/src/tools/scripts/coentrify-update.py +242 -0
  255. package/src/tools/scripts/unlink-missing-standards.py +138 -0
  256. package/src/tools/specs/changelog-append.md +15 -0
  257. package/src/tools/specs/coentrify-json-check.md +21 -0
  258. package/src/tools/specs/commit-gate.md +32 -0
  259. package/src/tools/specs/healing-append.md +15 -0
  260. package/src/tools/specs/landing.md +29 -0
  261. package/src/tools/specs/refuse-wrap-up-questions.md +22 -0
  262. package/src/tools/specs/reload-core-rules.md +20 -0
@@ -0,0 +1,39 @@
1
+ # Game Phases: Design
2
+
3
+ The second stage of a game ([Game Phases](game-phases.md)). Design is convergent: the game is decided, on paper and in a first playable.
4
+
5
+ ## Lore
6
+
7
+ The skeleton of the lore, the red thread of the world: how the story starts, how it ends and how its parts connect. The main parts are there and fit. Not every dialog and every person: the details come later. Done When: the lore holds that framework and the director has approved it. Its work is Lore tickets. Gate: do the main parts fit together?
8
+
9
+ ## World Building
10
+
11
+ The world itself: its places, how they connect and how big it is. Its work is Lore tickets. Gate: does the world hold what the lore and the gameplay need?
12
+
13
+ ## Gameplay
14
+
15
+ The main gameplay: the core loop and the main mechanics. Its work is Game tickets. Gate: is the main gameplay decided?
16
+
17
+ ## First Playable
18
+
19
+ One of everything, rough, in the real project: one of each kind of content and one of each mechanic, playable together. Game tickets design it, and the Feature tickets they lead to build it. Gate: does the core hold up when played?
20
+
21
+ - A first playable is never a demo. A demo is public, and the first playable stays internal.
22
+ - It shows that the core holds up when played, and that the project builds end to end.
23
+ - Beside it stands a style sample: a few assets at target quality, which set the look and show what a part costs.
24
+ - Nothing else is polished, since polish waits for Alpha.
25
+
26
+ ## Game Design
27
+
28
+ The world translated into the game's levels and features, represented by docs and tickets. Nothing is built. Done When: every part of the world has its levels and features in docs and filed tickets, refined once their phase comes, and the director has approved the design as a whole. Its work is Game tickets. Gate: is the whole game on paper?
29
+
30
+ ## The Order
31
+
32
+ - Lore, World Building and Gameplay lean on each other.
33
+ - The order on this page is the default, and a phase gate may send the game back a phase.
34
+
35
+ ## Related
36
+
37
+ - [Game Phases: Concept](game-phases-concept.md)
38
+ - [Game Phases: Development](game-phases-development.md)
39
+ - [Game Work Workflow](game-work-workflow.md)
@@ -0,0 +1,30 @@
1
+ # Game Phases: Development
2
+
3
+ The third stage of a game ([Game Phases](game-phases.md)). The designed game is built.
4
+
5
+ ## Pre-Alpha
6
+
7
+ Functionally complete: the full game playable from start to finish, perhaps badly paced, buggy and visually imperfect, with every part there. Gate: is every part there?
8
+
9
+ - Every part a level needs is present and reads as what it is: its objects, sounds, voices, music or its silence, and the interface it needs.
10
+ - A rough part is fine. A missing part is not.
11
+ - The right vibe counts.
12
+ - Polish waits: the look and the finish of a working part belong to Alpha, and so does its debt, until the game's whole shape stands. An agent pushes back on polish.
13
+ - What a part does is good from its first version ([Always Polished](game-design-laws-quality.md#always-polished)).
14
+ - Content the director has not decided takes the agent's recommendation under Veto ([Game Work Workflow](game-work-workflow.md#content)), and Alpha polishes it.
15
+ - A ticket names the parts it adds in refinement, by kind, so a story shows what it brings: ten sound effects, say.
16
+ - Before a level lands, an inventory checks every part its tickets and its feature doc name: each is present and reads as what it is.
17
+ - The [Launch Strategy](launch-strategy.md) is picked before Alpha.
18
+
19
+ ## Alpha
20
+
21
+ Completeness: everything implemented properly everywhere and looking good, its passes done. A pass is an epic of checks and fine-tuning across every level, never new mechanics, so it belongs to Alpha. Gate: is every part right?
22
+
23
+ ## Beta
24
+
25
+ External, controlled playtesters. Gate: do strangers get it and keep playing?
26
+
27
+ ## Related
28
+
29
+ - [Game Phases: Design](game-phases-design.md)
30
+ - [Game Phases: Live](game-phases-live.md)
@@ -0,0 +1,19 @@
1
+ # Game Phases: Live
2
+
3
+ The fourth stage of a game ([Game Phases](game-phases.md)). The game is out. Post-Release has no phase gate, since the game lives on.
4
+
5
+ ## Release
6
+
7
+ 1.0 going out, once the director feels good about it, by the [Launch Strategy](launch-strategy.md) the game picked. Gate: is the game out, and does it run for players?
8
+
9
+ ## Aftercare
10
+
11
+ Right after the release, what breaks fixed fast and the first feedback sorted. Gate: is what broke at release fixed, and the first feedback sorted?
12
+
13
+ ## Post-Release
14
+
15
+ The public's feedback, for as long as the game lives. The game is an everlasting project: no version is scoped as the release, and after 1.0 the players' feedback lands on the same lists.
16
+
17
+ ## Related
18
+
19
+ - [Game Phases: Development](game-phases-development.md)
@@ -0,0 +1,52 @@
1
+ # Game Phases
2
+
3
+ A game goes through four stages, and each stage holds phases. A phase ends at a phase gate. The page shape of a phase is in [Work Tracking](../tickets-workflow/work-tracking.md#phases), and the game layer around the phases in [Game Work Workflow](game-work-workflow.md).
4
+
5
+ ## Why
6
+
7
+ The game grows in steady steps, and a mistake is caught while it is still cheap.
8
+
9
+ ## Three Words
10
+
11
+ - A stage groups phases. A studio with several games reads each game's place in one word.
12
+ - A phase is what Work Tracking calls a phase: an epic names it, and every rule about the current phase holds for it.
13
+ - A phase ends at its phase gate ([Project Lifecycle](../behavior/project-lifecycle.md)): a gate finds the right path forward.
14
+ - The industry also calls a phase gate a milestone.
15
+ - A unit of the game's content is a level, never a stage.
16
+
17
+ ## The Stages
18
+
19
+ | Stage | What It Is | Phases |
20
+ |---|---|---|
21
+ | [Concept](game-phases-concept.md) | divergent: everything can change and nothing is wrong | Idea, Gathering, Outline, Prototype |
22
+ | [Design](game-phases-design.md) | convergent: the game is decided, on paper and in a first playable | Lore, World Building, Gameplay, First Playable, Game Design |
23
+ | [Development](game-phases-development.md) | the designed game is built | Pre-Alpha, Alpha, Beta |
24
+ | [Live](game-phases-live.md) | the game is out | Release, Aftercare, Post-Release |
25
+
26
+ ## How To Apply
27
+
28
+ - Concept is loose inside: its phases may overlap and loop back.
29
+ - For every rule about the current phase, Concept counts as one phase.
30
+ - From Design on, a game is in one phase at a time.
31
+ - Every phase holds for every game, even when it is short: Pong's world is a black void, and its story can be a single line.
32
+ - The page of a phase carries the leading question of its phase gate in a `Gate:` line.
33
+ - Post-Release, the last phase of Live, has no phase gate, since the game is an everlasting project. Its page reads `Gate: none - the game is an everlasting project`.
34
+
35
+ ## The Greybox
36
+
37
+ A greybox is the tool of three phases.
38
+
39
+ - Prototype greyboxes the core loop.
40
+ - World Building greyboxes the world of a 3D game, since only moving through it shows whether its size is right.
41
+ - First Playable is a greybox with one of everything.
42
+ - Pre-Alpha replaces the greyboxes with parts that read as what they are.
43
+
44
+ ## Outsiders
45
+
46
+ - A public demo is no phase. Where the [Launch Strategy](launch-strategy.md) has a demo, it is cut from the game during Alpha, when the main gameplay works and one part of the content is polished.
47
+ - A demo is never built early.
48
+ - The phase gates of Pre-Alpha and Alpha allow a playtest by outsiders. Beta stays the phase that is about them.
49
+
50
+ ## Related
51
+
52
+ - [Project Lifecycle](../behavior/project-lifecycle.md)
@@ -0,0 +1,47 @@
1
+ # Game Work Workflow
2
+
3
+ The work workflow is generic ([Work Workflow](../tickets-workflow/work-workflow.md)). This standard holds what its terms mean when the product is a game.
4
+
5
+ ## Why
6
+
7
+ What is specific to a game stands in one place, and the Work Workflow stays generic.
8
+
9
+ ## Terms
10
+
11
+ - The user is the player. A ticket addresses the player as you: "when you enter the hall, it shows no title".
12
+ - The seeded scenarios a bug's trace tries first are the devbox's ([Devbox](devbox.md)).
13
+ - The extras that make a game special land in their epic and phase like any other work. They are not essential, but a game without them falls flat, so they are never only for after the release.
14
+
15
+ ## Intake
16
+
17
+ - Playtest feedback gets its playtest file first, kept by the conductor, then its units go through intake ([Playtest Files](../records/playtest-files.md)).
18
+ - While a version stabilizes, anything new waits for its epic ([Stabilize Before Adding](../tickets-workflow/stabilize-before-adding.md)).
19
+
20
+ ## Content
21
+
22
+ - Content the director has not decided, dialog lines, names, numbers, quest wording or a song's pick, takes the agent's recommendation as long as its core message is clear, and stands under Veto, in every phase. It never waits on refinement.
23
+ - A choice under Veto decides how a part looks, sounds or counts, never that a part is left out. One that drops a part is sent back before it lands.
24
+
25
+ ## Design Ticket Types
26
+
27
+ A game's work in the Design stage is tracked in two types of its own, on top of [Work Tracking](../tickets-workflow/work-tracking.md#types). Both carry the sections of a Debt ticket ([Ticket Template](../tickets-workflow/ticket-template.md#sections-per-type)).
28
+
29
+ - Lore and Game tickets end in a decided doc, so each gets the director's verdict, like a Docs ticket.
30
+ - Lore, in `lore`, prefix `LORE`: the design of the world and its story. Its outcome is a decided lore doc. Lore tickets carry the Lore and World Building phases.
31
+ - Game, in `game`, prefix `GAME`: the design of the game. Its outcome is a decided feature doc and the feature tickets it leads to, refined once their phase comes. Game tickets carry the Gameplay, First Playable and Game Design phases.
32
+ - The Concept stage has no tickets, apart from its prototype's and an idea that Gathering files for later.
33
+ - A Game or Lore ticket names, in its Current Situation, each conflict between the docs and the intended design that it resolves, one per bullet.
34
+
35
+ ## Phases
36
+
37
+ A game's phases sit in four stages. Each phase in full is in [Game Phases](game-phases.md).
38
+
39
+ - Concept - Idea, Gathering, Outline and Prototype: everything can change.
40
+ - Design - Lore, World Building, Gameplay, First Playable and Game Design: the game is decided.
41
+ - Development - Pre-Alpha, Alpha and Beta: the designed game is built.
42
+ - Live - Release, Aftercare and Post-Release: the game is out.
43
+
44
+ ## Related
45
+
46
+ - [Gamedev Working Cadence](gamedev-working-cadence.md)
47
+ - [Changelog Per Version](../records/changelog-per-version.md)
@@ -0,0 +1,52 @@
1
+ # Gamedev Working Cadence
2
+
3
+ A game day runs in one loop: the director plays and writes, the conductor logs, plans and lands item by item with proof, closes the version, and the director plays the next one. All work runs through the [Work Workflow](../tickets-workflow/work-workflow.md). This file adds the rhythm of the day around it. Every step leaves a file behind, so any session can pick the day up.
4
+
5
+ ## Why
6
+
7
+ Every playtest plays a named version, and knows what changed in it.
8
+
9
+ ## Session Start
10
+
11
+ - The wiki runs and its URL is handed over ([VitePress Wiki](../tooling/vitepress-wiki.md)), and the director's inboxes are pointed to in the order of [Work Workflow](../tickets-workflow/work-workflow.md), the accept list first.
12
+
13
+ ## Intake
14
+
15
+ - A big dump of ideas and feedback is logged and processed, then the report offers a few focus areas for the next iteration and the director picks one. The bugs are scheduled the way intake schedules any work ([Work Workflow](../tickets-workflow/work-workflow.md#intake)). The rest is grouped into epics on the roadmap, so nothing is lost and the work keeps its focus.
16
+ - Feedback on an open version is a cutoff, never more scope: close the version as it stands and plan what is open plus the new feedback for the next one. One cycle of playtest, review and changelog per version.
17
+ - Dev Tiers recommends the order, and the director decides it ([Dev Tiers](../behavior/dev-tiers.md)).
18
+ - Content the agent names (names, numbers, hints) follows [Game Work Workflow](game-work-workflow.md#content) and [Incremental Pacing](incremental-pacing.md).
19
+
20
+ ## Per Item
21
+
22
+ - Every item lands with its proof, since an item without proof has to be checked again by hand.
23
+ - Tests run as [Building A Ticket](../tickets-workflow/building-a-ticket.md#building) says, and the full suites once at the version's close.
24
+
25
+ ## Version Close
26
+
27
+ - What a version is follows the game's phase ([Game Phases](game-phases.md)). A version closes on the director's go, and the day may go on after it. Once builds go out, a version is a build, and a playtest names the version it played.
28
+ - The version closes with the suites green and the version tagged.
29
+ - Nothing lands between the full suites and the tag without its touched suite run again.
30
+
31
+ ## In A Browser
32
+
33
+ - Green at the close includes the whole pre-push hook (`npm run hooks:pre-push`, the project's full pre-push chain) by its exit code, run before the tag and never left for the director's push.
34
+ - The full browser suite runs as two halves when it outlasts the background cap ([Playwright Parallel Runs](../tooling/playwright-parallel-runs.md)).
35
+
36
+ ## Wind-Down
37
+
38
+ - Once the director calls a wind-down, a soft freeze, no new agent is started to build, not even for a chore already approved. The work in progress finishes and the close runs to its end, so the work halts without a forced stop.
39
+ - Everything the director says during it is logged and filed as usual, and briefed in the next session, however small or close to an item in hand it looks.
40
+
41
+ ## Day Close
42
+
43
+ - The day closes with the activity log ([Activity Log](../records/activity-log.md)).
44
+ - The report in chat references the changelog on the wiki instead of summarizing. It names an addition of the agent's own made outside a ticket for a veto ([Flag Every Addition Of Your Own](../behavior/flag-every-addition-of-your-own.md)), since a ticket's stand in its Veto.
45
+
46
+ ## Related
47
+
48
+ - [The Conductor](../tickets-workflow/the-conductor.md)
49
+ - [Agent Roles](../tickets-workflow/agent-roles.md)
50
+ - [Game Work Workflow](game-work-workflow.md)
51
+ - [Request Log](../records/request-log.md)
52
+ - [Playtest Files](../records/playtest-files.md)
@@ -0,0 +1,22 @@
1
+ # Incremental Pacing
2
+
3
+ Pacing is a game mechanic of its own. Every level gets a pacing doc under a pacing folder in the docs that mirrors the level's configuration: the currency, the goal and its size, the unlock gates, the tiers of producers with cost, output and what opens and reveals them, the upgrade lines with cost and effect, the hints per progress, the odds of encounters. The doc and the configuration change together.
4
+
5
+ ## Why
6
+
7
+ The director tunes a level's pacing from the doc, without reading code.
8
+
9
+ ## How To Apply
10
+
11
+ - A table per level makes the curve visible at a glance, the tiers comparable and the gaps findable.
12
+ - Names of producers, upgrades, tiers, hints and units are content, filled in as [Game Work Workflow](game-work-workflow.md#content) says and recorded in the pacing doc. Level names never travel between projects.
13
+ - A new level's pacing goes into the doc together with its build, the agent's numbers under the ticket's Veto. The build mirrors the doc.
14
+ - An unlock gate is written as a rule the player can feel, such as the next producer after the second upgrade, with the reason next to it.
15
+ - A getting-used period sits between a new mechanic and the next: the new one is used by hand for a while, such as a few dozen clicks, before anything runs on its own.
16
+ - Names within one family never contain each other.
17
+
18
+ ## Related
19
+
20
+ - [Substring Locator Collisions](../e2e/substring-locator-collisions.md)
21
+ - [Flag Every Addition Of Your Own](../behavior/flag-every-addition-of-your-own.md)
22
+ - [Feature Template](../docs/feature-template.md)
@@ -0,0 +1,50 @@
1
+ # Launch Strategy
2
+
3
+ A game picks how it goes out. The default is the quiet launch: the full game on day one, as a surprise.
4
+
5
+ ## Why
6
+
7
+ A game meets its players at its best, the first time they hear of it.
8
+
9
+ ## The Quiet Launch
10
+
11
+ - The full game is released on day one. No wishlist campaign comes before it, and no demo on the store page.
12
+ - The store page is set up before the release and stays unpublished as long as the store allows, such as Steam's two weeks of Coming Soon, for internal review and testing. Its visits are no goal.
13
+ - The one thing that travels is a video of the game being played: someone enjoying the main loop, or an interesting moment.
14
+ - The video goes out once the game can be bought. Its viewer reads the description, goes to the game and buys it.
15
+ - That video is no trailer: no cutscene, no voice-over and no targeted ad.
16
+ - No award campaigns, and no asking for attention.
17
+ - A vibe video or a demo for a collaborator is no marketing. A hired composer then knows what to base the music on.
18
+ - After the release, fixes and updates follow what the players do.
19
+
20
+ ## The Other Choices
21
+
22
+ - A wishlist campaign: the store page goes up months early, and the release date is announced ahead.
23
+ - A public demo: cut from the game during Alpha, and shown at a festival before the release.
24
+ - A closed beta, in place of a public demo: the whole game in Beta, gated by who plays it.
25
+ - Building in public: devlogs and a community from early on.
26
+ - A publisher: the marketing is in someone else's hands, for a share of the revenue.
27
+ - Early access: the game is sold before it is whole, in public while it is in Beta. What is sold is polished, and the rest is gated or left out, so it is a demo that is paid for, gated by content.
28
+
29
+ ## What To Weigh
30
+
31
+ - A good game sells itself.
32
+ - The quiet launch starts slower. A store shows a new game to more people when its wishlists and early sales are high.
33
+ - It leans on the game clipping well ([Fun First](game-design-laws-experience.md#fun-first)).
34
+ - It is for a small studio. A big studio launches another way.
35
+ - It carries [Respect](game-design-laws-experience.md#respect) to the time before the purchase.
36
+ - Issues show with a small crowd first, and are fixed before many players meet them.
37
+ - A wishlist spends the first moment a player hears of the game, and the second look has to convince more.
38
+ - A game wishlisted on its potential is checked at the release, and removed when the potential is not there. It takes a big game to come back from that.
39
+ - Every other choice spends attention before the game is done: the director's and the players'.
40
+ - A promise made early has to be kept. A date that slips, or a game that falls short of its trailer, costs trust.
41
+
42
+ ## How To Apply
43
+
44
+ - The strategy is picked before Alpha, since a wishlist campaign or a festival demo starts months ahead.
45
+ - The pick stands on the page of the Release phase. A hygiene check fails that page without one.
46
+
47
+ ## Related
48
+
49
+ - [Game Phases: Live](game-phases-live.md)
50
+ - [Game Design Laws: Progress](game-design-laws-progress.md)
@@ -0,0 +1,24 @@
1
+ # Measure Sound, Never Guess
2
+
3
+ The level of a new sound is measured, never guessed.
4
+
5
+ ## Why
6
+
7
+ Every sound sits at the right level beside the others.
8
+
9
+ ## How To Apply
10
+
11
+ - Read the loudness against a sound the director already knows: another scene's bed, a click.
12
+ - A level worked out on paper misleads, since filtered soft noise has little energy up high.
13
+ - A reading counts only when the mix was silent before it: a long recording bleeds into the next reading.
14
+ - Silence the scene's own random sounds and beds first, and wait for silence between readings.
15
+
16
+ ## In A Browser
17
+
18
+ - A throwaway probe spec taps an analyzer onto everything reaching the speakers.
19
+ - The reel's track is checked per half second.
20
+
21
+ ## Related
22
+
23
+ - [Captures And Reels](captures-and-reels.md)
24
+ - [Game Design Laws: Experience](game-design-laws-experience.md)
@@ -0,0 +1,29 @@
1
+ # Overview
2
+
3
+ The Gamedev standards: game development.
4
+
5
+ - [2D Visual Design](2d-visual-design.md) - drawn scenes keep one perspective: verticals vertical, edges to the vanishing point, repeats converging, patterns foreshortened. Checked with lines drawn over a capture
6
+ - [Captures And Reels](captures-and-reels.md) - proof from scripted captures per item, never by hand, reels on demand, videos untracked in git
7
+ - [Devbox](devbox.md) - a one-key devbox on every scene, on the shared seeded scenarios
8
+ - [Game Design Laws](game-design-laws.md) - the generic game design laws as an index. A game's laws doc adopts, leaves out or overrides them by name
9
+ - [Game Design Laws: Experience](game-design-laws-experience.md) - what the player lives moment to moment
10
+ - [Game Design Laws: Guidance](game-design-laws-guidance.md) - what the game hints and teaches
11
+ - [Game Design Laws: Own Style](game-design-laws-own-style.md) - what makes the game its own
12
+ - [Game Design Laws: Progress](game-design-laws-progress.md) - the shape of the whole game
13
+ - [Game Design Laws: Quality](game-design-laws-quality.md) - the bar everything in the game meets
14
+ - [Game Design Laws: Story](game-design-laws-story.md) - what the game says
15
+ - [Game Design Laws: UI](game-design-laws-ui.md) - the screen and the controls
16
+ - [Game Design Laws: World](game-design-laws-world.md) - the world the player moves through
17
+ - [Game Phases](game-phases.md) - a game's phases in four stages, each phase but Post-Release ending at a phase gate, with the greybox, demos and outside playtests
18
+ - [Game Phases: Concept](game-phases-concept.md) - the divergent stage: Idea, Gathering, Outline and Prototype, loose inside and without tickets
19
+ - [Game Phases: Design](game-phases-design.md) - the convergent stage: Lore, World Building, Gameplay, First Playable and Game Design. A first playable is never a demo
20
+ - [Game Phases: Development](game-phases-development.md) - Pre-Alpha is functionally complete: every part present, rough allowed, undecided content on the agent's recommendation. Alpha polishes, Beta is for outsiders
21
+ - [Game Phases: Live](game-phases-live.md) - Release, Aftercare and Post-Release. An everlasting project, so Post-Release has no phase gate
22
+ - [Game Work Workflow](game-work-workflow.md) - the game layer on the work workflow: the user is the player, addressed as you, the game's own words, playtests feed intake, Lore and Game ticket types, the four stages in a line each
23
+ - [Gamedev Working Cadence](gamedev-working-cadence.md) - the game day loop, feedback on an open version is a cutoff, full pre-push hook before the tag, nothing new after a wind-down
24
+ - [Incremental Pacing](incremental-pacing.md) - a pacing doc per level mirroring the configuration
25
+ - [Launch Strategy](launch-strategy.md) - how a game goes out: the quiet launch by default, the other choices, and what to weigh
26
+ - [Measure Sound, Never Guess](measure-sound-never-guess.md) - the level of a new sound is measured against a known sound, never guessed
27
+ - [Own Icons](own-icons.md) - own icon sprite, named by concept, with a wiki index page
28
+ - [Silent Runs](silent-runs.md) - an agent's runs of a game make no sound: muted Playwright captures for a walk, never the browser pane on a game with sound
29
+ - [Sprite Sheet Frames](sprite-sheet-frames.md) - read frame size and row order from the sheet's pixels
@@ -0,0 +1,19 @@
1
+ # Own Icons
2
+
3
+ A game draws its own icons: one SVG sprite with a symbol per icon, drawn in the game's stroke style, named by concept, and listed on an index page in the wiki that renders every symbol with its name.
4
+
5
+ ## Why
6
+
7
+ The game's look is its own, down to the icons.
8
+
9
+ ## How To Apply
10
+
11
+ - Add the symbol to the sprite and the name to the icon constant in the same change. The index page follows the sprite, never a hand list.
12
+ - The index page makes the set reviewable in one look, so a misdrawn icon is caught on the wiki before a playtest.
13
+ - Draw the recognizable silhouette first: a pickaxe has two points, a hammer a head and a short handle.
14
+
15
+ ## Related
16
+
17
+ - [Game Design Laws: Own Style](game-design-laws-own-style.md)
18
+ - [Name By Concept, Not Copy](../code/name-by-concept-not-copy.md)
19
+ - [VitePress Wiki](../tooling/vitepress-wiki.md)
@@ -0,0 +1,26 @@
1
+ # Silent Runs
2
+
3
+ Every run the agent starts of a product with sound, a game above all, is silent.
4
+
5
+ ## Why
6
+
7
+ The director's focus stays unbroken.
8
+
9
+ ## How To Apply
10
+
11
+ - The director works beside the agent, and sound from a preview an agent opened plays on until someone closes it in that agent's session.
12
+ - A preview already open on a game is stopped at once.
13
+ - The agent never starts a game session for the director to look at: the director runs the game, or checks the acceptance captures and videos.
14
+
15
+ ## In A Browser
16
+
17
+ - A walk through the game, a check or a capture goes through the muted Playwright configs.
18
+ - The browser pane plays the game's sound out loud, and is never opened on a game that has sound.
19
+ - Walk a player journey through a capture spec, its screenshots read step by step, with the capture spec's output folder pointed at the scratchpad.
20
+ - Every Chromium launch for a game takes `--mute-audio`, and another engine its own mute setting, such as Firefox's `media.volume_scale` at 0. A new Playwright config carries it from the start.
21
+
22
+ ## Related
23
+
24
+ - [Own Ports, Own Processes](../behavior/own-ports-own-processes.md)
25
+ - [Use The E2E Pipeline For Browser Probing](../e2e/use-the-e2e-pipeline-for-browser-probing.md)
26
+ - [Walk The User's Journey](../ui/walk-the-users-journey.md)
@@ -0,0 +1,23 @@
1
+ # Sprite Sheet Frames
2
+
3
+ Before a sheet is sliced into frames, the frame size and the row order are read from the pixels, never assumed from the tile size or a preview at a glance: print the alpha mask of the first cell, or render the sheet with a labeled grid, and check where a character's feet land and which way each row faces.
4
+
5
+ ## Why
6
+
7
+ Every frame shows the whole character, facing the right way.
8
+
9
+ ## How To Apply
10
+
11
+ - Render the sheet with a grid-labeling script (columns and rows numbered) at a zoom where a single frame fills the view, and print the alpha mask of one cell to see the frame's true height.
12
+ - Confirm each direction row by the face and the feet, never by the order such sheets usually have.
13
+ - Put the frame size and the row map in one constant next to the loader, and check a capture of a walking character before the version closes.
14
+
15
+ ## Examples
16
+
17
+ - A 16 by 32 character sheet sliced at the 16 pixel tile size shows every character as a head only.
18
+ - Side rows read backwards from a small preview make a character walk the wrong way.
19
+
20
+ ## Related
21
+
22
+ - [Review Every Capture Before Reporting](../behavior/review-every-capture-before-reporting.md)
23
+ - [Browser Captures Go To Disk](../tooling/browser-captures-go-to-disk.md)
@@ -0,0 +1,43 @@
1
+ # Overview
2
+
3
+ The rules, conventions and templates a project adopts.
4
+
5
+ ## Core Rules
6
+
7
+ The rules every task follows, in every session. An agent reads them before anything else and again after a compaction, and holds to each one as it would to a check.
8
+
9
+ - [Always Make No Mistakes](behavior/always-make-no-mistakes.md)
10
+ - [Always Verify Before Reporting Done](behavior/always-verify-before-reporting-done.md)
11
+ - [Always Work From A Plan](behavior/always-work-from-a-plan.md)
12
+ - [General Working Rules](behavior/general-working-rules.md)
13
+ - [Normal Dashes](behavior/normal-dashes.md)
14
+ - [Prose Style](behavior/prose-style.md)
15
+ - [Review Changes Before Reporting Done](behavior/review-changes-before-reporting-done.md)
16
+ - [Understand The Need](behavior/understand-the-need.md)
17
+ - [Use US English Everywhere](behavior/use-us-english-everywhere.md)
18
+
19
+ ## Modules
20
+
21
+ Every module has an overview of its own standards.
22
+
23
+ - [AI](ai/overview.md) - building with models
24
+ - [Angular](angular/overview.md) - rules for Angular
25
+ - [Architecture](architecture/overview.md) - patterns that cut across a codebase
26
+ - [Behavior](behavior/overview.md) - how an agent works and what an agent checks
27
+ - [Code](code/overview.md) - rules that hold in any language
28
+ - [Commits](commits/overview.md) - how work is committed
29
+ - [Docs](docs/overview.md) - documentation rules and templates
30
+ - [E2E](e2e/overview.md) - end-to-end tests
31
+ - [Electron](electron/overview.md) - the Electron shell
32
+ - [Gamedev](gamedev/overview.md) - game development
33
+ - [Records](records/overview.md) - the dated trails a project keeps
34
+ - [Reporting](reporting/overview.md) - reports and proof
35
+ - [Scripts](scripts/overview.md) - npm scripts
36
+ - [Security](security/overview.md) - hard boundaries
37
+ - [Simple Workflow](simple-workflow/overview.md) - the work tracked in flat lists
38
+ - [Tests](tests/overview.md) - test design
39
+ - [Tickets Workflow](tickets-workflow/overview.md) - the work tracked in tickets
40
+ - [Tooling](tooling/overview.md) - development tools
41
+ - [TypeScript](typescript/overview.md) - rules for TypeScript
42
+ - [UI](ui/overview.md) - components and styling
43
+ - [Web](web/overview.md) - rules for HTML and CSS
@@ -0,0 +1,33 @@
1
+ # Activity Log
2
+
3
+ Completed work goes to `docs/records/activity/<date>.md`, one file per day, H1 the date with the DEV day (`2026-09-14 - DEV day 6`). The days before the agent are reconstructed from the commit history. Plans and lists still drop finished items. The activity log is where a day's progress stays readable.
4
+
5
+ ## Why
6
+
7
+ The director sees the progress of a project at a glance, and a new session starts from the last one.
8
+
9
+ ## The Page
10
+
11
+ - The Standup: what the director would tell a colleague who is not close to the work.
12
+ - Standing: one line with the suites' counts and the open bugs and debt.
13
+ - Next: one line with the plan's head.
14
+
15
+ ## The Standup
16
+
17
+ - Three to five bullets, the day's biggest outcomes first, in plain words.
18
+ - One more bullet with roughly how many hours it took. The hours run from the day's first log entry, or its first commit without a log, to its last commit.
19
+ - A summary, never a list of every change: the changelog and git hold that.
20
+ - Terse: "worked on the sign-in", never "we worked mainly on".
21
+ - No version numbers, links, times, agent or process talk.
22
+
23
+ ## How To Apply
24
+
25
+ - Write the day's file when the first batch closes, in the commit after the tag, and extend it with every batch after: the standup rewritten to cover the whole day. A batch's close is never called the day's close while the day goes on.
26
+ - The day closes on the director's word: the batch closes, the file is extended once more, and the report says so.
27
+ - The day's close adds its row to the activity folder's Hours page (day, DEV day, from, to, hours) and updates that week's and month's totals.
28
+
29
+ ## Related
30
+
31
+ - [Request Log](request-log.md)
32
+ - [Remove Completed Items From Docs](../simple-workflow/remove-completed-items-from-docs.md)
33
+ - [Gamedev Working Cadence](../gamedev/gamedev-working-cadence.md)
@@ -0,0 +1,43 @@
1
+ # Changelog Per Version
2
+
3
+ Every version gets its own page in `docs/records/changelog/<version>.md`, listed newest on top in the wiki. Its list is a view the wiki generates from the tickets that landed in the version, so no builder appends to it and no conductor keeps it.
4
+
5
+ ## Why
6
+
7
+ A changelog says what a version holds: for testing it, for sharing it and for migrating to it.
8
+
9
+ ## The Page
10
+
11
+ - The H1 carries the DEV day as a suffix: `# 0.0.33 - DEV day 13`, so the wiki's menu shows it. A page in progress carries the day it is being worked on, retitled the morning a new day starts on it, and the tag day at the close.
12
+ - The header, kept by hand, names the tag date with its DEV day and, for an app that ships packages, whether this build was packaged.
13
+ - Under it, the generated list: every ticket that landed in the version, workspace tickets included, in landing order, each line its id and its link, `- FEAT-214: [Upload Retries After A Dropped Connection](/tickets/FEAT-214)`.
14
+ - A ticket belongs to the version whose tag first holds its landing commit. One landed after the last tag lists under the version in progress.
15
+ - An in-game "What's New", where a game has one, shows the player-facing tickets alone, never the workspace's or a secret.
16
+
17
+ ## The DEV Day
18
+
19
+ - The DEV day counts the days with a commit, read from git, since the first day an agent worked on the project. The day turns at 04:00 local time, so a session past midnight stays on the day it started.
20
+ - Earlier days count as proof of concept (POC) days.
21
+ - Every dated record carries it: the log, the activity, the playtests, the user tests and the changelog.
22
+
23
+ ## Versions
24
+
25
+ - A version closes on the director's word, and the work merged since the last tag is its batch: the closing commit is tagged `v<version>`.
26
+ - The bump and the next page wait for the next version's first landing, which bumps the app and creates the page with its header.
27
+ - An unused version gets deleted.
28
+
29
+ ## Without Tickets
30
+
31
+ A project without tickets keeps the list through its append script.
32
+
33
+ - The page holds one `## Changed` list.
34
+ - Every landing appends one line at the bottom, ending in its time: ``- <what changed> `HH:MM` ``.
35
+ - No line is written free hand.
36
+ - The script refuses a second bullet, a semicolon that chains two items, and a line without its time.
37
+
38
+ ## Related
39
+
40
+ - [Work Tracking](../tickets-workflow/work-tracking.md)
41
+ - [Captures And Reels](../gamedev/captures-and-reels.md)
42
+ - [Playtest Files](playtest-files.md)
43
+ - [Change Report](../reporting/change-report.md)
@@ -0,0 +1,23 @@
1
+ # Healing Log
2
+
3
+ Every change that automatic healing makes to the harness gets one entry in `docs/records/healing-log.md`. An entry stays until the director has ruled on it.
4
+
5
+ ## Why
6
+
7
+ The harness heals on its own, and the director keeps the last word on every change.
8
+
9
+ ## How To Apply
10
+
11
+ - An entry is one line: the date, what went wrong, what changed, and the commit. The change is committed first, and its entry follows in a commit of its own, naming the change's commit. `- 2026-11-19 - a commit followed a git add in one command - Verify Staging Before Committing gets a check in the commit gate - 85f1950`
12
+ - The entry goes in through the project's append script, so every entry has the same shape and the log can be counted.
13
+ - One entry holds one change. A mistake that changed a rule and a check gets two entries.
14
+ - The director rules on an entry: keep it, change it, or revert it.
15
+ - A ruled entry leaves the log, and git keeps it ([Remove Completed Items From Docs](../simple-workflow/remove-completed-items-from-docs.md)).
16
+ - A change that holds beyond the project is filed with coentrify as [File A Change With Coentrify](../behavior/file-a-change-with-coentrify.md) says, without waiting for the ruling when `filing` is automatic.
17
+ - The log is read as a whole now and then. A trigger that comes back points at a rule that is still too weak.
18
+ - Healing on `review` files the change in the workflow, and writes no entry.
19
+
20
+ ## Related
21
+
22
+ - [Always Make No Mistakes](../behavior/always-make-no-mistakes.md)
23
+ - [Changelog Per Version](changelog-per-version.md)
@@ -0,0 +1,10 @@
1
+ # Overview
2
+
3
+ The Records standards: the dated trails a project keeps.
4
+
5
+ - [Activity Log](activity-log.md) - a daily activity page: a short standup, what stands and what is next
6
+ - [Changelog Per Version](changelog-per-version.md) - a page per version, generated: the tickets that landed in it, each its id and link, in landing order. Nothing written by hand but the header. Without tickets, a line per landing through the append script. The DEV day counts the days with a commit
7
+ - [Healing Log](healing-log.md) - every change automatic healing made, one line each, until the director rules on it
8
+ - [Playtest Files](playtest-files.md) - a numbered file per playtest. Feedback units become work in the project's workflow
9
+ - [Request Log](request-log.md) - log everything the director says before the work is filed, shell-written time headings
10
+ - [User Test Files](user-test-files.md) - a numbered file per session with real users, in the shape of a playtest file