smd-engine 0.6.2__tar.gz → 0.6.4__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 (204) hide show
  1. {smd_engine-0.6.2 → smd_engine-0.6.4}/CHANGELOG.md +41 -0
  2. {smd_engine-0.6.2 → smd_engine-0.6.4}/PKG-INFO +1 -1
  3. {smd_engine-0.6.2 → smd_engine-0.6.4}/cases/example/bakeries-c2.board.yaml +1 -0
  4. {smd_engine-0.6.2 → smd_engine-0.6.4}/cases/example_ru/pekarni-c2.board.yaml +1 -0
  5. smd_engine-0.6.4/cases/spectra_coffee/README.md +54 -0
  6. smd_engine-0.6.4/cases/spectra_coffee/bank.story.yaml +52 -0
  7. smd_engine-0.6.4/cases/spectra_coffee/buyer.story.yaml +54 -0
  8. smd_engine-0.6.4/cases/spectra_coffee/owner.story.yaml +58 -0
  9. smd_engine-0.6.4/cases/spectra_coffee/sources.yaml +52 -0
  10. smd_engine-0.6.4/cases/spectra_coffee/spectra-coffee-c1.board.yaml +282 -0
  11. smd_engine-0.6.4/cases/spectra_coffee/successor-premortem.story.yaml +49 -0
  12. smd_engine-0.6.4/cases/spectra_coffee/taxonomies.yaml +14 -0
  13. {smd_engine-0.6.2 → smd_engine-0.6.4}/docs/README.md +3 -0
  14. {smd_engine-0.6.2 → smd_engine-0.6.4}/docs/checks.md +4 -3
  15. {smd_engine-0.6.2 → smd_engine-0.6.4}/docs/commands.md +4 -2
  16. {smd_engine-0.6.2 → smd_engine-0.6.4}/docs/data-model.md +8 -24
  17. smd_engine-0.6.4/docs/hypotheses.md +31 -0
  18. {smd_engine-0.6.2 → smd_engine-0.6.4}/docs/method/README.md +2 -0
  19. smd_engine-0.6.4/docs/method/formal-stance.md +51 -0
  20. smd_engine-0.6.4/docs/method/robustness-rules.md +62 -0
  21. {smd_engine-0.6.2 → smd_engine-0.6.4}/docs/method/structural-moves.md +9 -0
  22. {smd_engine-0.6.2 → smd_engine-0.6.4}/docs/profiles.md +1 -1
  23. {smd_engine-0.6.2 → smd_engine-0.6.4}/docs/red-lines.md +3 -1
  24. {smd_engine-0.6.2 → smd_engine-0.6.4}/docs/stages.md +5 -1
  25. smd_engine-0.6.4/docs/stories.md +94 -0
  26. {smd_engine-0.6.2 → smd_engine-0.6.4}/procedures/README.md +1 -0
  27. {smd_engine-0.6.2 → smd_engine-0.6.4}/procedures/field-result.md +5 -1
  28. {smd_engine-0.6.2 → smd_engine-0.6.4}/procedures/functional-plan.md +1 -1
  29. {smd_engine-0.6.2 → smd_engine-0.6.4}/procedures/qualification-pass.md +2 -1
  30. smd_engine-0.6.4/procedures/story.md +85 -0
  31. {smd_engine-0.6.2 → smd_engine-0.6.4}/procedures/visionary-tract.md +7 -3
  32. {smd_engine-0.6.2 → smd_engine-0.6.4}/profiles/classic-two-boards.yaml +3 -0
  33. {smd_engine-0.6.2 → smd_engine-0.6.4}/profiles/management-four-boards.yaml +2 -0
  34. {smd_engine-0.6.2 → smd_engine-0.6.4}/profiles/program-three-boards.yaml +4 -0
  35. {smd_engine-0.6.2 → smd_engine-0.6.4}/pyproject.toml +1 -1
  36. {smd_engine-0.6.2 → smd_engine-0.6.4}/roles/methodologist.md +2 -0
  37. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/agree.py +4 -1
  38. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/apply.py +68 -4
  39. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/cli.py +208 -1
  40. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/records.py +2 -1
  41. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/render/assets/graph.js +8 -1
  42. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/render/graph.py +6 -2
  43. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/render/index.py +16 -0
  44. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/render/light.py +2 -1
  45. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/render/markdown.py +1 -0
  46. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/render/sessionflow.py +2 -1
  47. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/render/svg.py +20 -4
  48. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/render/text.py +17 -4
  49. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/schemas/board_patch.schema.json +24 -4
  50. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/schemas/board_set.schema.json +11 -3
  51. smd_engine-0.6.4/src/smd_engine/schemas/story.schema.json +80 -0
  52. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/status.py +2 -1
  53. smd_engine-0.6.4/src/smd_engine/story/__init__.py +4 -0
  54. smd_engine-0.6.4/src/smd_engine/story/check.py +394 -0
  55. smd_engine-0.6.4/src/smd_engine/story/gaps.py +325 -0
  56. smd_engine-0.6.4/src/smd_engine/story/model.py +224 -0
  57. smd_engine-0.6.4/src/smd_engine/story/numbers.py +373 -0
  58. smd_engine-0.6.4/src/smd_engine/story/paths.py +269 -0
  59. smd_engine-0.6.4/src/smd_engine/story/render.py +116 -0
  60. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/validate/__init__.py +11 -1
  61. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/validate/context.py +4 -0
  62. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/validate/hypotheses.py +185 -2
  63. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/validate/management.py +33 -14
  64. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/validate/structure.py +15 -4
  65. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/validate/tract.py +25 -3
  66. smd_engine-0.6.4/src/smd_engine/verdict.py +318 -0
  67. smd_engine-0.6.4/tests/story_helpers.py +67 -0
  68. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_ai_roles.py +1 -1
  69. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_apply.py +130 -0
  70. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_beer_layer.py +44 -8
  71. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_hypothesis_standard.py +3 -1
  72. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_procedure_checks.py +28 -0
  73. smd_engine-0.6.4/tests/test_render_carries.py +108 -0
  74. smd_engine-0.6.4/tests/test_robustness.py +245 -0
  75. smd_engine-0.6.4/tests/test_story_case.py +192 -0
  76. smd_engine-0.6.4/tests/test_story_check.py +480 -0
  77. smd_engine-0.6.4/tests/test_story_numbers.py +106 -0
  78. smd_engine-0.6.4/tests/test_story_paths.py +339 -0
  79. {smd_engine-0.6.2 → smd_engine-0.6.4}/uv.lock +1 -1
  80. smd_engine-0.6.2/src/smd_engine/verdict.py +0 -123
  81. {smd_engine-0.6.2 → smd_engine-0.6.4}/.claude/agents/smd-game-technician.md +0 -0
  82. {smd_engine-0.6.2 → smd_engine-0.6.4}/.claude/agents/smd-methodologist.md +0 -0
  83. {smd_engine-0.6.2 → smd_engine-0.6.4}/.claude/agents/smd-visionary.md +0 -0
  84. {smd_engine-0.6.2 → smd_engine-0.6.4}/.claude/commands/procedure.md +0 -0
  85. {smd_engine-0.6.2 → smd_engine-0.6.4}/.flake8 +0 -0
  86. {smd_engine-0.6.2 → smd_engine-0.6.4}/.github/workflows/ci.yml +0 -0
  87. {smd_engine-0.6.2 → smd_engine-0.6.4}/.github/workflows/release.yml +0 -0
  88. {smd_engine-0.6.2 → smd_engine-0.6.4}/.gitignore +0 -0
  89. {smd_engine-0.6.2 → smd_engine-0.6.4}/.python-version +0 -0
  90. {smd_engine-0.6.2 → smd_engine-0.6.4}/CONTRIBUTING.md +0 -0
  91. {smd_engine-0.6.2 → smd_engine-0.6.4}/LICENSE +0 -0
  92. {smd_engine-0.6.2 → smd_engine-0.6.4}/README.md +0 -0
  93. {smd_engine-0.6.2 → smd_engine-0.6.4}/README_ru.md +0 -0
  94. {smd_engine-0.6.2 → smd_engine-0.6.4}/cases/example/bakeries-c1.board.yaml +0 -0
  95. {smd_engine-0.6.2 → smd_engine-0.6.4}/cases/example/golden/README.md +0 -0
  96. {smd_engine-0.6.2 → smd_engine-0.6.4}/cases/example/golden/bakeries-c2-expected.board.yaml +0 -0
  97. {smd_engine-0.6.2 → smd_engine-0.6.4}/cases/example/golden/s3_transcript.txt +0 -0
  98. {smd_engine-0.6.2 → smd_engine-0.6.4}/cases/example/patches/bakeries-c2-1.patch.yaml +0 -0
  99. {smd_engine-0.6.2 → smd_engine-0.6.4}/cases/example/sources.yaml +0 -0
  100. {smd_engine-0.6.2 → smd_engine-0.6.4}/cases/example/two-boards-c1.board.yaml +0 -0
  101. {smd_engine-0.6.2 → smd_engine-0.6.4}/cases/example_ru/pekarni-c1.board.yaml +0 -0
  102. {smd_engine-0.6.2 → smd_engine-0.6.4}/cases/example_ru/pekarni-oru-c1.board.yaml +0 -0
  103. {smd_engine-0.6.2 → smd_engine-0.6.4}/cases/example_ru/pekarnya-holding-c1.board.yaml +0 -0
  104. {smd_engine-0.6.2 → smd_engine-0.6.4}/cases/example_ru/sources.yaml +0 -0
  105. {smd_engine-0.6.2 → smd_engine-0.6.4}/docs/changelog-0.2-0.5.md +0 -0
  106. {smd_engine-0.6.2 → smd_engine-0.6.4}/docs/first-board.md +0 -0
  107. {smd_engine-0.6.2 → smd_engine-0.6.4}/docs/glossary.md +0 -0
  108. {smd_engine-0.6.2 → smd_engine-0.6.4}/docs/method/encodable.md +0 -0
  109. {smd_engine-0.6.2 → smd_engine-0.6.4}/docs/method/odi-problematization.md +0 -0
  110. {smd_engine-0.6.2 → smd_engine-0.6.4}/docs/method/reconciliation.md +0 -0
  111. {smd_engine-0.6.2 → smd_engine-0.6.4}/docs/method/roles-and-actors.md +0 -0
  112. {smd_engine-0.6.2 → smd_engine-0.6.4}/docs/method/smd-classic.md +0 -0
  113. {smd_engine-0.6.2 → smd_engine-0.6.4}/docs/method/sources.md +0 -0
  114. {smd_engine-0.6.2 → smd_engine-0.6.4}/docs/method/triz-systems.md +0 -0
  115. {smd_engine-0.6.2 → smd_engine-0.6.4}/docs/plan.md +0 -0
  116. {smd_engine-0.6.2 → smd_engine-0.6.4}/lenses/README.md +0 -0
  117. {smd_engine-0.6.2 → smd_engine-0.6.4}/lenses/beer-viable-system.md +0 -0
  118. {smd_engine-0.6.2 → smd_engine-0.6.4}/lenses/design-chain.md +0 -0
  119. {smd_engine-0.6.2 → smd_engine-0.6.4}/lenses/fliamer-diamond.md +0 -0
  120. {smd_engine-0.6.2 → smd_engine-0.6.4}/lenses/khaprov-levels.md +0 -0
  121. {smd_engine-0.6.2 → smd_engine-0.6.4}/lenses/khaprov-ontology.md +0 -0
  122. {smd_engine-0.6.2 → smd_engine-0.6.4}/lenses/scamper-check.md +0 -0
  123. {smd_engine-0.6.2 → smd_engine-0.6.4}/lenses/schukin-boundaries.md +0 -0
  124. {smd_engine-0.6.2 → smd_engine-0.6.4}/lenses/schukin-interface-tax.md +0 -0
  125. {smd_engine-0.6.2 → smd_engine-0.6.4}/lenses/three-positions.md +0 -0
  126. {smd_engine-0.6.2 → smd_engine-0.6.4}/lenses/triz-contradictions.md +0 -0
  127. {smd_engine-0.6.2 → smd_engine-0.6.4}/procedures/ingest-transcript.md +0 -0
  128. {smd_engine-0.6.2 → smd_engine-0.6.4}/procedures/positional-construction.md +0 -0
  129. {smd_engine-0.6.2 → smd_engine-0.6.4}/procedures/problematization.md +0 -0
  130. {smd_engine-0.6.2 → smd_engine-0.6.4}/procedures/reflexive-protocol.md +0 -0
  131. {smd_engine-0.6.2 → smd_engine-0.6.4}/procedures/small-situation.md +0 -0
  132. {smd_engine-0.6.2 → smd_engine-0.6.4}/procedures/solo-session.md +0 -0
  133. {smd_engine-0.6.2 → smd_engine-0.6.4}/procedures/stakeholder-ontology.md +0 -0
  134. {smd_engine-0.6.2 → smd_engine-0.6.4}/procedures/theses-to-board.md +0 -0
  135. {smd_engine-0.6.2 → smd_engine-0.6.4}/roles/README.md +0 -0
  136. {smd_engine-0.6.2 → smd_engine-0.6.4}/roles/actors.md +0 -0
  137. {smd_engine-0.6.2 → smd_engine-0.6.4}/roles/game-technician.md +0 -0
  138. {smd_engine-0.6.2 → smd_engine-0.6.4}/roles/researcher.md +0 -0
  139. {smd_engine-0.6.2 → smd_engine-0.6.4}/roles/visionary.md +0 -0
  140. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/__init__.py +0 -0
  141. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/compare.py +0 -0
  142. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/eval.py +0 -0
  143. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/leverage.py +0 -0
  144. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/migrate.py +0 -0
  145. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/nextstep.py +0 -0
  146. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/pack.py +0 -0
  147. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/profile.py +0 -0
  148. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/redline.py +0 -0
  149. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/render/__init__.py +0 -0
  150. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/render/assets/frames.css +0 -0
  151. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/render/assets/frames.js +0 -0
  152. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/render/assets/graph.css +0 -0
  153. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/render/frames.py +0 -0
  154. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/render/frames_page.py +0 -0
  155. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/render/frames_text.py +0 -0
  156. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/render/graph_ui.py +0 -0
  157. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/render/html.py +0 -0
  158. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/render/layout.py +0 -0
  159. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/render/mermaid.py +0 -0
  160. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/render/vault.py +0 -0
  161. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/revise.py +0 -0
  162. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/scaffold.py +0 -0
  163. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/schemas/__init__.py +0 -0
  164. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/schemas/source_manifest.schema.json +0 -0
  165. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/schemas/taxonomies.schema.json +0 -0
  166. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/screen.py +0 -0
  167. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/sources.py +0 -0
  168. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/validate/ai.py +0 -0
  169. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/validate/graph.py +0 -0
  170. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/validate/hints.py +0 -0
  171. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/validate/manifest.py +0 -0
  172. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/validate/ontology.py +0 -0
  173. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/validate/redlines.py +0 -0
  174. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/validate/signoffs.py +0 -0
  175. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/validate/taxonomies.py +0 -0
  176. {smd_engine-0.6.2 → smd_engine-0.6.4}/src/smd_engine/validate/theses.py +0 -0
  177. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/conftest.py +0 -0
  178. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_action_program.py +0 -0
  179. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_agree.py +0 -0
  180. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_beer_render.py +0 -0
  181. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_compare.py +0 -0
  182. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_eval.py +0 -0
  183. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_export.py +0 -0
  184. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_frames.py +0 -0
  185. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_graph.py +0 -0
  186. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_ingestion.py +0 -0
  187. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_lenses.py +0 -0
  188. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_management.py +0 -0
  189. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_migrate.py +0 -0
  190. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_nextstep.py +0 -0
  191. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_ontology_continuum.py +0 -0
  192. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_procedures.py +0 -0
  193. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_profile.py +0 -0
  194. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_publish.py +0 -0
  195. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_record_boards.py +0 -0
  196. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_red_lines.py +0 -0
  197. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_render_and_cli.py +0 -0
  198. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_render_fields.py +0 -0
  199. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_render_ru_pages.py +0 -0
  200. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_render_ru_values.py +0 -0
  201. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_revise.py +0 -0
  202. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_scaffold.py +0 -0
  203. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_status.py +0 -0
  204. {smd_engine-0.6.2 → smd_engine-0.6.4}/tests/test_validate.py +0 -0
