smd-engine 0.7.0__tar.gz → 0.7.2__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.7.0 → smd_engine-0.7.2}/CHANGELOG.md +24 -1
- {smd_engine-0.7.0 → smd_engine-0.7.2}/PKG-INFO +1 -1
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/example/deal/answers_boris.yaml +2 -2
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/example/deal/answers_gleb.yaml +2 -2
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/example/deal/answers_vera.yaml +2 -2
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/example/deal/pack.yaml +12 -3
- {smd_engine-0.7.0 → smd_engine-0.7.2}/docs/commands.md +6 -5
- {smd_engine-0.7.0 → smd_engine-0.7.2}/docs/deal-mode.md +59 -10
- {smd_engine-0.7.0 → smd_engine-0.7.2}/docs/stages.md +1 -1
- {smd_engine-0.7.0 → smd_engine-0.7.2}/docs/task-packs.md +6 -5
- {smd_engine-0.7.0 → smd_engine-0.7.2}/procedures/task-diff.md +2 -2
- {smd_engine-0.7.0 → smd_engine-0.7.2}/procedures/task-pack.md +3 -2
- {smd_engine-0.7.0 → smd_engine-0.7.2}/pyproject.toml +1 -1
- smd_engine-0.7.2/src/smd_engine/deal/agenda_views.py +182 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/deal/cli.py +80 -2
- smd_engine-0.7.2/src/smd_engine/deal/consent.py +197 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/deal/seal_cmd.py +27 -4
- smd_engine-0.7.2/src/smd_engine/deal/signing.py +238 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/deal/verdict.py +73 -10
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/deal/verdict_cmd.py +53 -3
- smd_engine-0.7.2/src/smd_engine/deal/verify.py +365 -0
- smd_engine-0.7.2/src/smd_engine/deal/verify_cmd.py +33 -0
- smd_engine-0.7.2/src/smd_engine/deal/verify_extra.py +221 -0
- smd_engine-0.7.2/src/smd_engine/deal/verify_report.py +90 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/deal/views.py +31 -32
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/schemas/task_answers.schema.json +1 -1
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/schemas/task_pack.schema.json +3 -1
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/schemas/task_verdicts.schema.json +6 -2
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/agenda.py +1 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/bounds.py +1 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/check.py +3 -1
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/cli.py +21 -8
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/deal_check.py +23 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/deal_items.py +1 -1
- smd_engine-0.7.2/src/smd_engine/task/deal_labels.py +356 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/deal_render.py +6 -3
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/deal_web.py +28 -2
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/diff.py +46 -3
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/diff_md.py +29 -5
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/labels.py +4 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/names.py +2 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/pack_html.py +6 -4
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/positions.py +23 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/deal_helpers.py +80 -1
- smd_engine-0.7.2/tests/test_deal_added.py +163 -0
- smd_engine-0.7.2/tests/test_deal_agenda_leaks.py +132 -0
- smd_engine-0.7.2/tests/test_deal_bindings.py +275 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_deal_positions.py +56 -0
- smd_engine-0.7.2/tests/test_deal_signed.py +300 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_deal_verdict.py +25 -5
- smd_engine-0.7.2/tests/test_deal_verify.py +325 -0
- smd_engine-0.7.2/tests/test_deal_verify_forged.py +210 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_deal_views.py +166 -3
- {smd_engine-0.7.0 → smd_engine-0.7.2}/uv.lock +1 -1
- smd_engine-0.7.0/src/smd_engine/deal/consent.py +0 -75
- smd_engine-0.7.0/src/smd_engine/task/deal_labels.py +0 -186
- {smd_engine-0.7.0 → smd_engine-0.7.2}/.claude/agents/smd-game-technician.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/.claude/agents/smd-methodologist.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/.claude/agents/smd-visionary.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/.claude/commands/procedure.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/.flake8 +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/.github/workflows/ci.yml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/.github/workflows/release.yml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/.gitignore +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/.python-version +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/CONTRIBUTING.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/LICENSE +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/README.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/README_ru.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/example/bakeries-c1.board.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/example/bakeries-c2.board.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/example/golden/README.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/example/golden/bakeries-c2-expected.board.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/example/golden/s3_transcript.txt +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/example/patches/bakeries-c2-1.patch.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/example/sources.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/example/task/answers_ana.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/example/task/answers_ben.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/example/task/answers_cy.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/example/task/pack.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/example/task/replies_ana.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/example/task/replies_ben.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/example/task/transcript_ben.txt +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/example/two-boards-c1.board.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/example_ru/pekarni-c1.board.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/example_ru/pekarni-c2.board.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/example_ru/pekarni-oru-c1.board.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/example_ru/pekarnya-holding-c1.board.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/example_ru/sources.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/spectra_coffee/README.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/spectra_coffee/bank.story.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/spectra_coffee/buyer.story.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/spectra_coffee/owner.story.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/spectra_coffee/sources.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/spectra_coffee/spectra-coffee-c1.board.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/spectra_coffee/successor-premortem.story.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/cases/spectra_coffee/taxonomies.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/docs/README.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/docs/changelog-0.2-0.5.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/docs/checks.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/docs/data-model.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/docs/first-board.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/docs/glossary.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/docs/hypotheses.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/docs/method/README.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/docs/method/encodable.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/docs/method/formal-stance.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/docs/method/odi-problematization.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/docs/method/reconciliation.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/docs/method/robustness-rules.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/docs/method/roles-and-actors.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/docs/method/smd-classic.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/docs/method/sources.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/docs/method/structural-moves.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/docs/method/triz-systems.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/docs/plan.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/docs/profiles.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/docs/red-lines.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/docs/stories.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/lenses/README.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/lenses/beer-viable-system.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/lenses/design-chain.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/lenses/fliamer-diamond.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/lenses/khaprov-levels.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/lenses/khaprov-ontology.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/lenses/scamper-check.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/lenses/schukin-boundaries.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/lenses/schukin-interface-tax.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/lenses/three-positions.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/lenses/triz-contradictions.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/procedures/README.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/procedures/field-result.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/procedures/functional-plan.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/procedures/ingest-transcript.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/procedures/positional-construction.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/procedures/problematization.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/procedures/qualification-pass.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/procedures/reflexive-protocol.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/procedures/small-situation.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/procedures/solo-session.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/procedures/stakeholder-ontology.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/procedures/story.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/procedures/theses-to-board.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/procedures/visionary-tract.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/profiles/classic-two-boards.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/profiles/management-four-boards.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/profiles/program-three-boards.yaml +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/roles/README.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/roles/actors.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/roles/game-technician.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/roles/methodologist.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/roles/researcher.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/roles/visionary.md +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/__init__.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/agree.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/apply.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/cli.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/compare.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/deal/__init__.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/deal/ledger.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/deal/overlap.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/deal/sealed.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/eval.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/leverage.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/migrate.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/nextstep.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/pack.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/profile.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/records.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/redline.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/render/__init__.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/render/assets/frames.css +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/render/assets/frames.js +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/render/assets/graph.css +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/render/assets/graph.js +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/render/frames.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/render/frames_page.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/render/frames_text.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/render/graph.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/render/graph_ui.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/render/html.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/render/index.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/render/layout.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/render/light.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/render/markdown.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/render/mermaid.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/render/sessionflow.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/render/svg.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/render/text.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/render/vault.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/revise.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/scaffold.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/schemas/__init__.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/schemas/board_patch.schema.json +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/schemas/board_set.schema.json +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/schemas/source_manifest.schema.json +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/schemas/story.schema.json +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/schemas/task_acceptance.schema.json +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/schemas/task_replies.schema.json +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/schemas/task_sealed.schema.json +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/schemas/taxonomies.schema.json +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/screen.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/sources.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/status.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/story/__init__.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/story/check.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/story/gaps.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/story/model.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/story/numbers.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/story/paths.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/story/render.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/__init__.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/acceptance.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/asking.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/assets/task.css +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/assets/task.js +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/diff_html.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/model.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/overwrite.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/pack_md.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/pairs.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/ranges.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/refs.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/svg.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/task/web.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/validate/__init__.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/validate/ai.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/validate/context.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/validate/graph.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/validate/hints.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/validate/hypotheses.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/validate/management.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/validate/manifest.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/validate/ontology.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/validate/redlines.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/validate/signoffs.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/validate/structure.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/validate/taxonomies.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/validate/theses.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/validate/tract.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/src/smd_engine/verdict.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/conftest.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/story_helpers.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_action_program.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_agree.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_ai_roles.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_apply.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_beer_layer.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_beer_render.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_compare.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_deal_acceptance.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_deal_golden.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_deal_items.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_deal_ranges.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_deal_sealed.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_eval.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_export.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_frames.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_graph.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_hypothesis_standard.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_ingestion.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_lenses.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_management.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_migrate.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_nextstep.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_ontology_continuum.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_procedure_checks.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_procedures.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_profile.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_publish.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_record_boards.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_red_lines.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_render_and_cli.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_render_carries.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_render_fields.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_render_ru_pages.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_render_ru_values.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_revise.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_robustness.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_scaffold.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_status.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_story_case.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_story_check.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_story_numbers.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_story_paths.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_task.py +0 -0
- {smd_engine-0.7.0 → smd_engine-0.7.2}/tests/test_validate.py +0 -0
|
@@ -4,9 +4,32 @@ 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.2 - 2026-11-02
|
|
8
|
+
|
|
9
|
+
The sealed floor audited and bound to the pack text (the case owner, dz02#l=69). Schema 0.1 stays; every new field is optional, and 0.7.0 and 0.7.1 packs, answers, consent files and ledgers still load (old entries are reported `unbound`). Packs without positions give the same bytes as before.
|
|
10
|
+
|
|
11
|
+
- `smd deal verify pack.yaml --ledger verdicts.yaml [--answers ...] [--sealed dir] [--diff diff.yaml] [--json]`: an audit of the ledger any party can run (`src/smd_engine/deal/verify.py`, `verify_extra.py`, `verify_report.py`, `verify_cmd.py`). It checks the chain and head; each consent entry (signature over its stored text with the member's key, hash, bindings to the deal, topic, run, buyer, core sha256 and key list); each counted verdict (the consents it names are earlier, valid, current, for the same topic, run and buyer, with its commitments; seller, and buyer for a second run; run number and cap of two; answers sha256 against the files given, their signatures and commitments); with `--sealed` the outcome recomputed from the sealed files (signatures checked, no number printed); with `--diff` its head and verdicts. Lines are `ok`, `FAIL` or `unbound (old entry)` (labels in English and Russian, `VERIFY_LABELS` in `deal_labels.py`); exit 1 on a `FAIL` or an `unbound` entry (fail closed; `--allow-unbound` for a ledger known to be old); the last line says "all checks passed" only when nothing is `unbound` (else "no check failed, but not fully verified"), and `--json` has `complete`. A counted verdict whose `consents` list is empty is a `FAIL` (the consents it needs are not among them). A counted verdict whose `answers` lack the floor or the ceiling party, or name a non-member, is a `FAIL`. Entries from before 0.7.2 are `unbound`; after the first 0.7.2 entry a later one without the new fields is `FAIL`. `consent.binding_code` is new (the codes behind `binding_problem`). Tests: `tests/test_deal_verify.py`, `tests/test_deal_verify_forged.py` (an empty `consents` list, replaced or replayed inputs, `--allow-unbound`).
|
|
12
|
+
- Bindings of the sealed floor (packs with `deal.sealed_floor: true`; schema 0.1, new fields optional). The `task_consent` file names `pack.sha256` (the core sha256) and `keys` (`key_list_sha` in `signing.py`: sha256 of the sorted `<member> <key>` lines); `smd deal consent` and `smd deal verdict` refuse a consent whose values differ from the pack, and a 0.7.1 consent without them (re-sign; it stays readable in an old ledger and a verdict does not count it). The answers files of members with an `ssh_key` are signed (`answers_<member>.yaml.sig`, namespace `smd-deal`); `smd deal verdict` refuses an unsigned or badly signed one, `smd task diff` only warns. The verdict entry records `answers: {member: sha256}` and, when counted, `consents: [entry sha256, ...]` (schema `task_verdicts`; the chain covers them, older entries without them still verify). A swapped-back older answers file is caught by the signed consents (`commitment_changed`) and its sha256 is on record. Packs without positions give the same bytes as before. Tests: `tests/test_deal_bindings.py`.
|
|
13
|
+
- Deal packs: the diff id of an added point is `add-<member>-<8 hex of the sha256 of its text>` (`-2`, `-3` on a repeat of a shared text; an unshared point hashes its text with a prefix, so no private point is counted in a shared id), no longer `add-<member>-<n>`, whose number showed how many unshared points a member has. Group packs keep the old ids. A diff made before this change has the old ids; make it again.
|
|
14
|
+
- Deal pack forms (`pack.html`, `pack.<position>.html`): each added point has a box «показать всем позициям» / "share with all positions", off by default, and the hint says a point is for the author's position only unless shared; the downloaded answers file carries `share: true` when ticked. Group pages are byte for byte as before, a group pack with a range item or a fact item included (the share box is added only to a deal pack's page).
|
|
15
|
+
- `cases/example/deal/pack.yaml` names `task-diff 0.2.1`; the answers files are restamped.
|
|
16
|
+
- Docs: `deal-mode.md` (the cycle, signatures with the new bindings, "Limits of the signatures" rewritten as closed and still open, "Verifying the ledger", threat model), `commands.md`, `task-packs.md`, `stages.md`.
|
|
17
|
+
|
|
18
|
+
## 0.7.1 - 2026-11-02
|
|
19
|
+
|
|
20
|
+
Fixes to the weak points of deal mode that 0.7.0 left open (the case owner, dz02#l=63). Schema 0.1 stays; every new field is optional, and 0.7.0 packs, answers, diffs and ledgers still load. Packs without positions give the same bytes as before (the pilot pack and the group example were compared byte for byte).
|
|
21
|
+
|
|
22
|
+
- Agendas without leaks. `smd task agenda` on a deal diff writes the common agenda, read by every party: a point with an `audience` shows no question, text, refs, options, claim, answers, item id, class, route or reason. On the call it appears as `annex-1`, `annex-2`... under the item's new `call_title` (a neutral title the pack author writes; `smd task check` warns when one is missing), else under «Точка приложения» / "Annex point". It is not listed under any pair. A settled annex point is left out. Item numbers are counted over the core items only. A fact dispute over a buyer-side claim (new diff field `buyer_claim`) is left out, and a value point shows only `open` or `settled`. The `labels` block keeps the shown points only. Sealed price points stay, with their verdict and no question.
|
|
23
|
+
- Per-position agendas. `smd deal views --replies ... --members ...` also writes `agenda.<position>.yaml` and `.md`, filtered by the rules of the views, with a `view` block (`src/smd_engine/deal/agenda_views.py`).
|
|
24
|
+
- Added points. In a deal pack a point a member adds is for the author's position only, until the author marks it `share: true` in the answers file. Only the audience owes it a reply.
|
|
25
|
+
- `agenda.md` shows `call_by_pair` as «Точки для созвона по парам» / "Call points by pair".
|
|
26
|
+
- Signatures (OpenSSH, no new Python dependency; `src/smd_engine/deal/signing.py`). Pack members may carry `ssh_key`. With `deal.sealed_floor: true`, `smd task check` requires a key for every seller and buyer and rejects a malformed key. The namespace is `smd-deal` and the signer is the member id. `smd deal seal --key` signs the sealed file; without the flag it prints the `ssh-keygen -Y sign` command. `smd deal consent` verifies the consent file (`--signature`, default `<file>.sig`) and stores the signed text and the signature in the ledger entry. `smd deal verdict` re-verifies every consent it counts and the sealed floor and ceiling (`--floor-sig`, `--ceiling-sig`), and refuses unsigned or badly signed files without logging. A holder operator without the parties' private keys can no longer forge their consent. An unsigned 0.7.0 consent can be replaced once by a signed one with the same commitments. `docs/deal-mode.md` lists the limits: a hand-written verdict entry is not re-verified, a consent is not bound to the pack's core sha, and answers files are unsigned.
|
|
27
|
+
- Procedures `task-pack` 0.2.2 and `task-diff` 0.2.1. Docs: `deal-mode.md` (agendas, signatures, threat model), `task-packs.md`, `commands.md`, `stages.md`.
|
|
28
|
+
- Changelog: the 0.7.0 entry no longer calls itself untagged, and it no longer names the asking price as not built.
|
|
29
|
+
|
|
7
30
|
## 0.7.0 - 2026-11-02
|
|
8
31
|
|
|
9
|
-
Deal mode, package version 0.7.0 (
|
|
32
|
+
Deal mode, package version 0.7.0 (the case owner, dz02#l=43 and dz02#l=47). Schema stays 0.1 with optional fields; packs without them are unchanged, and their renders are byte for byte as before (`tests/test_deal_golden.py`). `pyproject.toml` goes from 0.6.5 to 0.7.0. Docs: `docs/deal-mode.md` (the cycle, positions, item kinds, views, the sealed branch, the trust step for pilots with age-encrypted transfer and a RAM disk, the threat model, what leaks), the re-run rule in `docs/task-packs.md` (the shared part by anyone, the sealed part only by the holder program), `docs/commands.md`, `docs/README.md`. The asking price and the optional sealed floor are in the last bullet.
|
|
10
33
|
|
|
11
34
|
- Positions, audience, shared core and annex per position; `smd task render --position`; alpha on the core only.
|
|
12
35
|
- 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/`.
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.5
|
|
2
2
|
Name: smd-engine
|
|
3
|
-
Version: 0.7.
|
|
3
|
+
Version: 0.7.2
|
|
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
|
|
@@ -3,8 +3,8 @@ schema_version: "0.1"
|
|
|
3
3
|
pack:
|
|
4
4
|
id: bakery-sale
|
|
5
5
|
version: "1"
|
|
6
|
-
sha256: "
|
|
7
|
-
annex: {position: buyer, sha256: "
|
|
6
|
+
sha256: "ff3f0133dbf3596c26d05a9410a0d5febfcddcedec79af7fbf48bbadc5598f5f"
|
|
7
|
+
annex: {position: buyer, sha256: "35b25dc48f138d648d4c999e154411c02aae7c7a20d84cb7078d9d9f60e89375"}
|
|
8
8
|
member: boris
|
|
9
9
|
date: "2026-11-03"
|
|
10
10
|
drafted_by: self
|
|
@@ -3,8 +3,8 @@ schema_version: "0.1"
|
|
|
3
3
|
pack:
|
|
4
4
|
id: bakery-sale
|
|
5
5
|
version: "1"
|
|
6
|
-
sha256: "
|
|
7
|
-
annex: {position: broker, sha256: "
|
|
6
|
+
sha256: "ff3f0133dbf3596c26d05a9410a0d5febfcddcedec79af7fbf48bbadc5598f5f"
|
|
7
|
+
annex: {position: broker, sha256: "56072184ee793f34fc3a116cb86c69446860ec2fb7332776935791dc56b439e3"}
|
|
8
8
|
member: gleb
|
|
9
9
|
date: "2026-11-03"
|
|
10
10
|
drafted_by: self
|
|
@@ -3,8 +3,8 @@ schema_version: "0.1"
|
|
|
3
3
|
pack:
|
|
4
4
|
id: bakery-sale
|
|
5
5
|
version: "1"
|
|
6
|
-
sha256: "
|
|
7
|
-
annex: {position: seller, sha256: "
|
|
6
|
+
sha256: "ff3f0133dbf3596c26d05a9410a0d5febfcddcedec79af7fbf48bbadc5598f5f"
|
|
7
|
+
annex: {position: seller, sha256: "c73f2cf96a6ba1737aad29f20a6e2662f9dfd8c0808ad82dc711f92158693cc4"}
|
|
8
8
|
member: vera
|
|
9
9
|
date: "2026-11-03"
|
|
10
10
|
drafted_by: self
|
|
@@ -17,8 +17,12 @@ positions:
|
|
|
17
17
|
- {id: buyer, label: Buyer, kind: buyer}
|
|
18
18
|
- {id: broker, label: Sell-side broker, kind: broker_sell}
|
|
19
19
|
members:
|
|
20
|
-
|
|
21
|
-
|
|
20
|
+
# ssh_key: the party's OpenSSH public key; with deal.sealed_floor his consents and
|
|
21
|
+
# sealed files are signed with the private half. These two keys are made up and
|
|
22
|
+
# their private halves were deleted: nobody can sign for Vera or Boris here.
|
|
23
|
+
# The tests make keys of their own and put them into a copy of this pack.
|
|
24
|
+
- {id: vera, name: Vera, position: seller, ssh_key: "ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAINFml7IJZKaSAhJg31js3yoSUic5KUw41wTJ7RYnGUSx vera-example"}
|
|
25
|
+
- {id: boris, name: Boris, position: buyer, ssh_key: "ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIKJw+2kx/CgXui0RByFjhG3b6uU1c+Hb7F4yzKc8SD6K boris-example"}
|
|
22
26
|
- {id: gleb, name: Gleb, position: broker, principal: vera}
|
|
23
27
|
pairs:
|
|
24
28
|
- {id: seller-buyer, members: [vera, boris]}
|
|
@@ -139,16 +143,19 @@ items:
|
|
|
139
143
|
question: Why does the owner sell now, and what must stay unsaid at the first meeting?
|
|
140
144
|
kind: text
|
|
141
145
|
audience: [seller]
|
|
146
|
+
call_title: Own position
|
|
142
147
|
- id: first-year
|
|
143
148
|
section: Own position
|
|
144
149
|
question: What would you change in the first year?
|
|
145
150
|
kind: text
|
|
146
151
|
audience: [buyer]
|
|
152
|
+
call_title: Own position
|
|
147
153
|
- id: broker-note
|
|
148
154
|
section: Own position
|
|
149
155
|
question: Which weak points of the file will you raise first with the buyer?
|
|
150
156
|
kind: text
|
|
151
157
|
audience: [broker]
|
|
158
|
+
call_title: Own position
|
|
152
159
|
- id: handover
|
|
153
160
|
section: Plan
|
|
154
161
|
question: For how many weeks is a hand-over of the baking work to the buyer realistic?
|
|
@@ -165,12 +172,14 @@ items:
|
|
|
165
172
|
kind: bound
|
|
166
173
|
bound: {topic: price, side: floor, unit: EUR}
|
|
167
174
|
audience: [seller]
|
|
175
|
+
call_title: Price
|
|
168
176
|
- id: price-ceiling
|
|
169
177
|
section: Price
|
|
170
178
|
question: Optionally seal the highest price you would pay, once you have studied the business.
|
|
171
179
|
kind: bound
|
|
172
180
|
bound: {topic: price, side: ceiling, unit: EUR, stage: full-map}
|
|
173
181
|
audience: [buyer]
|
|
182
|
+
call_title: Price
|
|
174
183
|
- id: price-talk
|
|
175
184
|
section: Price
|
|
176
185
|
question: Are you ready to discuss the price, at the level the seller asks or below it?
|
|
@@ -183,4 +192,4 @@ items:
|
|
|
183
192
|
required: false
|
|
184
193
|
stage: full-map
|
|
185
194
|
diff:
|
|
186
|
-
procedure: task-diff 0.2.
|
|
195
|
+
procedure: task-diff 0.2.1
|
|
@@ -32,12 +32,13 @@ uv run smd story paths cases/spectra_coffee/spectra-coffee-c1.board.yaml --audie
|
|
|
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
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
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
|
|
35
|
+
uv run smd task diff cases/example/task/pack.yaml cases/example/task/answers_*.yaml -o out/diff # (deal packs with deal.sealed_floor: warns for each answers file of a key holder without a valid `<file>.sig`; 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
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
|
|
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; with `--replies r.yaml... --members a,b,c` it also writes agenda.<position>.yaml and .md cut the same way (the common `smd task agenda` shows an annex point only under its call_title); 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; with `--key <private key>` it also signs the file with ssh-keygen (`<file>.sig`), else it prints the command to run; 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; with deal.sealed_floor it verifies the signatures of the counted consents (bound to the pack's core sha256 and key list), of the answers files of key holders (`<file>.sig`) and of the sealed files (`--floor-sig`, `--ceiling-sig`) and refuses the run if one is missing or bad, and the entry records `answers` and `consents`; 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; with deal.sealed_floor the file needs his SSH signature (`--signature`, default `<evidence>.sig`), kept in the entry
|
|
41
|
+
uv run smd deal verify cases/example/deal/pack.yaml --ledger verdicts.yaml --answers answers_vera.yaml answers_boris.yaml answers_gleb.yaml --sealed safe/ --diff out/diff.yaml # audit a ledger (any party; exit 1 on a FAIL, else 0): chain and head; each consent's signature, hash, bindings (this deal, topic, run, buyer, core sha256, key list); each counted verdict's consents (earlier, valid, current, seller and for a second run buyer), run number and cap, recorded answers sha256 against the files given; with --sealed (the holder's folder of sealed files and .sig) the outcome is recomputed, no number printed; with --diff its head and verdicts; entries from before 0.7.2 read unbound (the last line then says not fully verified, and the exit is 1 unless --allow-unbound); a counted verdict that names no consents (consents: []) is a FAIL; --json for a report; docs/deal-mode.md
|
|
41
42
|
uv run smd sources cases/example/sources.yaml --clean-room --deny-lineage earlier-concept
|
|
42
43
|
uv run smd sources path/to/sources.yaml --folder /local/folder
|
|
43
44
|
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
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Deal mode: task packs for a sale or transfer
|
|
2
2
|
|
|
3
|
-
A task pack (see `task-packs.md`) serves a group that answers apart. Deal mode adds optional fields so that the same cycle serves counterparties: a seller, a buyer, brokers, and a neutral holder of one sealed number. Nothing here changes a group pack: a pack with none of the new fields validates, renders and diffs byte for byte as before (`tests/test_deal_golden.py`). Schema stays `0.1`;
|
|
3
|
+
A task pack (see `task-packs.md`) serves a group that answers apart. Deal mode adds optional fields so that the same cycle serves counterparties: a seller, a buyer, brokers, and a neutral holder of one sealed number. Nothing here changes a group pack: a pack with none of the new fields validates, renders and diffs byte for byte as before (`tests/test_deal_golden.py`). Schema stays `0.1`; deal mode came with 0.7.0, 0.7.1 added signatures and per-position agendas, and 0.7.2 bound consents and answers to the pack and added `smd deal verify`. The invented example is `cases/example/deal/`. The decisions behind it are the case owner's, 2 November 2026 (dz02#l=43, dz02#l=47, and dz02#l=55 on the price: asking price first).
|
|
4
4
|
|
|
5
5
|
What deal mode is for: the parties read the same description of the business, find where they read it differently, and arrive at the table with one picture. They may then agree on everything except the price. That is a normal, successful result, so the price is never a stop. The seller states an asking price in the pack, and the price is bargained at an in-person meeting. Only if the seller switches it on does the engine also report a flag on whether his sealed floor and the buyer's sealed ceiling met.
|
|
6
6
|
|
|
@@ -41,14 +41,20 @@ A pack may also pin the map the members are asked to accept (`map: {id, version,
|
|
|
41
41
|
|
|
42
42
|
## Views
|
|
43
43
|
|
|
44
|
-
`smd deal views pack.yaml diff.yaml -o out/views` writes `diff.<position>.yaml`, `.md` and `.html` for each position (`--position` limits it). **The full `diff.yaml` in deal mode is the holder's file only.** It holds every answer of every member, the points of every annex (audience), and a `labels` block that names every item. A party is never sent it, nor its `diff.md` or `diff.html`; each position is sent its own view. `smd task diff` prints a warning when it writes a deal diff that has annex points. A view leaves out the annex points not for the position and the entries of the `labels` block for them (`tests/test_deal_views.py` checks that no hidden item id or question is in a view's yaml, md or html). The agenda
|
|
44
|
+
`smd deal views pack.yaml diff.yaml -o out/views` writes `diff.<position>.yaml`, `.md` and `.html` for each position (`--position` limits it). **The full `diff.yaml` in deal mode is the holder's file only.** It holds every answer of every member, the points of every annex (audience), and a `labels` block that names every item. A party is never sent it, nor its `diff.md` or `diff.html`; each position is sent its own view. `smd task diff` prints a warning when it writes a deal diff that has annex points. A view leaves out the annex points not for the position and the entries of the `labels` block for them (`tests/test_deal_views.py` checks that no hidden item id or question is in a view's yaml, md or html). The agenda has its own rules: see "Agendas" below.
|
|
45
45
|
|
|
46
46
|
A view also leaves out:
|
|
47
47
|
- points not for the position (`audience`);
|
|
48
48
|
- a fact dispute over a claim of the buyer's side, unless the viewer is on that side;
|
|
49
49
|
- on a value point (`nature: value`, a `value` conflict, a range with no nature), the class, route, `sets`, `silent` and the other side's answers. The viewer sees only `open` or `settled`.
|
|
50
50
|
|
|
51
|
-
A side is sell (seller, sell-side broker), buy (buyer, buy-side broker) or the position alone. A broker is on the side of his principal's position and gets his principal's view of the other side. The summary, `by_pair`, labels and transcripts are cut the same way. A view has a `view` block (`position`, and the sha256 of the whole diff). A reply may carry `view`, the sha256 of the view it answers; `smd task check --replies` refuses another view's sha256. An agenda is built from the whole diff only
|
|
51
|
+
A side is sell (seller, sell-side broker), buy (buyer, buy-side broker) or the position alone. A broker is on the side of his principal's position and gets his principal's view of the other side. The summary, `by_pair`, labels and transcripts are cut the same way. A view has a `view` block (`position`, and the sha256 of the whole diff). A reply may carry `view`, the sha256 of the view it answers; `smd task check --replies` refuses another view's sha256. An agenda is built from the whole diff only (see "Agendas").
|
|
52
|
+
|
|
53
|
+
## Agendas
|
|
54
|
+
|
|
55
|
+
`smd task agenda` on a deal diff writes the **common agenda**, for every reader of the call. A point with an `audience` (an annex point, also an added point that is not shared) never shows its question, text, refs, options, claim, red line, answers or item id. If it is on the call it appears as `annex-1`, `annex-2`... under the item's `call_title` (a neutral title the pack author writes; `smd task check` warns when an item with an audience has none, or when a core item has one), else under the generic «Точка приложения» / "Annex point". It shows no class, route or reason: the members who chose discuss or did not reply would name its audience, and a rejected red line is not said to be one. It is not listed under a pair in `call_by_pair`, which would name its audience. The item numbers are counted again over the core items, as the core pack numbers them, so a number never skips a hidden item. A settled annex point is left out and the counts follow the lists. The sealed price points are the exception: their verdict is the shared state of the price, so they stay on the list, with class, verdict and who committed, but with no question or id. The `labels` block and `call_by_pair` keep the shown points only. The common agenda is read by both sides, so it follows the sell side's view: a fact dispute over a claim of the buyer's side (`buyer_claim: true` on the diff point, set by `smd task diff`) is left out of it, and a value point shows only `open` or `settled`, with no route and no replies. A diff made before 0.7.1 has no `buyer_claim`; make it again.
|
|
56
|
+
|
|
57
|
+
`smd deal views pack.yaml diff.yaml -o out/views --replies replies_*.yaml --members a,b,c` also writes `agenda.<position>.yaml` and `.md` for each position it writes views for. The agenda is cut by the rules of the position's view (no point outside the audience, no buyer-side fact dispute for the sell side, a value point shown as `open` or `settled` with the replies of the position's own side only, labels numbered over the items the position holds and `call_by_pair` cut to the points shown) and has a `view` block (`position`, sha256 of the whole diff). A point of the position's own annex keeps its question. A group agenda is unchanged.
|
|
52
58
|
|
|
53
59
|
`pairs: [{id, members: [a, b]}]` names the member pairs compared on their own. The diff then has `by_pair` (class and route per point from the two answers only) and the agenda has `call_by_pair`.
|
|
54
60
|
|
|
@@ -93,7 +99,48 @@ The route is `price_meeting`: the parties meet in person and bargain, holding a
|
|
|
93
99
|
|
|
94
100
|
**Ledger.** `verdicts.yaml` (record `task_verdicts`) is append-only and hash-chained: each entry has `prev_sha256` and its own `sha256`, so an edited entry breaks the chain. It contains verdicts, consents and the public commitments, and no number. `smd task diff --ledger verdicts.yaml` verifies the chain and writes each bound point's `verdict` and the `ledger_head` into `diff.yaml`; a ledger cut short later no longer matches an earlier diff, and `task diff` refuses to overwrite that file. If a party's commitment in the answers is not the one the latest counted run used, the point reads `not_tested` and carries `changed_since_run` (the members), so a verdict is never shown for a number nobody has compared. The first entry of a deal's ledger, the seller's consent to run 1 or a verdict, takes `--new` to start it; without it the file must exist, so a mistyped path cannot start a new ledger with a run count of zero.
|
|
95
101
|
|
|
96
|
-
**Run cap and the seller's consent.** One run per seller-buyer pair, topic and deal, and every run, the first included, needs the seller's consent entry naming the buyer. A second run needs a consent entry from each of the two parties. `smd deal consent pack.yaml <topic> --member <id> --evidence <file> --ledger verdicts.yaml` logs one; the first consent of a deal takes `--new`, which starts the ledger. The evidence is the party's `task_consent` file: `record`, `deal`, `pack: {id}`, `topic`, `run`, `member`, `buyer` (the member who commits the ceiling) and `commitments: {floor, ceiling}`, the two commitments now in the answers files. The command refuses a file for another member, run, topic, deal or buyer, and a buyer's consent to the first run; the entry keeps the buyer, the file's sha256 and the commitments. With a number missing the result is `no_floor` or `no_ceiling`, not `consent_missing`. A run whose commitments differ from those in both consents is `commitment_changed`; after a party changes his number both consent again, and see the new commitment.
|
|
102
|
+
**Run cap and the seller's consent.** One run per seller-buyer pair, topic and deal, and every run, the first included, needs the seller's consent entry naming the buyer. A second run needs a consent entry from each of the two parties. `smd deal consent pack.yaml <topic> --member <id> --evidence <file> --ledger verdicts.yaml` logs one; the first consent of a deal takes `--new`, which starts the ledger. The evidence is the party's `task_consent` file: `record`, `deal`, `pack: {id, sha256}`, `keys`, `topic`, `run`, `member`, `buyer` (the member who commits the ceiling) and `commitments: {floor, ceiling}`, the two commitments now in the answers files. The command refuses a file for another member, run, topic, deal or buyer, and a buyer's consent to the first run; the entry keeps the buyer, the file's sha256 and the commitments, and with the sealed floor the file's text (`signed`) and the signature. With a number missing the result is `no_floor` or `no_ceiling`, not `consent_missing`. A run whose commitments differ from those in both consents is `commitment_changed`; after a party changes his number both consent again, and see the new commitment. A file cannot be reused for another party or run. With the sealed floor the file is also signed (see "Signatures"), so the engine can tell who wrote it. A broker cannot consent. Two runs at most; a third is `cap_reached`. A run that returns `not_tested` gives nothing away and does not count. Each counted run gives each side at most one bit.
|
|
103
|
+
|
|
104
|
+
## Signatures
|
|
105
|
+
|
|
106
|
+
Without signatures the holder's operator could write both parties' consent files and sealed files (the trust step below). With `deal.sealed_floor: true` the parties sign with OpenSSH keys, and the engine adds no dependency: it calls `ssh-keygen -Y` (OpenSSH 8.0 or later; a sealed-floor command fails with a clear error where it is missing). The private key is never read by the engine.
|
|
107
|
+
|
|
108
|
+
- **Keys.** `members[].ssh_key` is one OpenSSH public key line (`ssh-ed25519 AAAA... name`). `smd task check` requires it for every member in a seller or buyer position (a broker needs none), refuses a malformed line and a key shared by two members. A member's key is in the core, so changing it voids the answers. Without `sealed_floor` the field is not asked for.
|
|
109
|
+
- **Namespace and signer.** Namespace `smd-deal`; the signer principal is the member id.
|
|
110
|
+
- **Sealed file.** `smd deal seal pack.yaml <item> -o dir --key <private key>` signs the sealed file after writing it (`ssh-keygen -Y sign`, signature `<file>.sig`). Without `--key`, or when signing fails (a wrong key path or passphrase), it prints the commitment and the command for the party to run; the file stays, since a second seal of the item is refused. The party sends the signature with the sealed file.
|
|
111
|
+
- **Consent.** The party signs his `task_consent` file, which names `pack.sha256` (the core sha256 of the pack he was sent) and `keys` (the sha256 of the pack's key list: the lines `<member> <type> <base64>` of every member with a key, comment dropped, sorted, joined by newlines; `key_list_sha` in `signing.py`). `smd deal consent` refuses a consent whose `pack.sha256` or `keys` differs from the pack it is given, and one that names neither (a 0.7.1 consent: the message says to write it again and sign it again); `smd deal consent` takes `--signature` (default `<evidence>.sig`), verifies the file against his key in the pack and refuses a missing or bad signature. The ledger entry also stores the exact text (`signed`, with `evidence` its sha256) and the armored `signature`, so anyone with the ledger can verify the consent again. A ledger from before signatures or before the bindings stays readable; its unsigned (0.7.0) or unbound (0.7.1) consent is replaced by a signed, bound consent naming the same commitments (`smd deal consent` takes it once), since a sealed-floor verdict refuses the old one. A consent whose text the YAML ledger cannot keep exactly (a control character such as U+0085 in a one-line flow-style file) is refused, so that the entry hash stays valid.
|
|
112
|
+
- **Answers files.** A member with an `ssh_key` signs his `answers_<member>.yaml` as it is (`ssh-keygen -Y sign -f <private key> -n smd-deal answers_<member>.yaml`, signature `answers_<member>.yaml.sig` beside it); a broker without a key signs nothing. The signature covers the whole file, so he signs again after every change, such as a new commitment. `smd task diff` on a sealed-floor pack only warns for each answers file of a key-holding member that has no valid signature (stderr; the diff is written as usual), since the group may diff before it signs; `smd deal verdict` refuses (see below).
|
|
113
|
+
- **Verdict.** In a sealed-floor pack `smd deal verdict` first re-verifies every consent entry it counts for the run (signature, `evidence` against `signed`, the entry's commitments and buyer against the signed text, and `pack.sha256` and `keys` against the pack; a consent that names neither is refused), then the answers file of every member with a key given with `--answers` (`<file>.sig`, signer the member id), then the floor file against the seller's key and the ceiling file, if given, against the buyer's (`--floor-sig`, `--ceiling-sig`, default `<file>.sig`). It refuses the run, and logs nothing, if one is unsigned or bad. A run past the cap counts and opens nothing, so nothing is checked. The verdict entry then records `answers: {member: sha256}`, the sha256 of each answers file it read, and, when the run is counted (`met` or `not_met`), `consents: [entry sha256, ...]`, the consent entries it counted (seller first, by entry number); the hash chain covers both, so a later audit can tie a verdict to its signed inputs. Entries of older ledgers have neither and still verify. A consent names the commitments, so an older answers file swapped back by the operator (its signature still valid) shows as `commitment_changed` and is not counted, and the entry records its sha256 for the party to compare with his own copy; no separate sha rule was added, since a second run already needs both parties' signed consents to the commitments now in the answers.
|
|
114
|
+
|
|
115
|
+
The operator can still read both numbers (see the threat model); what he can no longer do is consent or commit for a party, within the pack the party holds.
|
|
116
|
+
|
|
117
|
+
**Limits of the signatures.** In 0.7.1 three things were open; 0.7.2 closes the first two in part and narrows the third.
|
|
118
|
+
|
|
119
|
+
Closed in 0.7.2:
|
|
120
|
+
|
|
121
|
+
- A consent is bound to the pack: it names the core sha256 and the key list, so it cannot be carried to a fork of the pack with other text or other keys. An older signed answers file put back by the operator shows as `commitment_changed`, and the answers sha256 is on record in the verdict entry.
|
|
122
|
+
- A verdict entry names the consents it counted and the answers files it read, and `smd deal verify` (below) re-checks them against the signed consents, the answers files and, for the holder, the sealed files. A hand-written or replayed entry is a `FAIL`.
|
|
123
|
+
- Answers files of key holders are signed; `smd deal verdict` refuses an unsigned one.
|
|
124
|
+
|
|
125
|
+
Still open:
|
|
126
|
+
|
|
127
|
+
- A ledger of the old kind from its first entry (no signed, bound consent) passes `smd deal verify` with every line `unbound`, and so does a ledger whose first entries are old and whose later ones are signed: the old entries before the first 0.7.2 entry cannot be told from forged ones, since a 0.7.0 or 0.7.1 ledger is legitimately like that. The summary says "no check failed, but not fully verified" and counts them, and the exit code is 1: an `unbound` line is not proven. `--allow-unbound` gives exit 0 for a ledger known to come from 0.7.0 or 0.7.1. Entries from before 0.7.2 cannot be checked in full, and a consent made before 0.7.2 is refused by a new run.
|
|
128
|
+
- The comparison of the two numbers is re-run only by someone who has the sealed files, so the holder or a party who is shown them.
|
|
129
|
+
- A consistent forgery from the first entry is caught only by a party who kept an earlier diff or the ledger head. An operator who forks the pack with keys of his own gets a ledger whose consents the fork's parties would have to sign; a party compares the core sha256 of the pack he was sent with the one the holder used.
|
|
130
|
+
- A signature proves who wrote a file, not that it is the current one; it is the signed commitments in the consents that catch a replaced answers file, and only for runs that have a consent.
|
|
131
|
+
|
|
132
|
+
## Verifying the ledger
|
|
133
|
+
|
|
134
|
+
`smd deal verify pack.yaml --ledger verdicts.yaml [--answers answers_*.yaml] [--sealed <folder>] [--diff diff.yaml] [--json] [--allow-unbound]` is an audit any party or a third party can run. It reads only what it is given, changes nothing, and prints one line per check: `ok`, `FAIL`, `unbound (old entry)` or `skipped` (Russian packs: `ок`, `СБОЙ`, `не привязано (старая запись)`, `пропущено`). The exit code is 1 if any line is `FAIL` or `unbound`, else 0; with `--allow-unbound` an `unbound` line does not make it 1. The last line says `all checks passed` only when nothing failed and nothing is `unbound`; with `unbound` lines and no `FAIL` it says `no check failed, but not fully verified (old entries)`. `--json` prints the same as a machine-readable report: `ok`, `complete` (`ok` and no `unbound`), `counts`, `ledger_head` and the checks, each with `check` (code), `status`, `entry`, `detail` and `text`. A sealed-floor pack needs `ssh-keygen`.
|
|
135
|
+
|
|
136
|
+
- **Chain.** The entries are numbered in order, each follows the one before it and has the sha256 of its text; the head is printed.
|
|
137
|
+
- **Each consent entry.** The signed text hashes to `evidence`; its signature is the member's, made with the key the pack lists, namespace `smd-deal`; the text names this deal, pack id, topic, run, member and buyer, and the commitments of the entry; its `pack.sha256` and `keys` are the pack's. The member is a party to the topic, the buyer is the one who commits the ceiling, and the seller alone consents to the first run.
|
|
138
|
+
- **Each counted verdict entry.** The run is the next counted run of the topic and at most two (a `not_tested` entry is not counted). The consents it names (`consents`) are consent entries earlier in the chain, valid by the rule above, for the same topic, run and buyer, with the commitments the verdict recorded, each the latest of its member before the verdict; the seller consented, and for a second run the buyer too (a verdict that names no consents, `consents: []`, is `FAIL` for the same reason: the consents it needs are not among them). The answers sha256 it recorded (`answers`) is matched to the files given with `--answers`: each file is for this text of the pack and signed by its member, and the commitment in it is the one the run used. A recorded file that is not among those given is `FAIL` only for the latest run that read that member's answers, since an earlier run may have read a version nobody passed; for the rest it is `skipped`.
|
|
139
|
+
- **`--sealed`, the holder's check.** The folder holds the sealed files and their `.sig`. Each is found by its commitment, checked against the pack (deal, pack core sha256, member, item, side, unit) and its signature, and the comparison of the method the entry names is run again in memory; a result other than the logged one is `FAIL`. A run whose sealed file is not in the folder is `skipped`. No number, salt or gap is ever printed; the report says only `met` or `not_met`. Without `--sealed` the step is skipped and the report says so.
|
|
140
|
+
- **`--diff`.** The diff is for this text of the pack; its `ledger_head` is an entry of the ledger, and each sealed point's `verdict` is the one the ledger had at that entry (`not_tested` is also right when the point carries `changed_since_run`). A diff made earlier, before more entries were added, still passes.
|
|
141
|
+
- **Entries from before 0.7.2** (an unsigned or unbound consent, a verdict that names no consents or answers) cannot be checked in full and are `unbound`; for a verdict the engine still looks for the earlier consent entries it needed. Once any entry has the 0.7.2 fields, a later entry without them is `FAIL`: the engine always writes them, so such an entry was written by hand. (A 0.7.1 holder program that keeps adding to a ledger a 0.7.2 program has begun is therefore also `FAIL`.)
|
|
142
|
+
|
|
143
|
+
What it cannot show: an operator who writes a whole ledger of the old kind, with no signed bound consent in it, or who rewrites the entries before the first 0.7.2 entry into the old kind, gets those lines `unbound`, the summary "not fully verified" and exit 1; only `--allow-unbound`, which a party gives for a ledger he knows to be old, turns that into exit 0. The comparison of two numbers is verified only by someone with the sealed files. A ledger that is a consistent forgery from its first entry is caught only by a party who kept a diff or the head. Code: `src/smd_engine/deal/verify.py`, `verify_extra.py`, `verify_report.py`, `verify_cmd.py`; tests: `tests/test_deal_verify.py`.
|
|
97
144
|
|
|
98
145
|
## Holder and model consent
|
|
99
146
|
|
|
@@ -114,7 +161,7 @@ Anyone can run `smd task diff --ledger verdicts.yaml` and check that the verdict
|
|
|
114
161
|
|
|
115
162
|
## Trust step for pilots
|
|
116
163
|
|
|
117
|
-
In a pilot the sealed files reach an organisation that runs the holder program. This is a trust step in that organisation and its machine; `local-v1` does not remove it. No dependency is added for it; the transfer happens outside the engine (decision ДМ5 А).
|
|
164
|
+
In a pilot the sealed files reach an organisation that runs the holder program. This is a trust step in that organisation and its machine; `local-v1` does not remove it. Signatures (above) stop the operator from consenting or committing for a party, not from reading the numbers. No dependency is added for it; the transfer happens outside the engine (decision ДМ5 А).
|
|
118
165
|
|
|
119
166
|
1. The party encrypts the sealed file to the organisation's age key, on his own machine, and sends only the encrypted file.
|
|
120
167
|
2. The organisation decrypts into the run only, on a RAM disk, runs `smd deal verdict`, then unmounts the disk.
|
|
@@ -132,12 +179,13 @@ On Linux use a tmpfs such as `/dev/shm`. The hdiutil sector count is in 512-byte
|
|
|
132
179
|
|
|
133
180
|
| Who | What they are trusted with | What goes wrong if they fail |
|
|
134
181
|
|---|---|---|
|
|
135
|
-
| the holder's operator | to read both numbers once, in memory, and to log the verdict honestly | it learns both numbers; a dishonest ledger is caught
|
|
182
|
+
| the holder's operator | to read both numbers once, in memory, and to log the verdict honestly | it learns both numbers; a dishonest ledger is caught by `smd deal verify` (hand-written or replayed entries, not the numbers) or by a party that kept a diff. With `sealed_floor` it cannot consent or commit for a party in the pack he holds: that needs the party's signature (limits: "Signatures") |
|
|
183
|
+
| the party's SSH key | to be kept by the party | whoever holds it can consent and seal in his name; the pack lists the public key, so a changed key voids the answers |
|
|
136
184
|
| the party's own machine | to keep his sealed file private | a copy of the file is the number |
|
|
137
185
|
| the other party | nothing | learns only what the flag and the shared files show |
|
|
138
186
|
| a broker | the shared core and his principal's view | no sealed file, no consent right, never the operator |
|
|
139
187
|
|
|
140
|
-
What the design guarantees: a party cannot change his number after he commits it without the change showing (the commitment is in the answers and the verdict recomputes it; each counted run records the commitments it used, the diff flags a later change, and a further run needs both parties to consent to the new commitments); the commitment does not reveal a round price (salt); the other party never receives the number or the gap; a cut or edited ledger is detectable against any earlier diff.
|
|
188
|
+
What the design guarantees: a party cannot change his number after he commits it without the change showing (the commitment is in the answers and the verdict recomputes it; each counted run records the commitments it used, the diff flags a later change, and a further run needs both parties to consent to the new commitments); the commitment does not reveal a round price (salt); the other party never receives the number or the gap; a cut or edited ledger is detectable against any earlier diff; with `sealed_floor` every counted consent, answers file of a key holder and sealed file carries the party's signature, which the verdict checks before it opens anything, and the consent is tied to the pack text and keys it was written for.
|
|
141
189
|
|
|
142
190
|
What it does not guarantee. Misstatement before the commitment is unavoidable, since no mechanism makes a party name his true limit (the Myerson-Satterthwaite result); the commitment only fixes it afterwards.
|
|
143
191
|
|
|
@@ -147,17 +195,18 @@ What it does not guarantee. Misstatement before the commitment is unavoidable, s
|
|
|
147
195
|
- **More pairs, more bits.** The cap is per seller-buyer pair. A buyer who is not serious could multiply the checks by multiplying packs; that is why a run needs the seller's own consent naming the buyer, and why the sealed floor is off unless he switches it on. The engine does not tell a serious buyer from a probe; the seller decides whom to send the pack to, whether to commit a floor at all, and which buyer to consent to.
|
|
148
196
|
- **The holder's operator** sees both numbers in memory at the run, and the plaintext on the RAM disk for its duration. Swap and core dumps on that machine are outside the engine.
|
|
149
197
|
- **`committed_by` and `silent`** in the diff show who committed and who did not. A buyer with no ceiling is visible as such; the verdict `not_tested` with `no_ceiling` adds nothing to it.
|
|
198
|
+
- **The signature files and the ledger.** A signed consent entry stores its exact text and signature, so anyone with the ledger can read the buyer named, the commitments and the date. The signatures carry the member id as signer and nothing about a number.
|
|
150
199
|
- **The ledger** shows the dates of runs and consents and the commitments, which are in the answers anyway.
|
|
151
200
|
- **The cap-reached and consent-missing reasons** show that a further run was asked for.
|
|
152
|
-
- **Views** keep the other side's value answers out, but a viewer still sees every shared-core point. The agenda
|
|
201
|
+
- **Views** keep the other side's value answers out, but a viewer still sees every shared-core point. The common agenda shows a value point as `open` or `settled` only, and who discussed or did not reply, but not their answers, and nothing of an annex point but a neutral title (see "Agendas"). The id of an added point in a deal pack is `add-<member>-<8 hex of the sha256 of its text>` (with `-2`, `-3` on a repeated shared text; a point the author kept to his position hashes its text with a prefix, so its id differs and no private copy is counted in the suffix of a shared one), so the id of a shared point does not tell how many unshared points its author has; it is the same for the same answers file. A group pack keeps `add-<member>-<n>`. A 0.7.1 diff has the old ids; make the diff again, and the replies that name them with it.
|
|
153
202
|
|
|
154
203
|
Sealed values and salts do not appear in `diff.yaml`, `diff.md`, `diff.html`, an agenda, a view, the ledger or an error message; tests grep those outputs for the test numbers and salts (`tests/test_deal_sealed.py`, `tests/test_deal_verdict.py`).
|
|
155
204
|
|
|
156
205
|
## Commands
|
|
157
206
|
|
|
158
|
-
`smd task check | render | diff | agenda` take the new fields (`render --stage`); the deal commands are `smd deal views | seal | verdict | consent`. Examples: `commands.md`.
|
|
207
|
+
`smd task check | render | diff | agenda` take the new fields (`render --stage`); the deal commands are `smd deal views | seal | verdict | consent | verify`. Examples: `commands.md`.
|
|
159
208
|
|
|
160
|
-
## Not
|
|
209
|
+
## Not yet built
|
|
161
210
|
|
|
162
211
|
- A two-party or split-trust comparison (a multiparty protocol instead of `local-v1`): the `Comparator` protocol is the place for it.
|
|
163
212
|
- Real use of the sealed branch in a deal, before one role-play and one consenting deal.
|
|
@@ -54,7 +54,7 @@ Plan approved 2026-10-25 (`docs/plan.md`). Each step is a branch and a PR. The s
|
|
|
54
54
|
| Патчи | `set` on a relation by `from`, `to`, `kind`; `carries` shown in the renders | done in v0.6.3 |
|
|
55
55
|
| Путь назад | Way back on adjoin moves: `move.return`, hint `move-return`; computability check in the qualification pass (dz02#l=11) | done in v0.6.4 |
|
|
56
56
|
| АС2 | Task packs for async group work: `smd task check`, `render`, `diff`, `agenda`; schemas task_pack, task_answers, task_replies 0.1; procedures task-pack, task-diff (dz02#l=11, #l=15, #l=31) | done in v0.6.5 |
|
|
57
|
-
| ДМ | Deal mode for a sale or transfer: positions and views, fact, line, range and bound items, map acceptance, the sealed price flag with a holder, ledger and run cap; `docs/deal-mode.md` (dz02#l=43, #l=47) | done in 0.7.0
|
|
57
|
+
| ДМ | Deal mode for a sale or transfer: positions and views, fact, line, range and bound items, map acceptance, the sealed price flag with a holder, ledger and run cap; `docs/deal-mode.md` (dz02#l=43, #l=47) | done in 0.7.0; signatures, per-position agendas and call titles in 0.7.1; consent and answers bindings and `smd deal verify` in 0.7.2 |
|
|
58
58
|
|
|
59
59
|
## Structural moves (Invention as a Structural Operation)
|
|
60
60
|
|
|
@@ -40,7 +40,7 @@ They are plain YAML named by the cycle. `smd validate` does not discover them; `
|
|
|
40
40
|
|
|
41
41
|
**Pack.** `id`, `version`, `date`, `due`, `lang` (ru or en: the language of the rendered pages), `members` (id, name), `facilitator` (a member id), `task` (`what`, `why`, `feeds` with `text` and `ids`), `ontology` (`terms` with definition and source address; `elements` with id, label, optional `tier` 1 to 6 and `kind`; `relations` with from, to, kind), `sources`, `term_check` (3 to 7 items), `items`, `diff.procedure`. An item has `id`, `section`, `question`, `kind` (`choice`, `multi`, `text`, `number`, `ids`, `steps`), `options` (id, label, context; required for `choice` and `multi`), an optional `recommendation` (`value`, `reason`; only where the item is a gate), `refs` and `required` (default true).
|
|
42
42
|
|
|
43
|
-
**Answers.** `pack` (id, version and the sha256 of the pack file), `member`, `date`, `drafted_by` (`self` or `model_edited`), optional `transcripts`, `term_check` (item id to text), `answers` (item id to `value`, `reason`, `source`, `confidence` low, medium or high, `term_note`), `added` (points the member adds, with `refs`). A value is an option id for `choice`, a list of them for `multi`, a number, a text, a list of ids, or a list of steps.
|
|
43
|
+
**Answers.** `pack` (id, version and the sha256 of the pack file), `member`, `date`, `drafted_by` (`self` or `model_edited`), optional `transcripts`, `term_check` (item id to text), `answers` (item id to `value`, `reason`, `source`, `confidence` low, medium or high, `term_note`), `added` (points the member adds, with `refs`; in a deal pack `share: true`, see Deal mode below). A value is an option id for `choice`, a list of them for `multi`, a number, a text, a list of ids, or a list of steps.
|
|
44
44
|
|
|
45
45
|
**Replies.** `diff` (the sha256 of `diff.yaml`), `member`, `date`, `replies` (point id to `choice` accept, keep or discuss, `accept_member` when accepting, `note`).
|
|
46
46
|
|
|
@@ -113,7 +113,7 @@ The whole of deal mode, with the sealed branch, the trust step for pilots and th
|
|
|
113
113
|
|
|
114
114
|
For a sale or transfer, whose members are counterparties, a pack adds optional fields. Group packs are unchanged and render byte for byte as before (`tests/test_deal_golden.py`). The invented example is `cases/example/deal/`; schema stays `0.1`.
|
|
115
115
|
|
|
116
|
-
- **Positions and audience.** `positions` (seller, buyer, broker_sell, broker_buy, successor, family, adviser, verifier, stakeholder, other); `members[].position`, `members[].principal` (a broker names whom he acts for). An item or ontology term with `audience` (position ids) is in the annex of those positions; the rest is the shared core. A deal pack is stamped with the sha256 of its core (`smd task check` prints it and each annex sha256); answers carry it and `pack.annex: {position, sha256}`. `smd task render --position <id>` writes the core and that position's annex only.
|
|
116
|
+
- **Positions and audience.** `positions` (seller, buyer, broker_sell, broker_buy, successor, family, adviser, verifier, stakeholder, other); `members[].position`, `members[].principal` (a broker names whom he acts for), `members[].ssh_key` (an OpenSSH public key; required for a seller and a buyer when `deal.sealed_floor` is on, see `deal-mode.md`, "Signatures"). An item or ontology term with `audience` (position ids) is in the annex of those positions; the rest is the shared core. A deal pack is stamped with the sha256 of its core (`smd task check` prints it and each annex sha256); answers carry it and `pack.annex: {position, sha256}`. `smd task render --position <id>` writes the core and that position's annex only.
|
|
117
117
|
- **Alpha** is computed on the shared core, leaving out items with an audience and items of `nature` value or position; `alpha.basis` says how many.
|
|
118
118
|
- **Fact items.** `kind: fact` with a `claim` (`text`, `asserted_by`, `source`, `level` stated or checked); answers holds, does_not_hold, cannot_say, optionally `source_ids`. Sources may carry `sha256` and `date`. A disagreement is `conflict: fact`, route `check`.
|
|
119
119
|
- **Reading and fit.** `nature` (term, fact, value, position) and `fit_of` (the reading item). A fit point that conflicts while its reading conflicts gets `after_reading` and the route `call`.
|
|
@@ -129,9 +129,10 @@ For a sale or transfer, whose members are counterparties, a pack adds optional f
|
|
|
129
129
|
- **Model consent.** `deal.model_consent` (default false). A pack with a `deal` block gives its diff `model_pass_allowed`, and the pages say so; when it is false the model pass of `procedures/task-diff.md` stops there and no transcript is read. A diff never takes a `task_sealed` file as input.
|
|
130
130
|
|
|
131
131
|
- **Verdict and ledger.** `smd deal verdict pack.yaml <topic> --answers a.yaml b.yaml --floor sealed_<seller>_<item>.yaml [--ceiling sealed_<buyer>_<item>.yaml] --ledger verdicts.yaml` is the holder's command. It checks the cap first, then opens each sealed file, accepts it only when its deal, pack core sha, member, item, side and unit are the pack's and its recomputed commitment equals the one in the member's answers, and compares the two numbers with the comparator named by `holder.method` (`local-v1`: floor at most ceiling; `src/smd_engine/deal/overlap.py` defines the `Comparator` protocol, so a two-party protocol can replace it without changing the files, the commitments, the ledger or the verdict). The result is one entry in the ledger (`task_verdicts`; entries are hash-chained by `prev_sha256` and each has its own `sha256`): `met`, `not_met`, or `not_tested` with a `reason` (`no_floor`, `no_ceiling`, `bad_commitment`, `unit_mismatch`, `consent_missing`, `commitment_changed`, `cap_reached`). The ledger and everything printed hold no number, no salt and no gap. A buyer who gives no ceiling gets `not_tested` (`no_ceiling`) and the price goes to the meeting. `smd task diff ... --ledger verdicts.yaml` verifies the chain and writes each bound point's `verdict` (the latest run made, else `not_tested`) and `ledger_head`; a ledger cut short later no longer matches the head of an earlier diff, and `task diff` refuses to overwrite that diff.yaml. A commitment in the answers that differs from the one the latest counted run used makes the points `not_tested` with `changed_since_run`. The first run of a ledger takes `--new`; without it the file must exist. A diff made before the verdict is replaced by the one with `--ledger` (they differ in the sealed points' verdict fields only); other differences still need `--force`.
|
|
132
|
-
- **Run cap.** One run per seller-buyer pair, topic and deal. Every run needs a `consent` entry by the seller naming the buyer (the consent file has `buyer`; the first consent of a deal takes `--new`); a second run needs one from each of the two parties too (`smd deal consent pack.yaml <topic> --member <id> --evidence <file> --ledger verdicts.yaml`; the file is the party's `task_consent` record for this deal, topic, run and member naming the floor and ceiling commitments now in the answers; the entry keeps its sha256 and the commitments, and a run with other commitments is `commitment_changed`; the holder's own word is not enough,
|
|
132
|
+
- **Run cap.** One run per seller-buyer pair, topic and deal. Every run needs a `consent` entry by the seller naming the buyer (the consent file has `buyer`; the first consent of a deal takes `--new`); a second run needs one from each of the two parties too (`smd deal consent pack.yaml <topic> --member <id> --evidence <file> --ledger verdicts.yaml`; the file is the party's `task_consent` record for this deal, topic, run and member naming the floor and ceiling commitments now in the answers; the entry keeps its sha256 and the commitments, and a run with other commitments is `commitment_changed`; the holder's own word is not enough, in a sealed-floor pack the file also names the pack's core sha256 and key list, is signed, and a verdict entry records the answers files it read and the consents it counted: docs/deal-mode.md; a broker cannot consent); two runs at most, and a third is `cap_reached`. A run that returns `not_tested` gives nothing away and does not use a run. Pilots: the parties send their sealed files to the organisation age-encrypted, outside the engine; it decrypts them only for the run, on a RAM disk. This is a trust step in the holder and its machine, which `local-v1` does not remove.
|
|
133
133
|
|
|
134
|
-
- **Pairs.** `pairs: [{id, members: [a, b], label?}]` names the member pairs compared on their own (a seller and a buyer, a broker and a buyer); each member is one of the pack's, the two differ, and a pair appears once. The diff then has `by_pair`: for each pair, the class and route of each point both members were asked (an item with an `audience` only if both are in it; added points are left out), worked out from their two answers only, with a summary. The classes of the whole diff are unchanged. The agenda has `call_by_pair`: for each pair, the ids of the points on the call that a pair member put there (discuss, no reply, or a rejected red line). A point on the call that no pair put there stays in `call` only.
|
|
135
|
-
- **
|
|
134
|
+
- **Pairs.** `pairs: [{id, members: [a, b], label?}]` names the member pairs compared on their own (a seller and a buyer, a broker and a buyer); each member is one of the pack's, the two differ, and a pair appears once. The diff then has `by_pair`: for each pair, the class and route of each point both members were asked (an item with an `audience` only if both are in it; added points are left out), worked out from their two answers only, with a summary. The classes of the whole diff are unchanged. The agenda has `call_by_pair`: for each pair, the ids of the points on the call that a pair member put there (discuss, no reply, or a rejected red line). A point on the call that no pair put there stays in `call` only. `agenda.md` lists them in the section "Call points by pair" ("Точки для созвона по парам"): per pair its two members and the call points by number and question.
|
|
135
|
+
- **Added points.** In a deal pack a point a member adds gets `audience` = the member's position, so only that position and the holder (who has the whole diff) see it, and only that position owes a reply. `share: true` on the added entry lifts the restriction; the form of a deal pack (`pack.html`, `pack.<position>.html`) has an unchecked box «показать всем позициям» / "share with all positions" on each added row and writes `share: true` when it is ticked. The diff id of an added point in a deal pack is `add-<member>-<8 hex of the sha256 of its text>` (`-2`, `-3` count only repeats of a shared point; an unshared point hashes its text with a prefix; a group pack keeps `add-<member>-<n>`), so it does not show how many unshared points the author has. In a group pack `share` is ignored and `smd task check` warns.
|
|
136
|
+
- **Views.** `smd deal views pack.yaml diff.yaml -o out/views [--position id]` writes `diff.<position>.yaml`, `.md` and `.html` for each position: a `task_diff` with a `view` block (`position`, `diff`: the sha256 of the whole diff.yaml). The whole diff is for whoever runs it; a view is what a position is sent. It leaves out the points not for the position (`audience`); a fact dispute (class `conflict`) over a claim of the buyer's side, unless the viewer is on that side; and, on a value point (`nature: value`, a `value` conflict, or a range with no nature), the class, route, `sets`, `silent` and the answers of the other side, which shows only the class `open` or `settled`. A side is "sell" (seller, sell-side broker), "buy" (buyer, buy-side broker) or the position alone; a broker is on the side of the position his principal holds, so he gets his principal's view of the other side's answers, within his own audience. The summary, `by_pair`, labels and transcripts are cut the same way. A view is rendered and replied to like a diff (`smd task render`); an agenda is built from the whole diff only; `smd deal views` takes `--replies` and `--members` and then also writes `agenda.<position>.yaml` and `.md`, cut like the view; the common agenda (`smd task agenda`) shows an annex point only under its `call_title` and leaves a settled one out (`deal-mode.md`, "Agendas"). Item field `call_title` (optional string): the neutral title of an item with an `audience` on the common agenda. `smd task check --replies r.yaml --diff diff.<position>.yaml` checks `diff` in the reply against the view's `view.diff`; a reply may carry `view`, the sha256 of the view file, which the view's page writes into the reply it exports, and the check refuses another view's sha256.
|
|
136
137
|
|
|
137
138
|
Procedures `task-pack` and `task-diff` are at 0.2.0 for these fields.
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
id: task-diff
|
|
3
3
|
title: The model's part of the diff of a task pack
|
|
4
4
|
step: 3
|
|
5
|
-
version: 0.2.
|
|
5
|
+
version: 0.2.1
|
|
6
6
|
role: игротехник
|
|
7
7
|
profile: any
|
|
8
8
|
inputs:
|
|
@@ -17,7 +17,7 @@ sources: ["decision log dz02#l=11 and dz02#l=15 (case owner, gates АС3 В, А
|
|
|
17
17
|
|
|
18
18
|
# The model's part of the diff of a task pack
|
|
19
19
|
|
|
20
|
-
`smd task diff` has already compared what a script can compare: the structured items (choice, multi, number, ids, steps) and the added points. This procedure covers the rest: the points whose class is `to_read` and the subtype of every `conflict`. You read what the members wrote and classify it. You never decide for them.
|
|
20
|
+
`smd task diff` has already compared what a script can compare: the structured items (choice, multi, number, ids, steps) and the added points (in a deal pack an added point is for the author's position unless he shared it; leave its audience as the script set it). This procedure covers the rest: the points whose class is `to_read` and the subtype of every `conflict`. You read what the members wrote and classify it. You never decide for them.
|
|
21
21
|
|
|
22
22
|
The result is a draft by an AI. Any member can reclassify a point when they reply to the diff, and the raw answers stay attached to every point.
|
|
23
23
|
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
id: task-pack
|
|
3
3
|
title: Build a task pack for a group that answers apart
|
|
4
4
|
step: 3
|
|
5
|
-
version: 0.2.
|
|
5
|
+
version: 0.2.2
|
|
6
6
|
role: игротехник
|
|
7
7
|
profile: any
|
|
8
8
|
inputs:
|
|
@@ -61,7 +61,8 @@ Each item has `id`, `section`, `question`, `kind` and `required`.
|
|
|
61
61
|
|
|
62
62
|
A pack for a sale, a transfer or any task whose members are counterparties adds fields; leave them out for a group.
|
|
63
63
|
- `positions` (seller, buyer, broker_sell, broker_buy, successor, family, adviser, verifier, stakeholder, other) and, on each member, `position` (and `principal` for a broker: the member he acts for). A broker is never the one who runs the diff.
|
|
64
|
-
- `audience` (position ids) on an item or an ontology term puts it in the annex of those positions; without it the entry is in the shared core. Put in the annex only what one position needs to answer alone. The core carries the terms, facts and red lines everyone reads alike.
|
|
64
|
+
- `audience` (position ids) on an item or an ontology term puts it in the annex of those positions; without it the entry is in the shared core. Give every item with an `audience` a `call_title`, a neutral title for the common agenda (it must not hint at the content); `smd task check` warns when it is missing. Put in the annex only what one position needs to answer alone. The core carries the terms, facts and red lines everyone reads alike.
|
|
65
|
+
- A point a member adds in a deal pack is for the author's position only (audience = his position) unless he marks it `share: true`; only that position and the holder see it, and only that position replies. In the agenda it appears under a neutral title.
|
|
65
66
|
- Split reading from fit. A reading item (`nature: term` or `fact`) asks what the business is; a fit item (`nature: value` or `position`, `fit_of: <reading item>`) asks whether it suits the member. Alpha leaves out value and position items.
|
|
66
67
|
- `kind: fact` takes a `claim` (`text`, `asserted_by` a position, `source` an id from `sources`, `level` stated or checked). Give the source its `sha256` and `date`. Mark a claim `checked` only when a source or the verifier has confirmed it. Members answer holds, does_not_hold or cannot_say and may name `source_ids`.
|
|
67
68
|
- `kind: line` takes a `line` as `docs/red-lines.md` gives it. Members answer accept or reject; the wanted change goes in the reason. A walk-away price is not a red line.
|