smd-engine 0.7.7__tar.gz → 0.7.9__tar.gz

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 (293) hide show
  1. {smd_engine-0.7.7 → smd_engine-0.7.9}/.github/workflows/ci.yml +38 -1
  2. {smd_engine-0.7.7 → smd_engine-0.7.9}/CHANGELOG.md +50 -38
  3. {smd_engine-0.7.7 → smd_engine-0.7.9}/PKG-INFO +3 -3
  4. {smd_engine-0.7.7 → smd_engine-0.7.9}/README.md +2 -2
  5. {smd_engine-0.7.7 → smd_engine-0.7.9}/README_ru.md +2 -2
  6. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/example/bakeries-c2.board.yaml +1 -1
  7. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/example_ru/pekarni-c2.board.yaml +1 -1
  8. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/spectra_coffee/README.md +1 -1
  9. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/spectra_coffee/bank.story.yaml +1 -1
  10. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/spectra_coffee/buyer.story.yaml +1 -1
  11. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/spectra_coffee/owner.story.yaml +1 -1
  12. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/spectra_coffee/spectra-coffee-c1.board.yaml +3 -2
  13. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/spectra_coffee/successor-premortem.story.yaml +1 -1
  14. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/spectra_coffee/taxonomies.yaml +2 -2
  15. {smd_engine-0.7.7 → smd_engine-0.7.9}/docs/changelog-0.2-0.5.md +20 -20
  16. {smd_engine-0.7.7 → smd_engine-0.7.9}/docs/checks.md +10 -10
  17. {smd_engine-0.7.7 → smd_engine-0.7.9}/docs/commands.md +1 -1
  18. {smd_engine-0.7.7 → smd_engine-0.7.9}/docs/data-model.md +11 -11
  19. {smd_engine-0.7.7 → smd_engine-0.7.9}/docs/deal-mode.md +2 -2
  20. {smd_engine-0.7.7 → smd_engine-0.7.9}/docs/hypotheses.md +2 -2
  21. {smd_engine-0.7.7 → smd_engine-0.7.9}/docs/method/README.md +1 -1
  22. {smd_engine-0.7.7 → smd_engine-0.7.9}/docs/method/formal-stance.md +2 -2
  23. {smd_engine-0.7.7 → smd_engine-0.7.9}/docs/method/robustness-rules.md +1 -1
  24. {smd_engine-0.7.7 → smd_engine-0.7.9}/docs/method/roles-and-actors.md +1 -1
  25. {smd_engine-0.7.7 → smd_engine-0.7.9}/docs/method/sources.md +1 -1
  26. {smd_engine-0.7.7 → smd_engine-0.7.9}/docs/method/structural-moves.md +1 -1
  27. {smd_engine-0.7.7 → smd_engine-0.7.9}/docs/profiles.md +7 -7
  28. {smd_engine-0.7.7 → smd_engine-0.7.9}/docs/red-lines.md +1 -1
  29. {smd_engine-0.7.7 → smd_engine-0.7.9}/docs/stages.md +33 -33
  30. {smd_engine-0.7.7 → smd_engine-0.7.9}/docs/stories.md +2 -2
  31. {smd_engine-0.7.7 → smd_engine-0.7.9}/docs/task-packs.md +3 -3
  32. {smd_engine-0.7.7 → smd_engine-0.7.9}/lenses/beer-viable-system.md +1 -1
  33. {smd_engine-0.7.7 → smd_engine-0.7.9}/lenses/khaprov-levels.md +3 -3
  34. {smd_engine-0.7.7 → smd_engine-0.7.9}/lenses/three-positions.md +1 -1
  35. {smd_engine-0.7.7 → smd_engine-0.7.9}/procedures/field-result.md +3 -3
  36. {smd_engine-0.7.7 → smd_engine-0.7.9}/procedures/functional-plan.md +1 -1
  37. {smd_engine-0.7.7 → smd_engine-0.7.9}/procedures/qualification-pass.md +1 -1
  38. {smd_engine-0.7.7 → smd_engine-0.7.9}/procedures/stakeholder-ontology.md +2 -2
  39. {smd_engine-0.7.7 → smd_engine-0.7.9}/procedures/story.md +1 -1
  40. {smd_engine-0.7.7 → smd_engine-0.7.9}/procedures/task-diff.md +1 -1
  41. {smd_engine-0.7.7 → smd_engine-0.7.9}/procedures/task-pack.md +1 -1
  42. {smd_engine-0.7.7 → smd_engine-0.7.9}/procedures/visionary-tract.md +1 -1
  43. {smd_engine-0.7.7 → smd_engine-0.7.9}/profiles/classic-two-boards.yaml +2 -2
  44. {smd_engine-0.7.7 → smd_engine-0.7.9}/profiles/management-four-boards.yaml +10 -10
  45. {smd_engine-0.7.7 → smd_engine-0.7.9}/profiles/program-three-boards.yaml +2 -2
  46. {smd_engine-0.7.7 → smd_engine-0.7.9}/pyproject.toml +1 -1
  47. {smd_engine-0.7.7 → smd_engine-0.7.9}/roles/methodologist.md +1 -1
  48. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/apply.py +16 -1
  49. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/pack.py +2 -2
  50. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/profile_model.py +3 -3
  51. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/profile_parse.py +1 -1
  52. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/redline.py +3 -3
  53. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/render/graph.py +2 -2
  54. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/render/index.py +2 -2
  55. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/render/light.py +3 -1
  56. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/render/markdown.py +5 -3
  57. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/render/svg.py +7 -5
  58. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/render/text.py +16 -3
  59. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/schemas/board_set.schema.json +10 -9
  60. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/status.py +1 -1
  61. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/story/__init__.py +1 -1
  62. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/validate/ai.py +1 -1
  63. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/validate/context.py +2 -2
  64. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/validate/graph.py +1 -1
  65. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/validate/hints.py +1 -1
  66. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/validate/hypotheses.py +1 -1
  67. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/validate/management.py +12 -13
  68. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/validate/redlines.py +4 -4
  69. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/validate/structure.py +8 -7
  70. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/validate/tract.py +2 -2
  71. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/verdict.py +1 -1
  72. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_action_program.py +2 -2
  73. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_ai_roles.py +1 -1
  74. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_apply.py +31 -0
  75. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_beer_layer.py +3 -3
  76. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_hypothesis_standard.py +1 -1
  77. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_management.py +1 -1
  78. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_procedure_checks.py +1 -1
  79. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_profile.py +2 -2
  80. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_record_boards.py +6 -6
  81. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_red_lines.py +1 -1
  82. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_render_fields.py +1 -1
  83. smd_engine-0.7.9/tests/test_render_header.py +107 -0
  84. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_render_ru_pages.py +1 -1
  85. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_render_ru_values.py +8 -7
  86. {smd_engine-0.7.7 → smd_engine-0.7.9}/uv.lock +1 -1
  87. {smd_engine-0.7.7 → smd_engine-0.7.9}/.claude/agents/smd-game-technician.md +0 -0
  88. {smd_engine-0.7.7 → smd_engine-0.7.9}/.claude/agents/smd-methodologist.md +0 -0
  89. {smd_engine-0.7.7 → smd_engine-0.7.9}/.claude/agents/smd-visionary.md +0 -0
  90. {smd_engine-0.7.7 → smd_engine-0.7.9}/.claude/commands/procedure.md +0 -0
  91. {smd_engine-0.7.7 → smd_engine-0.7.9}/.flake8 +0 -0
  92. {smd_engine-0.7.7 → smd_engine-0.7.9}/.github/workflows/release.yml +0 -0
  93. {smd_engine-0.7.7 → smd_engine-0.7.9}/.gitignore +0 -0
  94. {smd_engine-0.7.7 → smd_engine-0.7.9}/.python-version +0 -0
  95. {smd_engine-0.7.7 → smd_engine-0.7.9}/CONTRIBUTING.md +0 -0
  96. {smd_engine-0.7.7 → smd_engine-0.7.9}/LICENSE +0 -0
  97. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/example/bakeries-c1.board.yaml +0 -0
  98. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/example/deal/answers_boris.yaml +0 -0
  99. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/example/deal/answers_gleb.yaml +0 -0
  100. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/example/deal/answers_vera.yaml +0 -0
  101. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/example/deal/pack.yaml +0 -0
  102. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/example/golden/README.md +0 -0
  103. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/example/golden/bakeries-c2-expected.board.yaml +0 -0
  104. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/example/golden/s3_transcript.txt +0 -0
  105. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/example/patches/bakeries-c2-1.patch.yaml +0 -0
  106. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/example/sources.yaml +0 -0
  107. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/example/task/answers_ana.yaml +0 -0
  108. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/example/task/answers_ben.yaml +0 -0
  109. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/example/task/answers_cy.yaml +0 -0
  110. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/example/task/pack.yaml +0 -0
  111. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/example/task/replies_ana.yaml +0 -0
  112. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/example/task/replies_ben.yaml +0 -0
  113. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/example/task/transcript_ben.txt +0 -0
  114. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/example/two-boards-c1.board.yaml +0 -0
  115. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/example_ru/pekarni-c1.board.yaml +0 -0
  116. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/example_ru/pekarni-oru-c1.board.yaml +0 -0
  117. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/example_ru/pekarnya-holding-c1.board.yaml +0 -0
  118. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/example_ru/sources.yaml +0 -0
  119. {smd_engine-0.7.7 → smd_engine-0.7.9}/cases/spectra_coffee/sources.yaml +0 -0
  120. {smd_engine-0.7.7 → smd_engine-0.7.9}/docs/README.md +0 -0
  121. {smd_engine-0.7.7 → smd_engine-0.7.9}/docs/first-board.md +0 -0
  122. {smd_engine-0.7.7 → smd_engine-0.7.9}/docs/glossary.md +0 -0
  123. {smd_engine-0.7.7 → smd_engine-0.7.9}/docs/method/encodable.md +0 -0
  124. {smd_engine-0.7.7 → smd_engine-0.7.9}/docs/method/odi-problematization.md +0 -0
  125. {smd_engine-0.7.7 → smd_engine-0.7.9}/docs/method/reconciliation.md +0 -0
  126. {smd_engine-0.7.7 → smd_engine-0.7.9}/docs/method/smd-classic.md +0 -0
  127. {smd_engine-0.7.7 → smd_engine-0.7.9}/docs/method/triz-systems.md +0 -0
  128. {smd_engine-0.7.7 → smd_engine-0.7.9}/docs/plan.md +0 -0
  129. {smd_engine-0.7.7 → smd_engine-0.7.9}/lenses/README.md +0 -0
  130. {smd_engine-0.7.7 → smd_engine-0.7.9}/lenses/design-chain.md +0 -0
  131. {smd_engine-0.7.7 → smd_engine-0.7.9}/lenses/fliamer-diamond.md +0 -0
  132. {smd_engine-0.7.7 → smd_engine-0.7.9}/lenses/khaprov-ontology.md +0 -0
  133. {smd_engine-0.7.7 → smd_engine-0.7.9}/lenses/scamper-check.md +0 -0
  134. {smd_engine-0.7.7 → smd_engine-0.7.9}/lenses/schukin-boundaries.md +0 -0
  135. {smd_engine-0.7.7 → smd_engine-0.7.9}/lenses/schukin-interface-tax.md +0 -0
  136. {smd_engine-0.7.7 → smd_engine-0.7.9}/lenses/triz-contradictions.md +0 -0
  137. {smd_engine-0.7.7 → smd_engine-0.7.9}/procedures/README.md +0 -0
  138. {smd_engine-0.7.7 → smd_engine-0.7.9}/procedures/ingest-transcript.md +0 -0
  139. {smd_engine-0.7.7 → smd_engine-0.7.9}/procedures/positional-construction.md +0 -0
  140. {smd_engine-0.7.7 → smd_engine-0.7.9}/procedures/problematization.md +0 -0
  141. {smd_engine-0.7.7 → smd_engine-0.7.9}/procedures/reflexive-protocol.md +0 -0
  142. {smd_engine-0.7.7 → smd_engine-0.7.9}/procedures/small-situation.md +0 -0
  143. {smd_engine-0.7.7 → smd_engine-0.7.9}/procedures/solo-session.md +0 -0
  144. {smd_engine-0.7.7 → smd_engine-0.7.9}/procedures/theses-to-board.md +0 -0
  145. {smd_engine-0.7.7 → smd_engine-0.7.9}/roles/README.md +0 -0
  146. {smd_engine-0.7.7 → smd_engine-0.7.9}/roles/actors.md +0 -0
  147. {smd_engine-0.7.7 → smd_engine-0.7.9}/roles/game-technician.md +0 -0
  148. {smd_engine-0.7.7 → smd_engine-0.7.9}/roles/researcher.md +0 -0
  149. {smd_engine-0.7.7 → smd_engine-0.7.9}/roles/visionary.md +0 -0
  150. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/__init__.py +0 -0
  151. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/agree.py +0 -0
  152. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/cli.py +0 -0
  153. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/cli_boards.py +0 -0
  154. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/cli_session.py +0 -0
  155. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/cli_story.py +0 -0
  156. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/compare.py +0 -0
  157. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/deal/__init__.py +0 -0
  158. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/deal/agenda_views.py +0 -0
  159. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/deal/cli.py +0 -0
  160. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/deal/consent.py +0 -0
  161. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/deal/ledger.py +0 -0
  162. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/deal/overlap.py +0 -0
  163. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/deal/seal_cmd.py +0 -0
  164. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/deal/sealed.py +0 -0
  165. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/deal/signing.py +0 -0
  166. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/deal/verdict.py +0 -0
  167. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/deal/verdict_cmd.py +0 -0
  168. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/deal/verify.py +0 -0
  169. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/deal/verify_cmd.py +0 -0
  170. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/deal/verify_diff.py +0 -0
  171. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/deal/verify_extra.py +0 -0
  172. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/deal/verify_report.py +0 -0
  173. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/deal/views.py +0 -0
  174. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/eval.py +0 -0
  175. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/leverage.py +0 -0
  176. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/migrate.py +0 -0
  177. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/nextstep.py +0 -0
  178. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/profile.py +0 -0
  179. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/records.py +0 -0
  180. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/render/__init__.py +0 -0
  181. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/render/assets/frames.css +0 -0
  182. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/render/assets/frames.js +0 -0
  183. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/render/assets/graph.css +0 -0
  184. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/render/assets/graph.js +0 -0
  185. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/render/frames.py +0 -0
  186. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/render/frames_page.py +0 -0
  187. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/render/frames_text.py +0 -0
  188. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/render/graph_ui.py +0 -0
  189. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/render/html.py +0 -0
  190. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/render/layout.py +0 -0
  191. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/render/mermaid.py +0 -0
  192. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/render/sessionflow.py +0 -0
  193. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/render/vault.py +0 -0
  194. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/revise.py +0 -0
  195. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/scaffold.py +0 -0
  196. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/schemas/__init__.py +0 -0
  197. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/schemas/board_patch.schema.json +0 -0
  198. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/schemas/source_manifest.schema.json +0 -0
  199. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/schemas/story.schema.json +0 -0
  200. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/schemas/task_acceptance.schema.json +0 -0
  201. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/schemas/task_answers.schema.json +0 -0
  202. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/schemas/task_pack.schema.json +0 -0
  203. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/schemas/task_replies.schema.json +0 -0
  204. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/schemas/task_sealed.schema.json +0 -0
  205. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/schemas/task_verdicts.schema.json +0 -0
  206. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/schemas/taxonomies.schema.json +0 -0
  207. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/screen.py +0 -0
  208. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/sources.py +0 -0
  209. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/story/check.py +0 -0
  210. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/story/gaps.py +0 -0
  211. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/story/model.py +0 -0
  212. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/story/numbers.py +0 -0
  213. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/story/paths.py +0 -0
  214. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/story/render.py +0 -0
  215. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/__init__.py +0 -0
  216. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/acceptance.py +0 -0
  217. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/agenda.py +0 -0
  218. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/asking.py +0 -0
  219. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/assets/task.css +0 -0
  220. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/assets/task.js +0 -0
  221. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/bounds.py +0 -0
  222. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/check.py +0 -0
  223. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/cli.py +0 -0
  224. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/deal_check.py +0 -0
  225. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/deal_items.py +0 -0
  226. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/deal_labels.py +0 -0
  227. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/deal_render.py +0 -0
  228. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/deal_web.py +0 -0
  229. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/diff.py +0 -0
  230. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/diff_html.py +0 -0
  231. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/diff_md.py +0 -0
  232. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/labels.py +0 -0
  233. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/model.py +0 -0
  234. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/names.py +0 -0
  235. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/overwrite.py +0 -0
  236. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/pack_html.py +0 -0
  237. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/pack_md.py +0 -0
  238. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/pairs.py +0 -0
  239. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/positions.py +0 -0
  240. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/ranges.py +0 -0
  241. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/refs.py +0 -0
  242. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/svg.py +0 -0
  243. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/task/web.py +0 -0
  244. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/validate/__init__.py +0 -0
  245. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/validate/manifest.py +0 -0
  246. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/validate/ontology.py +0 -0
  247. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/validate/signoffs.py +0 -0
  248. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/validate/taxonomies.py +0 -0
  249. {smd_engine-0.7.7 → smd_engine-0.7.9}/src/smd_engine/validate/theses.py +0 -0
  250. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/conftest.py +0 -0
  251. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/deal_helpers.py +0 -0
  252. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/story_helpers.py +0 -0
  253. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_agree.py +0 -0
  254. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_beer_render.py +0 -0
  255. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_compare.py +0 -0
  256. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_deal_acceptance.py +0 -0
  257. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_deal_added.py +0 -0
  258. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_deal_agenda_leaks.py +0 -0
  259. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_deal_bindings.py +0 -0
  260. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_deal_golden.py +0 -0
  261. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_deal_items.py +0 -0
  262. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_deal_positions.py +0 -0
  263. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_deal_ranges.py +0 -0
  264. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_deal_sealed.py +0 -0
  265. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_deal_signed.py +0 -0
  266. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_deal_verdict.py +0 -0
  267. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_deal_verify.py +0 -0
  268. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_deal_verify_diff.py +0 -0
  269. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_deal_verify_forged.py +0 -0
  270. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_deal_views.py +0 -0
  271. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_eval.py +0 -0
  272. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_export.py +0 -0
  273. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_frames.py +0 -0
  274. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_graph.py +0 -0
  275. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_ingestion.py +0 -0
  276. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_lenses.py +0 -0
  277. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_migrate.py +0 -0
  278. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_nextstep.py +0 -0
  279. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_ontology_continuum.py +0 -0
  280. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_procedures.py +0 -0
  281. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_publish.py +0 -0
  282. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_render_and_cli.py +0 -0
  283. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_render_carries.py +0 -0
  284. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_revise.py +0 -0
  285. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_robustness.py +0 -0
  286. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_scaffold.py +0 -0
  287. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_status.py +0 -0
  288. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_story_case.py +0 -0
  289. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_story_check.py +0 -0
  290. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_story_numbers.py +0 -0
  291. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_story_paths.py +0 -0
  292. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_task.py +0 -0
  293. {smd_engine-0.7.7 → smd_engine-0.7.9}/tests/test_validate.py +0 -0