@@ -4,6 +4,47 @@ Dates are those of the tag. All tags v0.2.1 to v0.3.5 were made on 2026-10-29. T
4
4
 
5
5
  ## Unreleased
6
6
 
7
+ ## 0.6.4 - 2026-11-02
8
+
9
+ 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 MIPT 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.
10
+
11
+ - 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.
12
+ - 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.
13
+ - `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.
14
+ - Test: `test_move_return_asked_of_an_adjoin` in `tests/test_procedure_checks.py`.
15
+ - 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.
16
+
17
+ 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.
18
+
19
+ - `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`.
20
+ - 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.
21
+ - `story.schema.json`: optional `context`, unique ids. Schema version 0.1 is unchanged, as old files stay valid.
22
+ - `smd story render --md` lists the context ids apart, under a heading of their own (with `--boards`, each with its label).
23
+ - `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`).
24
+ - 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.
25
+ - 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.
26
+
27
+ ## 0.6.3 - 2026-11-01
28
+
29
+ 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 MIPT case's five boards validate as before (0 errors, 150 warnings, 143 hints) and so do the eight example records.
30
+
31
+ 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.
32
+
33
+ - `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`.
34
+ - 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.
35
+ - 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`).
36
+ - 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`.
37
+ - 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.
38
+ - 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.
39
+ - `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.
40
+ - 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.
41
+ - `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`.
42
+ - `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`.
43
+ - Procedure `story` and `docs/stories.md`.
44
+ - `cases/spectra_coffee/`: an invented business map with four checked stories, kept checked by a test.
45
+ - Patches: `set` addresses a relation by `from` + `to` + `kind` (optional `match_label`) and sets `carries`, `label`, `voice`, `cites`; an entry that fits none or several relations is refused naming the candidates, and so is an entry with both an `id` and `from`, `to`, `kind`. Backward compatible.
46
+ - Renders: what a flow carries is written on the screen, in the frames (light and zoom), in the graph page and in the index (table of flows); English or Russian word by language.
47
+
7
48
  ## 0.6.2 - 2026-10-31
