smd-engine 0.6.4__tar.gz → 0.7.0__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.
- {smd_engine-0.6.4 → smd_engine-0.7.0}/CHANGELOG.md +24 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/PKG-INFO +1 -1
- smd_engine-0.7.0/cases/example/deal/answers_boris.yaml +25 -0
- smd_engine-0.7.0/cases/example/deal/answers_gleb.yaml +24 -0
- smd_engine-0.7.0/cases/example/deal/answers_vera.yaml +24 -0
- smd_engine-0.7.0/cases/example/deal/pack.yaml +186 -0
- smd_engine-0.7.0/cases/example/task/answers_ana.yaml +33 -0
- smd_engine-0.7.0/cases/example/task/answers_ben.yaml +37 -0
- smd_engine-0.7.0/cases/example/task/answers_cy.yaml +31 -0
- smd_engine-0.7.0/cases/example/task/pack.yaml +110 -0
- smd_engine-0.7.0/cases/example/task/replies_ana.yaml +17 -0
- smd_engine-0.7.0/cases/example/task/replies_ben.yaml +16 -0
- smd_engine-0.7.0/cases/example/task/transcript_ben.txt +5 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/docs/README.md +2 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/docs/commands.md +8 -0
- smd_engine-0.7.0/docs/deal-mode.md +163 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/docs/stages.md +2 -0
- smd_engine-0.7.0/docs/task-packs.md +137 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/procedures/README.md +2 -0
- smd_engine-0.7.0/procedures/task-diff.md +112 -0
- smd_engine-0.7.0/procedures/task-pack.md +90 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/pyproject.toml +1 -1
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/cli.py +6 -1
- smd_engine-0.7.0/src/smd_engine/deal/__init__.py +2 -0
- smd_engine-0.7.0/src/smd_engine/deal/cli.py +116 -0
- smd_engine-0.7.0/src/smd_engine/deal/consent.py +75 -0
- smd_engine-0.7.0/src/smd_engine/deal/ledger.py +132 -0
- smd_engine-0.7.0/src/smd_engine/deal/overlap.py +40 -0
- smd_engine-0.7.0/src/smd_engine/deal/seal_cmd.py +63 -0
- smd_engine-0.7.0/src/smd_engine/deal/sealed.py +155 -0
- smd_engine-0.7.0/src/smd_engine/deal/verdict.py +212 -0
- smd_engine-0.7.0/src/smd_engine/deal/verdict_cmd.py +72 -0
- smd_engine-0.7.0/src/smd_engine/deal/views.py +144 -0
- smd_engine-0.7.0/src/smd_engine/schemas/task_acceptance.schema.json +40 -0
- smd_engine-0.7.0/src/smd_engine/schemas/task_answers.schema.json +95 -0
- smd_engine-0.7.0/src/smd_engine/schemas/task_pack.schema.json +305 -0
- smd_engine-0.7.0/src/smd_engine/schemas/task_replies.schema.json +36 -0
- smd_engine-0.7.0/src/smd_engine/schemas/task_sealed.schema.json +34 -0
- smd_engine-0.7.0/src/smd_engine/schemas/task_verdicts.schema.json +60 -0
- smd_engine-0.7.0/src/smd_engine/task/__init__.py +1 -0
- smd_engine-0.7.0/src/smd_engine/task/acceptance.py +203 -0
- smd_engine-0.7.0/src/smd_engine/task/agenda.py +151 -0
- smd_engine-0.7.0/src/smd_engine/task/asking.py +104 -0
- smd_engine-0.7.0/src/smd_engine/task/assets/task.css +77 -0
- smd_engine-0.7.0/src/smd_engine/task/assets/task.js +318 -0
- smd_engine-0.7.0/src/smd_engine/task/bounds.py +250 -0
- smd_engine-0.7.0/src/smd_engine/task/check.py +276 -0
- smd_engine-0.7.0/src/smd_engine/task/cli.py +241 -0
- smd_engine-0.7.0/src/smd_engine/task/deal_check.py +263 -0
- smd_engine-0.7.0/src/smd_engine/task/deal_items.py +84 -0
- smd_engine-0.7.0/src/smd_engine/task/deal_labels.py +186 -0
- smd_engine-0.7.0/src/smd_engine/task/deal_render.py +227 -0
- smd_engine-0.7.0/src/smd_engine/task/deal_web.py +87 -0
- smd_engine-0.7.0/src/smd_engine/task/diff.py +342 -0
- smd_engine-0.7.0/src/smd_engine/task/diff_html.py +261 -0
- smd_engine-0.7.0/src/smd_engine/task/diff_md.py +285 -0
- smd_engine-0.7.0/src/smd_engine/task/labels.py +442 -0
- smd_engine-0.7.0/src/smd_engine/task/model.py +94 -0
- smd_engine-0.7.0/src/smd_engine/task/names.py +108 -0
- smd_engine-0.7.0/src/smd_engine/task/overwrite.py +47 -0
- smd_engine-0.7.0/src/smd_engine/task/pack_html.py +339 -0
- smd_engine-0.7.0/src/smd_engine/task/pack_md.py +198 -0
- smd_engine-0.7.0/src/smd_engine/task/pairs.py +102 -0
- smd_engine-0.7.0/src/smd_engine/task/positions.py +138 -0
- smd_engine-0.7.0/src/smd_engine/task/ranges.py +94 -0
- smd_engine-0.7.0/src/smd_engine/task/refs.py +30 -0
- smd_engine-0.7.0/src/smd_engine/task/svg.py +390 -0
- smd_engine-0.7.0/src/smd_engine/task/web.py +70 -0
- smd_engine-0.7.0/tests/deal_helpers.py +98 -0
- smd_engine-0.7.0/tests/test_deal_acceptance.py +157 -0
- smd_engine-0.7.0/tests/test_deal_golden.py +42 -0
- smd_engine-0.7.0/tests/test_deal_items.py +298 -0
- smd_engine-0.7.0/tests/test_deal_positions.py +354 -0
- smd_engine-0.7.0/tests/test_deal_ranges.py +169 -0
- smd_engine-0.7.0/tests/test_deal_sealed.py +354 -0
- smd_engine-0.7.0/tests/test_deal_verdict.py +576 -0
- smd_engine-0.7.0/tests/test_deal_views.py +368 -0
- smd_engine-0.7.0/tests/test_task.py +475 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/uv.lock +1 -1
- {smd_engine-0.6.4 → smd_engine-0.7.0}/.claude/agents/smd-game-technician.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/.claude/agents/smd-methodologist.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/.claude/agents/smd-visionary.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/.claude/commands/procedure.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/.flake8 +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/.github/workflows/ci.yml +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/.github/workflows/release.yml +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/.gitignore +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/.python-version +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/CONTRIBUTING.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/LICENSE +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/README.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/README_ru.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/cases/example/bakeries-c1.board.yaml +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/cases/example/bakeries-c2.board.yaml +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/cases/example/golden/README.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/cases/example/golden/bakeries-c2-expected.board.yaml +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/cases/example/golden/s3_transcript.txt +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/cases/example/patches/bakeries-c2-1.patch.yaml +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/cases/example/sources.yaml +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/cases/example/two-boards-c1.board.yaml +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/cases/example_ru/pekarni-c1.board.yaml +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/cases/example_ru/pekarni-c2.board.yaml +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/cases/example_ru/pekarni-oru-c1.board.yaml +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/cases/example_ru/pekarnya-holding-c1.board.yaml +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/cases/example_ru/sources.yaml +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/cases/spectra_coffee/README.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/cases/spectra_coffee/bank.story.yaml +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/cases/spectra_coffee/buyer.story.yaml +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/cases/spectra_coffee/owner.story.yaml +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/cases/spectra_coffee/sources.yaml +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/cases/spectra_coffee/spectra-coffee-c1.board.yaml +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/cases/spectra_coffee/successor-premortem.story.yaml +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/cases/spectra_coffee/taxonomies.yaml +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/docs/changelog-0.2-0.5.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/docs/checks.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/docs/data-model.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/docs/first-board.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/docs/glossary.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/docs/hypotheses.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/docs/method/README.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/docs/method/encodable.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/docs/method/formal-stance.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/docs/method/odi-problematization.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/docs/method/reconciliation.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/docs/method/robustness-rules.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/docs/method/roles-and-actors.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/docs/method/smd-classic.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/docs/method/sources.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/docs/method/structural-moves.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/docs/method/triz-systems.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/docs/plan.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/docs/profiles.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/docs/red-lines.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/docs/stories.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/lenses/README.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/lenses/beer-viable-system.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/lenses/design-chain.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/lenses/fliamer-diamond.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/lenses/khaprov-levels.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/lenses/khaprov-ontology.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/lenses/scamper-check.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/lenses/schukin-boundaries.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/lenses/schukin-interface-tax.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/lenses/three-positions.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/lenses/triz-contradictions.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/procedures/field-result.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/procedures/functional-plan.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/procedures/ingest-transcript.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/procedures/positional-construction.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/procedures/problematization.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/procedures/qualification-pass.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/procedures/reflexive-protocol.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/procedures/small-situation.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/procedures/solo-session.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/procedures/stakeholder-ontology.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/procedures/story.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/procedures/theses-to-board.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/procedures/visionary-tract.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/profiles/classic-two-boards.yaml +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/profiles/management-four-boards.yaml +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/profiles/program-three-boards.yaml +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/roles/README.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/roles/actors.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/roles/game-technician.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/roles/methodologist.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/roles/researcher.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/roles/visionary.md +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/__init__.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/agree.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/apply.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/compare.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/eval.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/leverage.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/migrate.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/nextstep.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/pack.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/profile.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/records.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/redline.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/render/__init__.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/render/assets/frames.css +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/render/assets/frames.js +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/render/assets/graph.css +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/render/assets/graph.js +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/render/frames.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/render/frames_page.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/render/frames_text.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/render/graph.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/render/graph_ui.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/render/html.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/render/index.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/render/layout.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/render/light.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/render/markdown.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/render/mermaid.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/render/sessionflow.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/render/svg.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/render/text.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/render/vault.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/revise.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/scaffold.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/schemas/__init__.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/schemas/board_patch.schema.json +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/schemas/board_set.schema.json +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/schemas/source_manifest.schema.json +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/schemas/story.schema.json +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/schemas/taxonomies.schema.json +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/screen.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/sources.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/status.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/story/__init__.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/story/check.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/story/gaps.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/story/model.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/story/numbers.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/story/paths.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/story/render.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/validate/__init__.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/validate/ai.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/validate/context.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/validate/graph.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/validate/hints.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/validate/hypotheses.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/validate/management.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/validate/manifest.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/validate/ontology.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/validate/redlines.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/validate/signoffs.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/validate/structure.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/validate/taxonomies.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/validate/theses.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/validate/tract.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/src/smd_engine/verdict.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/conftest.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/story_helpers.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_action_program.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_agree.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_ai_roles.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_apply.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_beer_layer.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_beer_render.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_compare.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_eval.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_export.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_frames.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_graph.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_hypothesis_standard.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_ingestion.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_lenses.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_management.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_migrate.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_nextstep.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_ontology_continuum.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_procedure_checks.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_procedures.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_profile.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_publish.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_record_boards.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_red_lines.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_render_and_cli.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_render_carries.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_render_fields.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_render_ru_pages.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_render_ru_values.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_revise.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_robustness.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_scaffold.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_status.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_story_case.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_story_check.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_story_numbers.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_story_paths.py +0 -0
- {smd_engine-0.6.4 → smd_engine-0.7.0}/tests/test_validate.py +0 -0
|
@@ -4,6 +4,30 @@ 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.7.0 - 2026-11-02
|
|
8
|
+
|
|
9
|
+
Deal mode, package version 0.7.0 (branch feat/deal-mode; the case owner, dz02#l=43 and dz02#l=47). Not tagged or released. Schema stays 0.1 with optional fields; packs without them are unchanged, and their renders are byte for byte as before (`tests/test_deal_golden.py`). `pyproject.toml` goes from 0.6.5 to 0.7.0. Docs: `docs/deal-mode.md` (the cycle, positions, item kinds, views, the sealed branch, the trust step for pilots with age-encrypted transfer and a RAM disk, the threat model, what leaks), the re-run rule in `docs/task-packs.md` (the shared part by anyone, the sealed part only by the holder program), `docs/commands.md`, `docs/README.md`. Not built: the shared asking price and the optional sealed floor with the seller's consent (plan section 7).
|
|
10
|
+
|
|
11
|
+
- Positions, audience, shared core and annex per position; `smd task render --position`; alpha on the core only.
|
|
12
|
+
- Fact items with evidence (`claim`, `source_ids`, source `sha256` and `date`), `nature` and `fit_of` with `after_reading`, red-line items (`kind: line`, class `line_rejected`, route `blocking`). Procedures `task-pack` and `task-diff` 0.2.0. Example in `cases/example/deal/`.
|
|
13
|
+
- Map acceptance: pack `map` (board id, version, sha256), record `task_acceptance` (vocabulary, elements, independent check, pinned to the board's sha256, void on any edit), `smd task check --acceptance [--board] [--prior]` with the elements to ask again found by `compare.compare` (`src/smd_engine/task/acceptance.py`). The engine writes no acceptance.
|
|
14
|
+
- Item kind `range` (`{min, max, unit, date?}`, the unit named by the item): identical spans agree, nested spans refine, spans with a common stretch are the new class `compatible` (route `accept_unless_objected`), spans with none are a `value` conflict; a wrong unit or `min` above `max` is an error (`src/smd_engine/task/ranges.py`).
|
|
15
|
+
- Pairs and per-position views: pack `pairs` (member pairs), diff `by_pair`, agenda `call_by_pair` (`src/smd_engine/task/pairs.py`); `smd deal views` writes `diff.<position>.yaml`, `.md` and `.html` (`src/smd_engine/deal/`): no point outside the audience, no buyer-side fact dispute for the seller's side, value points as `open` or `settled` with the other side's answers removed, a broker on his principal's side. Replies may carry `view`, the sha256 of the view.
|
|
16
|
+
- Sealed bounds, holder and model consent (the case owner, dz02#l=47; price is a flag, never a stop): item kind `bound` (`topic`, `side` floor or ceiling, `unit`, `stage`) with a seller's floor committed at day 0 and an optional buyer's ceiling committed only at the last of `deal.stages` (a ceiling in an earlier stage is an error); `smd deal seal` writes the private `task_sealed` file and prints the sha256 commitment, which is all an answers file may hold; the diff point has class `sealed`, route `price_meeting`, `committed_by`, `silent` and `verdict` (`not_tested`) and no answers; pack `holder` (a broker is never the operator) and `deal: {id, stages, model_consent}`; the diff says `model_pass_allowed` and the model procedure stops when it is false; a `task_sealed` file is refused as an input. Russian page wording «цена: ... — торг на личной встрече» (`src/smd_engine/task/bounds.py`, `src/smd_engine/deal/sealed.py`).
|
|
17
|
+
- Verdict, ledger and run cap (dz02#l=47): `smd deal verdict` compares a sealed floor and ceiling of one topic behind a `Comparator` protocol (`LocalComparator`, method `local-v1`, `src/smd_engine/deal/overlap.py`) and appends `met`, `not_met` or `not_tested` to a hash-chained ledger `verdicts.yaml` (record `task_verdicts`; no number, salt or gap in it; commitments of a file are checked against the answers). One run per seller-buyer pair and topic; a second only after `smd deal consent` has logged both parties; two at most; a run that was not tested does not count. `smd task diff --ledger` writes each bound point's verdict and `ledger_head`, so a cut ledger no longer matches an earlier diff. Pages read «цена: условия сошлись / не сошлись / не проверено — торг на личной встрече».
|
|
18
|
+
- Asking price first (ЦН1 А, the case owner, dz02#l=55; overrides the sealed floor and ceiling being the default price route). A deal pack with a seller states `deal.asking_price: {value, unit, stage?}`, shared; the seller chooses the stage at which the pack pages open it (default: the stage after `nda`), `smd task render --stage` shows «запрашиваемая цена» / "asking price" from that stage on, and the diff, its views and the agenda show it (`src/smd_engine/task/asking.py`); a deal pack with a seller and no asking price is a `smd task check` error. The sealed branch is optional and off by default: `deal.sealed_floor: true` is needed for any `bound` item (a check error otherwise), and then every verdict run, the first included, needs the seller's consent in the ledger naming the buyer (the `task_consent` file and the ledger entry gain `buyer`; `smd deal consent --new` starts a ledger; the per-pair cap of two stays). The buyer gives no number: the example pack has an optional shared choice item `price-talk` at the last stage (item field `stage`). Verdict tests keep their meaning with `sealed_floor: true` in the example. Security: `smd task diff` prints a warning when a deal diff has annex points (full diff: holder only; send parties their views from `smd deal views`), `docs/deal-mode.md` says so, and a test checks that no hidden annex item id or question is in any view. Procedure `task-pack` 0.2.1. Docs: `deal-mode.md`, `task-packs.md`, `commands.md`.
|
|
19
|
+
|
|
20
|
+
## 0.6.5 - 2026-11-02
|
|
21
|
+
|
|
22
|
+
Task packs (the case owner, 2 November 2026, dz02#l=11 and dz02#l=15, gate АС2 В): the engine carries the tooling for group work in an async mode. No change to the board schema or to any existing command; the package version is not bumped.
|
|
23
|
+
|
|
24
|
+
- Three new schemas, `task_pack`, `task_answers` and `task_replies` (schema 0.1), and the commands `smd task check | render | diff | agenda` (`src/smd_engine/task/`). The files are plain YAML named by the cycle, not record files that `smd validate` discovers. `docs/task-packs.md` describes the cycle: a pack, a term check in every pack (АС6 А), blind answers (АС4 А), a diff that anyone can re-run with the raw answers attached (АС3 В), a reply per open point (accept another member's answer, keep mine, discuss), and a call only for the points marked discuss or left without a reply (АС5 А).
|
|
25
|
+
- `smd task diff` classes the structured items by script: agreement, refinement (one set holds another, for multi and ids), conflict, only one (a point raised by one member, and every added point); identical `steps` sets agree, others conflict until the model marks them compatible. Text, term-check items and the subtype of a conflict (term, position, fact, value) are left to the model (`procedures/task-diff.md`, `class_by: model`, an AI draft). Krippendorff's alpha over the choice items and per section reuses `agree.alpha_nominal`. The diff has no date, so the same answers give the same bytes.
|
|
26
|
+
- Voice (dz02#l=15): an answers file may list transcripts (`path`, `sha256`, `note`) as a fuller raw source of the member's position; the diff verifies each sha256 when the file exists. When members propose different next steps the conflict goes to the call unless the model marks the steps compatible (both can be done, or one after the other), when they are listed as compatible and accepted.
|
|
27
|
+
- `smd task render` writes `pack.md` (tables, the cycle and the ontology relations as Mermaid) and `pack.html` (one offline file with the ontology as inline SVG, the items as a form that saves itself in the browser, and a button that downloads `answers_<member>.yaml`); given a `diff.yaml` it writes `diff.md` and `diff.html`, the latter with a reply form that downloads `replies_<member>.yaml`. Ru and en. `smd task agenda` writes `agenda.md` and `agenda.yaml`.
|
|
28
|
+
- Procedures `task-pack` and `task-diff` (0.1.0), `docs/task-packs.md`, `docs/commands.md`, and an invented example in `cases/example/task/` (three members, six items of every kind, answers and replies) with `tests/test_task.py`.
|
|
29
|
+
- Task pages, after the owner looked at the generated pack (dz02#l=31): the ontology drawing wraps every label into its box and sizes the boxes to the text, with no overlapping boxes and arrows that bend round boxes; with many sources to one target (82 elements in the pilot pack) each target is drawn with its sources under it, in columns; a narrow drawing is shown on a phone. An `ids` item is a searchable checklist of element labels grouped under the element their relations lead to, with a count; the answer is still a list of ids; `pack.md` lists the same. The Russian label of the facilitator is «Ведущий». Tables stack on a narrow screen. `diff.html`, `diff.md` and `agenda.md` follow the rule of the pack: items by number and question, members by name, options and refs by label; ids stay in files and attributes. `diff.yaml` gets a `labels` block for this (members, item numbers, options, terms, elements); a diff without it is shown with ids as before, and the example replies carry the new diff sha256.
|
|
30
|
+
|
|
7
31
|
## 0.6.4 - 2026-11-02
|
|
8
32
|
|
|
9
33
|
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.
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.5
|
|
2
2
|
Name: smd-engine
|
|
3
|
-
Version: 0.
|
|
3
|
+
Version: 0.7.0
|
|
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
|
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
record: task_answers
|
|
2
|
+
schema_version: "0.1"
|
|
3
|
+
pack:
|
|
4
|
+
id: bakery-sale
|
|
5
|
+
version: "1"
|
|
6
|
+
sha256: "2768f4c5b53308e79e31c669c5e84aa12eac1594245458798e056a1e8238e2a1"
|
|
7
|
+
annex: {position: buyer, sha256: "5064fce96360737fde4ab8317e08af78af5a770057d6ef94be5d394e8055496b"}
|
|
8
|
+
member: boris
|
|
9
|
+
date: "2026-11-03"
|
|
10
|
+
drafted_by: self
|
|
11
|
+
term_check:
|
|
12
|
+
tc-clients: Customers with a contract or a standing order, not walk-in people.
|
|
13
|
+
tc-key: The person without whom the first month fails.
|
|
14
|
+
tc-ready: When the suppliers and the lease are in writing and transferable.
|
|
15
|
+
answers:
|
|
16
|
+
read-clients: {value: contracts, reason: "Walk-in sales are hard to check."}
|
|
17
|
+
key-person: {value: owner}
|
|
18
|
+
first-year: {value: "Keep the menu, change the supplier of flour."}
|
|
19
|
+
margin: {value: cannot_say, reason: "I have not seen the cost of flour.", source_ids: [s2]}
|
|
20
|
+
lease-term: {value: holds, source_ids: [s3]}
|
|
21
|
+
fit-clients: {value: partly, reason: "I want more contract customers."}
|
|
22
|
+
rl-staff: {value: reject, reason: "A line at 60 percent is enough for me."}
|
|
23
|
+
handover: {value: {min: 6, max: 12, unit: weeks, date: "2026-11-03"}}
|
|
24
|
+
next-steps: {value: ["visit the bakery"]}
|
|
25
|
+
price-talk: {value: below}
|
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
record: task_answers
|
|
2
|
+
schema_version: "0.1"
|
|
3
|
+
pack:
|
|
4
|
+
id: bakery-sale
|
|
5
|
+
version: "1"
|
|
6
|
+
sha256: "2768f4c5b53308e79e31c669c5e84aa12eac1594245458798e056a1e8238e2a1"
|
|
7
|
+
annex: {position: broker, sha256: "e26fb77cd1ee2af7bd9b8c0d23b964c8326bd6086e71a2881430d12ecd01f0e6"}
|
|
8
|
+
member: gleb
|
|
9
|
+
date: "2026-11-03"
|
|
10
|
+
drafted_by: self
|
|
11
|
+
term_check:
|
|
12
|
+
tc-clients: Regulars, the way the accounts count them.
|
|
13
|
+
tc-key: The head baker, if he has no contract.
|
|
14
|
+
tc-ready: When a buyer can see the numbers.
|
|
15
|
+
answers:
|
|
16
|
+
read-clients: {value: regulars}
|
|
17
|
+
key-person: {value: baker, reason: "The owner is replaceable, the baker is not."}
|
|
18
|
+
broker-note: {value: "The lease ends in two years."}
|
|
19
|
+
margin: {value: holds, source_ids: [s2]}
|
|
20
|
+
lease-term: {value: holds}
|
|
21
|
+
fit-clients: {value: fits}
|
|
22
|
+
rl-staff: {value: accept}
|
|
23
|
+
handover: {value: {min: 4, max: 8, unit: weeks}}
|
|
24
|
+
next-steps: {value: ["share the accounts", "visit the bakery"]}
|
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
record: task_answers
|
|
2
|
+
schema_version: "0.1"
|
|
3
|
+
pack:
|
|
4
|
+
id: bakery-sale
|
|
5
|
+
version: "1"
|
|
6
|
+
sha256: "2768f4c5b53308e79e31c669c5e84aa12eac1594245458798e056a1e8238e2a1"
|
|
7
|
+
annex: {position: seller, sha256: "ac3efdecb997477a7ef779ded108781d2b7b3221a581de97d2295f359de79577"}
|
|
8
|
+
member: vera
|
|
9
|
+
date: "2026-11-03"
|
|
10
|
+
drafted_by: self
|
|
11
|
+
term_check:
|
|
12
|
+
tc-clients: People who come back at least once a month, shop and cafe together.
|
|
13
|
+
tc-key: I am; the bakers can be replaced within weeks.
|
|
14
|
+
tc-ready: When the oven and the recipes work without me for a month.
|
|
15
|
+
answers:
|
|
16
|
+
read-clients: {value: regulars, reason: "The cafe regulars are most of the revenue."}
|
|
17
|
+
key-person: {value: owner, reason: "I know the suppliers and the lease holder."}
|
|
18
|
+
sale-reason: {value: "Health. The family does not want to continue."}
|
|
19
|
+
margin: {value: holds, reason: "The accounts show 43 percent.", source_ids: [s2]}
|
|
20
|
+
lease-term: {value: holds, source_ids: [s3]}
|
|
21
|
+
fit-clients: {value: fits}
|
|
22
|
+
rl-staff: {value: accept}
|
|
23
|
+
handover: {value: {min: 4, max: 8, unit: weeks}, reason: "The head baker needs a month to teach the recipes."}
|
|
24
|
+
next-steps: {value: ["share the accounts", "visit the bakery"]}
|
|
@@ -0,0 +1,186 @@
|
|
|
1
|
+
# Invented example of a deal pack: the sale of a small bakery. The three members
|
|
2
|
+
# and their answers are made up. Positions and `audience` make the shared core
|
|
3
|
+
# and one annex per position; `pairs` name the member pairs compared on their
|
|
4
|
+
# own. Answers carry the sha256 of the core and of the member's annex. After any
|
|
5
|
+
# edit here, restamp the answers (tests/deal_helpers.py restamp, see
|
|
6
|
+
# tests/test_deal_positions.py).
|
|
7
|
+
record: task_pack
|
|
8
|
+
schema_version: "0.1"
|
|
9
|
+
id: bakery-sale
|
|
10
|
+
title: Sale of the corner bakery - reading the business alike
|
|
11
|
+
version: "1"
|
|
12
|
+
date: "2026-11-02"
|
|
13
|
+
due: "2026-11-05"
|
|
14
|
+
lang: en
|
|
15
|
+
positions:
|
|
16
|
+
- {id: seller, label: Seller, kind: seller}
|
|
17
|
+
- {id: buyer, label: Buyer, kind: buyer}
|
|
18
|
+
- {id: broker, label: Sell-side broker, kind: broker_sell}
|
|
19
|
+
members:
|
|
20
|
+
- {id: vera, name: Vera, position: seller}
|
|
21
|
+
- {id: boris, name: Boris, position: buyer}
|
|
22
|
+
- {id: gleb, name: Gleb, position: broker, principal: vera}
|
|
23
|
+
pairs:
|
|
24
|
+
- {id: seller-buyer, members: [vera, boris]}
|
|
25
|
+
- {id: broker-buyer, members: [gleb, boris]}
|
|
26
|
+
facilitator: gleb
|
|
27
|
+
holder: {kind: organisation, name: Neutral Escrow Office, program: smd-engine 0.7.0, method: local-v1}
|
|
28
|
+
deal:
|
|
29
|
+
id: bakery-2026
|
|
30
|
+
stages: [nda, full-map]
|
|
31
|
+
model_consent: false
|
|
32
|
+
# The seller states the asking price; the pages open it at `stage` (default:
|
|
33
|
+
# the stage after nda). The buyer names no number in the pack. The sealed floor
|
|
34
|
+
# is off by default; it is on here so that the verdict tests have a floor and
|
|
35
|
+
# a ceiling to compare.
|
|
36
|
+
asking_price: {value: 95000, unit: EUR, stage: full-map}
|
|
37
|
+
sealed_floor: true
|
|
38
|
+
task:
|
|
39
|
+
what: >-
|
|
40
|
+
Read the same description of the bakery, say what the main terms mean to
|
|
41
|
+
you, and say where you read the business differently.
|
|
42
|
+
why: >-
|
|
43
|
+
Seller and buyer should meet at the table holding one picture of the
|
|
44
|
+
business. The seller states the asking price; the buyer names no number here.
|
|
45
|
+
feeds:
|
|
46
|
+
text: the list of terms and facts to settle before the meeting
|
|
47
|
+
ids: [client-base, gap-successor]
|
|
48
|
+
ontology:
|
|
49
|
+
terms:
|
|
50
|
+
- term: client base
|
|
51
|
+
definition: the customers who bought at least once in the last 90 days
|
|
52
|
+
source: s1
|
|
53
|
+
- term: key person
|
|
54
|
+
definition: a person whose leaving would stop a function for more than a month
|
|
55
|
+
source: s1
|
|
56
|
+
- term: family plan
|
|
57
|
+
definition: what the owner's family intends to do with the proceeds and the premises
|
|
58
|
+
source: s1
|
|
59
|
+
audience: [seller]
|
|
60
|
+
elements:
|
|
61
|
+
- {id: goal-sale, label: sale of the bakery, tier: 2, kind: goal}
|
|
62
|
+
- {id: p-owner, label: owner, tier: 3, kind: position}
|
|
63
|
+
- {id: fn-bread, label: bread production, tier: 4, kind: function}
|
|
64
|
+
- {id: fn-cafe, label: cafe counter, tier: 4, kind: function}
|
|
65
|
+
- {id: place-lease, label: premises lease, tier: 5, kind: place_for_others}
|
|
66
|
+
- {id: gap-successor, label: who runs the bakery after the owner, kind: gap}
|
|
67
|
+
relations:
|
|
68
|
+
- {from: goal-sale, to: p-owner, kind: intent of}
|
|
69
|
+
- {from: p-owner, to: fn-bread, kind: answers for}
|
|
70
|
+
- {from: p-owner, to: fn-cafe, kind: answers for}
|
|
71
|
+
- {from: place-lease, to: fn-bread, kind: premises}
|
|
72
|
+
- {from: gap-successor, to: goal-sale, kind: blocks}
|
|
73
|
+
sources:
|
|
74
|
+
- {id: s1, address: "s1#t=00:04:00", note: the owner describes the bakery}
|
|
75
|
+
- {id: s2, address: s2, note: accounts of the last year, sha256: 4b1c9d6a0e7f2358a1d4c6e9b03f5a7218d9c0e4f6a3b5d7c91e2f40a8b6d3c5, date: "2026-10-20"}
|
|
76
|
+
- {id: s3, address: s3, note: the lease contract of the premises, sha256: 7e2a5c8f1b4d6093e8a7c5b2d1f40963a8e7c6b5d4f3a2910e8d7c6b5a4f3e21, date: "2026-09-02"}
|
|
77
|
+
term_check:
|
|
78
|
+
- {id: tc-clients, term: client base, question: "What is the client base of this bakery, in your own words?"}
|
|
79
|
+
- {id: tc-key, term: key person, question: "Who is a key person here, and why?"}
|
|
80
|
+
- {id: tc-ready, term: ready to run, question: "When is the bakery ready to be run by someone else?"}
|
|
81
|
+
items:
|
|
82
|
+
- id: read-clients
|
|
83
|
+
section: Reading
|
|
84
|
+
question: How should the client base be counted?
|
|
85
|
+
kind: choice
|
|
86
|
+
options:
|
|
87
|
+
- {id: contracts, label: Contract customers only, context: "Few customers, stable orders."}
|
|
88
|
+
- {id: regulars, label: Regulars of the last 90 days, context: "Cafe and shop together."}
|
|
89
|
+
- {id: ever, label: Everyone who ever bought, context: "The widest count."}
|
|
90
|
+
refs: [fn-cafe, fn-bread]
|
|
91
|
+
nature: term
|
|
92
|
+
- id: key-person
|
|
93
|
+
section: Reading
|
|
94
|
+
question: Who is the key person of the bakery?
|
|
95
|
+
kind: choice
|
|
96
|
+
options:
|
|
97
|
+
- {id: owner, label: The owner}
|
|
98
|
+
- {id: baker, label: The head baker}
|
|
99
|
+
- {id: nobody, label: Nobody}
|
|
100
|
+
refs: [p-owner, gap-successor]
|
|
101
|
+
nature: term
|
|
102
|
+
- id: margin
|
|
103
|
+
section: Reading
|
|
104
|
+
question: Do the accounts support the claim below?
|
|
105
|
+
kind: fact
|
|
106
|
+
claim:
|
|
107
|
+
text: The gross margin of the bakery in 2025 was above 40 percent.
|
|
108
|
+
asserted_by: seller
|
|
109
|
+
source: s2
|
|
110
|
+
level: stated
|
|
111
|
+
nature: fact
|
|
112
|
+
- id: lease-term
|
|
113
|
+
section: Reading
|
|
114
|
+
question: Do the lease contract and the claim below agree?
|
|
115
|
+
kind: fact
|
|
116
|
+
claim:
|
|
117
|
+
text: The lease of the premises runs until the end of 2028.
|
|
118
|
+
asserted_by: seller
|
|
119
|
+
source: s3
|
|
120
|
+
level: checked
|
|
121
|
+
nature: fact
|
|
122
|
+
- id: fit-clients
|
|
123
|
+
section: Reading
|
|
124
|
+
question: Does this client base fit what you want from the bakery?
|
|
125
|
+
kind: choice
|
|
126
|
+
options:
|
|
127
|
+
- {id: fits, label: It fits}
|
|
128
|
+
- {id: partly, label: It fits in part}
|
|
129
|
+
- {id: unfit, label: It does not fit}
|
|
130
|
+
nature: position
|
|
131
|
+
fit_of: read-clients
|
|
132
|
+
- id: rl-staff
|
|
133
|
+
section: Red lines
|
|
134
|
+
question: Will you keep the baking staff in the first year, as the line below says?
|
|
135
|
+
kind: line
|
|
136
|
+
line: {metric: share of the baking staff kept, unit: "%", min: 80, since: "2026-12-01", until: "2027-12-31", recovery_days: 30}
|
|
137
|
+
- id: sale-reason
|
|
138
|
+
section: Own position
|
|
139
|
+
question: Why does the owner sell now, and what must stay unsaid at the first meeting?
|
|
140
|
+
kind: text
|
|
141
|
+
audience: [seller]
|
|
142
|
+
- id: first-year
|
|
143
|
+
section: Own position
|
|
144
|
+
question: What would you change in the first year?
|
|
145
|
+
kind: text
|
|
146
|
+
audience: [buyer]
|
|
147
|
+
- id: broker-note
|
|
148
|
+
section: Own position
|
|
149
|
+
question: Which weak points of the file will you raise first with the buyer?
|
|
150
|
+
kind: text
|
|
151
|
+
audience: [broker]
|
|
152
|
+
- id: handover
|
|
153
|
+
section: Plan
|
|
154
|
+
question: For how many weeks is a hand-over of the baking work to the buyer realistic?
|
|
155
|
+
kind: range
|
|
156
|
+
unit: weeks
|
|
157
|
+
nature: value
|
|
158
|
+
- id: next-steps
|
|
159
|
+
section: Plan
|
|
160
|
+
question: What are the next steps before the meeting, in order?
|
|
161
|
+
kind: steps
|
|
162
|
+
- id: price-floor
|
|
163
|
+
section: Price
|
|
164
|
+
question: Seal the lowest price you would accept. The number stays with you.
|
|
165
|
+
kind: bound
|
|
166
|
+
bound: {topic: price, side: floor, unit: EUR}
|
|
167
|
+
audience: [seller]
|
|
168
|
+
- id: price-ceiling
|
|
169
|
+
section: Price
|
|
170
|
+
question: Optionally seal the highest price you would pay, once you have studied the business.
|
|
171
|
+
kind: bound
|
|
172
|
+
bound: {topic: price, side: ceiling, unit: EUR, stage: full-map}
|
|
173
|
+
audience: [buyer]
|
|
174
|
+
- id: price-talk
|
|
175
|
+
section: Price
|
|
176
|
+
question: Are you ready to discuss the price, at the level the seller asks or below it?
|
|
177
|
+
kind: choice
|
|
178
|
+
options:
|
|
179
|
+
- {id: at-asking, label: At the level asked}
|
|
180
|
+
- {id: below, label: Below the level asked}
|
|
181
|
+
- {id: not-yet, label: Not yet}
|
|
182
|
+
nature: position
|
|
183
|
+
required: false
|
|
184
|
+
stage: full-map
|
|
185
|
+
diff:
|
|
186
|
+
procedure: task-diff 0.2.0
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
# Invented answers of Ana (bakeries example). Written blind: before seeing Ben's or Cy's.
|
|
2
|
+
record: task_answers
|
|
3
|
+
schema_version: "0.1"
|
|
4
|
+
pack: {id: bakeries-first-service, version: "1", sha256: 5a05efaca298804a5f75c55660df226bec5f24e0d09000a37324785bef0373b8}
|
|
5
|
+
member: ana
|
|
6
|
+
date: "2026-01-21"
|
|
7
|
+
drafted_by: self
|
|
8
|
+
term_check:
|
|
9
|
+
tc-plant: A site that three or more bakeries use. The bakeries stay independent; none of them owns the site alone.
|
|
10
|
+
tc-pilot: Three bakeries for six weeks on one function, then stop and count.
|
|
11
|
+
tc-payer: The party that signs the invoice. A payer may also be a receiver.
|
|
12
|
+
answers:
|
|
13
|
+
first-function:
|
|
14
|
+
value: dough
|
|
15
|
+
reason: The other two functions depend on its output, and the mills already deliver to it.
|
|
16
|
+
source: "s1#t=00:31:00"
|
|
17
|
+
confidence: high
|
|
18
|
+
shared-risks:
|
|
19
|
+
value: [price, quality]
|
|
20
|
+
reason: Both show up in the first week of any pilot.
|
|
21
|
+
confidence: medium
|
|
22
|
+
payer-view:
|
|
23
|
+
value: The bakeries pay per kilo of dough. The organiser does not pay.
|
|
24
|
+
confidence: medium
|
|
25
|
+
pilot-bakeries:
|
|
26
|
+
value: 3
|
|
27
|
+
reason: Three is what one night shift can serve.
|
|
28
|
+
confidence: high
|
|
29
|
+
next-steps:
|
|
30
|
+
value:
|
|
31
|
+
- Ask the mills for a price list
|
|
32
|
+
- Draft the quality standard
|
|
33
|
+
confidence: medium
|
|
@@ -0,0 +1,37 @@
|
|
|
1
|
+
# Invented answers of Ben. A model drafted them from his voice notes and he edited them.
|
|
2
|
+
record: task_answers
|
|
3
|
+
schema_version: "0.1"
|
|
4
|
+
pack: {id: bakeries-first-service, version: "1", sha256: 5a05efaca298804a5f75c55660df226bec5f24e0d09000a37324785bef0373b8}
|
|
5
|
+
member: ben
|
|
6
|
+
date: "2026-01-22"
|
|
7
|
+
drafted_by: model_edited
|
|
8
|
+
transcripts:
|
|
9
|
+
- {path: transcript_ben.txt, sha256: 96c9452b17b7813847779fde911010eca469afc1fea32c0f96937cf10c4388b1, note: voice notes recorded while answering}
|
|
10
|
+
term_check:
|
|
11
|
+
tc-plant: A site owned by the organiser's company, where bakeries rent capacity.
|
|
12
|
+
tc-pilot: A first run with a stop rule written down beforehand.
|
|
13
|
+
tc-payer: The party that funds the equipment.
|
|
14
|
+
answers:
|
|
15
|
+
first-function:
|
|
16
|
+
value: dough
|
|
17
|
+
reason: Dough is the only function with a physical site to share.
|
|
18
|
+
confidence: high
|
|
19
|
+
shared-risks:
|
|
20
|
+
value: [price, quality, payer]
|
|
21
|
+
reason: Without a payer the pilot stops, whatever the flour costs.
|
|
22
|
+
confidence: medium
|
|
23
|
+
payer-view:
|
|
24
|
+
value: The bank leases the equipment and the bakeries pay a fee.
|
|
25
|
+
term_note: I read "payer" as the party that funds the equipment, not the one that signs the invoice.
|
|
26
|
+
confidence: low
|
|
27
|
+
pilot-bakeries:
|
|
28
|
+
value: 3
|
|
29
|
+
confidence: high
|
|
30
|
+
check-first:
|
|
31
|
+
value: [fn-dough, place-mills]
|
|
32
|
+
reason: The mills' delivery terms decide the dough price.
|
|
33
|
+
confidence: medium
|
|
34
|
+
next-steps:
|
|
35
|
+
value:
|
|
36
|
+
- Ask the mills for a price list
|
|
37
|
+
confidence: medium
|
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
# Invented answers of Cy.
|
|
2
|
+
record: task_answers
|
|
3
|
+
schema_version: "0.1"
|
|
4
|
+
pack: {id: bakeries-first-service, version: "1", sha256: 5a05efaca298804a5f75c55660df226bec5f24e0d09000a37324785bef0373b8}
|
|
5
|
+
member: cy
|
|
6
|
+
date: "2026-01-22"
|
|
7
|
+
drafted_by: self
|
|
8
|
+
term_check:
|
|
9
|
+
tc-plant: A kitchen that bakeries can book by the hour.
|
|
10
|
+
tc-pilot: Two weeks on night logistics with the vehicles we already have.
|
|
11
|
+
tc-payer: The bakery that orders. The bank is a lender, not a payer.
|
|
12
|
+
answers:
|
|
13
|
+
first-function:
|
|
14
|
+
value: logistics
|
|
15
|
+
reason: It needs no site and can start with the vehicles the bakeries already have.
|
|
16
|
+
confidence: medium
|
|
17
|
+
shared-risks:
|
|
18
|
+
value: [price]
|
|
19
|
+
confidence: low
|
|
20
|
+
payer-view:
|
|
21
|
+
value: Each bakery pays for its own deliveries; the plant is not paid for at all.
|
|
22
|
+
confidence: medium
|
|
23
|
+
pilot-bakeries:
|
|
24
|
+
value: 3
|
|
25
|
+
confidence: high
|
|
26
|
+
next-steps:
|
|
27
|
+
value:
|
|
28
|
+
- Visit a dairy cooperative
|
|
29
|
+
confidence: low
|
|
30
|
+
added:
|
|
31
|
+
- {text: Agree a stop rule before the pilot starts, refs: [tc-pilot]}
|
|
@@ -0,0 +1,110 @@
|
|
|
1
|
+
# Invented example: a task pack for the bakeries case. The three members and
|
|
2
|
+
# their answers are made up; the answers are built so that each class of the
|
|
3
|
+
# diff appears at least once. Answers carry the sha256 of this file: after any
|
|
4
|
+
# edit here, run the commands in tests/test_task.py (REGENERATE) again.
|
|
5
|
+
record: task_pack
|
|
6
|
+
schema_version: "0.1"
|
|
7
|
+
id: bakeries-first-service
|
|
8
|
+
title: Bakeries - the first service of the shared plant
|
|
9
|
+
version: "1"
|
|
10
|
+
date: "2026-01-20"
|
|
11
|
+
due: "2026-01-23"
|
|
12
|
+
lang: en
|
|
13
|
+
members:
|
|
14
|
+
- {id: ana, name: Ana}
|
|
15
|
+
- {id: ben, name: Ben}
|
|
16
|
+
- {id: cy, name: Cy}
|
|
17
|
+
facilitator: ana
|
|
18
|
+
task:
|
|
19
|
+
what: >-
|
|
20
|
+
Choose which function the shared plant takes first, name the risks the
|
|
21
|
+
group must watch, say who pays, and propose the next steps.
|
|
22
|
+
why: >-
|
|
23
|
+
The board has three functions of the new frame and an empty place for the
|
|
24
|
+
payer (gap-payer). The group cannot start a pilot until it agrees on the
|
|
25
|
+
first function and on a next step.
|
|
26
|
+
feeds:
|
|
27
|
+
text: the pilot function on the board and the plan items for the next two weeks
|
|
28
|
+
ids: [fn-dough, fn-logistics, fn-quality, gap-payer]
|
|
29
|
+
ontology:
|
|
30
|
+
terms:
|
|
31
|
+
- term: shared plant
|
|
32
|
+
definition: one production site that several independent bakeries use, owned by none of them alone
|
|
33
|
+
source: s1#t=00:31:00
|
|
34
|
+
- term: pilot
|
|
35
|
+
definition: a first run of one function with at most three bakeries, with a stop rule agreed beforehand
|
|
36
|
+
source: s3#t=00:05:00
|
|
37
|
+
- term: payer
|
|
38
|
+
definition: the party that carries the cost of a function, whether or not it receives the result
|
|
39
|
+
source: s2
|
|
40
|
+
- term: quality standard
|
|
41
|
+
definition: the written conditions a batch of dough must meet before it leaves the plant
|
|
42
|
+
source: s2
|
|
43
|
+
elements:
|
|
44
|
+
- {id: goal-shared, label: shared production for independent bakeries, tier: 2, kind: goal}
|
|
45
|
+
- {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}
|
|
48
|
+
- {id: fn-quality, label: quality standard, tier: 4, kind: function}
|
|
49
|
+
- {id: place-mills, label: regional mills, tier: 5, kind: place_for_others}
|
|
50
|
+
- {id: gap-payer, label: who pays for the shared plant, kind: gap}
|
|
51
|
+
relations:
|
|
52
|
+
- {from: goal-shared, to: p-organiser, kind: intent of}
|
|
53
|
+
- {from: p-organiser, to: fn-dough, kind: answers for}
|
|
54
|
+
- {from: p-organiser, to: fn-logistics, kind: answers for}
|
|
55
|
+
- {from: p-organiser, to: fn-quality, kind: answers for}
|
|
56
|
+
- {from: place-mills, to: fn-dough, kind: flour}
|
|
57
|
+
- {from: fn-dough, to: fn-quality, kind: dough to check}
|
|
58
|
+
- {from: gap-payer, to: goal-shared, kind: blocks}
|
|
59
|
+
sources:
|
|
60
|
+
- {id: s1, address: "s1#t=00:31:00", note: the organiser describes the new frame}
|
|
61
|
+
- {id: s2, address: s2, note: earlier concept note of the group}
|
|
62
|
+
- {id: s3, address: "s3#t=00:05:00", note: "second session: the pilot idea"}
|
|
63
|
+
term_check:
|
|
64
|
+
- {id: tc-plant, term: shared plant, question: "What does \"shared plant\" mean for you here, in your own words?"}
|
|
65
|
+
- {id: tc-pilot, term: pilot, question: "What would a pilot be, and when would you call it finished?"}
|
|
66
|
+
- {id: tc-payer, term: payer, question: "Who is a payer, and can the payer also be a receiver?"}
|
|
67
|
+
items:
|
|
68
|
+
- id: first-function
|
|
69
|
+
section: Scope
|
|
70
|
+
question: Which function should the shared plant take first?
|
|
71
|
+
kind: choice
|
|
72
|
+
options:
|
|
73
|
+
- {id: dough, label: Dough production, context: "Mills deliver flour; the most volume, the most capital."}
|
|
74
|
+
- {id: logistics, label: Night logistics, context: "Needs vehicles and drivers, not a site."}
|
|
75
|
+
- {id: quality, label: Quality standard, context: "A paper function; cheap, but nothing is produced."}
|
|
76
|
+
recommendation: {value: dough, reason: the other two functions depend on its output}
|
|
77
|
+
refs: [fn-dough, fn-logistics, fn-quality]
|
|
78
|
+
required: true
|
|
79
|
+
- id: shared-risks
|
|
80
|
+
section: Scope
|
|
81
|
+
question: Which risks must the pilot watch?
|
|
82
|
+
kind: multi
|
|
83
|
+
options:
|
|
84
|
+
- {id: price, label: Flour price swings}
|
|
85
|
+
- {id: quality, label: Batches below the standard}
|
|
86
|
+
- {id: payer, label: Nobody agrees to pay}
|
|
87
|
+
- {id: drivers, label: No night drivers}
|
|
88
|
+
refs: [place-mills, gap-payer]
|
|
89
|
+
- id: payer-view
|
|
90
|
+
section: Scope
|
|
91
|
+
question: Who should pay for the plant, and why?
|
|
92
|
+
kind: text
|
|
93
|
+
refs: [gap-payer]
|
|
94
|
+
- id: pilot-bakeries
|
|
95
|
+
section: Plan
|
|
96
|
+
question: With how many bakeries does the pilot start?
|
|
97
|
+
kind: number
|
|
98
|
+
refs: [goal-shared]
|
|
99
|
+
- id: check-first
|
|
100
|
+
section: Plan
|
|
101
|
+
question: Which elements of the board must be checked before the pilot?
|
|
102
|
+
kind: ids
|
|
103
|
+
refs: [fn-dough, fn-logistics, fn-quality, place-mills]
|
|
104
|
+
required: false
|
|
105
|
+
- id: next-steps
|
|
106
|
+
section: Plan
|
|
107
|
+
question: What are the next steps, in order?
|
|
108
|
+
kind: steps
|
|
109
|
+
diff:
|
|
110
|
+
procedure: task-diff 0.1.0
|
|
@@ -0,0 +1,17 @@
|
|
|
1
|
+
# Invented replies of Ana to the diff of the three answers. The diff sha256 is that of
|
|
2
|
+
# the diff.yaml that `smd task diff` writes from pack.yaml and the three answers files.
|
|
3
|
+
record: task_replies
|
|
4
|
+
schema_version: "0.1"
|
|
5
|
+
diff: 7a519d4438ad4399347dfe1884d2a7e02c3486fc5bbd149b7c2d0c770a478c37
|
|
6
|
+
member: ana
|
|
7
|
+
date: "2026-01-24"
|
|
8
|
+
replies:
|
|
9
|
+
tc-plant: {choice: discuss, note: "Ben's plant has an owner; mine has none. We use one word for two things."}
|
|
10
|
+
tc-pilot: {choice: keep}
|
|
11
|
+
tc-payer: {choice: keep}
|
|
12
|
+
first-function: {choice: keep, note: "Dough first: the other two depend on its output."}
|
|
13
|
+
shared-risks: {choice: accept, accept_member: ben}
|
|
14
|
+
payer-view: {choice: discuss}
|
|
15
|
+
next-steps: {choice: keep}
|
|
16
|
+
check-first: {choice: accept, accept_member: ben}
|
|
17
|
+
add-cy-1: {choice: accept, accept_member: cy}
|
|
@@ -0,0 +1,16 @@
|
|
|
1
|
+
# Invented replies of Ben to the diff. He leaves the term check points as positions and
|
|
2
|
+
# sends the first function to the call.
|
|
3
|
+
record: task_replies
|
|
4
|
+
schema_version: "0.1"
|
|
5
|
+
diff: 7a519d4438ad4399347dfe1884d2a7e02c3486fc5bbd149b7c2d0c770a478c37
|
|
6
|
+
member: ben
|
|
7
|
+
date: "2026-01-24"
|
|
8
|
+
replies:
|
|
9
|
+
tc-plant: {choice: keep}
|
|
10
|
+
tc-pilot: {choice: keep}
|
|
11
|
+
tc-payer: {choice: keep}
|
|
12
|
+
first-function: {choice: discuss, note: "Cy's logistics-first needs a different pilot rule."}
|
|
13
|
+
shared-risks: {choice: keep}
|
|
14
|
+
payer-view: {choice: keep}
|
|
15
|
+
next-steps: {choice: accept, accept_member: ana}
|
|
16
|
+
add-cy-1: {choice: accept, accept_member: cy}
|
|
@@ -0,0 +1,5 @@
|
|
|
1
|
+
Ben, voice notes while answering the pack bakeries-first-service. Invented transcript.
|
|
2
|
+
|
|
3
|
+
[00:00] I think dough has to go first, because it is the only function with a site.
|
|
4
|
+
[00:40] The risk nobody wants to say out loud is that nobody pays.
|
|
5
|
+
[01:10] When I say payer I mean whoever funds the equipment, not whoever gets the invoice.
|
|
@@ -12,6 +12,8 @@ Start with `README.md` in the repository root. This folder holds the reference d
|
|
|
12
12
|
| `checks.md` | the checks the validator runs: errors, warnings and hints, and the profile and source of each hint |
|
|
13
13
|
| `hypotheses.md` | hypothesis fields: `type`, `rule`, `observed`, `rivals`, the verdict and its robustness fields |
|
|
14
14
|
| `stories.md` | stories as a checked view over the boards: `smd story paths` and `smd story check`, the story file, rules G1-G7 and S1-S5 |
|
|
15
|
+
| `task-packs.md` | task packs for a group that answers apart: the cycle, the files, `smd task check`, `render`, `diff` and `agenda`, the classes and routes of the diff |
|
|
16
|
+
| `deal-mode.md` | deal mode for a sale or transfer: positions and views, item kinds, the sealed price flag with its holder, ledger and run cap, the trust step for pilots, the threat model and what leaks |
|
|
15
17
|
| `red-lines.md` | red lines: `red_line`, the structured value `line`, `observed` values and the breach rule |
|
|
16
18
|
| `profiles.md` | the profile format: boards and their regions, kinds, the screen layout, the ids every profile defines, the checks of a profile file |
|
|
17
19
|
| `commands.md` | the commands of `smd` with examples, and the exit codes |
|
|
@@ -30,6 +30,14 @@ uv run smd vault cases/example/bakeries-c2.board.yaml out/vault --sources cases/
|
|
|
30
30
|
uv run smd pack solo-session cases/example/bakeries-c2.board.yaml --sources cases/example/sources.yaml -o out/pack.md # attach to any model; --sources carries the manifest, --taxonomies the taxonomy file; with board sets, the skeleton of the latest cycle as "Cells to fill"; prints `pack sha256: <hex>` to stderr, the hash of what it wrote, for `run.pack_sha256`
|
|
31
31
|
uv run smd story paths cases/spectra_coffee/spectra-coffee-c1.board.yaml --audience place-bank # walks of 4-9 items over typed links from the protagonist through a conflict to a resolution, best first; --allow-refers, --limit, --yaml (story skeletons), --gaps (where no typed walk exists and the links that would make one); docs/stories.md
|
|
32
32
|
uv run smd story check cases/spectra_coffee/bank.story.yaml --boards cases/spectra_coffee/spectra-coffee-c1.board.yaml # a story file against rules G1-G7 and S1-S5: ids, levels, numbers, allow-list, dropped oppositions, board stamp, ids off the walk that `context` does not list; exit 1 on an error; `smd story render story.yaml --md` prints a story as Markdown; paths, check and render take --sources and --taxonomies
|
|
33
|
+
uv run smd task check cases/example/task/pack.yaml cases/example/task/answers_ana.yaml --replies cases/example/task/replies_ana.yaml --diff out/diff/diff.yaml # a task pack and its files: schemas, pack sha256, member, item ids, option ids, transcript sha256; --replies and --diff check replies against the diff; --acceptance (with --board, --prior) checks map acceptances and names the elements to ask again; exit 1 on an error; docs/task-packs.md
|
|
34
|
+
uv run smd task render cases/example/task/pack.yaml -o out/pack # pack.md (tables, the cycle and the ontology relations as Mermaid) and pack.html (one offline file: ontology as inline SVG, the items as a form with autosave, an export button for answers_<member>.yaml); given a diff.yaml it writes diff.md and diff.html; a deal pack (with positions) is rendered as its shared core, and `--position <id>` writes pack.<id>.md and pack.<id>.html with that position's annex, and `--stage <id>` shows the seller's asking price from the stage that opens it on (else the pages say when it opens)
|
|
35
|
+
uv run smd task diff cases/example/task/pack.yaml cases/example/task/answers_*.yaml -o out/diff # (deal packs: --ledger verdicts.yaml adds the verdicts and the ledger head; a deal diff with annex points is the holder's file only and the command warns, send parties their views from `smd deal views`) the answers side by side: diff.yaml, diff.md, diff.html; refuses answers with another pack sha256 and a diff.yaml that differs from the new one (--force overwrites); the model's part is procedures/task-diff.md
|
|
36
|
+
uv run smd task agenda out/diff/diff.yaml cases/example/task/replies_ana.yaml cases/example/task/replies_ben.yaml --members ana,ben,cy -o out/agenda.md # the points for the call (a member's discuss, or no reply to an open point) and the points settled before it: agenda.md and agenda.yaml; refuses replies for another diff
|
|
37
|
+
uv run smd deal views cases/example/deal/pack.yaml out/diff/diff.yaml -o out/views # deal pack: diff.<position>.yaml, .md, .html for each position (--position limits it): no point outside the position's audience, no buyer-side fact dispute for the seller's side, value points open or settled only with the other side's answers removed; a broker gets his principal's view; docs/task-packs.md
|
|
38
|
+
uv run smd deal seal cases/example/deal/pack.yaml price-floor -o ~/sealed # deal pack: seal a number for a bound item on your own machine; asks for the number unseen (or --value), writes sealed_<member>_<item>.yaml (private, outside every repo) and prints the commitment to put in your answers file; the number and the salt are never printed; docs/task-packs.md
|
|
39
|
+
uv run smd deal verdict cases/example/deal/pack.yaml price --answers answers_vera.yaml answers_boris.yaml --floor sealed_vera_price-floor.yaml --ceiling sealed_boris_price-ceiling.yaml --ledger verdicts.yaml # the holder (--new for the first entry of a ledger when no consent started it): compare a sealed floor and ceiling (holder.method, local-v1) and append met, not_met or not_tested to the hash-chained ledger; prints the verdict in the pack language and never a number; every run needs the seller's consent naming the buyer, a second also the buyer's, two runs at most; docs/task-packs.md
|
|
40
|
+
uv run smd deal consent cases/example/deal/pack.yaml price --member vera --evidence consent_vera.yaml --ledger verdicts.yaml --new # log one party consent to the next run: his task_consent file (this deal, topic, run, member, buyer and the two commitments); the seller's for every run (the first consent of a deal takes --new), the buyer's too for a second run
|
|
33
41
|
uv run smd sources cases/example/sources.yaml --clean-room --deny-lineage earlier-concept
|
|
34
42
|
uv run smd sources path/to/sources.yaml --folder /local/folder
|
|
35
43
|
uv run smd sources path/to/sources.yaml --folder /local/folder --refresh [ids] # recompute sha256 of the named sources (default: every decision_log); a source that already carries `lines` gets its count rewritten, one that does not is not given one; edit only those lines of the manifest
|