@@ -25,7 +25,7 @@ jobs:
25
25
  # Python tooling - only if pyproject.toml exists
26
26
  - name: Install uv
27
27
  if: hashFiles('pyproject.toml') != ''
28
- uses: astral-sh/setup-uv@07a047e608db84b3d8c06cd9a7c7dcc9c355c18e # v10.3.2
28
+ uses: astral-sh/setup-uv@68559e99cc807c1eb7e9238fd43a15bba460eec2 # v10.3.3
29
29
  with:
30
30
  enable-cache: true
31
31
  cache-dependency-glob: "uv.lock"
@@ -113,3 +113,40 @@ jobs:
113
113
  vuln-type: 'os,library'
114
114
  severity: 'CRITICAL,HIGH'
115
115
  cache: 'false'
116
+
117
+ # Node tooling - only if package-lock.json exists. After Trivy, so the scan sees
118
+ # the repository, not node_modules or the build output. Node 22 matches the
119
+ # deploy workflows. The build is `npm run ci:build` when the repo defines it (a
120
+ # build that needs no secrets), else the `npm run build` a deploy runs, so a
121
+ # dependency PR that breaks the site fails here instead of in the deploy.
122
+ - name: Set up Node
123
+ if: hashFiles('package-lock.json') != ''
124
+ uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7.1.0
125
+ with:
126
+ node-version: 22
127
+ cache: npm
128
+
129
+ - name: Install Node Dependencies
130
+ if: hashFiles('package-lock.json') != ''
131
+ run: npm ci
132
+
133
+ - name: Build (Node)
134
+ if: hashFiles('package-lock.json') != ''
135
+ run: |
136
+ # Last resort when no secret-free build exists (marker file)
137
+ if [ -f ".ci-skip-build" ]; then
138
+ echo "Build skipped (.ci-skip-build marker found)"
139
+ exit 0
140
+ fi
141
+ if [ "$(npm pkg get 'scripts.ci:build')" != "{}" ]; then
142
+ script="ci:build"
143
+ elif [ "$(npm pkg get scripts.build)" != "{}" ]; then
144
+ script="build"
145
+ else
146
+ echo "No build script, skipping."
147
+ exit 0
148
+ fi
149
+ # Tracked editor-rule symlinks (.cursorrules, .clinerules) have absolute
150
+ # targets that do not exist on the runner; next build stops on them.
151
+ find . -maxdepth 1 -xtype l -print -delete
152
+ npm run "$script"
@@ -2,9 +2,21 @@
2
2
 
3
3
  Dates are those of the tag. All tags v0.2.1 to v0.3.5 were made on 2026-10-29. The version in `pyproject.toml` stayed at 0.2.0 through v0.2.4 and at 0.3.0 from v0.3.0 to v0.3.5; 0.3.6 is the first release whose package version equals its tag.
4
4
 
5
+ ## 0.7.9 - 2026-11-14
6
+
7
+ The changelog entries, procedures, docs, code comments and tests no longer cite the case's private decision log: no line references into it, no gate codes and no dated decisions of the case owner. Each statement says the rule in words, and a procedure's sources name the public document that holds the rule. The public export scan now refuses such citations. No code change in behaviour; schema 0.3 and every record, pack and ledger of 0.7.8 load as before.
8
+
9
+ ## 0.7.8 - 2026-11-14
10
+
11
+ The header of a patched board names its current state, and tier 1 has its Russian name «намерение». Schema 0.3 gains an optional field; every record, patch, pack and ledger of 0.7.7 loads as before.
12
+
13
+ - `smd apply` sets `state.date` to the patch's `date` when the patch has one; a new `date` key goes after `state.version`. The board schema takes the optional `state.date` (a date, like the other dates of a record). The result stays deterministic and reads back byte for byte.
14
+ - The header of the screen (SVG, also `--light` and the frames) and of the Markdown digest names the cycle by `state.version` when it is set and gives `state.date` when it is set: a board patched to 5.31 on 14 November shows `цикл 5.31 · черновик · 2026-11-14`, not the cycle number and the date the record was made. A record without `state.version` and `state.date` renders byte for byte as in 0.7.7 (`tests/test_render_header.py` pins every example board).
15
+ - Tier 1 is «намерение» / "intent": the intent of every position regarding the business. «Замысел» names only the controlling instance, the owner's (or founder's), «замысел собственника». The example case `spectra_coffee` (taxonomy, board 1.0.3 and its stories), `docs/data-model.md`, lens `khaprov-levels` 0.2.4, procedure `stakeholder-ontology` 0.2.1 and the case's README say so; the 0.7.7 entry below records the earlier name.
16
+
5
17
  ## 0.7.7 - 2026-11-09
6
18
 