8
49
 
9
50
  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.
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.5
2
2
  Name: smd-engine
3
- Version: 0.6.2
3
+ Version: 0.6.4
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
@@ -59,6 +59,7 @@ relations:
59
59
  - {from: place-mills, to: fn-dough, kind: flow, carries: material, label: "flour"}
60
60
  - {from: p-owner, to: fn-dough, kind: flow, carries: money, label: "pays per tonne"}
61
61
  - {from: rl-unsold, to: fn-dough, kind: refers, label: "the night's volume is planned inside the line"}
62
+ - {from: rl-unsold, to: p-owner, kind: flow, carries: information, label: "the nightly report goes to the owner, who set the line"}
62
63
  - {from: fn-dough, to: fn-logistics, kind: flow, carries: product, label: "dough to deliver"}
63
64
  - {from: p-owner, to: fn-logistics, kind: flow, carries: money, label: "pays inside the dough price, for now"}
64
65
  - {from: fn-logistics, to: p-owner, kind: flow, carries: product, label: "dough before four in the morning"}
@@ -59,6 +59,7 @@ relations:
59
59
  - {from: place-mills, to: fn-dough, kind: flow, carries: material, label: "мука"}
60
60
  - {from: p-owner, to: fn-dough, kind: flow, carries: money, label: "платит за тонну"}
