smd-engine 0.7.6__tar.gz → 0.7.7__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 (292) hide show
  1. {smd_engine-0.7.6 → smd_engine-0.7.7}/CHANGELOG.md +10 -0
  2. {smd_engine-0.7.6 → smd_engine-0.7.7}/PKG-INFO +3 -3
  3. {smd_engine-0.7.6 → smd_engine-0.7.7}/README.md +2 -2
  4. {smd_engine-0.7.6 → smd_engine-0.7.7}/README_ru.md +2 -2
  5. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/example/deal/answers_boris.yaml +1 -1
  6. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/example/deal/answers_gleb.yaml +1 -1
  7. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/example/deal/answers_vera.yaml +1 -1
  8. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/example/deal/pack.yaml +8 -4
  9. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/example/task/answers_ana.yaml +1 -1
  10. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/example/task/answers_ben.yaml +1 -1
  11. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/example/task/answers_cy.yaml +1 -1
  12. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/example/task/pack.yaml +7 -3
  13. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/example/task/replies_ana.yaml +1 -1
  14. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/example/task/replies_ben.yaml +1 -1
  15. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/spectra_coffee/README.md +5 -5
  16. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/spectra_coffee/bank.story.yaml +1 -1
  17. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/spectra_coffee/buyer.story.yaml +1 -1
  18. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/spectra_coffee/owner.story.yaml +1 -1
  19. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/spectra_coffee/spectra-coffee-c1.board.yaml +7 -4
  20. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/spectra_coffee/successor-premortem.story.yaml +1 -1
  21. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/spectra_coffee/taxonomies.yaml +2 -2
  22. {smd_engine-0.7.6 → smd_engine-0.7.7}/docs/data-model.md +4 -2
  23. {smd_engine-0.7.6 → smd_engine-0.7.7}/docs/method/roles-and-actors.md +1 -1
  24. {smd_engine-0.7.6 → smd_engine-0.7.7}/lenses/khaprov-levels.md +6 -6
  25. {smd_engine-0.7.6 → smd_engine-0.7.7}/procedures/README.md +1 -1
  26. {smd_engine-0.7.6 → smd_engine-0.7.7}/procedures/positional-construction.md +2 -2
  27. {smd_engine-0.7.6 → smd_engine-0.7.7}/procedures/stakeholder-ontology.md +29 -8
  28. {smd_engine-0.7.6 → smd_engine-0.7.7}/pyproject.toml +1 -1
  29. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_deal_golden.py +7 -7
  30. {smd_engine-0.7.6 → smd_engine-0.7.7}/uv.lock +1 -1
  31. {smd_engine-0.7.6 → smd_engine-0.7.7}/.claude/agents/smd-game-technician.md +0 -0
  32. {smd_engine-0.7.6 → smd_engine-0.7.7}/.claude/agents/smd-methodologist.md +0 -0
  33. {smd_engine-0.7.6 → smd_engine-0.7.7}/.claude/agents/smd-visionary.md +0 -0
  34. {smd_engine-0.7.6 → smd_engine-0.7.7}/.claude/commands/procedure.md +0 -0
  35. {smd_engine-0.7.6 → smd_engine-0.7.7}/.flake8 +0 -0
  36. {smd_engine-0.7.6 → smd_engine-0.7.7}/.github/workflows/ci.yml +0 -0
  37. {smd_engine-0.7.6 → smd_engine-0.7.7}/.github/workflows/release.yml +0 -0
  38. {smd_engine-0.7.6 → smd_engine-0.7.7}/.gitignore +0 -0
  39. {smd_engine-0.7.6 → smd_engine-0.7.7}/.python-version +0 -0
  40. {smd_engine-0.7.6 → smd_engine-0.7.7}/CONTRIBUTING.md +0 -0
  41. {smd_engine-0.7.6 → smd_engine-0.7.7}/LICENSE +0 -0
  42. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/example/bakeries-c1.board.yaml +0 -0
  43. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/example/bakeries-c2.board.yaml +0 -0
  44. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/example/golden/README.md +0 -0
  45. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/example/golden/bakeries-c2-expected.board.yaml +0 -0
  46. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/example/golden/s3_transcript.txt +0 -0
  47. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/example/patches/bakeries-c2-1.patch.yaml +0 -0
  48. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/example/sources.yaml +0 -0
  49. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/example/task/transcript_ben.txt +0 -0
  50. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/example/two-boards-c1.board.yaml +0 -0
  51. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/example_ru/pekarni-c1.board.yaml +0 -0
  52. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/example_ru/pekarni-c2.board.yaml +0 -0
  53. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/example_ru/pekarni-oru-c1.board.yaml +0 -0
  54. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/example_ru/pekarnya-holding-c1.board.yaml +0 -0
  55. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/example_ru/sources.yaml +0 -0
  56. {smd_engine-0.7.6 → smd_engine-0.7.7}/cases/spectra_coffee/sources.yaml +0 -0
  57. {smd_engine-0.7.6 → smd_engine-0.7.7}/docs/README.md +0 -0
  58. {smd_engine-0.7.6 → smd_engine-0.7.7}/docs/changelog-0.2-0.5.md +0 -0
  59. {smd_engine-0.7.6 → smd_engine-0.7.7}/docs/checks.md +0 -0
  60. {smd_engine-0.7.6 → smd_engine-0.7.7}/docs/commands.md +0 -0
  61. {smd_engine-0.7.6 → smd_engine-0.7.7}/docs/deal-mode.md +0 -0
  62. {smd_engine-0.7.6 → smd_engine-0.7.7}/docs/first-board.md +0 -0
  63. {smd_engine-0.7.6 → smd_engine-0.7.7}/docs/glossary.md +0 -0
  64. {smd_engine-0.7.6 → smd_engine-0.7.7}/docs/hypotheses.md +0 -0
  65. {smd_engine-0.7.6 → smd_engine-0.7.7}/docs/method/README.md +0 -0
  66. {smd_engine-0.7.6 → smd_engine-0.7.7}/docs/method/encodable.md +0 -0
  67. {smd_engine-0.7.6 → smd_engine-0.7.7}/docs/method/formal-stance.md +0 -0
  68. {smd_engine-0.7.6 → smd_engine-0.7.7}/docs/method/odi-problematization.md +0 -0
  69. {smd_engine-0.7.6 → smd_engine-0.7.7}/docs/method/reconciliation.md +0 -0
  70. {smd_engine-0.7.6 → smd_engine-0.7.7}/docs/method/robustness-rules.md +0 -0
  71. {smd_engine-0.7.6 → smd_engine-0.7.7}/docs/method/smd-classic.md +0 -0
  72. {smd_engine-0.7.6 → smd_engine-0.7.7}/docs/method/sources.md +0 -0
  73. {smd_engine-0.7.6 → smd_engine-0.7.7}/docs/method/structural-moves.md +0 -0
  74. {smd_engine-0.7.6 → smd_engine-0.7.7}/docs/method/triz-systems.md +0 -0
  75. {smd_engine-0.7.6 → smd_engine-0.7.7}/docs/plan.md +0 -0
  76. {smd_engine-0.7.6 → smd_engine-0.7.7}/docs/profiles.md +0 -0
  77. {smd_engine-0.7.6 → smd_engine-0.7.7}/docs/red-lines.md +0 -0
  78. {smd_engine-0.7.6 → smd_engine-0.7.7}/docs/stages.md +0 -0
  79. {smd_engine-0.7.6 → smd_engine-0.7.7}/docs/stories.md +0 -0
  80. {smd_engine-0.7.6 → smd_engine-0.7.7}/docs/task-packs.md +0 -0
  81. {smd_engine-0.7.6 → smd_engine-0.7.7}/lenses/README.md +0 -0
  82. {smd_engine-0.7.6 → smd_engine-0.7.7}/lenses/beer-viable-system.md +0 -0
  83. {smd_engine-0.7.6 → smd_engine-0.7.7}/lenses/design-chain.md +0 -0
  84. {smd_engine-0.7.6 → smd_engine-0.7.7}/lenses/fliamer-diamond.md +0 -0
  85. {smd_engine-0.7.6 → smd_engine-0.7.7}/lenses/khaprov-ontology.md +0 -0
  86. {smd_engine-0.7.6 → smd_engine-0.7.7}/lenses/scamper-check.md +0 -0
  87. {smd_engine-0.7.6 → smd_engine-0.7.7}/lenses/schukin-boundaries.md +0 -0
  88. {smd_engine-0.7.6 → smd_engine-0.7.7}/lenses/schukin-interface-tax.md +0 -0
  89. {smd_engine-0.7.6 → smd_engine-0.7.7}/lenses/three-positions.md +0 -0
  90. {smd_engine-0.7.6 → smd_engine-0.7.7}/lenses/triz-contradictions.md +0 -0
  91. {smd_engine-0.7.6 → smd_engine-0.7.7}/procedures/field-result.md +0 -0
  92. {smd_engine-0.7.6 → smd_engine-0.7.7}/procedures/functional-plan.md +0 -0
  93. {smd_engine-0.7.6 → smd_engine-0.7.7}/procedures/ingest-transcript.md +0 -0
  94. {smd_engine-0.7.6 → smd_engine-0.7.7}/procedures/problematization.md +0 -0
  95. {smd_engine-0.7.6 → smd_engine-0.7.7}/procedures/qualification-pass.md +0 -0
  96. {smd_engine-0.7.6 → smd_engine-0.7.7}/procedures/reflexive-protocol.md +0 -0
  97. {smd_engine-0.7.6 → smd_engine-0.7.7}/procedures/small-situation.md +0 -0
  98. {smd_engine-0.7.6 → smd_engine-0.7.7}/procedures/solo-session.md +0 -0
  99. {smd_engine-0.7.6 → smd_engine-0.7.7}/procedures/story.md +0 -0
  100. {smd_engine-0.7.6 → smd_engine-0.7.7}/procedures/task-diff.md +0 -0
  101. {smd_engine-0.7.6 → smd_engine-0.7.7}/procedures/task-pack.md +0 -0
  102. {smd_engine-0.7.6 → smd_engine-0.7.7}/procedures/theses-to-board.md +0 -0
  103. {smd_engine-0.7.6 → smd_engine-0.7.7}/procedures/visionary-tract.md +0 -0
  104. {smd_engine-0.7.6 → smd_engine-0.7.7}/profiles/classic-two-boards.yaml +0 -0
  105. {smd_engine-0.7.6 → smd_engine-0.7.7}/profiles/management-four-boards.yaml +0 -0
  106. {smd_engine-0.7.6 → smd_engine-0.7.7}/profiles/program-three-boards.yaml +0 -0
  107. {smd_engine-0.7.6 → smd_engine-0.7.7}/roles/README.md +0 -0
  108. {smd_engine-0.7.6 → smd_engine-0.7.7}/roles/actors.md +0 -0
  109. {smd_engine-0.7.6 → smd_engine-0.7.7}/roles/game-technician.md +0 -0
  110. {smd_engine-0.7.6 → smd_engine-0.7.7}/roles/methodologist.md +0 -0
  111. {smd_engine-0.7.6 → smd_engine-0.7.7}/roles/researcher.md +0 -0
  112. {smd_engine-0.7.6 → smd_engine-0.7.7}/roles/visionary.md +0 -0
  113. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/__init__.py +0 -0
  114. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/agree.py +0 -0
  115. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/apply.py +0 -0
  116. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/cli.py +0 -0
  117. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/cli_boards.py +0 -0
  118. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/cli_session.py +0 -0
  119. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/cli_story.py +0 -0
  120. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/compare.py +0 -0
  121. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/deal/__init__.py +0 -0
  122. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/deal/agenda_views.py +0 -0
  123. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/deal/cli.py +0 -0
  124. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/deal/consent.py +0 -0
  125. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/deal/ledger.py +0 -0
  126. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/deal/overlap.py +0 -0
  127. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/deal/seal_cmd.py +0 -0
  128. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/deal/sealed.py +0 -0
  129. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/deal/signing.py +0 -0
  130. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/deal/verdict.py +0 -0
  131. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/deal/verdict_cmd.py +0 -0
  132. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/deal/verify.py +0 -0
  133. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/deal/verify_cmd.py +0 -0
  134. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/deal/verify_diff.py +0 -0
  135. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/deal/verify_extra.py +0 -0
  136. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/deal/verify_report.py +0 -0
  137. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/deal/views.py +0 -0
  138. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/eval.py +0 -0
  139. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/leverage.py +0 -0
  140. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/migrate.py +0 -0
  141. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/nextstep.py +0 -0
  142. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/pack.py +0 -0
  143. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/profile.py +0 -0
  144. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/profile_model.py +0 -0
  145. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/profile_parse.py +0 -0
  146. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/records.py +0 -0
  147. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/redline.py +0 -0
  148. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/render/__init__.py +0 -0
  149. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/render/assets/frames.css +0 -0
  150. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/render/assets/frames.js +0 -0
  151. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/render/assets/graph.css +0 -0
  152. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/render/assets/graph.js +0 -0
  153. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/render/frames.py +0 -0
  154. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/render/frames_page.py +0 -0
  155. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/render/frames_text.py +0 -0
  156. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/render/graph.py +0 -0
  157. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/render/graph_ui.py +0 -0
  158. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/render/html.py +0 -0
  159. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/render/index.py +0 -0
  160. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/render/layout.py +0 -0
  161. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/render/light.py +0 -0
  162. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/render/markdown.py +0 -0
  163. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/render/mermaid.py +0 -0
  164. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/render/sessionflow.py +0 -0
  165. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/render/svg.py +0 -0
  166. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/render/text.py +0 -0
  167. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/render/vault.py +0 -0
  168. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/revise.py +0 -0
  169. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/scaffold.py +0 -0
  170. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/schemas/__init__.py +0 -0
  171. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/schemas/board_patch.schema.json +0 -0
  172. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/schemas/board_set.schema.json +0 -0
  173. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/schemas/source_manifest.schema.json +0 -0
  174. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/schemas/story.schema.json +0 -0
  175. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/schemas/task_acceptance.schema.json +0 -0
  176. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/schemas/task_answers.schema.json +0 -0
  177. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/schemas/task_pack.schema.json +0 -0
  178. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/schemas/task_replies.schema.json +0 -0
  179. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/schemas/task_sealed.schema.json +0 -0
  180. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/schemas/task_verdicts.schema.json +0 -0
  181. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/schemas/taxonomies.schema.json +0 -0
  182. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/screen.py +0 -0
  183. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/sources.py +0 -0
  184. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/status.py +0 -0
  185. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/story/__init__.py +0 -0
  186. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/story/check.py +0 -0
  187. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/story/gaps.py +0 -0
  188. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/story/model.py +0 -0
  189. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/story/numbers.py +0 -0
  190. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/story/paths.py +0 -0
  191. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/story/render.py +0 -0
  192. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/__init__.py +0 -0
  193. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/acceptance.py +0 -0
  194. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/agenda.py +0 -0
  195. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/asking.py +0 -0
  196. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/assets/task.css +0 -0
  197. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/assets/task.js +0 -0
  198. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/bounds.py +0 -0
  199. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/check.py +0 -0
  200. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/cli.py +0 -0
  201. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/deal_check.py +0 -0
  202. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/deal_items.py +0 -0
  203. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/deal_labels.py +0 -0
  204. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/deal_render.py +0 -0
  205. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/deal_web.py +0 -0
  206. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/diff.py +0 -0
  207. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/diff_html.py +0 -0
  208. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/diff_md.py +0 -0
  209. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/labels.py +0 -0
  210. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/model.py +0 -0
  211. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/names.py +0 -0
  212. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/overwrite.py +0 -0
  213. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/pack_html.py +0 -0
  214. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/pack_md.py +0 -0
  215. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/pairs.py +0 -0
  216. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/positions.py +0 -0
  217. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/ranges.py +0 -0
  218. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/refs.py +0 -0
  219. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/svg.py +0 -0
  220. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/task/web.py +0 -0
  221. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/validate/__init__.py +0 -0
  222. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/validate/ai.py +0 -0
  223. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/validate/context.py +0 -0
  224. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/validate/graph.py +0 -0
  225. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/validate/hints.py +0 -0
  226. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/validate/hypotheses.py +0 -0
  227. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/validate/management.py +0 -0
  228. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/validate/manifest.py +0 -0
  229. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/validate/ontology.py +0 -0
  230. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/validate/redlines.py +0 -0
  231. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/validate/signoffs.py +0 -0
  232. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/validate/structure.py +0 -0
  233. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/validate/taxonomies.py +0 -0
  234. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/validate/theses.py +0 -0
  235. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/validate/tract.py +0 -0
  236. {smd_engine-0.7.6 → smd_engine-0.7.7}/src/smd_engine/verdict.py +0 -0
  237. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/conftest.py +0 -0
  238. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/deal_helpers.py +0 -0
  239. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/story_helpers.py +0 -0
  240. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_action_program.py +0 -0
  241. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_agree.py +0 -0
  242. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_ai_roles.py +0 -0
  243. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_apply.py +0 -0
  244. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_beer_layer.py +0 -0
  245. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_beer_render.py +0 -0
  246. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_compare.py +0 -0
  247. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_deal_acceptance.py +0 -0
  248. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_deal_added.py +0 -0
  249. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_deal_agenda_leaks.py +0 -0
  250. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_deal_bindings.py +0 -0
  251. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_deal_items.py +0 -0
  252. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_deal_positions.py +0 -0
  253. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_deal_ranges.py +0 -0
  254. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_deal_sealed.py +0 -0
  255. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_deal_signed.py +0 -0
  256. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_deal_verdict.py +0 -0
  257. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_deal_verify.py +0 -0
  258. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_deal_verify_diff.py +0 -0
  259. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_deal_verify_forged.py +0 -0
  260. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_deal_views.py +0 -0
  261. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_eval.py +0 -0
  262. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_export.py +0 -0
  263. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_frames.py +0 -0
  264. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_graph.py +0 -0
  265. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_hypothesis_standard.py +0 -0
  266. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_ingestion.py +0 -0
  267. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_lenses.py +0 -0
  268. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_management.py +0 -0
  269. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_migrate.py +0 -0
  270. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_nextstep.py +0 -0
  271. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_ontology_continuum.py +0 -0
  272. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_procedure_checks.py +0 -0
  273. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_procedures.py +0 -0
  274. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_profile.py +0 -0
  275. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_publish.py +0 -0
  276. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_record_boards.py +0 -0
  277. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_red_lines.py +0 -0
  278. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_render_and_cli.py +0 -0
  279. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_render_carries.py +0 -0
  280. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_render_fields.py +0 -0
  281. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_render_ru_pages.py +0 -0
  282. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_render_ru_values.py +0 -0
  283. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_revise.py +0 -0
  284. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_robustness.py +0 -0
  285. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_scaffold.py +0 -0
  286. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_status.py +0 -0
  287. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_story_case.py +0 -0
  288. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_story_check.py +0 -0
  289. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_story_numbers.py +0 -0
  290. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_story_paths.py +0 -0
  291. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_task.py +0 -0
  292. {smd_engine-0.7.6 → smd_engine-0.7.7}/tests/test_validate.py +0 -0