7
- The meanings of the six tiers in the examples, a lens and a procedure (the case owner, 9 November 2026). No code change in behaviour; schema 0.3 and every record, pack and ledger of 0.7.6 load as before.
19
+ The meanings of the six tiers in the examples, a lens and a procedure (the case owner's request). No code change in behaviour; schema 0.3 and every record, pack and ledger of 0.7.6 load as before.
8
20
 
9
21
  - The tier of an element is the tier of the field of what it stands for, not of its kind. The example packs in `cases/example/deal/` and `cases/example/task/` now put a goal (a position's intent) at tier 1, production, logistics and the cafe counter at tier 5 and the premises lease at tier 3; their answers, replies and the golden render hashes are restamped.
10
22
  - Tier 1 is «замысел» / "intent": the intent of every position regarding the business (owner, bank, employees, buyer), the owner's being the controlling one; the owner's control is a tier-3 field. Procedure `stakeholder-ontology` 0.2.0 records the position's intent as a tier-1 `goal` element next to its ontology (new section 3a) and treats every stakeholder ontology as tier-1 content of its position; `positional-construction` 0.2.9 and `docs/method/roles-and-actors.md` follow.
@@ -14,7 +26,7 @@ The meanings of the six tiers in the examples, a lens and a procedure (the case
14
26
 
15
27
  ## 0.7.6 - 2026-11-07
16
28
 
17
- A currency review of the documentation (the case owner, 7 November 2026). No code change in behaviour; schema 0.3 and every record, pack and ledger of 0.7.5 load as before.
29
+ A currency review of the documentation (the case owner's request). No code change in behaviour; schema 0.3 and every record, pack and ledger of 0.7.5 load as before.
18
30
 
19
31
  - `README.md` and `README_ru.md` give the current version and list the `story`, `task` and `deal` commands; `CONTRIBUTING.md` lists `task/`, `deal/`, `story/` and `cases/spectra_coffee/`; `docs/README.md` lists `changelog-0.2-0.5.md`.
20
32
  - `docs/release.md` records the finished rename and first publication; `docs/plan.md` is marked as the historical plan of 25 October 2026 and lists the three profiles.
@@ -24,7 +36,7 @@ A currency review of the documentation (the case owner, 7 November 2026). No cod
24
36
 
25
37
  ## 0.7.5 - 2026-11-07
26
38
 
27
- The engine and its cases are kept apart (the case owner, 7 November 2026). No code change in behaviour; schema 0.3 and every record, pack and ledger of 0.7.4 load as before.
39
+ The engine and its cases are kept apart (the case owner's request). No code change in behaviour; schema 0.3 and every record, pack and ledger of 0.7.4 load as before.
28
40
 
29
41
  - Docs, comments and examples no longer name a real case's ids or hypotheses; the data-model taxonomy example uses the neutral `spectra-coffee-fiction` case.
30
42
  - The public export scan refuses case ids (pattern "private case id").
@@ -32,22 +44,22 @@ The engine and its cases are kept apart (the case owner, 7 November 2026). No co
32
44
 
33
45
  ## 0.7.4 - 2026-11-03
34
46
 
35
- `smd deal verify --diff` no longer trusts the diff's own list of answers files when a counted run follows its head, and `cli.py` and `profile.py` are split (release go dz03#l=31). Schema 0.1 stays; no file format changes, and every 0.7.3 pack, answers file, ledger and diff still loads.
47
+ `smd deal verify --diff` no longer trusts the diff's own list of answers files when a counted run follows its head, and `cli.py` and `profile.py` are split. Schema 0.1 stays; no file format changes, and every 0.7.3 pack, answers file, ledger and diff still loads.
36
48
 
37
- - Code layout, no change in behaviour (the case owner, dz03#l=7): `cli.py` (1168 lines) keeps the parser and `main`; the commands moved to `cli_boards.py`, `cli_session.py` and `cli_story.py`. `profile.py` (941 lines) keeps loading; the constants and classes moved to `profile_model.py` and the parsing to `profile_parse.py`. Every name stays importable from `smd_engine.profile`, and `smd = smd_engine.cli:main` is unchanged.
49
+ - Code layout, no change in behaviour (the case owner's request): `cli.py` (1168 lines) keeps the parser and `main`; the commands moved to `cli_boards.py`, `cli_session.py` and `cli_story.py`. `profile.py` (941 lines) keeps loading; the constants and classes moved to `profile_model.py` and the parsing to `profile_parse.py`. Every name stays importable from `smd_engine.profile`, and `smd = smd_engine.cli:main` is unchanged.
38
50
  - `smd deal verify --diff` no longer trusts the diff's own `answers_files` when the ledger has a counted run after the diff's head (two findings of the automated security review of 0.7.3: a holder could point the head before the run and drop or make up a committer's answers sha, and the point read `ok`). Such a run fails the diff unless a file given with `--answers`, signed by the party, shows the diff read other answers than the run (`diff_later_run`); for a committer whose files are given, the file the diff names must be one of them (`diff_answers_file`). A party who checks an older diff gives the answers files it names. Tests: `tests/test_deal_verify_diff.py`.
39
51
 
40
52
  ## 0.7.3 - 2026-11-03
41
53
 
42
- `smd deal verify --diff` now catches a holder who hides a logged verdict from the parties' diff (the case owner, dz02#l=79; release go dz03#l=7). Schema 0.1 stays; no file format changes, and every 0.7.2 pack, answers file, ledger and diff still loads.
54
+ `smd deal verify --diff` now catches a holder who hides a logged verdict from the parties' diff (the case owner's request). Schema 0.1 stays; no file format changes, and every 0.7.2 pack, answers file, ledger and diff still loads.
43
55
 
44
- - Changelog: the 0.7.2 entry cites the case owner's go as dz02#l=71 (it said #l=69, a line that is the heading of that message).
45
- - `smd deal verify --diff` checks a sealed point shown `not_tested` against the ledger (the case owner, dz02#l=79). Before, a point shown `not_tested` with any `changed_since_run` passed, so a holder could hide a logged verdict from the parties' diff. Now, over a counted run, each member named in `changed_since_run` must commit a side of the topic, the answers file the diff read for him (`answers_files`) must not be the one the run recorded, and, when that file is given with `--answers`, its commitment must differ from the one the run used; without the file the line is `skipped`, and with that member's files given but none of them the one the diff names it fails. A counted run logged after the diff's head (or at all, with no head) on the very answers files the diff read fails the diff, so an old or removed head cannot hide a verdict either. A view must name a position of the pack. Every bound item the diff (or view) should show must be there as one sealed point of its topic and side, and the sealed points must name one ledger head or none. New check codes `diff_missing`, `diff_not_bound`, `diff_point_shape`, `diff_head_mixed`, `diff_changed_who`, `diff_changed_same`, `diff_changed_nofile`, `diff_changed_ok`, `diff_changed_file`, `diff_stale`, `diff_view`, `diff_view_bad` (labels in English and Russian); `ledger.last_run`. The diff checks moved to `src/smd_engine/deal/verify_diff.py`. Tests: `tests/test_deal_verify_diff.py`.
56
+ - Changelog: a wrong citation in the 0.7.2 entry is corrected.
57
+ - `smd deal verify --diff` checks a sealed point shown `not_tested` against the ledger (the case owner's request). Before, a point shown `not_tested` with any `changed_since_run` passed, so a holder could hide a logged verdict from the parties' diff. Now, over a counted run, each member named in `changed_since_run` must commit a side of the topic, the answers file the diff read for him (`answers_files`) must not be the one the run recorded, and, when that file is given with `--answers`, its commitment must differ from the one the run used; without the file the line is `skipped`, and with that member's files given but none of them the one the diff names it fails. A counted run logged after the diff's head (or at all, with no head) on the very answers files the diff read fails the diff, so an old or removed head cannot hide a verdict either. A view must name a position of the pack. Every bound item the diff (or view) should show must be there as one sealed point of its topic and side, and the sealed points must name one ledger head or none. New check codes `diff_missing`, `diff_not_bound`, `diff_point_shape`, `diff_head_mixed`, `diff_changed_who`, `diff_changed_same`, `diff_changed_nofile`, `diff_changed_ok`, `diff_changed_file`, `diff_stale`, `diff_view`, `diff_view_bad` (labels in English and Russian); `ledger.last_run`. The diff checks moved to `src/smd_engine/deal/verify_diff.py`. Tests: `tests/test_deal_verify_diff.py`.
46
58
  - `procedures/task-diff.md`: the example model-pass line names `task-diff 0.2.1`, the procedure's version.
47
59
 
48
60
  ## 0.7.2 - 2026-11-02
49
61
 
50
- The sealed floor audited and bound to the pack text (the case owner, dz02#l=71). Schema 0.1 stays; every new field is optional, and 0.7.0 and 0.7.1 packs, answers, consent files and ledgers still load (old entries are reported `unbound`). Packs without positions give the same bytes as before.
62
+ The sealed floor audited and bound to the pack text (the case owner's request). Schema 0.1 stays; every new field is optional, and 0.7.0 and 0.7.1 packs, answers, consent files and ledgers still load (old entries are reported `unbound`). Packs without positions give the same bytes as before.
51
63
 
52
64
  - `smd deal verify pack.yaml --ledger verdicts.yaml [--answers ...] [--sealed dir] [--diff diff.yaml] [--json]`: an audit of the ledger any party can run (`src/smd_engine/deal/verify.py`, `verify_extra.py`, `verify_report.py`, `verify_cmd.py`). It checks the chain and head; each consent entry (signature over its stored text with the member's key, hash, bindings to the deal, topic, run, buyer, core sha256 and key list); each counted verdict (the consents it names are earlier, valid, current, for the same topic, run and buyer, with its commitments; seller, and buyer for a second run; run number and cap of two; answers sha256 against the files given, their signatures and commitments); with `--sealed` the outcome recomputed from the sealed files (signatures checked, no number printed); with `--diff` its head and verdicts. Lines are `ok`, `FAIL` or `unbound (old entry)` (labels in English and Russian, `VERIFY_LABELS` in `deal_labels.py`); exit 1 on a `FAIL` or an `unbound` entry (fail closed; `--allow-unbound` for a ledger known to be old); the last line says "all checks passed" only when nothing is `unbound` (else "no check failed, but not fully verified"), and `--json` has `complete`. A counted verdict whose `consents` list is empty is a `FAIL` (the consents it needs are not among them). A counted verdict whose `answers` lack the floor or the ceiling party, or name a non-member, is a `FAIL`. Entries from before 0.7.2 are `unbound`; after the first 0.7.2 entry a later one without the new fields is `FAIL`. `consent.binding_code` is new (the codes behind `binding_problem`). Tests: `tests/test_deal_verify.py`, `tests/test_deal_verify_forged.py` (an empty `consents` list, replaced or replayed inputs, `--allow-unbound`).
53
65
  - Bindings of the sealed floor (packs with `deal.sealed_floor: true`; schema 0.1, new fields optional). The `task_consent` file names `pack.sha256` (the core sha256) and `keys` (`key_list_sha` in `signing.py`: sha256 of the sorted `<member> <key>` lines); `smd deal consent` and `smd deal verdict` refuse a consent whose values differ from the pack, and a 0.7.1 consent without them (re-sign; it stays readable in an old ledger and a verdict does not count it). The answers files of members with an `ssh_key` are signed (`answers_<member>.yaml.sig`, namespace `smd-deal`); `smd deal verdict` refuses an unsigned or badly signed one, `smd task diff` only warns. The verdict entry records `answers: {member: sha256}` and, when counted, `consents: [entry sha256, ...]` (schema `task_verdicts`; the chain covers them, older entries without them still verify). A swapped-back older answers file is caught by the signed consents (`commitment_changed`) and its sha256 is on record. Packs without positions give the same bytes as before. Tests: `tests/test_deal_bindings.py`.
@@ -58,7 +70,7 @@ The sealed floor audited and bound to the pack text (the case owner, dz02#l=71).
58
70
 
59
71
  ## 0.7.1 - 2026-11-02
60
72
 
61
- Fixes to the weak points of deal mode that 0.7.0 left open (the case owner, dz02#l=63). Schema 0.1 stays; every new field is optional, and 0.7.0 packs, answers, diffs and ledgers still load. Packs without positions give the same bytes as before (the pilot pack and the group example were compared byte for byte).
73
+ Fixes to the weak points of deal mode that 0.7.0 left open (the case owner's request). Schema 0.1 stays; every new field is optional, and 0.7.0 packs, answers, diffs and ledgers still load. Packs without positions give the same bytes as before (the pilot pack and the group example were compared byte for byte).
62
74
 
63
75
  - Agendas without leaks. `smd task agenda` on a deal diff writes the common agenda, read by every party: a point with an `audience` shows no question, text, refs, options, claim, answers, item id, class, route or reason. On the call it appears as `annex-1`, `annex-2`... under the item's new `call_title` (a neutral title the pack author writes; `smd task check` warns when one is missing), else under «Точка приложения» / "Annex point". It is not listed under any pair. A settled annex point is left out. Item numbers are counted over the core items only. A fact dispute over a buyer-side claim (new diff field `buyer_claim`) is left out, and a value point shows only `open` or `settled`. The `labels` block keeps the shown points only. Sealed price points stay, with their verdict and no question.
64
76
  - Per-position agendas. `smd deal views --replies ... --members ...` also writes `agenda.<position>.yaml` and `.md`, filtered by the rules of the views, with a `view` block (`src/smd_engine/deal/agenda_views.py`).
@@ -70,62 +82,62 @@ Fixes to the weak points of deal mode that 0.7.0 left open (the case owner, dz02
70
82
 
71
83
  ## 0.7.0 - 2026-11-02
72
84
 
73
- Deal mode, package version 0.7.0 (the case owner, dz02#l=43 and dz02#l=47). Schema stays 0.1 with optional fields; packs without them are unchanged, and their renders are byte for byte as before (`tests/test_deal_golden.py`). `pyproject.toml` goes from 0.6.5 to 0.7.0. Docs: `docs/deal-mode.md` (the cycle, positions, item kinds, views, the sealed branch, the trust step for pilots with age-encrypted transfer and a RAM disk, the threat model, what leaks), the re-run rule in `docs/task-packs.md` (the shared part by anyone, the sealed part only by the holder program), `docs/commands.md`, `docs/README.md`. The asking price and the optional sealed floor are in the last bullet.
85
+ Deal mode, package version 0.7.0 (the case owner's request). Schema stays 0.1 with optional fields; packs without them are unchanged, and their renders are byte for byte as before (`tests/test_deal_golden.py`). `pyproject.toml` goes from 0.6.5 to 0.7.0. Docs: `docs/deal-mode.md` (the cycle, positions, item kinds, views, the sealed branch, the trust step for pilots with age-encrypted transfer and a RAM disk, the threat model, what leaks), the re-run rule in `docs/task-packs.md` (the shared part by anyone, the sealed part only by the holder program), `docs/commands.md`, `docs/README.md`. The asking price and the optional sealed floor are in the last bullet.
74
86
 
75
87
  - Positions, audience, shared core and annex per position; `smd task render --position`; alpha on the core only.
76
88
  - Fact items with evidence (`claim`, `source_ids`, source `sha256` and `date`), `nature` and `fit_of` with `after_reading`, red-line items (`kind: line`, class `line_rejected`, route `blocking`). Procedures `task-pack` and `task-diff` 0.2.0. Example in `cases/example/deal/`.
77
89
  - Map acceptance: pack `map` (board id, version, sha256), record `task_acceptance` (vocabulary, elements, independent check, pinned to the board's sha256, void on any edit), `smd task check --acceptance [--board] [--prior]` with the elements to ask again found by `compare.compare` (`src/smd_engine/task/acceptance.py`). The engine writes no acceptance.
78
90
  - Item kind `range` (`{min, max, unit, date?}`, the unit named by the item): identical spans agree, nested spans refine, spans with a common stretch are the new class `compatible` (route `accept_unless_objected`), spans with none are a `value` conflict; a wrong unit or `min` above `max` is an error (`src/smd_engine/task/ranges.py`).
79
91
  - Pairs and per-position views: pack `pairs` (member pairs), diff `by_pair`, agenda `call_by_pair` (`src/smd_engine/task/pairs.py`); `smd deal views` writes `diff.<position>.yaml`, `.md` and `.html` (`src/smd_engine/deal/`): no point outside the audience, no buyer-side fact dispute for the seller's side, value points as `open` or `settled` with the other side's answers removed, a broker on his principal's side. Replies may carry `view`, the sha256 of the view.
80
- - Sealed bounds, holder and model consent (the case owner, dz02#l=47; price is a flag, never a stop): item kind `bound` (`topic`, `side` floor or ceiling, `unit`, `stage`) with a seller's floor committed at day 0 and an optional buyer's ceiling committed only at the last of `deal.stages` (a ceiling in an earlier stage is an error); `smd deal seal` writes the private `task_sealed` file and prints the sha256 commitment, which is all an answers file may hold; the diff point has class `sealed`, route `price_meeting`, `committed_by`, `silent` and `verdict` (`not_tested`) and no answers; pack `holder` (a broker is never the operator) and `deal: {id, stages, model_consent}`; the diff says `model_pass_allowed` and the model procedure stops when it is false; a `task_sealed` file is refused as an input. Russian page wording «цена: ... — торг на личной встрече» (`src/smd_engine/task/bounds.py`, `src/smd_engine/deal/sealed.py`).
81
- - Verdict, ledger and run cap (dz02#l=47): `smd deal verdict` compares a sealed floor and ceiling of one topic behind a `Comparator` protocol (`LocalComparator`, method `local-v1`, `src/smd_engine/deal/overlap.py`) and appends `met`, `not_met` or `not_tested` to a hash-chained ledger `verdicts.yaml` (record `task_verdicts`; no number, salt or gap in it; commitments of a file are checked against the answers). One run per seller-buyer pair and topic; a second only after `smd deal consent` has logged both parties; two at most; a run that was not tested does not count. `smd task diff --ledger` writes each bound point's verdict and `ledger_head`, so a cut ledger no longer matches an earlier diff. Pages read «цена: условия сошлись / не сошлись / не проверено — торг на личной встрече».
82
- - Asking price first (ЦН1 А, the case owner, dz02#l=55; overrides the sealed floor and ceiling being the default price route). A deal pack with a seller states `deal.asking_price: {value, unit, stage?}`, shared; the seller chooses the stage at which the pack pages open it (default: the stage after `nda`), `smd task render --stage` shows «запрашиваемая цена» / "asking price" from that stage on, and the diff, its views and the agenda show it (`src/smd_engine/task/asking.py`); a deal pack with a seller and no asking price is a `smd task check` error. The sealed branch is optional and off by default: `deal.sealed_floor: true` is needed for any `bound` item (a check error otherwise), and then every verdict run, the first included, needs the seller's consent in the ledger naming the buyer (the `task_consent` file and the ledger entry gain `buyer`; `smd deal consent --new` starts a ledger; the per-pair cap of two stays). The buyer gives no number: the example pack has an optional shared choice item `price-talk` at the last stage (item field `stage`). Verdict tests keep their meaning with `sealed_floor: true` in the example. Security: `smd task diff` prints a warning when a deal diff has annex points (full diff: holder only; send parties their views from `smd deal views`), `docs/deal-mode.md` says so, and a test checks that no hidden annex item id or question is in any view. Procedure `task-pack` 0.2.1. Docs: `deal-mode.md`, `task-packs.md`, `commands.md`.
92
+ - Sealed bounds, holder and model consent (the case owner's request; price is a flag, never a stop): item kind `bound` (`topic`, `side` floor or ceiling, `unit`, `stage`) with a seller's floor committed at day 0 and an optional buyer's ceiling committed only at the last of `deal.stages` (a ceiling in an earlier stage is an error); `smd deal seal` writes the private `task_sealed` file and prints the sha256 commitment, which is all an answers file may hold; the diff point has class `sealed`, route `price_meeting`, `committed_by`, `silent` and `verdict` (`not_tested`) and no answers; pack `holder` (a broker is never the operator) and `deal: {id, stages, model_consent}`; the diff says `model_pass_allowed` and the model procedure stops when it is false; a `task_sealed` file is refused as an input. Russian page wording «цена: ... — торг на личной встрече» (`src/smd_engine/task/bounds.py`, `src/smd_engine/deal/sealed.py`).
93
+ - Verdict, ledger and run cap: `smd deal verdict` compares a sealed floor and ceiling of one topic behind a `Comparator` protocol (`LocalComparator`, method `local-v1`, `src/smd_engine/deal/overlap.py`) and appends `met`, `not_met` or `not_tested` to a hash-chained ledger `verdicts.yaml` (record `task_verdicts`; no number, salt or gap in it; commitments of a file are checked against the answers). One run per seller-buyer pair and topic; a second only after `smd deal consent` has logged both parties; two at most; a run that was not tested does not count. `smd task diff --ledger` writes each bound point's verdict and `ledger_head`, so a cut ledger no longer matches an earlier diff. Pages read «цена: условия сошлись / не сошлись / не проверено — торг на личной встрече».
94
+ - Asking price first (the case owner's decision; overrides the sealed floor and ceiling being the default price route). A deal pack with a seller states `deal.asking_price: {value, unit, stage?}`, shared; the seller chooses the stage at which the pack pages open it (default: the stage after `nda`), `smd task render --stage` shows «запрашиваемая цена» / "asking price" from that stage on, and the diff, its views and the agenda show it (`src/smd_engine/task/asking.py`); a deal pack with a seller and no asking price is a `smd task check` error. The sealed branch is optional and off by default: `deal.sealed_floor: true` is needed for any `bound` item (a check error otherwise), and then every verdict run, the first included, needs the seller's consent in the ledger naming the buyer (the `task_consent` file and the ledger entry gain `buyer`; `smd deal consent --new` starts a ledger; the per-pair cap of two stays). The buyer gives no number: the example pack has an optional shared choice item `price-talk` at the last stage (item field `stage`). Verdict tests keep their meaning with `sealed_floor: true` in the example. Security: `smd task diff` prints a warning when a deal diff has annex points (full diff: holder only; send parties their views from `smd deal views`), `docs/deal-mode.md` says so, and a test checks that no hidden annex item id or question is in any view. Procedure `task-pack` 0.2.1. Docs: `deal-mode.md`, `task-packs.md`, `commands.md`.
83
95
 
84
96
  ## 0.6.5 - 2026-11-02
85
97
 
86
- Task packs (the case owner, 2 November 2026, dz02#l=11 and dz02#l=15, gate АС2 В): the engine carries the tooling for group work in an async mode. No change to the board schema or to any existing command; the package version is not bumped.
98
+ Task packs (the case owner's decision): the engine carries the tooling for group work in an async mode. No change to the board schema or to any existing command; the package version is not bumped.
87
99
 
88
- - Three new schemas, `task_pack`, `task_answers` and `task_replies` (schema 0.1), and the commands `smd task check | render | diff | agenda` (`src/smd_engine/task/`). The files are plain YAML named by the cycle, not record files that `smd validate` discovers. `docs/task-packs.md` describes the cycle: a pack, a term check in every pack (АС6 А), blind answers (АС4 А), a diff that anyone can re-run with the raw answers attached (АС3 В), a reply per open point (accept another member's answer, keep mine, discuss), and a call only for the points marked discuss or left without a reply (АС5 А).
100
+ - Three new schemas, `task_pack`, `task_answers` and `task_replies` (schema 0.1), and the commands `smd task check | render | diff | agenda` (`src/smd_engine/task/`). The files are plain YAML named by the cycle, not record files that `smd validate` discovers. `docs/task-packs.md` describes the cycle: a pack, a term check in every pack, blind answers, a diff that anyone can re-run with the raw answers attached, a reply per open point (accept another member's answer, keep mine, discuss), and a call only for the points marked discuss or left without a reply.
89
101
  - `smd task diff` classes the structured items by script: agreement, refinement (one set holds another, for multi and ids), conflict, only one (a point raised by one member, and every added point); identical `steps` sets agree, others conflict until the model marks them compatible. Text, term-check items and the subtype of a conflict (term, position, fact, value) are left to the model (`procedures/task-diff.md`, `class_by: model`, an AI draft). Krippendorff's alpha over the choice items and per section reuses `agree.alpha_nominal`. The diff has no date, so the same answers give the same bytes.
90
- - Voice (dz02#l=15): an answers file may list transcripts (`path`, `sha256`, `note`) as a fuller raw source of the member's position; the diff verifies each sha256 when the file exists. When members propose different next steps the conflict goes to the call unless the model marks the steps compatible (both can be done, or one after the other), when they are listed as compatible and accepted.
102
+ - Voice: an answers file may list transcripts (`path`, `sha256`, `note`) as a fuller raw source of the member's position; the diff verifies each sha256 when the file exists. When members propose different next steps the conflict goes to the call unless the model marks the steps compatible (both can be done, or one after the other), when they are listed as compatible and accepted.
91
103
  - `smd task render` writes `pack.md` (tables, the cycle and the ontology relations as Mermaid) and `pack.html` (one offline file with the ontology as inline SVG, the items as a form that saves itself in the browser, and a button that downloads `answers_<member>.yaml`); given a `diff.yaml` it writes `diff.md` and `diff.html`, the latter with a reply form that downloads `replies_<member>.yaml`. Ru and en. `smd task agenda` writes `agenda.md` and `agenda.yaml`.
92
104
  - Procedures `task-pack` and `task-diff` (0.1.0), `docs/task-packs.md`, `docs/commands.md`, and an invented example in `cases/example/task/` (three members, six items of every kind, answers and replies) with `tests/test_task.py`.
93
- - Task pages, after the owner looked at the generated pack (dz02#l=31): the ontology drawing wraps every label into its box and sizes the boxes to the text, with no overlapping boxes and arrows that bend round boxes; with many sources to one target (82 elements in the pilot pack) each target is drawn with its sources under it, in columns; a narrow drawing is shown on a phone. An `ids` item is a searchable checklist of element labels grouped under the element their relations lead to, with a count; the answer is still a list of ids; `pack.md` lists the same. The Russian label of the facilitator is «Ведущий». Tables stack on a narrow screen. `diff.html`, `diff.md` and `agenda.md` follow the rule of the pack: items by number and question, members by name, options and refs by label; ids stay in files and attributes. `diff.yaml` gets a `labels` block for this (members, item numbers, options, terms, elements); a diff without it is shown with ids as before, and the example replies carry the new diff sha256.
105
+ - Task pages, after the owner looked at the generated pack: the ontology drawing wraps every label into its box and sizes the boxes to the text, with no overlapping boxes and arrows that bend round boxes; with many sources to one target (82 elements in the pilot pack) each target is drawn with its sources under it, in columns; a narrow drawing is shown on a phone. An `ids` item is a searchable checklist of element labels grouped under the element their relations lead to, with a count; the answer is still a list of ids; `pack.md` lists the same. The Russian label of the facilitator is «Ведущий». Tables stack on a narrow screen. `diff.html`, `diff.md` and `agenda.md` follow the rule of the pack: items by number and question, members by name, options and refs by label; ids stay in files and attributes. `diff.yaml` gets a `labels` block for this (members, item numbers, options, terms, elements); a diff without it is shown with ids as before, and the example replies carry the new diff sha256.
94
106
 
95
107
  ## 0.6.4 - 2026-11-02
96
108
 
97
- Two method changes asked for by the case owner on 2 November 2026 (dz02#l=11) and one fix (dz02#l=15). Schema 0.3 stays; the new field is optional and old records stay valid. The first case's five boards validate as before (0 errors, 150 warnings); hints go from 143 to 156, the 13 new ones being `move-return` on adjoin elements.
109
+ Two method changes asked for by the case owner and one fix. Schema 0.3 stays; the new field is optional and old records stay valid. The first case's five boards validate as before (0 errors, 150 warnings); hints go from 143 to 156, the 13 new ones being `move-return` on adjoin elements.
98
110
 
99
111
  - Move field `return` (board-set schema, `$defs.move`): the way back, what the move changes in the terms it started from (a decision, a prediction, a test) and what is lost on the way back. New hint `move-return` (→ visionary-tract.md §7, `program-three-boards` only, like `move-via`): an element whose `move` is an `adjoin`, with status `candidate` or `accepted` or none, and no `return`. A `rejected` adjoin, other ops and the moves on theses are not read. The Markdown digest shows `return` after `via` ("way back" / "путь назад"). The board patch schema does not restate move fields and is unchanged.
100
112
  - Docs: `docs/data-model.md` (Moves), `docs/method/structural-moves.md` (new subsection "Way back": the requirement, three examples, pending in the paper's `PENDING_UPDATES.md` as an owner decision), `docs/stages.md`, `docs/checks.md`. `visionary-tract` 0.2.4: each adjoin candidate states its way back; the example carries one.
101
113
  - `qualification-pass` 0.4.2: new classic-checks row "Computability" (A. Moitra quoting K. Jain: "If my laptop can't find it, then neither can the market"): a position, explanation or plan that needs an actor to solve what the actor cannot compute with the information and time it has is weak or unworkable, e.g. assuming a Nash equilibrium. A line in `roles/methodologist.md`. No code.
102
114
  - Test: `test_move_return_asked_of_an_adjoin` in `tests/test_procedure_checks.py`.
103
- - Fix (dz02#l=15): the hint `move-via` read a move's `status` directly, so a move without `status` (the schema does not require it) crashed `smd validate --hints` with a KeyError. A move with no status is now read as a candidate, as `signoffs` reads it; the `move-via` test covers it.
115
+ - Fix: the hint `move-via` read a move's `status` directly, so a move without `status` (the schema does not require it) crashed `smd validate --hints` with a KeyError. A move with no status is now read as a candidate, as `signoffs` reads it; the `move-via` test covers it.
104
116
 
105
- Gate ИСТ1 (the case owner, 1 November 2026, dz01#l=31): the story view is strict. Schema 0.1 stays; the new field is optional.
117
+ The story view is strict (the case owner's decision). Schema 0.1 stays; the new field is optional.
106
118
 
107
119
  - `smd story check` rule S5: every id a sentence cites lies on the story's walk (the `path`, and the ids of `conflict` and `resolution` that lie on it) or is listed in the new optional story field `context`. A cited id that is neither is an error. An id in `context` is still held to the allow-list (G4) and to G1-G3; `context` ids must exist (S1). A story file written before this change can now fail S5: list the off-path ids it cites in `context`.
108
- - S5 counts no `open` hypothesis as on the walk: a sentence that cites one lists it in `context` (dz01#l=35). The four Spectra Coffee stories list the hypotheses they cite.
120
+ - S5 counts no `open` hypothesis as on the walk: a sentence that cites one lists it in `context`. The four Spectra Coffee stories list the hypotheses they cite.
109
121
  - `story.schema.json`: optional `context`, unique ids. Schema version 0.1 is unchanged, as old files stay valid.
110
122
  - `smd story render --md` lists the context ids apart, under a heading of their own (with `--boards`, each with its label).
111
123
  - `docs/stories.md` and `procedures/story.md` (0.2.0) describe the rule and the field. The four Spectra Coffee stories list their off-path ids in `context`; the buyer story has the August gap again (`sig-august`, `nb-qual`).
112
- - Review fixes to S5 (same gate, dz01#l=31: strict, with an explicit `context` list for anything off the path). A `context` id must be in `allow` (G4, an error): `smd story render` prints context ids with their labels, so `context` must not reach a fact the audience may not see. A `context` id that no sentence cites is a warning (S5). Narrower walk: a sentence cites without a `context` entry only ids on the path, the `conflict` and `resolution` ids that are on the path, and the `open` hypotheses; a `conflict` or `resolution` id off the path now needs a `context` entry. The docstring of `story/check.py`, `docs/stories.md` and `procedures/story.md` say the same.
124
+ - Review fixes to S5 (same decision: strict, with an explicit `context` list for anything off the path). A `context` id must be in `allow` (G4, an error): `smd story render` prints context ids with their labels, so `context` must not reach a fact the audience may not see. A `context` id that no sentence cites is a warning (S5). Narrower walk: a sentence cites without a `context` entry only ids on the path, the `conflict` and `resolution` ids that are on the path, and the `open` hypotheses; a `conflict` or `resolution` id off the path now needs a `context` entry. The docstring of `story/check.py`, `docs/stories.md` and `procedures/story.md` say the same.
113
125
  - The four Spectra Coffee stories needed no change to their ids under the narrower walk. They were edited by hand on 2026-11-01 after the procedure run (version 0.2.0 adds `context`); the story schema has no field for that, so each file carries a comment saying so, and its `run` stamp still names the procedure run.
114
126
 
115
127
  ## 0.6.3 - 2026-11-01
116
128
 
117
- Gates Ж1 Б and Ж2 Б (the case owner, 1 November 2026): the engine's formal stance and its six robustness rules. Schema 0.3 stays; every new field is optional and old records stay valid. The first case's five boards validate as before (0 errors, 150 warnings, 143 hints) and so do the eight example records.
129
+ The engine's formal stance and its six robustness rules (the case owner's decision). Schema 0.3 stays; every new field is optional and old records stay valid. The first case's five boards validate as before (0 errors, 150 warnings, 143 hints) and so do the eight example records.
118
130
 
119
- Gate ИСТ1 Б (1 November 2026) adds the story view, a checked view over the boards that is never a record. A board patch can also set fields on a relation, and the renders show what a flow carries. The three changes are separate and backward compatible; the first bullets below are the robustness rules, then the story view, then the patches and renders.
131
+ A second decision adds the story view, a checked view over the boards that is never a record. A board patch can also set fields on a relation, and the renders show what a flow carries. The three changes are separate and backward compatible; the first bullets below are the robustness rules, then the story view, then the patches and renders.
120
132
 
121
- - `docs/method/formal-stance.md` (gate Ж1 Б): formulas attach only to components marked `nature: natural`; answers are sets (consistency, corridors, regimes), never trajectory forecasts; artificial components get design mathematics; grounds (G.P. 1988, GP-T5 p. 251, as the hint `ought-without-fact` cites it; Lucas 1976; Grunberg and Modigliani 1954; Dekel, Lipman and Rustichini 1998, all marked unverified). `docs/method/robustness-rules.md` states R1-R6 and audits the numeric code; both linked from `docs/method/README.md`.
133
+ - `docs/method/formal-stance.md`: formulas attach only to components marked `nature: natural`; answers are sets (consistency, corridors, regimes), never trajectory forecasts; artificial components get design mathematics; grounds (G.P. 1988, GP-T5 p. 251, as the hint `ought-without-fact` cites it; Lucas 1976; Grunberg and Modigliani 1954; Dekel, Lipman and Rustichini 1998, all marked unverified). `docs/method/robustness-rules.md` states R1-R6 and audits the numeric code; both linked from `docs/method/README.md`.
122
134
  - R1 domain: `rule.domain` (named numeric ranges) and `rule.assumptions`, `observed.sample`. New verdict outcome `outside_domain` (a sample range not inside the domain; no reading) and a coverage phrase when the sample lies inside but covers part. New hint `domain-sample` (→ field-result.md §0.2) for an `observed` with no `sample` or one that omits a name of the domain. Errors: a reversed range; warnings: a sample name the domain lacks, a recorded result on a sample outside the domain.
123
135
  - R3: `agree.alpha_nominal` returns alpha `None` with a reason when the expected disagreement is not above 0, instead of dividing by it; boundary tests for `wilson` (k = 0, k = n, n = 1) and alpha. The rest of the numeric code was audited and needed no change (`docs/method/robustness-rules.md`).
124
136
  - R4 fragility: every share verdict reports `flips`, the smallest number of the n observations whose recoding changes the outcome (Fragility Index). `observed.unknown` (cases with a missing outcome) adds the verdict with none and with all of them counted, k/(n+m) and (k+m)/(n+m), Wilson on n+m (Manski bounds). Shown in the verdict hint, `smd status` and the SessionFlow export (Russian and English; `verdict.detail_text`). The exact text of the verdict hint gains a clause, so `tests/test_hypothesis_standard.py` expects it. `observed_text` shows `unknown`.
125
137
  - R5: hypotheses take `rivals` (ids of other hypotheses; an unknown or own id is an error); no averaging, no weights. The proposed hint on a model with rates that have no source is not built: the schema has no rates.
126
138
  - R6: `line-without-recovery` now covers every element with `red_line: true` as well as algedonic channels with a value, and is enabled on all three profiles (it named kinds and a relation of the management profile before). The address is an `escalates` relation to a post, position or place for others; on a profile without `escalates` it is a `flow` with `carries: information` to one (`management-four-boards` keeps `escalates` only). `recovery_time` is now allowed on any element with `red_line: true`, as `threshold` is. `rl-unsold` in `bakeries-c2` and `pekarni-c2` sends its nightly report to the owner, so the examples get no hint. New hint `surprise` (→ field-result.md §3): a hypothesis in `testing` refuted by its `observed` and, on the same count and metric, by every rival proposes a dated `signal` (a `note` where the profile has no signal kind) with `escaped: [ids]`; elements take optional `escaped` and `date` (only together; errors otherwise). New `tests/test_robustness.py` (21 tests); `tests/test_beer_layer.py` uses `absorbed-into-system-1` to test the refusal of a hint whose kinds a profile lacks.
127
139
  - `docs/hypotheses.md` holds the hypothesis fields, moved out of `docs/data-model.md` (it had reached 296 lines), with the robustness fields. `field-result` 0.3.3 (section 0.2 and section 3) names the new fields and the surprise.
128
- - Gate ИСТ1 Б (the case owner, 1 November 2026), stories as a checked view over the boards, never a record and never signed. `smd story paths`: walks over typed links from a protagonist through a conflict object (`opposes`, normality boundary, series of linked events, red line in breach) to a resolution object, ordered without weights; `--gaps` lists where no typed walk exists and the links that would make one; `--yaml` prints story skeletons.
140
+ - Stories as a checked view over the boards, never a record and never signed (the case owner's decision). `smd story paths`: walks over typed links from a protagonist through a conflict object (`opposes`, normality boundary, series of linked events, red line in breach) to a resolution object, ordered without weights; `--gaps` lists where no typed walk exists and the links that would make one; `--yaml` prints story skeletons.
129
141
  - `smd story check`: checks a story file against G1-G7 (ids, levels, numbers including compound Russian number words, whole dates, allow-list, dropped oppositions, comparatives, voice and board stamp) and S1-S4 (path structure). New record `story` (`story.schema.json`, schema 0.1, `*.story.yaml`), read by `smd validate`.
130
142
  - `smd story render <story.yaml> --md`: a story as readable Markdown with the board ids of each sentence in brackets. `smd story paths`, `check` and `render` take `--sources` and `--taxonomies`.
131
143
  - Procedure `story` and `docs/stories.md`.
@@ -135,20 +147,20 @@ Gate ИСТ1 Б (1 November 2026) adds the story view, a checked view over the b
135
147
 
136
148
  ## 0.6.2 - 2026-10-31
137
149
 
138
- Gate ОТП1 В (the case owner, 31.10): a board carries the parts of a split hypothesis, as the group's hypothesis matrix does. Schema 0.3 stays; old records stay valid.
150
+ A board carries the parts of a split hypothesis, as the group's hypothesis matrix does (the case owner's decision). Schema 0.3 stays; old records stay valid.
139
151
 
140
- - A hypothesis split into parts keeps its number and adds one lowercase Latin letter: `H2a`, `H2b` (gate ОТП1 В, the case owner 31.10: the group's hypothesis matrix splits composite hypotheses into parts, each with one type). The board schema accepts `^H[0-9]+[a-z]?$` for a hypothesis `id` and an ontology record's `test`, and the patch schema accepts it for an item id, so a patch can remove `H2` and add `H2a` and `H2b`. Old records stay valid. `docs/data-model.md` gives the rule.
152
+ - A hypothesis split into parts keeps its number and adds one lowercase Latin letter: `H2a`, `H2b` (the case owner's decision: the group's hypothesis matrix splits composite hypotheses into parts, each with one type). The board schema accepts `^H[0-9]+[a-z]?$` for a hypothesis `id` and an ontology record's `test`, and the patch schema accepts it for an item id, so a patch can remove `H2` and add `H2a` and `H2b`. Old records stay valid. `docs/data-model.md` gives the rule.
141
153
  - The changelog of 0.2.0-0.5.9 moved to `docs/changelog-0.2-0.5.md` (this file had passed 300 lines).
142
154
 
143
155
  ## 0.6.1 - 2026-10-31
144
156
 
145
- Follow-ups of 0.6.0 and two gates of 31.10: AI on roles and functions (ИИ1 Б) and structured red lines with observed values (КЛ1 В, with dates as decided 31.10). Schema 0.3 stays; every new field is optional and old records stay valid.
157
+ Follow-ups of 0.6.0 and two decisions of the case owner: AI on roles and functions, and structured red lines with observed values (with dates, as decided). Schema 0.3 stays; every new field is optional and old records stay valid.
146
158
 
147
- Follow-ups of the 0.6.0 reviews. The schema gains one optional field, `carries` on a `flow` (additive: old records stay valid), and `function-flows` reads it; a record that sets none reports as before. Gate ИИ1 Б adds two optional element fields, `ai` and `red_line`, and gate КЛ1 В two more, `line` and `observed` (additive, schema stays 0.3).
159
+ Follow-ups of the 0.6.0 reviews. The schema gains one optional field, `carries` on a `flow` (additive: old records stay valid), and `function-flows` reads it; a record that sets none reports as before. AI on the boards adds two optional element fields, `ai` and `red_line`, and the structured red lines two more, `line` and `observed` (additive, schema stays 0.3).
148
160
 
149
- - Red lines with a structured value (gate КЛ1 В, the case owner 31.10: «should the red_line threshold be a period (min;max)?», answered В; dates instead of a term in years). An element with `red_line: true`, or an `algedonic_channel`, takes `line`: `metric`, `unit`, a corridor (`min` and/or `max`, one-sided allowed) or a yes/no (`expect`), `since` (optional; the record's `date` when absent), `until` (required) and `recovery_days`. Errors: both a corridor and `expect`, or neither; `min` not below `max`; `until` not after the start; `recovery_days` and the channel's `recovery_time` both set and different; `line` on an element that is no red line. The free-text `threshold` stays as a fallback; `red-line-without-value` accepts either. Observations sit on the same element, `observed: [{value, date, source}]`: a value of the wrong type for the line is an error, a source not of kind `field_artefact` a warning (with a manifest). New `src/smd_engine/redline.py` holds the deterministic breach rule (observations from the line's start to `until`, sorted by date; a run of outside values spans to the next inside value, or, still open, to the later of the last observation and the record's `date`, never past `until`; a breach when longer than `recovery_days`, else `recovery_time`, any run when neither is set). Warnings: observations before the line takes force, and two on one date. The schema requires `metric` with `expect`. Numbers on the pages are plain digits (in Russian, a thin space between thousands and a decimal comma). New hints, all profiles: `red-line-breach` and `red-line-expired` (observations or the record dated after `until`; → field-result.md §5) and `red-line-outlives-pace` (the line's span in years longer than the `pace` of an element it is linked to, the analogue of `ontology-outlives-pace`; the case owner 26.10, H24; → functional-plan.md §4). New `validate/redlines.py`; the linking used by `ai-decision-unanswered` moved there and now reads `in` and `performed_by` both ways. The management hint `line-without-recovery` reads `line` too: a channel has a value when it has `threshold` or `line`, and a recovery time when it has `recovery_time` or `line.recovery_days`. `smd status` lists the red lines with a breach. The page, the digest, the index, the graph details and the frames details show the line in words («доля ФОТ от 18 до 25 %, с 01.01.2027 по 31.12.2031, восстановление 90 дней») and the last observation («27 % на 01.03.2027, вне коридора»). `bakeries-c2` and `pekarni-c2` carry the owner's red line `rl-unsold` (unsold dough at most 5 % of the night's volume, 01.03.2026 to 28.02.2027, recovery 14 days), with no observations; `--strict` stays 0/0. New `docs/red-lines.md` (the fields, the rule, the words), linked from `docs/data-model.md` and `docs/README.md`; `field-result` 0.3.2 gains section 5 (red lines from observations); `functional-plan` section 4, `docs/checks.md`, `docs/commands.md`.
161
+ - Red lines with a structured value (the case owner's decision: the red_line threshold may be a period (min; max), with dates instead of a term in years). An element with `red_line: true`, or an `algedonic_channel`, takes `line`: `metric`, `unit`, a corridor (`min` and/or `max`, one-sided allowed) or a yes/no (`expect`), `since` (optional; the record's `date` when absent), `until` (required) and `recovery_days`. Errors: both a corridor and `expect`, or neither; `min` not below `max`; `until` not after the start; `recovery_days` and the channel's `recovery_time` both set and different; `line` on an element that is no red line. The free-text `threshold` stays as a fallback; `red-line-without-value` accepts either. Observations sit on the same element, `observed: [{value, date, source}]`: a value of the wrong type for the line is an error, a source not of kind `field_artefact` a warning (with a manifest). New `src/smd_engine/redline.py` holds the deterministic breach rule (observations from the line's start to `until`, sorted by date; a run of outside values spans to the next inside value, or, still open, to the later of the last observation and the record's `date`, never past `until`; a breach when longer than `recovery_days`, else `recovery_time`, any run when neither is set). Warnings: observations before the line takes force, and two on one date. The schema requires `metric` with `expect`. Numbers on the pages are plain digits (in Russian, a thin space between thousands and a decimal comma). New hints, all profiles: `red-line-breach` and `red-line-expired` (observations or the record dated after `until`; → field-result.md §5) and `red-line-outlives-pace` (the line's span in years longer than the `pace` of an element it is linked to, the analogue of `ontology-outlives-pace`; the case owner's decision; → functional-plan.md §4). New `validate/redlines.py`; the linking used by `ai-decision-unanswered` moved there and now reads `in` and `performed_by` both ways. The management hint `line-without-recovery` reads `line` too: a channel has a value when it has `threshold` or `line`, and a recovery time when it has `recovery_time` or `line.recovery_days`. `smd status` lists the red lines with a breach. The page, the digest, the index, the graph details and the frames details show the line in words («доля ФОТ от 18 до 25 %, с 01.01.2027 по 31.12.2031, восстановление 90 дней») and the last observation («27 % на 01.03.2027, вне коридора»). `bakeries-c2` and `pekarni-c2` carry the owner's red line `rl-unsold` (unsold dough at most 5 % of the night's volume, 01.03.2026 to 28.02.2027, recovery 14 days), with no observations; `--strict` stays 0/0. New `docs/red-lines.md` (the fields, the rule, the words), linked from `docs/data-model.md` and `docs/README.md`; `field-result` 0.3.2 gains section 5 (red lines from observations); `functional-plan` section 4, `docs/checks.md`, `docs/commands.md`.
150
162
 
151
- - AI on the boards (gate ИИ1 Б, the case owner 31.10: "should flows include 'intelligence'? when AI is used", answered Б). AI is not a new `carries` value: an AI agent is an actor in `fillers`, and what it produces moves as information or product. Roles (kinds a profile flags `role`; a gap only with `of: position`) and functions take an optional `ai`: `assists` («ИИ помогает») or `performs` («выполняет ИИ»); anywhere else it is an error. A function's effective `ai` is its own, else that of the role in its `performed_by`. Elements take an optional `red_line: true` (agreed by the case owner, 31.10; refused on kinds flagged `light_off`: notes, and facts and signals on the default profile); its value, a threshold or yes/no, goes in `threshold`, now allowed on any red-line element, and the new hint `red-line-without-value` (all profiles, → functional-plan.md §4) names one without. An `algedonic_channel` with a `threshold` is a red line without it. `escalates` gains a second use: from a function to the role that answers for it at a red line. New hint `ai-decision-unanswered` (all three profiles, → functional-plan.md §3; new `validate/ai.py`): a function AI performs, linked to a red line (itself one, `in` one, performed by a red-line role, or joined to one by a relation of any kind), for which no role without `ai: performs` answers by `performed_by`, `subordinates` (role to function), `escalates` or a `flow` with `carries: information` (function to role); the case behind it is a hypothesis of the first case. `smd status` (counts) and `smd index` (top of the page) print «функции: выполняет ИИ n, ИИ помогает k, из m» when any element has `ai`, nothing otherwise. The page, the digest, the index, the graph details and the frames details show `ai` and `red_line` in words (`LABELS`). `fn-dough` in `bakeries-c2` and `pekarni-c2` has `ai: assists` (the night's volume planned with an AI demand forecast; the organiser decides); `--strict` stays 0/0. The first case has no `ai` and gets no new finding (0 errors, 150 warnings). `functional-plan` 0.2.7 (section 3) and `positional-construction` 0.2.8 (section 2) say where `ai` goes; `docs/method/roles-and-actors.md` gains "AI as an actor"; `docs/data-model.md`, `docs/checks.md`, `docs/commands.md`.
163
+ - AI on the boards (the case owner's decision on whether flows should include "intelligence" when AI is used). AI is not a new `carries` value: an AI agent is an actor in `fillers`, and what it produces moves as information or product. Roles (kinds a profile flags `role`; a gap only with `of: position`) and functions take an optional `ai`: `assists` («ИИ помогает») or `performs` («выполняет ИИ»); anywhere else it is an error. A function's effective `ai` is its own, else that of the role in its `performed_by`. Elements take an optional `red_line: true` (agreed by the case owner; refused on kinds flagged `light_off`: notes, and facts and signals on the default profile); its value, a threshold or yes/no, goes in `threshold`, now allowed on any red-line element, and the new hint `red-line-without-value` (all profiles, → functional-plan.md §4) names one without. An `algedonic_channel` with a `threshold` is a red line without it. `escalates` gains a second use: from a function to the role that answers for it at a red line. New hint `ai-decision-unanswered` (all three profiles, → functional-plan.md §3; new `validate/ai.py`): a function AI performs, linked to a red line (itself one, `in` one, performed by a red-line role, or joined to one by a relation of any kind), for which no role without `ai: performs` answers by `performed_by`, `subordinates` (role to function), `escalates` or a `flow` with `carries: information` (function to role); the case behind it is a hypothesis of the first case. `smd status` (counts) and `smd index` (top of the page) print «функции: выполняет ИИ n, ИИ помогает k, из m» when any element has `ai`, nothing otherwise. The page, the digest, the index, the graph details and the frames details show `ai` and `red_line` in words (`LABELS`). `fn-dough` in `bakeries-c2` and `pekarni-c2` has `ai: assists` (the night's volume planned with an AI demand forecast; the organiser decides); `--strict` stays 0/0. The first case has no `ai` and gets no new finding (0 errors, 150 warnings). `functional-plan` 0.2.7 (section 3) and `positional-construction` 0.2.8 (section 2) say where `ai` goes; `docs/method/roles-and-actors.md` gains "AI as an actor"; `docs/data-model.md`, `docs/checks.md`, `docs/commands.md`.
152
164
 
153
165
  - Example cases draw a clean functional plan. The hint `function-flows` fired on every function of `f-new` in `bakeries-c1`, `bakeries-c2`, `two-boards-c1`, `pekarni-c1`, `pekarni-c2` and the golden record `bakeries-c2-expected` (found by running `smd validate --hints` on every record under `cases/`; the two management-profile records do not enable it). `bakeries-c2` and `pekarni-c2` now draw the `flow` relations the story states (mills supply flour into the dough, the owner pays per tonne and receives the dough, dough goes to logistics, the owner pays inside the dough price for now and receives it before four in the morning); `two-boards-c1` draws flour, the dough and the delivery to the owner and links the open `gap-payer` to both functions. `bakeries-c1` and `pekarni-c1` are cycle 1, where K2 says nobody yet performs or pays: they draw the flour and the chain dough, quality standard, logistics, and leave the payer and the receiver as gaps (`gap-payer`, and a new `gap-receiver`, `of: position`) linked to each function by `refers`. `function-flows` and `unlinked-functions` are silent on all five; the hints left in cycle 1 (`performed_by`, `idle-positions`) are K2 itself. The golden record is unchanged, and its README says why. `tests/test_procedure_checks.py` checks the five records.
154
166
  - Relations of kind `flow` take an optional `carries` (`money`, `material`, `product`, `information`; schema additive, old records stay valid; words in both languages in `LABELS`, shown in the Markdown digest). `function-flows` reads a payer as an incoming flow of `money` from a position or place, an input as an incoming flow of anything but money, and a receiver as an outgoing flow of anything but money to a position or place, so a supplier (mills with flour) is no longer a payer. A receiver is also a non-money flow to a later function of the same frame that has one (followed along the chain, cycles walked once), so a middle function needs no direct line; on the first case's cycle 5 the function-flow hints go from 10 to 7. A flow with no `carries` is read as before for payer and input; the hint's wording names `carries: money`. All flows of the example cases set `carries`. `functional-plan` 0.2.6 asks for it (section 4). `docs/checks.md`, `docs/data-model.md`.
@@ -163,11 +175,11 @@ Follow-ups of the 0.6.0 reviews. The schema gains one optional field, `carries`
163
175
 
164
176
  ## 0.6.0 - 2026-10-31
165
177
 
166
- Method review of 31.10 (gates М1 В, Ф В, У В): reproducible runs, deterministic checks for rules the procedures asked a model to check by hand, a typed standard for hypotheses with a pre-registered decision rule, and a shorter path for new users. Schema 0.3 stays; every new field is optional and old records stay valid.
178
+ Method review of 31.10: reproducible runs, deterministic checks for rules the procedures asked a model to check by hand, a typed standard for hypotheses with a pre-registered decision rule, and a shorter path for new users. Schema 0.3 stays; every new field is optional and old records stay valid.
167
179
 
168
- - Hypothesis standard (method review 31.10, gates М1 В and Ф В, formal audit proposal 6). Three optional hypothesis fields, additive (schema stays 0.3, old records stay valid): `type` (`core`, `product`, `claim`, `estimate`, `probe`, `design`: how the hypothesis is read), `rule` (`{metric, op, threshold, n_min, basis}`: the pre-registered decision rule, a structured `revise_if`; `op` states the refutation condition) and `observed` (`{k, n, artefact}`). New `src/smd_engine/verdict.py`: the 95% Wilson score interval of k/n (Wilson 1927; reproduces 0.2553-0.3662 for 81/263, Newcombe 1998) and a proposed verdict for an untested or testing hypothesis when the threshold is a share strictly between 0 and 1 (`op` is `<`, `<=`, `>` or `>=`): too few (n below `n_min`), refuted, confirmed, or inconclusive (the interval straddles the threshold). The proposal is a hint (`verdict`) and a section of `smd status`; the sign-off stays human. New error: k greater than n; new warnings: a recorded result opposite to the proposal, and (with a manifest) an `observed.artefact` that is not of kind `field_artefact`; `validate_record` takes the manifest's kinds as `source_kinds`. New hints `hypothesis-type`, `hypothesis-rule`, `rule-basis`, `rule-n-min`, `type-status` (`docs/checks.md`), enabled on all three profiles; `revise-if` accepts a `rule` and leaves out claims and estimates (they get `hypothesis-rule`) and cores, designs and probes. The first case has no typed hypothesis and gets no new finding. Labels of the fields and of the six types in both languages; the page, the digest, the index and the graph show them under the hypothesis. `field-result` 0.3.0 gains section 0 (the six types and how each is read; the decision rule and the interval) and reads the proposal in section 3; `small-situation` 0.2.3 (section 4) gives each new H a `type`, and a claim or estimate a `rule` with its `basis`.
169
- - `smd agree <record> <record> [...] [--fields ...] [--json]` (the audit of 31.10, proposal 4, gate Ф В): how stable are the labels a procedure writes. Takes N runs of one procedure on one input; warns, and goes on, when `run.procedure`, `run.pack_sha256` or `run.inputs` differ or are missing. Theses are matched across runs by the address they cite (the matching of `smd eval`, generalised to N runs); elements of the first record are matched in the other runs as `smd compare` matches them. For `belt`, `kind`, `status`, `voice`, `of` and the move `op` of theses, and `kind`, `of` and `op` of elements, it prints Krippendorff's alpha (nominal, any number of runs, missing values allowed; written in the new `agree.py` from the coincidence matrix, no new dependency; `n/a` with the reason when only one value occurs), the share of cite addresses found by all, some or one run with the one-run-only addresses, and a reading by Krippendorff's conventional cut-offs (0.800, 0.667), stated as a convention; a field with fewer than five pairable units shows its alpha with "few units" and is left out of the reading line. The alpha code reproduces the 0.743 of Krippendorff's 2011 worked example. `eval` is unchanged. `docs/commands.md` and the golden README describe it.
170
- - `smd new <folder> [--profile] [--lang] [--case] [--title]` (UX audit of 31.10, gate У В): scaffolds a case folder that validates at once, `smd validate --strict` giving 0 errors and 0 warnings on every profile: `<case>-c1.board.yaml` (required fields, `profile`, an entry where the profile has the kind, one position to rename, empty lists), a `sources.yaml` skeleton with one entry, and a README naming the first procedure (`small-situation` on the default profile, `positional-construction` on the others). It refuses, writing nothing, if a file exists. `docs/first-board.md` starts from it.
180
+ - Hypothesis standard (method review 31.10, formal audit proposal 6). Three optional hypothesis fields, additive (schema stays 0.3, old records stay valid): `type` (`core`, `product`, `claim`, `estimate`, `probe`, `design`: how the hypothesis is read), `rule` (`{metric, op, threshold, n_min, basis}`: the pre-registered decision rule, a structured `revise_if`; `op` states the refutation condition) and `observed` (`{k, n, artefact}`). New `src/smd_engine/verdict.py`: the 95% Wilson score interval of k/n (Wilson 1927; reproduces 0.2553-0.3662 for 81/263, Newcombe 1998) and a proposed verdict for an untested or testing hypothesis when the threshold is a share strictly between 0 and 1 (`op` is `<`, `<=`, `>` or `>=`): too few (n below `n_min`), refuted, confirmed, or inconclusive (the interval straddles the threshold). The proposal is a hint (`verdict`) and a section of `smd status`; the sign-off stays human. New error: k greater than n; new warnings: a recorded result opposite to the proposal, and (with a manifest) an `observed.artefact` that is not of kind `field_artefact`; `validate_record` takes the manifest's kinds as `source_kinds`. New hints `hypothesis-type`, `hypothesis-rule`, `rule-basis`, `rule-n-min`, `type-status` (`docs/checks.md`), enabled on all three profiles; `revise-if` accepts a `rule` and leaves out claims and estimates (they get `hypothesis-rule`) and cores, designs and probes. The first case has no typed hypothesis and gets no new finding. Labels of the fields and of the six types in both languages; the page, the digest, the index and the graph show them under the hypothesis. `field-result` 0.3.0 gains section 0 (the six types and how each is read; the decision rule and the interval) and reads the proposal in section 3; `small-situation` 0.2.3 (section 4) gives each new H a `type`, and a claim or estimate a `rule` with its `basis`.
181
+ - `smd agree <record> <record> [...] [--fields ...] [--json]` (the audit of 31.10, proposal 4): how stable are the labels a procedure writes. Takes N runs of one procedure on one input; warns, and goes on, when `run.procedure`, `run.pack_sha256` or `run.inputs` differ or are missing. Theses are matched across runs by the address they cite (the matching of `smd eval`, generalised to N runs); elements of the first record are matched in the other runs as `smd compare` matches them. For `belt`, `kind`, `status`, `voice`, `of` and the move `op` of theses, and `kind`, `of` and `op` of elements, it prints Krippendorff's alpha (nominal, any number of runs, missing values allowed; written in the new `agree.py` from the coincidence matrix, no new dependency; `n/a` with the reason when only one value occurs), the share of cite addresses found by all, some or one run with the one-run-only addresses, and a reading by Krippendorff's conventional cut-offs (0.800, 0.667), stated as a convention; a field with fewer than five pairable units shows its alpha with "few units" and is left out of the reading line. The alpha code reproduces the 0.743 of Krippendorff's 2011 worked example. `eval` is unchanged. `docs/commands.md` and the golden README describe it.
182
+ - `smd new <folder> [--profile] [--lang] [--case] [--title]` (UX audit of 31.10): scaffolds a case folder that validates at once, `smd validate --strict` giving 0 errors and 0 warnings on every profile: `<case>-c1.board.yaml` (required fields, `profile`, an entry where the profile has the kind, one position to rename, empty lists), a `sources.yaml` skeleton with one entry, and a README naming the first procedure (`small-situation` on the default profile, `positional-construction` on the others). It refuses, writing nothing, if a file exists. `docs/first-board.md` starts from it.
171
183
  - `smd status <record> [--lang] [-o file.md]`: the core view of a board set on one page of Markdown (46 lines for the first case's cycle 5): state line, K not closed, hypotheses in testing and untested ones in leverage order, AI-voiced items waiting for a sign-off, transitions, counts per board and kind; lists are cut with "and N more". New `LABELS[...]["core"]` words in both languages.
172
184
  - `smd next <record>`: the procedure to run next with one line why and at most two alternatives, by the rule table `RULES` in `src/smd_engine/nextstep.py` (written out in `docs/commands.md`); procedures of another profile are skipped; "no rule fires" is an answer.
173
185
  - Hypothesis leverage (formal audit, section 4 row 5): for each untested hypothesis the size of what a refutation would reach (targets, K, ontology records testing it, theses on its targets, elements one relation away); a proposal, the group chooses. Listed by `smd status`, and a column "reach (proposal)" in the hypotheses table of `smd index`.
@@ -183,7 +195,7 @@ Method review of 31.10 (gates М1 В, Ф В, У В): reproducible runs, determin
183
195
  - `positional-construction` 0.2.6 (section 5) and `solo-session` 0.2.3 (section 3) point to it; `stakeholder-ontology` uses the full form "six-tier ontology of a business" at first use.
184
196
  - `procedures/README.md`, `lenses/README.md` (selection table: no lens offered) and `docs/method/roles-and-actors.md` (where the role rule is applied) list the new procedure.
185
197
 
186
- - Method review 31.10.2026 (gates Ф В and У В): rules the procedures asked the model to check by hand, which are exact graph or set conditions on the record, are now checks of the validator (`docs/checks.md`).
198
+ - Method review 31.10.2026: rules the procedures asked the model to check by hand, which are exact graph or set conditions on the record, are now checks of the validator (`docs/checks.md`).
187
199
  - New errors: a cycle of `belongs`, of `subordinates`, or of move sources (`move.from` of elements and theses). A cycle of `flow` is legitimate and is not checked.
188
200
  - New warning: an ontology position of `valid_for` with no line in `subjects` (the reverse of the existing warning).
189
201
  - New hints of the functional plan (functional-plan.md §4): `function-flows` (a function in a new frame with no payer, input or receiver `flow`, unless a gap with the matching `of` is linked to it), `unlinked-functions`, `idle-positions`.
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.5
2
2
  Name: smd-engine
3
- Version: 0.7.7
3
+ Version: 0.7.9
4
4
  Summary: Records, checks and renderings for SMD-style thinking sessions (three boards, cycles, qualifications)
5
5
  Project-URL: Homepage, https://github.com/viberesearch/smd-engine
6
6
  Project-URL: Repository, https://github.com/viberesearch/smd-engine
@@ -39,7 +39,7 @@ New here? Start with [docs/first-board.md](docs/first-board.md), a walkthrough f
39
39
 
40
40
  The default screen is the three-board screen of the MIPT program "Третья ступень" (org-activity, object and situation boards). A profile can lay out other boards: `classic-two-boards` is the classic org-activity and object-ontological pair. Terms that belong to the program and not to the classic method are marked as such in `roles/README.md`.
41
41
 
42
- Version 0.7.7 (`pyproject.toml`), schema 0.3. Python 3.14. The engine proposes and checks; a human decides, by sign-offs that each state a function.
42
+ Version 0.7.9 (`pyproject.toml`), schema 0.3. Python 3.14. The engine proposes and checks; a human decides, by sign-offs that each state a function.
43
43
 
44
44
  ## Install
45
45
 
@@ -150,7 +150,7 @@ A real case lives in the repository of its object of thinking; this repository h
150
150
  It runs the engine without a local copy, pinned to a release, for example in CI:
151
151
 
152
152
  ```bash
153
- uvx --from git+https://github.com/viberesearch/smd-engine@v0.7.7 smd validate . --sources sources.yaml --strict
153
+ uvx --from git+https://github.com/viberesearch/smd-engine@v0.7.9 smd validate . --sources sources.yaml --strict
154
154
  ```
155
155
 
156
156
  Generated drawings (`smd publish`) are build output and are not committed. Records of an older schema are moved with `smd migrate`.
@@ -14,7 +14,7 @@ New here? Start with [docs/first-board.md](docs/first-board.md), a walkthrough f
14
14
 
15
15
  The default screen is the three-board screen of the MIPT program "Третья ступень" (org-activity, object and situation boards). A profile can lay out other boards: `classic-two-boards` is the classic org-activity and object-ontological pair. Terms that belong to the program and not to the classic method are marked as such in `roles/README.md`.
16
16
 
17
- Version 0.7.7 (`pyproject.toml`), schema 0.3. Python 3.14. The engine proposes and checks; a human decides, by sign-offs that each state a function.
17
+ Version 0.7.9 (`pyproject.toml`), schema 0.3. Python 3.14. The engine proposes and checks; a human decides, by sign-offs that each state a function.
18
18
 
19
19
  ## Install
20
20
 
@@ -125,7 +125,7 @@ A real case lives in the repository of its object of thinking; this repository h
125
125
  It runs the engine without a local copy, pinned to a release, for example in CI:
126
126
 
127
127
  ```bash
128
- uvx --from git+https://github.com/viberesearch/smd-engine@v0.7.7 smd validate . --sources sources.yaml --strict
128
+ uvx --from git+https://github.com/viberesearch/smd-engine@v0.7.9 smd validate . --sources sources.yaml --strict
129
129
  ```
130
130
 
131
131
  Generated drawings (`smd publish`) are build output and are not committed. Records of an older schema are moved with `smd migrate`.
@@ -16,7 +16,7 @@
16
16
 
17
17
  † - термин программы «Третья ступень», не классической методологии (список ниже, в разделе «Слова программы»).
18
18
 
19
- Версия 0.7.7 (`pyproject.toml`), схема 0.3. Python 3.14. Программа предлагает и проверяет; решает человек, подписями, у каждой из которых названа функция.
19
+ Версия 0.7.9 (`pyproject.toml`), схема 0.3. Python 3.14. Программа предлагает и проверяет; решает человек, подписями, у каждой из которых названа функция.
20
20
 
21
21
  ## Установка
22
22
 
@@ -127,7 +127,7 @@ uv run smd frames cases/example_ru/pekarni-c2.board.yaml -o out/frames.html
127
127
  Движок запускается без локальной копии, с закреплённой версией, например в CI:
128
128
 
129
129
  ```bash
130
- uvx --from git+https://github.com/viberesearch/smd-engine@v0.7.7 smd validate . --sources sources.yaml --strict
130
+ uvx --from git+https://github.com/viberesearch/smd-engine@v0.7.9 smd validate . --sources sources.yaml --strict
131
131
  ```
132
132
 
133
133
  Порождённые рисунки (`smd publish`) - результат сборки, их не коммитят. Записи старой схемы переводят командой `smd migrate`.
@@ -43,7 +43,7 @@ elements:
43
43
  - {id: s-big, board: s, half: big, kind: situation, label: "independent bakeries close",
44
44
  seen_from: p-organiser}
45
45
  - {id: gap-risk, board: oo, kind: gap, label: "who carries unsold dough?", of: position}
46
- # A red line the owner sets for the pilot season (gate КЛ1 В, docs/red-lines.md); no
46
+ # A red line the owner sets for the pilot season (docs/red-lines.md); no
47
47
  # observations yet: the nightly reports start with the plant.
48
48
  - id: rl-unsold
49
49
  board: oo
@@ -43,7 +43,7 @@ elements:
43
43
  - {id: s-big, board: s, half: big, kind: situation, label: "независимые пекарни закрываются",
44
44
  seen_from: p-organiser}
45
45
  - {id: gap-risk, board: oo, kind: gap, label: "кто несёт риск непроданного теста?", of: position}
46
- # Красная линия владельца на пилотный сезон (ворота КЛ1 В, docs/red-lines.md); наблюдений
46
+ # Красная линия владельца на пилотный сезон (docs/red-lines.md); наблюдений
47
47
  # пока нет: ночные отчёты начнутся вместе с цехом.
48
48
  - id: rl-unsold
49
49
  board: oo
@@ -37,7 +37,7 @@ The six tiers of the OST ontology (intent, business model, business entity, prod
37
37
 
38
38
  | Tier | What the specification has | What this case adds |
39
39
  |---|---|---|
40
- | 1 intent (of each position; here the founder's, the controlling one) | nothing. The mission and values in the identity file are the shop's declared mission, not the owner's programme | the goal `goal-handover`, the founder's red line, the shareable ontology `O1` |
40
+ | 1 intent, «намерение» (of each position; here the founder's is the controlling instance, «замысел собственника») | nothing. The mission and values in the identity file are the shop's declared mission, not the owner's programme | the goal `goal-handover`, the founder's red line, the shareable ontology `O1` |
41
41
  | 2 business model | L0 (target cohort, desired perception), prices and margins of L3 | `m-model`, an unchecked revenue estimate, `fact-price` |
42
42
  | 3 business entity | nothing about the legal person. Supplier and sourcing requirements (L4, L5) touch contracts | trademark held by the founder, lease with a change-of-control consent, the buyer and the bank |
43
43
  | 4 product | L3 product specifications (6 items; their cost and price are tier 2) | `fn-shot`, `fact-spec` |
@@ -5,7 +5,7 @@ schema_version: "0.1"
5
5
  id: spectra-bank-scqa
6
6
  title: "Вымышленный пример: история для банка покупателя «Спектры Кофе», SCQA, черновик ИИ"
7
7
  boards:
8
- - {id: spectra-coffee-c1, version: "1.0.2", sha256: d82b1a87cc3bda9e88ae003f9e7e5a90fc48252040191154501aa6c069d08928}
8
+ - {id: spectra-coffee-c1, version: "1.0.3", sha256: 38217d92a7e923a824aa32caa99d404fe70db996e3921cedbe597c28893dc136}
9
9
  audience: place-bank
10
10
  protagonist: place-bank
11
11
  form: scqa
@@ -6,7 +6,7 @@ schema_version: "0.1"
6
6
  id: spectra-buyer-scqa
7
7
  title: "Вымышленный пример: история для покупателя «Спектры Кофе», SCQA, черновик ИИ"
8
8
  boards:
9
- - {id: spectra-coffee-c1, version: "1.0.2", sha256: d82b1a87cc3bda9e88ae003f9e7e5a90fc48252040191154501aa6c069d08928}
9
+ - {id: spectra-coffee-c1, version: "1.0.3", sha256: 38217d92a7e923a824aa32caa99d404fe70db996e3921cedbe597c28893dc136}
10
10
  audience: place-buyer
11
11
  protagonist: place-buyer
12
12
  form: scqa
@@ -6,7 +6,7 @@ schema_version: "0.1"
6
6
  id: spectra-owner-scqa
7
7
  title: "Вымышленный пример: история для основателя «Спектры Кофе», SCQA, черновик ИИ"
8
8
  boards:
9
- - {id: spectra-coffee-c1, version: "1.0.2", sha256: d82b1a87cc3bda9e88ae003f9e7e5a90fc48252040191154501aa6c069d08928}
9
+ - {id: spectra-coffee-c1, version: "1.0.3", sha256: 38217d92a7e923a824aa32caa99d404fe70db996e3921cedbe597c28893dc136}
10
10
  audience: p-founder
11
11
  protagonist: p-founder
12
12
  form: scqa
@@ -2,11 +2,12 @@
2
2
  # и банк выдуманы. Цифры меню, ролей и контрольных точек взяты из публичной
3
3
  # демонстрационной спецификации (источник s-spec), которая сама описывает вымышленное
4
4
  # предприятие; всё остальное придумано и помечено lineage: [fictional], voice: ai.
5
- # Доски собраны по шести уровням OST (замысел, модель, юридическое лицо, продукт,
5
+ # Доски собраны по шести уровням OST (намерение, модель, юридическое лицо, продукт,
6
6
  # процесс, организация): теги tier. Слои L0-L5 спецификации не те же самые: см. README.md.
7
7
  # Уровень записи — уровень поля её параметра: цена и маржа (fact-price) — модель бизнеса
8
8
  # (правка 1.0.1, 09.11.2026; было «продукт»). Правка 1.0.2: уровень 3 называется
9
9
  # «юридическое лицо» (было «юрлицо и права»).
10
+ # Правка 1.0.3: уровень 1 называется «намерение» (было «замысел»).
10
11
  record: board_set
11
12
  schema_version: "0.3"
12
13
  id: spectra-coffee-c1
@@ -278,7 +279,7 @@ signoffs:
278
279
  - {function: accept_result, target: H4, by: group, cycle: 1, date: "2026-10-31",
279
280
  note: "вымышленная подпись: отчёт о запуске второго кафе сверен со спецификацией"}
280
281
  state:
281
- version: "1.0.2"
282
+ version: "1.0.3"
282
283
  difficulty: "карта первая; порядок настройки помола держится на основателе"
283
284
  accepted: ["H4 подтверждена вымышленной подписью"]
284
285
  open: ["K1", "K2", "H1", "H2", "H3", "H5"]
@@ -6,7 +6,7 @@ schema_version: "0.1"
6
6
  id: spectra-successor-premortem
7
7
  title: "Вымышленный пример: премортем для будущего управляющего «Спектры Кофе», черновик ИИ"
8
8
  boards:
9
- - {id: spectra-coffee-c1, version: "1.0.2", sha256: d82b1a87cc3bda9e88ae003f9e7e5a90fc48252040191154501aa6c069d08928}
9
+ - {id: spectra-coffee-c1, version: "1.0.3", sha256: 38217d92a7e923a824aa32caa99d404fe70db996e3921cedbe597c28893dc136}
10
10
  audience: place-successor
11
11
  protagonist: place-successor
12
12
  form: premortem
@@ -1,12 +1,12 @@
1
1
  # Значения тегов вымышленного кейса: шесть уровней OST, те же id, что в первом
2
- # реальном кейсе (замысел -> организация). Уровни OST и слои L0-L5 публичной
2
+ # реальном кейсе (намерение -> организация). Уровни OST и слои L0-L5 публичной
3
3
  # спецификации не совпадают: соответствие в README.md этой папки.
4
4
  record: taxonomies
5
5
  schema_version: "0.1"
6
6
  case: spectra-coffee-fiction
7
7
  taxonomies:
8
8
  tier:
9
- - {id: intent, ru: "замысел", en: "intent"} # of each position; the owner's is the controlling one
9
+ - {id: intent, ru: "намерение", en: "intent"} # of each position; the owner's is the controlling instance, «замысел собственника»
10
10
  - {id: model, ru: "модель бизнеса", en: "business model"}
11
11
  - {id: entity, ru: "юридическое лицо", en: "business entity (legal person: rights, obligations, property)"}
12
12
  - {id: product, ru: "продукт", en: "product"}