61
61
  - {from: rl-unsold, to: fn-dough, kind: refers, label: "объём ночи планируют в пределах линии"}
62
+ - {from: rl-unsold, to: p-owner, kind: flow, carries: information, label: "ночной отчёт идёт владельцу, он задал линию"}
62
63
  - {from: fn-dough, to: fn-logistics, kind: flow, carries: product, label: "тесто к доставке"}
63
64
  - {from: p-owner, to: fn-logistics, kind: flow, carries: money, label: "платит в цене теста, пока так"}
64
65
  - {from: fn-logistics, to: p-owner, kind: flow, carries: product, label: "тесто к четырём утра"}
@@ -0,0 +1,54 @@
1
+ # Spectra Coffee: an invented business map with checked stories
2
+
3
+ **Everything here is invented.** "Spectra Coffee" is an invented coffee shop, its founder, head barista, buyer and bank are invented, and so are their words, figures and dates. The one thing not invented here is a list of what the public demonstration specification of that shop describes (6 menu items, 5 critical control points, 14 allergens, 3 roles, prices and margins); the shop it describes is itself invented (`sources.yaml`, source `s-spec`). No person in these files is real: people appear as roles. Every title says so, every element carries `lineage: [fictional]` and `voice: ai`, and the stories are marked «черновик ИИ». Nothing here was checked by a human.
4
+
5
+ The case is a sample of what a map of one business needs before a story can be told from it, and of what such a story looks like. It answers "what is required from us" with an example, so that a group or a broker does not start from an empty page.
6
+
7
+ ## Files
8
+
9
+ | File | Content |
10
+ |---|---|
11
+ | `spectra-coffee-c1.board.yaml` | the board set (default profile, Russian labels): 39 elements, 52 relations, 5 hypotheses, 2 K, 1 ontology record |
12
+ | `sources.yaml`, `taxonomies.yaml` | the invented sources; the six values of the `tier` tag |
13
+ | `owner.story.yaml` | SCQA for the founder: red line broken in August 2026 while the founder was away |
14
+ | `buyer.story.yaml` | SCQA for the buyer, a regional roaster chain: the trial month without the founder inside the series of handover events, and the August gap (`sig-august`, `nb-qual`, listed in `context`); the walk goes from the buyer through the journal and the training to the trial month and the cooperation of the transfer |
15
+ | `bank.story.yaml` | SCQA for the buyer's bank: the coverage red line (not below 1.3) and the 92 days between two measurements |
16
+ | `successor-premortem.story.yaml` | premortem for the future manager: a series of linked events that stops, with the causes and an early sign for each |
17
+
18
+ The invented situation: a founder aged 61 wants to hand over two cafes within 3 years and keep the taste of the drinks. Candidates: the head barista as manager (the place `place-successor`), a regional roaster chain as buyer, a bank that finances the buyer. The business depends on the founder in one place that the board can show: his own tuning of the grinder every morning, and the record of it (a red line `rl-dialin`, observed breach of 14 days).
19
+
20
+ ## What the board holds
21
+
22
+ - Positions, places for others, one goal, two frames (old and new), six functions with `performed_by`, 27 flows that carry money, material, information or product, `uses`, `produces`, `belongs` and `opposes` relations, and seven weak `refers` that are not yet typed.
23
+ - Two red lines with `red_line: true`, `line` and `observed`: `rl-dialin` is a yes/no (`expect: true`, `recovery_days: 3`) and `rl-cover` is a corridor (`min: 1.3`, `recovery_days: 60`); both are breached by the rule of `docs/red-lines.md`.
24
+ - A normality boundary `nb-qual` opposed by a signal `sig-august`; a series of linked events `gl-handover` with three events that `belongs` to it.
25
+ - Five hypotheses with typed rules: H1 is `testing` with `observed` (4 of 56 shifts, the engine's verdict is "inconclusive"), H2 and H3 are untested estimates, H4 is `confirmed` with a (invented) sign-off, H5 is a probe.
26
+ - Tier tags on elements for all six tiers (`tags: {tier: [...]}`), checked against `taxonomies.yaml`. The founder's own ontology has a shareable record `O1`; its private part is not on the board, as the engine never holds it.
27
+
28
+ ```bash
29
+ uv run smd validate cases/spectra_coffee --sources cases/spectra_coffee/sources.yaml --taxonomies cases/spectra_coffee/taxonomies.yaml --hints
30
+ uv run smd story paths cases/spectra_coffee/spectra-coffee-c1.board.yaml --audience place-bank --limit 3
31
+ uv run smd story check cases/spectra_coffee/bank.story.yaml --boards cases/spectra_coffee/spectra-coffee-c1.board.yaml
32
+ ```
33
+
34
+ ## How the six tiers and the public specification fit
35
+
36
+ The six tiers of the OST ontology (owner intent, business model, business entity and rights, product, process, organisation) and the levels L0-L5 of the public specification are **not the same axis**. The levels are the order in which one shop's specification is derived, from the customer experience it must create (L0) down to sourcing (L5). The tiers decompose a firm for a transfer. The levels map to tiers many to many:
37
+
38
+ | Tier | What the specification has | What this case adds |
39
+ |---|---|---|
40
+ | 1 owner intent | 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
+ | 2 business model | L0 (target cohort, desired perception), prices and margins of L3 | `m-model`, an unchecked revenue estimate |
42
+ | 3 entity and rights | 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
+ | 4 product | L3 product specifications (6 items, cost, price) | `fn-shot`, `fact-spec`, `fact-price` |
44
+ | 5 process | L2 process contracts (quality control, opening and closing, maintenance, HACCP, allergens). L1 signal requirements spread over tiers 2 and 5 | `fn-dialin`, `fn-journal`, `nb-qual`, `sig-august` |
45
+ | 6 organisation | the roles (barista, shift lead, manager) | the head barista, the place of the manager, staff, `fn-train` |
46
+
47
+ Tiers 1 and 3 are where the specification is silent. A real business map has the same two holes until someone fills them, and a story that crosses them has nothing to rest on: that is what the stories here show by what they do not say.
48
+
49
+ ## How the stories were made, and how they stay checked
50
+
51
+ 1. `smd story paths` listed the walks from each protagonist (`procedures/story.md`, section 1). The four walks used are among its default top five (`tests/test_story_paths.py` keeps it so), and each story's `conflict` and `resolution` come from the walk.
52
+ 2. The sentences were written for each audience, each on board ids; the allow-lists were cut by hand (the buyer and the bank do not see the founder's private estimate of his own share of mornings). Ids that a sentence uses but the path does not reach (a fact about the place, the August signal) are listed in each story's `context` (rule S5).
53
+ 3. Each story is stamped with the board version and the sha256 of the board file. `tests/test_story_case.py` runs `smd story check` on all four in CI. If the board changes in any way, the stories fail rule G7 until they are written again: that is the rule, not a defect.
54
+ 4. The stories are a view. They are not signed, and a correction goes to the board.
@@ -0,0 +1,52 @@
1
+ # ВЫМЫШЛЕННЫЙ ПРИМЕР, черновик ИИ. История для банка; не подписывается.
2
+ # Правлено вручную 2026-11-01 после смены процедуры story на 0.2.0 (список context, правило S5); штамп run ниже относится к прогону процедуры, а не к этим правкам.
3
+ record: story
4
+ schema_version: "0.1"
5
+ id: spectra-bank-scqa
6
+ title: "Вымышленный пример: история для банка покупателя «Спектры Кофе», SCQA, черновик ИИ"
7
+ boards:
8
+ - {id: spectra-coffee-c1, version: "1.0", sha256: 9f373ea726ef28d3294f770ba56baec88f122963b048713c8646095e951a703c}
9
+ audience: place-bank
10
+ protagonist: place-bank
11
+ form: scqa
12
+ allow: [place-bank, place-buyer, s-small, fact-revenue, fact-price, rl-cover, fn-books, fn-tranche, H3, coop-transfer]
13
+ path: [place-bank, fn-books, rl-cover, fn-tranche, place-buyer, coop-transfer]
14
+ conflict: [rl-cover]
15
+ resolution: [coop-transfer]
16
+ open: [H3]
17
+ context: [s-small, fact-revenue, fact-price, H3]
18
+ sentences:
19
+ - part: situation
20
+ level: hypothesis
21
+ ids: [place-bank, place-buyer, s-small]
22
+ text: "Допустим, банк рассматривает финансирование покупки двух кафе «Спектра Кофе» региональной сетью обжарочных."
23
+ - part: situation
24
+ level: unverified
25
+ ids: [fact-revenue]
26
+ text: "Выручку 2025 года основатель оценивает в 0,95 млн евро; эту оценку никто не проверял."
27
+ - part: situation
28
+ level: checked
29
+ ids: [fact-price]
30
+ text: "Капучино стоит 4,20 евро, маржа по ингредиентам 82,9 %, затраты на труд в неё не входят."
31
+ - part: complication
32
+ level: checked
33
+ ids: [rl-cover]
34
+ text: "Расчёт банка по отчётности кафе дал покрытие платежа 1,6 в марте 2026 года, 1,1 в июне и 1,5 в сентябре при красной линии не ниже 1,3."
35
+ - part: complication
36
+ level: checked
37
+ ids: [rl-cover]
38
+ text: "Между замерами 30 июня и 30 сентября 2026 года прошло 92 дня, и в начале этого срока покрытие было ниже линии."
39
+ - part: complication
40
+ level: checked
41
+ ids: [rl-cover]
42
+ text: "Этот срок длиннее восстановления в 60 дней, которое допускает линия."
43
+ - part: question
44
+ level: hypothesis
45
+ ids: [H3]
46
+ text: "Закроет ли покупатель сделку, если банк потребует покрытие не ниже 1,3 в трёх кварталах подряд?"
47
+ - part: answer
48
+ level: hypothesis
49
+ ids: [fn-tranche, fn-books, rl-cover]
50
+ text: "Предлагается поэтапное финансирование: транши открываются под линию покрытия, а отчётность кафе идёт банку каждый квартал."
51
+ voice: ai
52
+ run: {procedure: story, version: "0.2.0", model: claude-sonnet-5-5, date: "2026-11-01"}
@@ -0,0 +1,54 @@
1
+ # ВЫМЫШЛЕННЫЙ ПРИМЕР, черновик ИИ. История для покупателя; не подписывается.
2
+ # Список allow короче, чем у основателя: частные оценки основателя в него не входят.
3
+ # Правлено вручную 2026-11-01 после смены процедуры story на 0.2.0 (список context, правило S5); штамп run ниже относится к прогону процедуры, а не к этим правкам.
4
+ record: story
5
+ schema_version: "0.1"
6
+ id: spectra-buyer-scqa
7
+ title: "Вымышленный пример: история для покупателя «Спектры Кофе», SCQA, черновик ИИ"
8
+ boards:
9
+ - {id: spectra-coffee-c1, version: "1.0", sha256: 9f373ea726ef28d3294f770ba56baec88f122963b048713c8646095e951a703c}
10
+ audience: place-buyer
11
+ protagonist: place-buyer
12
+ form: scqa
13
+ allow: [place-buyer, s-small, fact-spec, H4, fact-revenue, fact-trademark, fact-lease,
14
+ H1, H2, fn-train, fn-journal, coop-transfer, ev-trial, gl-handover, nb-qual, sig-august]
15
+ path: [place-buyer, fn-journal, fn-train, ev-trial, gl-handover, coop-transfer]
16
+ conflict: [ev-trial, gl-handover]
17
+ resolution: [coop-transfer]
18
+ open: [H1, H2]
19
+ context: [s-small, fact-spec, H4, fact-revenue, fact-trademark, fact-lease, nb-qual, sig-august, H1, H2]
20
+ sentences:
21
+ - part: situation
22
+ level: hypothesis
23
+ ids: [place-buyer, s-small]
24
+ text: "Предположим, вы, региональная сеть обжарочных, рассматриваете покупку двух кафе «Спектра Кофе»."
25
+ - part: situation
26
+ level: checked
27
+ ids: [fact-spec, H4]
28
+ text: "Кафе работают по спецификации: 6 позиций меню, 5 критических контрольных точек, 14 аллергенов ЕС, а второе кафе запущено по той же спецификации без изменения контрактов качества."
29
+ - part: situation
30
+ level: unverified
31
+ ids: [fact-revenue]
32
+ text: "Выручку 2025 года основатель оценивает в 0,95 млн евро; эту оценку никто не проверял."
33
+ - part: situation
34
+ level: stated
35
+ ids: [fact-trademark, fact-lease]
36
+ text: "Товарный знак записан на основателя лично, а аренда флагманского кафе требует согласия арендодателя при смене владельца."
37
+ - part: complication
38
+ level: hypothesis
39
+ ids: [nb-qual, sig-august]
40
+ text: "Возможно, норма «смена работает без основателя» не выполняется: в августе 2026 запись настройки помола отсутствовала 14 дней подряд, пока основатель был в отъезде."
41
+ - part: complication
42
+ level: hypothesis
43
+ ids: [gl-handover, ev-trial]
44
+ text: "Передача идёт серией связанных событий: представление, пробный месяц, подписание; в пробный месяц старший бариста ведёт оба кафе 28 дней без основателя, и до него неизвестно, будет ли напиток выходить по спецификации без основателя."
45
+ - part: question
46
+ level: hypothesis
47
+ ids: [H1, H2]
48
+ text: "Будет ли старший бариста вести запись без основателя, и назовёте ли вы цену не позже чем через 6 месяцев непрерывного журнала?"
49
+ - part: answer
50
+ level: hypothesis
51
+ ids: [fn-train, ev-trial, fn-journal, coop-transfer]
52
+ text: "Предлагается пробный месяц на 28 дней: основатель обучает управляющего, а журнал настройки виден вам до сделки и входит в кооперацию передачи."
53
+ voice: ai
54
+ run: {procedure: story, version: "0.2.0", model: claude-sonnet-5-5, date: "2026-11-01"}
@@ -0,0 +1,58 @@
1
+ # ВЫМЫШЛЕННЫЙ ПРИМЕР, черновик ИИ. История для основателя; не подписывается.
2
+ # Исправления вносятся в карту (spectra-coffee-c1.board.yaml), потом текст пишется заново.
3
+ # Правлено вручную 2026-11-01 после смены процедуры story на 0.2.0 (список context, правило S5); штамп run ниже относится к прогону процедуры, а не к этим правкам.
4
+ record: story
5
+ schema_version: "0.1"
6
+ id: spectra-owner-scqa
7
+ title: "Вымышленный пример: история для основателя «Спектры Кофе», SCQA, черновик ИИ"
8
+ boards:
9
+ - {id: spectra-coffee-c1, version: "1.0", sha256: 9f373ea726ef28d3294f770ba56baec88f122963b048713c8646095e951a703c}
10
+ audience: p-founder
11
+ protagonist: p-founder
12
+ form: scqa
13
+ allow: [p-founder, goal-handover, fact-staff, fact-spec, s-small, fact-dialin-share, rl-dialin,
14
+ sig-august, nb-qual, H1, H2, H5, fn-dialin, fn-journal, coop-transfer, K1, fn-train, place-successor]
15
+ path: [p-founder, fn-dialin, rl-dialin, fn-journal, coop-transfer]
16
+ conflict: [rl-dialin]
17
+ resolution: [coop-transfer]
18
+ open: [H1, H2, H5]
19
+ context: [goal-handover, s-small, fact-staff, fact-spec, fact-dialin-share, nb-qual, sig-august, H1]
20
+ sentences:
21
+ - part: situation
22
+ level: stated
23
+ ids: [p-founder, goal-handover]
24
+ text: "Вам 61 год, вы основали «Спектру Кофе» и хотите передать дело в течение 3 лет, сохранив вкус напитков."
25
+ - part: situation
26
+ level: stated
27
+ ids: [s-small, fact-staff, fact-spec]
28
+ text: "В двух кафе работают 9 человек, а меню и процессы записаны в спецификации: 6 позиций меню, 5 критических контрольных точек, 14 аллергенов ЕС."
29
+ - part: situation
30
+ level: unverified
31
+ ids: [fact-dialin-share]
32
+ text: "По вашей оценке, вы сами настраиваете помол в 5 из 7 утренних смен; эту оценку никто не проверял."
33
+ - part: complication
34
+ level: checked
35
+ ids: [rl-dialin]
36
+ text: "Вы задали красную линию: настройка помола записана в журнал каждую неделю проверки."
37
+ - part: complication
38
+ level: checked
39
+ ids: [sig-august, rl-dialin]
40
+ text: "С 3 по 17 августа 2026 года, пока вы были в отъезде, записи не было 14 дней подряд, и это нарушение линии."
41
+ - part: complication
42
+ level: hypothesis
43
+ ids: [nb-qual, sig-august]
44
+ text: "Возможно, это значит, что норма «смена работает без основателя» пока не держится."
45
+ - part: question
46
+ level: hypothesis
47
+ ids: [H1]
48
+ text: "Будет ли старший бариста вести запись без вас так, чтобы не больше 10 % смен оставались без записи?"
49
+ - part: question
50
+ level: hypothesis
51
+ ids: [H1]
52
+ text: "В пробные дни записи не было в 4 сменах из 56, а порог равен 10 %; правило пока не даёт вывода."
53
+ - part: answer
54
+ level: hypothesis
55
+ ids: [fn-journal, coop-transfer, goal-handover]
56
+ text: "Предлагается связать журнал с передачей: он виден управляющему и покупателю, а кооперация передачи ведёт к вашей цели."
57
+ voice: ai
58
+ run: {procedure: story, version: "0.2.0", model: claude-sonnet-5-5, date: "2026-11-01"}
@@ -0,0 +1,52 @@
1
+ # ВЫМЫШЛЕННЫЙ ПРИМЕР. «Спектра Кофе» здесь выдуманная кофейня; всё, что про неё
2
+ # сказано ниже, придумано, кроме перечня того, что описано в публичной
3
+ # демонстрационной спецификации (s-spec), и та сама вымышлена. Файлов нет:
4
+ # адреса example.org ведут в никуда.
5
+ record: source_manifest
6
+ schema_version: "0.3"
7
+ case: spectra-coffee-fiction
8
+ location: "вымышленный пример; файлов нет"
9
+ sources:
10
+ - id: s-spec
11
+ title: "Публичная демонстрационная спецификация кофейни «Спектра Кофе» (сама вымышленная организация); из неё взяты цифры меню, ролей и контрольных точек"
12
+ kind: external
13
+ origin: external
14
+ date: "2026-05-29"
15
+ url: https://orgschema.com/demo
16
+ note: "Единственный источник, не придуманный здесь; но и он описывает вымышленное предприятие."
17
+ clean_room: allow
18
+ - id: s-talk
19
+ title: "Вымышленная беседа с вымышленным основателем, составлена ИИ (черновик ИИ)"
20
+ kind: transcript
21
+ origin: team
22
+ date: "2026-10-20"
23
+ url: https://example.org/spectra-fiction/talk
24
+ clean_room: allow
25
+ - id: s-log
26
+ title: "Вымышленный журнал настройки помола, 2026 год"
27
+ kind: field_artefact
28
+ origin: team
29
+ date: "2026-10-31"
30
+ url: https://example.org/spectra-fiction/dialin-log
31
+ clean_room: allow
32
+ - id: s-books
33
+ title: "Вымышленная отчётность двух кафе для расчёта банка, 2026 год"
34
+ kind: field_artefact
35
+ origin: team
36
+ date: "2026-10-31"
37
+ url: https://example.org/spectra-fiction/books
38
+ clean_room: allow
39
+ - id: s-trial
40
+ title: "Вымышленный протокол пробных смен старшего бариста без основателя"
41
+ kind: field_artefact
42
+ origin: team
43
+ date: "2026-10-31"
44
+ url: https://example.org/spectra-fiction/trial
45
+ clean_room: allow
46
+ - id: s-fork
47
+ title: "Вымышленный отчёт о запуске второго кафе по той же спецификации"
48
+ kind: field_artefact
49
+ origin: team
50
+ date: "2025-09-30"
51
+ url: https://example.org/spectra-fiction/second-cafe
52
+ clean_room: allow