@@ -2,6 +2,16 @@
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.7 - 2026-11-09
6
+
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.
8
+
9
+ - 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
+ - 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.
11
+ - `docs/data-model.md`: the taxonomy example uses `intent` and `model` and says that a tier value names a field, not a party.
12
+ - Lens `khaprov-levels` 0.2.2: culture as lived is tier 6, not tier 1; tier 3 is named «юридическое лицо».
13
+ - The example case `spectra_coffee`: `fact-price` (price and margin) is tagged tier 2, business model; tier 1 is labelled «замысел», tier 3 «юридическое лицо»; the board is 1.0.2 and its stories carry the new stamp.
14
+
5
15
  ## 0.7.6 - 2026-11-07
6
16
 
7
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.
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.5
2
2
  Name: smd-engine
3
- Version: 0.7.6
3
+ Version: 0.7.7
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.6 (`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.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.
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.6 smd validate . --sources sources.yaml --strict
153
+ uvx --from git+https://github.com/viberesearch/smd-engine@v0.7.7 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.6 (`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.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.
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.6 smd validate . --sources sources.yaml --strict
128
+ uvx --from git+https://github.com/viberesearch/smd-engine@v0.7.7 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.6 (`pyproject.toml`), схема 0.3. Python 3.14. Программа предлагает и проверяет; решает человек, подписями, у каждой из которых названа функция.
19
+ Версия 0.7.7 (`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.6 smd validate . --sources sources.yaml --strict
130
+ uvx --from git+https://github.com/viberesearch/smd-engine@v0.7.7 smd validate . --sources sources.yaml --strict
131
131
  ```
132
132
 
133
133
  Порождённые рисунки (`smd publish`) - результат сборки, их не коммитят. Записи старой схемы переводят командой `smd migrate`.
@@ -3,7 +3,7 @@ schema_version: "0.1"
3
3
  pack:
4
4
  id: bakery-sale
5
5
  version: "1"
6
- sha256: "ff3f0133dbf3596c26d05a9410a0d5febfcddcedec79af7fbf48bbadc5598f5f"
6
+ sha256: "8570e3264d60531c105b77956e865e794cb373fefb153186bd3fa786edacc2cb"
7
7
  annex: {position: buyer, sha256: "35b25dc48f138d648d4c999e154411c02aae7c7a20d84cb7078d9d9f60e89375"}
8
8
  member: boris
9
9
  date: "2026-11-03"
@@ -3,7 +3,7 @@ schema_version: "0.1"
3
3
  pack:
4
4
  id: bakery-sale
5
5
  version: "1"
6
- sha256: "ff3f0133dbf3596c26d05a9410a0d5febfcddcedec79af7fbf48bbadc5598f5f"
6
+ sha256: "8570e3264d60531c105b77956e865e794cb373fefb153186bd3fa786edacc2cb"
7
7
  annex: {position: broker, sha256: "56072184ee793f34fc3a116cb86c69446860ec2fb7332776935791dc56b439e3"}
8
8
  member: gleb
9
9
  date: "2026-11-03"
@@ -3,7 +3,7 @@ schema_version: "0.1"
3
3
  pack:
4
4
  id: bakery-sale
5
5
  version: "1"
6
- sha256: "ff3f0133dbf3596c26d05a9410a0d5febfcddcedec79af7fbf48bbadc5598f5f"
6
+ sha256: "8570e3264d60531c105b77956e865e794cb373fefb153186bd3fa786edacc2cb"
7
7
  annex: {position: seller, sha256: "c73f2cf96a6ba1737aad29f20a6e2662f9dfd8c0808ad82dc711f92158693cc4"}
8
8
  member: vera
9
9
  date: "2026-11-03"
@@ -62,11 +62,15 @@ ontology:
62
62
  source: s1
63
63
  audience: [seller]
64
64
  elements:
65
- - {id: goal-sale, label: sale of the bakery, tier: 2, kind: goal}
65
+ # tier = the tier of the field of what an element stands for, not of its kind:
66
+ # a goal is a position's intent (tier 1), a position's control is a tier-3
67
+ # field, an activity is a process (tier 5), a quality standard a
68
+ # specification (tier 4), a lease a tier-3 obligation; a gap has no tier.
69
+ - {id: goal-sale, label: sale of the bakery, tier: 1, kind: goal}
66
70
  - {id: p-owner, label: owner, tier: 3, kind: position}
67
- - {id: fn-bread, label: bread production, tier: 4, kind: function}
68
- - {id: fn-cafe, label: cafe counter, tier: 4, kind: function}
69
- - {id: place-lease, label: premises lease, tier: 5, kind: place_for_others}
71
+ - {id: fn-bread, label: bread production, tier: 5, kind: function}
72
+ - {id: fn-cafe, label: cafe counter, tier: 5, kind: function}
73
+ - {id: place-lease, label: premises lease, tier: 3, kind: place_for_others}
70
74
  - {id: gap-successor, label: who runs the bakery after the owner, kind: gap}
71
75
  relations:
72
76
  - {from: goal-sale, to: p-owner, kind: intent of}
@@ -1,7 +1,7 @@
1
1
  # Invented answers of Ana (bakeries example). Written blind: before seeing Ben's or Cy's.
2
2
  record: task_answers
3
3
  schema_version: "0.1"
4
- pack: {id: bakeries-first-service, version: "1", sha256: 5a05efaca298804a5f75c55660df226bec5f24e0d09000a37324785bef0373b8}
4
+ pack: {id: bakeries-first-service, version: "1", sha256: 5c7b11b1b3ead83dc821dfee6b3277d13ba62aaeac6699f83a4892fdea67ccb5}
5
5
  member: ana
6
6
  date: "2026-01-21"
7
7
  drafted_by: self
@@ -1,7 +1,7 @@
1
1
  # Invented answers of Ben. A model drafted them from his voice notes and he edited them.
2
2
  record: task_answers
3
3
  schema_version: "0.1"
4
- pack: {id: bakeries-first-service, version: "1", sha256: 5a05efaca298804a5f75c55660df226bec5f24e0d09000a37324785bef0373b8}
4
+ pack: {id: bakeries-first-service, version: "1", sha256: 5c7b11b1b3ead83dc821dfee6b3277d13ba62aaeac6699f83a4892fdea67ccb5}
5
5
  member: ben
6
6
  date: "2026-01-22"
7
7
  drafted_by: model_edited
@@ -1,7 +1,7 @@
1
1
  # Invented answers of Cy.
2
2
  record: task_answers
3
3
  schema_version: "0.1"
4
- pack: {id: bakeries-first-service, version: "1", sha256: 5a05efaca298804a5f75c55660df226bec5f24e0d09000a37324785bef0373b8}
4
+ pack: {id: bakeries-first-service, version: "1", sha256: 5c7b11b1b3ead83dc821dfee6b3277d13ba62aaeac6699f83a4892fdea67ccb5}
5
5
  member: cy
6
6
  date: "2026-01-22"
7
7
  drafted_by: self
@@ -41,10 +41,14 @@ ontology:
41
41
  definition: the written conditions a batch of dough must meet before it leaves the plant
42
42
  source: s2
43
43
  elements:
44
- - {id: goal-shared, label: shared production for independent bakeries, tier: 2, kind: goal}
44
+ # tier = the tier of the field of what an element stands for, not of its kind:
45
+ # a goal is a position's intent (tier 1), a position's control is a tier-3
46
+ # field, an activity is a process (tier 5), a quality standard a
47
+ # specification (tier 4), a lease a tier-3 obligation; a gap has no tier.
48
+ - {id: goal-shared, label: shared production for independent bakeries, tier: 1, kind: goal}
45
49
  - {id: p-organiser, label: organiser of shared production, tier: 3, kind: position}
46
- - {id: fn-dough, label: dough production, tier: 4, kind: function}
47
- - {id: fn-logistics, label: night logistics, tier: 4, kind: function}
50
+ - {id: fn-dough, label: dough production, tier: 5, kind: function}
51
+ - {id: fn-logistics, label: night logistics, tier: 5, kind: function}
48
52
  - {id: fn-quality, label: quality standard, tier: 4, kind: function}
49
53
  - {id: place-mills, label: regional mills, tier: 5, kind: place_for_others}
50
54
  - {id: gap-payer, label: who pays for the shared plant, kind: gap}
@@ -2,7 +2,7 @@
2
2
  # the diff.yaml that `smd task diff` writes from pack.yaml and the three answers files.
3
3
  record: task_replies
4
4
  schema_version: "0.1"
5
- diff: 7a519d4438ad4399347dfe1884d2a7e02c3486fc5bbd149b7c2d0c770a478c37
5
+ diff: 49fed4970a2323cf75a1cf495e5d587da788c6c9e1a2a3d545dfc90ba9d16afc
6
6
  member: ana
7
7
  date: "2026-01-24"
8
8
  replies:
@@ -2,7 +2,7 @@
2
2
  # sends the first function to the call.
3
3
  record: task_replies
4
4
  schema_version: "0.1"
5
- diff: 7a519d4438ad4399347dfe1884d2a7e02c3486fc5bbd149b7c2d0c770a478c37
5
+ diff: 49fed4970a2323cf75a1cf495e5d587da788c6c9e1a2a3d545dfc90ba9d16afc
6
6
  member: ben
7
7
  date: "2026-01-24"
8
8
  replies:
@@ -33,14 +33,14 @@ uv run smd story check cases/spectra_coffee/bank.story.yaml --boards cases/spect
33
33
 
34
34
  ## How the six tiers and the public specification fit
35
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:
36
+ The six tiers of the OST ontology (intent, business model, business entity, 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
37
 
38
38
  | Tier | What the specification has | What this case adds |
39
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` |
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` |
41
+ | 2 business model | L0 (target cohort, desired perception), prices and margins of L3 | `m-model`, an unchecked revenue estimate, `fact-price` |
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
+ | 4 product | L3 product specifications (6 items; their cost and price are tier 2) | `fn-shot`, `fact-spec` |
44
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
45
  | 6 organisation | the roles (barista, shift lead, manager) | the head barista, the place of the manager, staff, `fn-train` |
46
46
 
@@ -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", sha256: 40c9b9f8f0f3428ced672a7603a1e91f5a39b81447cdfb510f9a771166c6f5c0}
8
+ - {id: spectra-coffee-c1, version: "1.0.2", sha256: d82b1a87cc3bda9e88ae003f9e7e5a90fc48252040191154501aa6c069d08928}
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", sha256: 40c9b9f8f0f3428ced672a7603a1e91f5a39b81447cdfb510f9a771166c6f5c0}
9
+ - {id: spectra-coffee-c1, version: "1.0.2", sha256: d82b1a87cc3bda9e88ae003f9e7e5a90fc48252040191154501aa6c069d08928}
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", sha256: 40c9b9f8f0f3428ced672a7603a1e91f5a39b81447cdfb510f9a771166c6f5c0}
9
+ - {id: spectra-coffee-c1, version: "1.0.2", sha256: d82b1a87cc3bda9e88ae003f9e7e5a90fc48252040191154501aa6c069d08928}
10
10
  audience: p-founder
11
11
  protagonist: p-founder
12
12
  form: scqa
@@ -2,8 +2,11 @@
2
2
  # и банк выдуманы. Цифры меню, ролей и контрольных точек взяты из публичной
3
3
  # демонстрационной спецификации (источник s-spec), которая сама описывает вымышленное
4
4
  # предприятие; всё остальное придумано и помечено lineage: [fictional], voice: ai.
5
- # Доски собраны по шести уровням OST (замысел, модель, юрлицо и права, продукт,
6
- # процесс, организация): теги tier. Уровни L0-L5 спецификации не те же самые: см. README.md.
5
+ # Доски собраны по шести уровням OST (замысел, модель, юридическое лицо, продукт,
6
+ # процесс, организация): теги tier. Слои L0-L5 спецификации не те же самые: см. README.md.
7
+ # Уровень записи — уровень поля её параметра: цена и маржа (fact-price) — модель бизнеса
8
+ # (правка 1.0.1, 09.11.2026; было «продукт»). Правка 1.0.2: уровень 3 называется
9
+ # «юридическое лицо» (было «юрлицо и права»).
7
10
  record: board_set
8
11
  schema_version: "0.3"
9
12
  id: spectra-coffee-c1
@@ -110,7 +113,7 @@ elements:
110
113
  - {id: fact-spec, short: "6 позиций меню, 5 точек, 14 аллергенов", board: s, half: small, kind: fact, label: "спецификация описывает 6 позиций меню, 5 критических контрольных точек и 14 аллергенов ЕС",
111
114
  seen_from: p-broker, epistemic: checked, tags: {tier: [product]}, cites: [s-spec], lineage: [fictional], voice: ai}
112
115
  - {id: fact-price, short: "капучино 4,20 евро, маржа 82,9 %", board: s, half: small, kind: fact, label: "капучино стоит 4,20 евро, маржа по ингредиентам 82,9 %, затраты на труд не входят",
113
- seen_from: p-broker, epistemic: checked, tags: {tier: [product]}, cites: [s-spec], lineage: [fictional], voice: ai}
116
+ seen_from: p-broker, epistemic: checked, tags: {tier: [model]}, cites: [s-spec], lineage: [fictional], voice: ai}
114
117
  - {id: fact-revenue, board: s, half: small, kind: fact, label: "основатель оценивает выручку 2025 года в 0,95 млн евро",
115
118
  seen_from: p-founder, epistemic: unverified, tags: {tier: [model]}, cites: ["s-talk#t=00:12:00"], lineage: [fictional], voice: ai}
116
119
  - {id: fact-dialin-share, board: s, half: small, kind: fact, label: "основатель сам настраивает помол в 5 из 7 утренних смен",
@@ -275,7 +278,7 @@ signoffs:
275
278
  - {function: accept_result, target: H4, by: group, cycle: 1, date: "2026-10-31",
276
279
  note: "вымышленная подпись: отчёт о запуске второго кафе сверен со спецификацией"}
277
280
  state:
278
- version: "1.0"
281
+ version: "1.0.2"
279
282
  difficulty: "карта первая; порядок настройки помола держится на основателе"
280
283
  accepted: ["H4 подтверждена вымышленной подписью"]
281
284
  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", sha256: 40c9b9f8f0f3428ced672a7603a1e91f5a39b81447cdfb510f9a771166c6f5c0}
9
+ - {id: spectra-coffee-c1, version: "1.0.2", sha256: d82b1a87cc3bda9e88ae003f9e7e5a90fc48252040191154501aa6c069d08928}
10
10
  audience: place-successor
11
11
  protagonist: place-successor
12
12
  form: premortem
@@ -6,9 +6,9 @@ schema_version: "0.1"
6
6
  case: spectra-coffee-fiction
7
7
  taxonomies:
8
8
  tier:
9
- - {id: intent, ru: "замысел собственника", en: "owner intent"}
9
+ - {id: intent, ru: "замысел", en: "intent"} # of each position; the owner's is the controlling one
10
10
  - {id: model, ru: "модель бизнеса", en: "business model"}
11
- - {id: entity, ru: "юрлицо и права", en: "business entity (legal person and registered rights)"}
11
+ - {id: entity, ru: "юридическое лицо", en: "business entity (legal person: rights, obligations, property)"}
12
12
  - {id: product, ru: "продукт", en: "product"}
13
13
  - {id: process, ru: "процесс", en: "process"}
14
14
  - {id: organisation, ru: "организация", en: "organisation"}
@@ -218,10 +218,12 @@ schema_version: "0.1"
218
218
  case: spectra-coffee-fiction
219
219
  taxonomies:
220
220
  tier:
221
- - {id: t1, ru: "владелец и семья", en: "owner and family"}
222
- - {id: t2, ru: "сотрудники", en: "employees"}
221
+ - {id: intent, ru: "замысел", en: "intent"}
222
+ - {id: model, ru: "модель бизнеса", en: "business model"}
223
223
  ```
224
224
 
225
+ A tier value names a field of the business, not a party: tier 1 «замысел» / "intent" holds the intent of a position regarding the business (owner, bank, employees, buyer), and the tier of a record or line is the tier of the field of its parameter, whoever wrote it (`cases/spectra_coffee/taxonomies.yaml` has all six).
226
+
225
227
  `smd validate --taxonomies <file>` checks every `tags` value and every cell of a column bound by `detail.keys` against the file: an unknown taxonomy or value is an error naming the item and the value. In a bound cell, values are separated by `;` and spaces around them are trimmed; an empty cell is allowed. Without the file, a record that uses `tags` or `detail.keys` gets one warning. `smd publish --taxonomies <file>` validates with it; `smd pack --taxonomies <file>` carries it in the pack.
226
228
 
227
229
  ## Patches: a decision as a record
@@ -45,7 +45,7 @@ An AI agent is an actor like a fund or a bank: it goes in the `fillers` of the r
45
45
 
46
46
  ## A role with structure
47
47
 
48
- When one role has inner structure, the board shows one element with a `short` label, and its `detail` table holds the structure. Example: stakeholders on each of the six tiers of OST (Organizational Schema Theory), from the owner's intent to the organisation. In English the six are tiers and L0–L5 are the levels of the OST projection cascade; in Russian records «уровень» means a tier only.
48
+ When one role has inner structure, the board shows one element with a `short` label, and its `detail` table holds the structure. Example: stakeholders on each of the six tiers of OST (Organizational Schema Theory), from intent to the organisation. In English the six are tiers and L0–L5 are the levels of the OST projection cascade; in Russian records «уровень» means a tier only.
49
49
  - Columns of that table: tier, stakeholder, `fillers`, example of a line, data to check it by.
50
50
  - The table appears in the frames panel on click, in the HTML tables and in the Markdown digest. It is never drawn on the board.
51
51
  - Split the role into separate board elements only when the session works each part on its own.
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  id: khaprov-levels
3
3
  title: Seven levels of management complexity and three kinds of complexity
4
- version: 0.2.0
4
+ version: 0.2.2
5
5
  source: "Khaprov, expert lecture on the entrepreneur as organizer of complexity, program day 4, read through a local digest of the automatic transcript and the Q&A file (digest sections 1, 2.1-2.3, 2.5, 4, Q&A 1-2 and 10; the digest is not in the repo); Khaprov in the text below means that lecture"
6
6
  route: smd
7
7
  offered_by: [positional-construction, functional-plan]
@@ -66,14 +66,14 @@ Systems of systems (the third block of the lecture): at the technological order
66
66
 
67
67
  ## Diagonal: the seven levels and the six tiers of a business (AI draft)
68
68
 
69
- **AI draft**, from a working session of 29.10.2026; not Khaprov's and not yet accepted by the methodologist. Khaprov gives no tiers of a business. The six tiers are the case group's scheme of a business (OST): 1 замысел (intent), 2 модель бизнеса (business model), 3 юрлицо и права (legal entity and rights), 4 продукт (product), 5 процесс (process), 6 организация (organisation). The diagonal says at which level of complexity a change of each tier is decided. It is the engine's reading **(own extrapolation)**.
69
+ **AI draft**, from a working session of 29.10.2026; not Khaprov's and not yet accepted by the methodologist. Khaprov gives no tiers of a business. The six tiers are the case group's scheme of a business (OST): 1 замысел (intent of each position regarding the business; the owner's is the controlling one), 2 модель бизнеса (business model), 3 юридическое лицо (business entity: rights, obligations, property), 4 продукт (product), 5 процесс (process), 6 организация (organisation). The diagonal says at which level of complexity a change of each tier is decided. It is the engine's reading **(own extrapolation)**.
70
70
 
71
71
  | Level | Tier of a business | Where it goes in a record |
72
72
  |---|---|---|
73
73
  | 7 ontology | none: there is no seventh tier. Ontology is the frame of tier 1, recorded as an ontology record | the `ontology` record of the case (`object`, `valid_for`, `lives_in`, `tempos`, `horizon`, `covers`; lens `khaprov-ontology`) |
74
- | 6 culture, axiology | 1 замысел | an element tagged with tier 1 when the case has a tier taxonomy, `pace` in years |
75
- | 5 politics | 2 модель бизнеса, 3 юрлицо и права | as above, tiers 2 and 3 |
76
- | 4 strategy | 2 модель бизнеса, 3 юрлицо и права | as above, tiers 2 and 3 |
74
+ | 6 culture, axiology | 1 замысел: the stated purpose and values of each position regarding the business. Culture as lived is tier 6 организация, not tier 1 (case owner 09.11.2026) | an element tagged with tier 1 when the case has a tier taxonomy, `pace` in years; a record of culture as lived is tagged tier 6 |
75
+ | 5 politics | 2 модель бизнеса, 3 юридическое лицо | as above, tiers 2 and 3 |
76
+ | 4 strategy | 2 модель бизнеса, 3 юридическое лицо | as above, tiers 2 and 3 |
77
77
  | 3 programs | 4 продукт | as above, tier 4 |
78
78
  | 2 projects | 5 процесс | as above, tier 5 |
79
79
  | 1 objects | 5 процесс, 6 организация | as above, tiers 5 and 6 |
@@ -92,7 +92,7 @@ Pace falls as the level rises: what is decided at a higher level changes more sl
92
92
  8. If the problem sits at the level of a previous decision that cannot be repaired lower down, what is that decision and who made it?
93
93
  9. Does this case have a whole that spans several systems? What is that whole, and who in the existing systems (finance, state, suppliers, customers) supports it? List them as places for others, not as parties already agreed.
94
94
  10. Is the entrepreneurial function (working outside certainty, deciding at the top level) held by someone, and is it distinct from the manager's position in the case?
95
- 11. On the diagonal (AI draft): which tier of the business does this change touch, and at which level is it being decided? Is that the level the diagonal gives for the tier? A business model or rights question (tiers 2-3) settled as a project or an object is decided too low; an intent question (tier 1) needs culture, and the ontology record that frames it.
95
+ 11. On the diagonal (AI draft): which tier of the business does this change touch, and at which level is it being decided? Is that the level the diagonal gives for the tier? A business model or rights question (tiers 2-3) settled as a project or an object is decided too low; an intent question (tier 1) is decided at the level of culture and axiology, as the stated purpose and values of a position, and needs the ontology record that frames it. Culture as lived in the business is a tier-6 question, not a tier-1 one.
96
96
  12. Pace on the diagonal (AI draft): how many years does each tier on the boards take to change? Does the period grow with the level, as the diagonal expects? Where a higher tier is expected to change faster than a lower one, or a tier the ontology covers changes within the ontology's horizon, what does the group take as the reason?
97
97
 
98
98
  ## Output slots
@@ -24,7 +24,7 @@ Front matter, checked by `tests/test_procedures.py`:
24
24
  | `small-situation` | 3 | the human's answers to the four questions | the small situation, positions, places for others, hypotheses |
25
25
  | `visionary-tract` | 3 | the small situation | normality boundary, garland, model, bridge, view of oneself, goals: AI candidates with moves |
26
26
  | `positional-construction` | 3 | accepted candidates | the positional set, cooperation, ontology valid for named positions |
27
- | `stakeholder-ontology` | 3 | one stakeholder position (default, the owner, the tier-1 stakeholder) in a solo session or an interview | an ontology record valid for that position in its own words, the shareable part as a cited file, a note that the private part exists, the translation into the six-tier ontology with its losses |
27
+ | `stakeholder-ontology` | 3 | one stakeholder position (default, the owner, the controlling position) in a solo session or an interview | an ontology record valid for that position in its own words, the position's intent as a tier-1 `goal` element, the shareable part as a cited file, a note that the private part exists, the translation into the six-tier ontology with its losses |
28
28
  | `functional-plan` | 3 | the new frame and the positional set | functions with performer, payer and receiver; gaps for empty places |
29
29
  | `problematization` | 3 | a difficulty and a named scheme | plus/minus marking, gaps and problem theses, goals and themes |
30
30
  | `qualification-pass` | 3 | a board set | K items against the program's criteria and the classic checks |
@@ -2,7 +2,7 @@
2
2
  id: positional-construction
3
3
  title: Positional construction, shifts and a common object
4
4
  step: 3
5
- version: 0.2.8
5
+ version: 0.2.9
6
6
  role: визионер
7
7
  profile: any
8
8
  inputs:
@@ -143,7 +143,7 @@ ontology:
143
143
  - `subjects` has one line for each actor in `valid_for`, and for no other. The validator warns on a line for an actor outside `valid_for` and on an actor of `valid_for` with no line. For a place for others the line is your hypothesis of what the subject would be, so the record stays `voice: ai`.
144
144
  - `aspects` takes the object apart (the ontology aspects): `activity` (what is done), `carrier` (who or what performs it and keeps the ability), `ownership` (who holds the right), `management` (who decides), `separation` (how these come apart, or that they do not). Fill every aspect the human or the sources speak to; write "не определено" for an aspect nobody has spoken to, not a guess. The aspects feed `competes` and the test H.
145
145
  - `competes` answers Khaprov's ontology test, which is program vocabulary: what do we say we make; what does the competitor say; do objects compete here, or corporations and consortia? Write it as a statement the human can reject.
146
- - An ontology of one position in its own words (a stakeholder ontology, for example the Owner Ontology, the tier-1 stakeholder's) is elicited by `stakeholder-ontology`, with `valid_for` that one position. Read its object and subject as that position's subject here; do not reword them.
146
+ - An ontology of one position in its own words (a stakeholder ontology, for example the Owner Ontology, the controlling position's) is elicited by `stakeholder-ontology`, with `valid_for` that one position. Read its object and subject as that position's subject here; do not reword them.
147
147
  - `test` names a hypothesis H. An ontology is checked for realizability in activity, not for truth (GP1981). Write H:
148
148
 
149
149
  ```yaml
@@ -2,16 +2,17 @@
2
2
  id: stakeholder-ontology
3
3
  title: Stakeholder ontology in the position's own words
4
4
  step: 3
5
- version: 0.1.1
5
+ version: 0.2.0
6
6
  role: игротехник
7
7
  profile: any
8
8
  inputs:
9
- - one position whose ontology is elicited (default, the owner, the tier-1 stakeholder), as a `position` or `place_for_others` element of the record, or the human's statement of it
9
+ - one position whose ontology and intent are elicited (default, the owner, the controlling position), as a `position` or `place_for_others` element of the record, or the human's statement of it
10
10
  - a solo session with the person who occupies that position, or the registered transcript of an interview with that person
11
11
  - the case's source manifest, and its taxonomy file if the record uses `tags`
12
12
  - optional: the record's earlier ontology records, the case's journal or other records of the position's activity (registered sources)
13
13
  outputs:
14
14
  - one ontology record O valid for that one position, with object and subject in the position's own words, `competes`, `tags` and a `test` H
15
+ - the position's intent regarding this business (purpose, what it wants from the business, horizon, exit criteria) in its own words, as a `goal` element of that position tagged tier 1, next to the ontology record (section 3a)
15
16
  - the shareable part as a separate file registered in the manifest and cited by the record: a verbatim glossary of the position's terms as used in records, and the list of ontology-dependent records
16
17
  - a note in the record that the private part exists and who keeps it; the private part itself is not written to the board or the case repository
17
18
  - the translation into the six-tier ontology of a business as a separate, AI-voiced table that names what each translation loses
@@ -22,7 +23,7 @@ sources: [GP1981 (ontology valid for named positions, realizability, representat
22
23
 
23
24
  # Stakeholder ontology in the position's own words
24
25
 
25
- You help one person put down the ontology of the position they occupy: what exists in their activity, what its basic terms mean, what is connected to what, and what is absent, as written from that position. The owner is one of the stakeholders, the tier-1 one, and the default position: a stakeholder ontology, for example the Owner Ontology (the tier-1 stakeholder's). The positions of the other stakeholders are worked the same way: a manager, employees, a customer, a bank, a regulator, a buyer, a successor. One run works one position.
26
+ You help one person put down the ontology of the position they occupy: what exists in their activity, what its basic terms mean, what is connected to what, and what is absent, as written from that position; and next to it the position's intent regarding this business: why it deals with the business, what it wants from it, by when, and when it would stop. Tier 1 of the six tiers is the intent of every position that deals with the business (owner, bank, employees, union, customers, a state body, a buyer, a successor), and each stakeholder ontology is tier-1 content of its position. The owner is one of the stakeholders and the default position: the Owner Ontology is the stakeholder ontology of the owner, and the owner's intent is the controlling instance, the one the business's bodies accept by decision. What sets the owner apart is control (residual decision rights from the charter and the cap table), a tier-3 field, not a tier of its own. The positions of the other stakeholders are worked the same way: a manager, employees, a union, a customer, a bank, a state body, a buyer, a successor. One run works one position.
26
27
 
27
28
  There is no ontology without an author. A picture of an object is valid for the positions it is written from, and pictures from different positions differ without contradicting each other (GP1981). So the record names its one position in `valid_for`, and it is checked for realizability in activity, not for truth. Every system has an ontology, even when its owner cannot name it (Khaprov): an owner who says "we have no ontology" still answers the questions of section 2.
28
29
 
@@ -63,6 +64,8 @@ Then ask two questions for the record:
63
64
  - **What do you make, and what do the others say they make?** Khaprov's ontology test, in the holder's words: what we say we make; what the nearest competitor says; whether objects compete here, or firms and groups of firms. The answer goes into `competes`.
64
65
  - **Which of your records would a newcomer misread without you, and because of which word?** The answers give the list of ontology-dependent records (section 4).
65
66
 
67
+ Then ask for the position's intent regarding this business, in the holder's words (section 3a): Why do you deal with this business? What do you want from it? By when? What would make you stop or leave? Ask for an example each time, and do not use the word "intent" or any tier term in the question.
68
+
66
69
  Rules for the answers:
67
70
  - Write each answer verbatim, with its address in the log. Do not correct, shorten into your own words, or merge two answers.
68
71
  - Restate what you understood and let the holder correct it. The corrected wording is the holder's; your restatement is not kept.
@@ -91,7 +94,7 @@ ontology:
91
94
  - `valid_for` names exactly one position: the one whose words these are. A record valid for several positions needs a cooperation and is built by `positional-construction`, section 5.
92
95
  - `object` and `subjects` are the holder's words, quoted, each with an address in `cites`. `subjects` has one line, for that position.
93
96
  - `competes` is the holder's answer to the ontology test, quoted. If the holder gave none, leave the field out and put the question in `state.open`.
94
- - `tags`: the tier of the position in the case's tier taxonomy. The owner's ontology is tier-1 content, next to the owner's intent (`{tier: [intent]}` where the case's taxonomy calls tier 1 `intent`). A stakeholder of another tier takes that tier's value, if the case binds stakeholders to tiers. Without a taxonomy file, leave `tags` out.
97
+ - `tags`: every stakeholder ontology is tier-1 content of its position, next to that position's intent (`{tier: [intent]}` where the case's taxonomy calls tier 1 `intent`). Positions are not on tiers; their lines are, by the field of each line's parameter. Without a taxonomy file, leave `tags` out.
95
98
  - `cites`: the shareable file (section 4) and the log. Nothing in the record cites the private part.
96
99
  - `note`: in the case's language, that the private part exists and who keeps it, by position. Nothing of its content: no topic, no example, no count.
97
100
  - `voice: ai` until the holder has read the record back and said it is theirs; then drop it and record the decision in `state.accepted`. There is no sign-off function for an ontology record.
@@ -112,6 +115,20 @@ ontology:
112
115
 
113
116
  The holder may name another test. Write `revise_if` or say "способ проверки пока не определен" in the reply and keep `status: untested`. Never write `confirmed` or `refuted`: a result needs a field artefact and an `accept_result` sign-off (`field-result`).
114
117
 
118
+ ## 3a. The position's intent
119
+
120
+ The intent is tier-1 content of the position, recorded apart from its ontology: the ontology says in what terms the position asks its questions, the intent says which questions it asks of this business. Record it as one `goal` element on `od`, `seen_from` the position, `goal_source: own`, `tags: {tier: [intent]}` where the case's taxonomy calls tier 1 `intent`, with the holder's words quoted in `label` and their addresses in `cites`:
121
+
122
+ ```yaml
123
+ - {id: goal-owner, board: od, kind: goal, label: "<the holder's words>", seen_from: p-owner,
124
+ goal_source: own, epistemic: stated, tags: {tier: [intent]}, cites: ["s5#u=9"], voice: ai}
125
+ ```
126
+
127
+ - Only parameters of the position belong here: what it wants from this business and on what terms. A parameter that is recorded in the business's own records goes to the tier of its field, whoever said it: "a million by 2030" is the owner's intent (tier 1); "the family keeps at least 75% of the capital" is a cap-table parameter (tier 3).
128
+ - An intent stated by the holder and an intent attributed to a position by someone else (the owner's account of what the bank wants) are kept apart: the attributed one is `seen_from` the speaker, `epistemic: unverified`, and names the position it is about in `label`.
129
+ - The intent belongs to the position, not to the business. At a change of control only the controlling intent is replaced; the intents of the other positions stay with them.
130
+ - Whether the holder shares the intent is the holder's decision, as for the ontology (section 4). A private intent is not written to the board; the record's `note` says only that it exists and who keeps it.
131
+
115
132
  ## 4. The two parts
116
133
 
117
134
  | Part | Content | Where it is written | Who gets it |
@@ -175,9 +192,11 @@ Write the translation as one element of kind `concept` on the object board (`oo`
175
192
  | The analyst's words in the holder's mouth | six-tier or engine terms in `object`, `subjects` or the glossary; a restatement kept as a quote; a quote with no address | keep only the holder's corrected wording, each with an address; the rest goes to section 5 |
176
193
  | A non-holder speaks for the owner | the human in the session describes the owner's terms | record a thesis with that human's voice, `status: assumption`; the owner's words come from branch (a) or (b) |
177
194
  | The private part on the board | a causal belief, a deliberate absence, a judgement of a person in a label, note, thesis, the registered log or the shareable file | remove it and tell the holder at once; a copy already pushed stays in the repository history, and removing it there is the repository owner's decision |
178
- | The owner set apart from the stakeholders | "owner and stakeholder ontologies" as two kinds | the owner is the tier-1 stakeholder; the Owner Ontology is the stakeholder ontology of the owner position |
179
- | A seventh tier | the Owner Ontology written as a new tier or a new row of a six-tier table; Khaprov's seventh level of his complexity pyramid read as a seventh tier | the Owner Ontology is tier-1 content, next to the owner's intent: tag it with tier 1 |
180
- | Ontology and intent merged | the record's object states what the owner wants to achieve | the ontology says in what terms the questions are asked; the intent says which questions; both are tier 1, recorded apart |
195
+ | The owner set apart from the stakeholders | "owner and stakeholder ontologies" as two kinds | the owner is one of the stakeholders; the Owner Ontology is the stakeholder ontology of the owner position; every position's ontology and intent are its tier-1 content, the owner's intent being the controlling one |
196
+ | A seventh tier | the Owner Ontology written as a new tier or a new row of a six-tier table; Khaprov's seventh level of his complexity pyramid read as a seventh tier | a stakeholder ontology is tier-1 content, next to its position's intent: tag it with tier 1 |
197
+ | Ontology and intent merged | the record's object states what the position wants to achieve | the ontology says in what terms the questions are asked; the intent says which questions; both are tier 1, recorded apart (section 3a) |
198
+ | Tier 1 for the owner only | other positions' aims recorded outside the tiers, or the owner's intent called the tier | tier 1 is the intent of every position; the owner's is the controlling instance; the owner's control is a tier-3 field |
199
+ | A business parameter at tier 1 | a cap-table share, a price or a headcount written as the position's intent | tier 1 holds parameters of the position only; a parameter in the business's records goes to its field's tier |
181
200
  | Translation inside the elicitation | questions asked in tier terms; tier names in the holder's answers | ask in the holder's words; translate in section 5 |
182
201
  | Translation with no losses | a translation row with an empty or "none" loss column and no answer from the holder | name the loss or cite the holder's answer that there is none |
183
202
  | Absences filled | what the holder "should" have added as if it existed | record the absence as said; a gap, if any, is for `problematization` |
@@ -189,7 +208,8 @@ Write the translation as one element of kind `concept` on the object board (`oo`
189
208
  - `object`, `subjects` and `competes` are quotes, each with an address in `cites`; every glossary row has an address.
190
209
  - The private part appears nowhere in the record, the registered log or the shareable file; the record's `note` says only that it exists and who keeps it.
191
210
  - The translation is a separate `concept` element, `voice: ai`, with a loss named in every row.
192
- - No seventh tier; `tags` carries tier 1 for the owner.
211
+ - No seventh tier; `tags` carries tier 1 for the position's ontology and intent.
212
+ - The intent is a separate `goal` element of the position, in its own words, with parameters of the position only.
193
213
  - `test` names an H with `revise_if`, or the reply says why there is none.
194
214
  - Every AI-worded item has `voice: ai`.
195
215
 
@@ -199,6 +219,7 @@ In the reply give:
199
219
  - the branch of section 0 and the position worked;
200
220
  - the glossary and the list of ontology-dependent records, as they stand in the shareable file;
201
221
  - the ontology record and its H;
222
+ - the intent element, or the note that the holder keeps it private;
202
223
  - the translation table;
203
224
  - the decisions for the holder: is the record theirs; for each answer, shareable or private; does the translation lose what the table says; which test to run.
204
225
 
@@ -1,6 +1,6 @@
1
1
  [project]
2
2
  name = "smd-engine"
3
- version = "0.7.6"
3
+ version = "0.7.7"
4
4
  description = "Records, checks and renderings for SMD-style thinking sessions (three boards, cycles, qualifications)"
5
5
  readme = "README.md"
6
6
  license = "MIT AND CC-BY-4.0"
@@ -13,13 +13,13 @@ from smd_engine.cli import main
13
13
  TASK = Path(__file__).resolve().parents[1] / "cases" / "example" / "task"
14
14
 
15
15
  GOLDEN = {
16
- "pack.md": "987e5324ca5672208c48774a9bf7d12ebd89d842acaf0f88182206e90714728b",
17
- "pack.html": "0d1ccfe5af3404aff5db31f24db15d19b2f380ea6ac90631033d0c1f83f2fa36",
18
- "diff.yaml": "7a519d4438ad4399347dfe1884d2a7e02c3486fc5bbd149b7c2d0c770a478c37",
19
- "diff.md": "c76a0cd8763c1915fb484ac7a9d21bf3dffefe47d089a0f34438d222d2235c2d",
20
- "diff.html": "0f3fb204b0014ab6daa330a7afc964ea9b57a888449442b852039c21e454f2f7",
21
- "agenda.md": "9698e1638c6def5656d8dfb9991e2384e7078e68449aade6d20be53f8175779e",
22
- "agenda.yaml": "6814ebe42f2d360d982111fdf8ff98b99f56af8ba33b90eb339a70c97c1af37b",
16
+ "pack.md": "1a7a82e804325b714e0899a953487e83d2bd9f51962bfcb12883b842a3ed881e",
17
+ "pack.html": "f5c4e2ab3a303eb6cba7ce019ddd07f99f36a1eb3a3dc472e7640ea86ef0bfda",
18
+ "diff.yaml": "49fed4970a2323cf75a1cf495e5d587da788c6c9e1a2a3d545dfc90ba9d16afc",
19
+ "diff.md": "ea2bbf9310af5cc79e92549018af9a21a33e6701af60be700b6260d94f671558",
20
+ "diff.html": "835a0dd2cfc7c3828c162a3eadde579ecff9de88c9e70e587b13d29479485f02",
21
+ "agenda.md": "743849d6240b8d934ab3b52d6d37096a5acb0b540052beb013a8edc287e7bdcb",
22
+ "agenda.yaml": "8f078a35bb15beae95f73e977a75cbc5ea648753afe12d885de48765b422ef37",
23
23
  }
24
24
 
25
25
 
@@ -483,7 +483,7 @@ wheels = [
483
483
 
484
484
  [[package]]
485
485
  name = "smd-engine"
486
- version = "0.7.6"
486
+ version = "0.7.7"
487
487
  source = { editable = "." }
488
488
  dependencies = [
489
489
  { name = "jsonschema" },
File without changes
File without changes
File without changes
File without changes