smd-engine 0.7.4__tar.gz → 0.7.5__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.4 → smd_engine-0.7.5}/.github/workflows/ci.yml +28 -2
- {smd_engine-0.7.4 → smd_engine-0.7.5}/CHANGELOG.md +15 -7
- {smd_engine-0.7.4 → smd_engine-0.7.5}/PKG-INFO +1 -1
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/spectra_coffee/taxonomies.yaml +2 -2
- {smd_engine-0.7.4 → smd_engine-0.7.5}/docs/changelog-0.2-0.5.md +1 -1
- {smd_engine-0.7.4 → smd_engine-0.7.5}/docs/checks.md +4 -4
- {smd_engine-0.7.4 → smd_engine-0.7.5}/docs/commands.md +1 -1
- {smd_engine-0.7.4 → smd_engine-0.7.5}/docs/data-model.md +1 -1
- {smd_engine-0.7.4 → smd_engine-0.7.5}/docs/stories.md +1 -1
- {smd_engine-0.7.4 → smd_engine-0.7.5}/pyproject.toml +1 -1
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/validate/ai.py +1 -1
- {smd_engine-0.7.4 → smd_engine-0.7.5}/uv.lock +1 -1
- {smd_engine-0.7.4 → smd_engine-0.7.5}/.claude/agents/smd-game-technician.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/.claude/agents/smd-methodologist.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/.claude/agents/smd-visionary.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/.claude/commands/procedure.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/.flake8 +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/.github/workflows/release.yml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/.gitignore +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/.python-version +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/CONTRIBUTING.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/LICENSE +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/README.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/README_ru.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/example/bakeries-c1.board.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/example/bakeries-c2.board.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/example/deal/answers_boris.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/example/deal/answers_gleb.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/example/deal/answers_vera.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/example/deal/pack.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/example/golden/README.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/example/golden/bakeries-c2-expected.board.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/example/golden/s3_transcript.txt +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/example/patches/bakeries-c2-1.patch.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/example/sources.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/example/task/answers_ana.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/example/task/answers_ben.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/example/task/answers_cy.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/example/task/pack.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/example/task/replies_ana.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/example/task/replies_ben.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/example/task/transcript_ben.txt +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/example/two-boards-c1.board.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/example_ru/pekarni-c1.board.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/example_ru/pekarni-c2.board.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/example_ru/pekarni-oru-c1.board.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/example_ru/pekarnya-holding-c1.board.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/example_ru/sources.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/spectra_coffee/README.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/spectra_coffee/bank.story.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/spectra_coffee/buyer.story.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/spectra_coffee/owner.story.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/spectra_coffee/sources.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/spectra_coffee/spectra-coffee-c1.board.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/cases/spectra_coffee/successor-premortem.story.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/docs/README.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/docs/deal-mode.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/docs/first-board.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/docs/glossary.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/docs/hypotheses.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/docs/method/README.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/docs/method/encodable.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/docs/method/formal-stance.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/docs/method/odi-problematization.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/docs/method/reconciliation.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/docs/method/robustness-rules.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/docs/method/roles-and-actors.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/docs/method/smd-classic.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/docs/method/sources.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/docs/method/structural-moves.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/docs/method/triz-systems.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/docs/plan.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/docs/profiles.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/docs/red-lines.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/docs/stages.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/docs/task-packs.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/lenses/README.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/lenses/beer-viable-system.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/lenses/design-chain.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/lenses/fliamer-diamond.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/lenses/khaprov-levels.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/lenses/khaprov-ontology.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/lenses/scamper-check.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/lenses/schukin-boundaries.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/lenses/schukin-interface-tax.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/lenses/three-positions.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/lenses/triz-contradictions.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/procedures/README.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/procedures/field-result.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/procedures/functional-plan.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/procedures/ingest-transcript.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/procedures/positional-construction.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/procedures/problematization.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/procedures/qualification-pass.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/procedures/reflexive-protocol.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/procedures/small-situation.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/procedures/solo-session.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/procedures/stakeholder-ontology.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/procedures/story.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/procedures/task-diff.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/procedures/task-pack.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/procedures/theses-to-board.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/procedures/visionary-tract.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/profiles/classic-two-boards.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/profiles/management-four-boards.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/profiles/program-three-boards.yaml +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/roles/README.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/roles/actors.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/roles/game-technician.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/roles/methodologist.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/roles/researcher.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/roles/visionary.md +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/__init__.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/agree.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/apply.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/cli.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/cli_boards.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/cli_session.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/cli_story.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/compare.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/deal/__init__.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/deal/agenda_views.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/deal/cli.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/deal/consent.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/deal/ledger.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/deal/overlap.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/deal/seal_cmd.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/deal/sealed.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/deal/signing.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/deal/verdict.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/deal/verdict_cmd.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/deal/verify.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/deal/verify_cmd.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/deal/verify_diff.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/deal/verify_extra.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/deal/verify_report.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/deal/views.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/eval.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/leverage.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/migrate.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/nextstep.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/pack.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/profile.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/profile_model.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/profile_parse.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/records.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/redline.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/render/__init__.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/render/assets/frames.css +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/render/assets/frames.js +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/render/assets/graph.css +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/render/assets/graph.js +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/render/frames.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/render/frames_page.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/render/frames_text.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/render/graph.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/render/graph_ui.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/render/html.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/render/index.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/render/layout.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/render/light.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/render/markdown.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/render/mermaid.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/render/sessionflow.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/render/svg.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/render/text.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/render/vault.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/revise.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/scaffold.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/schemas/__init__.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/schemas/board_patch.schema.json +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/schemas/board_set.schema.json +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/schemas/source_manifest.schema.json +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/schemas/story.schema.json +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/schemas/task_acceptance.schema.json +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/schemas/task_answers.schema.json +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/schemas/task_pack.schema.json +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/schemas/task_replies.schema.json +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/schemas/task_sealed.schema.json +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/schemas/task_verdicts.schema.json +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/schemas/taxonomies.schema.json +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/screen.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/sources.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/status.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/story/__init__.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/story/check.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/story/gaps.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/story/model.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/story/numbers.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/story/paths.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/story/render.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/__init__.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/acceptance.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/agenda.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/asking.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/assets/task.css +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/assets/task.js +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/bounds.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/check.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/cli.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/deal_check.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/deal_items.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/deal_labels.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/deal_render.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/deal_web.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/diff.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/diff_html.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/diff_md.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/labels.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/model.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/names.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/overwrite.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/pack_html.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/pack_md.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/pairs.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/positions.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/ranges.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/refs.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/svg.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/task/web.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/validate/__init__.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/validate/context.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/validate/graph.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/validate/hints.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/validate/hypotheses.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/validate/management.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/validate/manifest.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/validate/ontology.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/validate/redlines.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/validate/signoffs.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/validate/structure.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/validate/taxonomies.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/validate/theses.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/validate/tract.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/src/smd_engine/verdict.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/conftest.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/deal_helpers.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/story_helpers.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_action_program.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_agree.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_ai_roles.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_apply.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_beer_layer.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_beer_render.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_compare.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_deal_acceptance.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_deal_added.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_deal_agenda_leaks.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_deal_bindings.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_deal_golden.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_deal_items.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_deal_positions.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_deal_ranges.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_deal_sealed.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_deal_signed.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_deal_verdict.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_deal_verify.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_deal_verify_diff.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_deal_verify_forged.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_deal_views.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_eval.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_export.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_frames.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_graph.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_hypothesis_standard.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_ingestion.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_lenses.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_management.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_migrate.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_nextstep.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_ontology_continuum.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_procedure_checks.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_procedures.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_profile.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_publish.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_record_boards.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_red_lines.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_render_and_cli.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_render_carries.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_render_fields.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_render_ru_pages.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_render_ru_values.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_revise.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_robustness.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_scaffold.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_status.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_story_case.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_story_check.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_story_numbers.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_story_paths.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_task.py +0 -0
- {smd_engine-0.7.4 → smd_engine-0.7.5}/tests/test_validate.py +0 -0
|
@@ -73,13 +73,39 @@ jobs:
|
|
|
73
73
|
echo "No tests found, skipping."
|
|
74
74
|
fi
|
|
75
75
|
|
|
76
|
+
# Trivy binary from its GitHub release, checked against the release's checksum
|
|
77
|
+
# file. setup-trivy (inside trivy-action) downloads the tarball from
|
|
78
|
+
# get.trivy.dev, which is NXDOMAIN since 2026-11-03 (aquasecurity/trivy#11537,
|
|
79
|
+
# aquasecurity/setup-trivy#42): curl exit 6. Installed outside the checkout so
|
|
80
|
+
# the scan of '.' does not see it.
|
|
81
|
+
- name: Install Trivy (GitHub release)
|
|
82
|
+
env:
|
|
83
|
+
TRIVY_VERSION: '0.70.0'
|
|
84
|
+
run: |
|
|
85
|
+
set -euo pipefail
|
|
86
|
+
base="https://github.com/aquasecurity/trivy/releases/download/v${TRIVY_VERSION}"
|
|
87
|
+
tgz="trivy_${TRIVY_VERSION}_Linux-64bit.tar.gz"
|
|
88
|
+
sums="trivy_${TRIVY_VERSION}_checksums.txt"
|
|
89
|
+
dir="$RUNNER_TEMP/trivy-bin"
|
|
90
|
+
mkdir -p "$dir"
|
|
91
|
+
cd "$RUNNER_TEMP"
|
|
92
|
+
curl -fsSL --retry 3 -o "$tgz" "$base/$tgz"
|
|
93
|
+
curl -fsSL --retry 3 -o "$sums" "$base/$sums"
|
|
94
|
+
grep " ${tgz}\$" "$sums" | sha256sum -c -
|
|
95
|
+
tar -xzf "$tgz" -C "$dir" trivy
|
|
96
|
+
rm -f "$tgz" "$sums"
|
|
97
|
+
echo "$dir" >> "$GITHUB_PATH"
|
|
98
|
+
"$dir/trivy" --version
|
|
99
|
+
|
|
76
100
|
# Security scan - runs for ALL project types
|
|
77
101
|
- name: Security (Trivy)
|
|
78
102
|
# Pinned by commit SHA (trivy-action tags were force-pushed in March 2026).
|
|
79
|
-
#
|
|
80
|
-
#
|
|
103
|
+
# skip-setup-trivy: the binary comes from the step above. cache: 'false'
|
|
104
|
+
# skips the trivy-DB cache step, where a setup-trivy change rejects the
|
|
105
|
+
# $HOME-containing default path and fails the step.
|
|
81
106
|
uses: aquasecurity/trivy-action@ed142fd0673e97e23eac54620cfb913e5ce36c25 # v0.36.0
|
|
82
107
|
with:
|
|
108
|
+
skip-setup-trivy: true
|
|
83
109
|
scan-type: 'fs'
|
|
84
110
|
scan-ref: '.'
|
|
85
111
|
exit-code: '1'
|
|
@@ -2,6 +2,14 @@
|
|
|
2
2
|
|
|
3
3
|
Dates are those of the tag. All tags v0.2.1 to v0.3.5 were made on 2026-10-29. The version in `pyproject.toml` stayed at 0.2.0 through v0.2.4 and at 0.3.0 from v0.3.0 to v0.3.5; 0.3.6 is the first release whose package version equals its tag.
|
|
4
4
|
|
|
5
|
+
## 0.7.5 - 2026-11-07
|
|
6
|
+
|
|
7
|
+
The engine and its cases are kept apart (the case owner, 7 November 2026). No code change in behaviour; schema 0.3 and every record, pack and ledger of 0.7.4 load as before.
|
|
8
|
+
|
|
9
|
+
- Docs, comments and examples no longer name a real case's ids or hypotheses; the data-model taxonomy example uses the neutral `spectra-coffee-fiction` case.
|
|
10
|
+
- The public export scan refuses case ids (pattern "private case id").
|
|
11
|
+
- Rule for maintainers: a case's need enters the engine only as a feature stated without the case, with a neutral example and tests.
|
|
12
|
+
|
|
5
13
|
## 0.7.4 - 2026-11-03
|
|
6
14
|
|
|
7
15
|
`smd deal verify --diff` no longer trusts the diff's own list of answers files when a counted run follows its head, and `cli.py` and `profile.py` are split (release go dz03#l=31). Schema 0.1 stays; no file format changes, and every 0.7.3 pack, answers file, ledger and diff still loads.
|
|
@@ -66,7 +74,7 @@ Task packs (the case owner, 2 November 2026, dz02#l=11 and dz02#l=15, gate АС2
|
|
|
66
74
|
|
|
67
75
|
## 0.6.4 - 2026-11-02
|
|
68
76
|
|
|
69
|
-
Two method changes asked for by the case owner on 2 November 2026 (dz02#l=11) and one fix (dz02#l=15). Schema 0.3 stays; the new field is optional and old records stay valid. The
|
|
77
|
+
Two method changes asked for by the case owner on 2 November 2026 (dz02#l=11) and one fix (dz02#l=15). Schema 0.3 stays; the new field is optional and old records stay valid. The first case's five boards validate as before (0 errors, 150 warnings); hints go from 143 to 156, the 13 new ones being `move-return` on adjoin elements.
|
|
70
78
|
|
|
71
79
|
- Move field `return` (board-set schema, `$defs.move`): the way back, what the move changes in the terms it started from (a decision, a prediction, a test) and what is lost on the way back. New hint `move-return` (→ visionary-tract.md §7, `program-three-boards` only, like `move-via`): an element whose `move` is an `adjoin`, with status `candidate` or `accepted` or none, and no `return`. A `rejected` adjoin, other ops and the moves on theses are not read. The Markdown digest shows `return` after `via` ("way back" / "путь назад"). The board patch schema does not restate move fields and is unchanged.
|
|
72
80
|
- Docs: `docs/data-model.md` (Moves), `docs/method/structural-moves.md` (new subsection "Way back": the requirement, three examples, pending in the paper's `PENDING_UPDATES.md` as an owner decision), `docs/stages.md`, `docs/checks.md`. `visionary-tract` 0.2.4: each adjoin candidate states its way back; the example carries one.
|
|
@@ -86,7 +94,7 @@ Gate ИСТ1 (the case owner, 1 November 2026, dz01#l=31): the story view is str
|
|
|
86
94
|
|
|
87
95
|
## 0.6.3 - 2026-11-01
|
|
88
96
|
|
|
89
|
-
Gates Ж1 Б and Ж2 Б (the case owner, 1 November 2026): the engine's formal stance and its six robustness rules. Schema 0.3 stays; every new field is optional and old records stay valid. The
|
|
97
|
+
Gates Ж1 Б and Ж2 Б (the case owner, 1 November 2026): the engine's formal stance and its six robustness rules. Schema 0.3 stays; every new field is optional and old records stay valid. The first case's five boards validate as before (0 errors, 150 warnings, 143 hints) and so do the eight example records.
|
|
90
98
|
|
|
91
99
|
Gate ИСТ1 Б (1 November 2026) adds the story view, a checked view over the boards that is never a record. A board patch can also set fields on a relation, and the renders show what a flow carries. The three changes are separate and backward compatible; the first bullets below are the robustness rules, then the story view, then the patches and renders.
|
|
92
100
|
|
|
@@ -120,10 +128,10 @@ Follow-ups of the 0.6.0 reviews. The schema gains one optional field, `carries`
|
|
|
120
128
|
|
|
121
129
|
- Red lines with a structured value (gate КЛ1 В, the case owner 31.10: «should the red_line threshold be a period (min;max)?», answered В; dates instead of a term in years). An element with `red_line: true`, or an `algedonic_channel`, takes `line`: `metric`, `unit`, a corridor (`min` and/or `max`, one-sided allowed) or a yes/no (`expect`), `since` (optional; the record's `date` when absent), `until` (required) and `recovery_days`. Errors: both a corridor and `expect`, or neither; `min` not below `max`; `until` not after the start; `recovery_days` and the channel's `recovery_time` both set and different; `line` on an element that is no red line. The free-text `threshold` stays as a fallback; `red-line-without-value` accepts either. Observations sit on the same element, `observed: [{value, date, source}]`: a value of the wrong type for the line is an error, a source not of kind `field_artefact` a warning (with a manifest). New `src/smd_engine/redline.py` holds the deterministic breach rule (observations from the line's start to `until`, sorted by date; a run of outside values spans to the next inside value, or, still open, to the later of the last observation and the record's `date`, never past `until`; a breach when longer than `recovery_days`, else `recovery_time`, any run when neither is set). Warnings: observations before the line takes force, and two on one date. The schema requires `metric` with `expect`. Numbers on the pages are plain digits (in Russian, a thin space between thousands and a decimal comma). New hints, all profiles: `red-line-breach` and `red-line-expired` (observations or the record dated after `until`; → field-result.md §5) and `red-line-outlives-pace` (the line's span in years longer than the `pace` of an element it is linked to, the analogue of `ontology-outlives-pace`; the case owner 26.10, H24; → functional-plan.md §4). New `validate/redlines.py`; the linking used by `ai-decision-unanswered` moved there and now reads `in` and `performed_by` both ways. The management hint `line-without-recovery` reads `line` too: a channel has a value when it has `threshold` or `line`, and a recovery time when it has `recovery_time` or `line.recovery_days`. `smd status` lists the red lines with a breach. The page, the digest, the index, the graph details and the frames details show the line in words («доля ФОТ от 18 до 25 %, с 01.01.2027 по 31.12.2031, восстановление 90 дней») and the last observation («27 % на 01.03.2027, вне коридора»). `bakeries-c2` and `pekarni-c2` carry the owner's red line `rl-unsold` (unsold dough at most 5 % of the night's volume, 01.03.2026 to 28.02.2027, recovery 14 days), with no observations; `--strict` stays 0/0. New `docs/red-lines.md` (the fields, the rule, the words), linked from `docs/data-model.md` and `docs/README.md`; `field-result` 0.3.2 gains section 5 (red lines from observations); `functional-plan` section 4, `docs/checks.md`, `docs/commands.md`.
|
|
122
130
|
|
|
123
|
-
- AI on the boards (gate ИИ1 Б, the case owner 31.10: "should flows include 'intelligence'? when AI is used", answered Б). AI is not a new `carries` value: an AI agent is an actor in `fillers`, and what it produces moves as information or product. Roles (kinds a profile flags `role`; a gap only with `of: position`) and functions take an optional `ai`: `assists` («ИИ помогает») or `performs` («выполняет ИИ»); anywhere else it is an error. A function's effective `ai` is its own, else that of the role in its `performed_by`. Elements take an optional `red_line: true` (agreed by the case owner, 31.10; refused on kinds flagged `light_off`: notes, and facts and signals on the default profile); its value, a threshold or yes/no, goes in `threshold`, now allowed on any red-line element, and the new hint `red-line-without-value` (all profiles, → functional-plan.md §4) names one without. An `algedonic_channel` with a `threshold` is a red line without it. `escalates` gains a second use: from a function to the role that answers for it at a red line. New hint `ai-decision-unanswered` (all three profiles, → functional-plan.md §3; new `validate/ai.py`): a function AI performs, linked to a red line (itself one, `in` one, performed by a red-line role, or joined to one by a relation of any kind), for which no role without `ai: performs` answers by `performed_by`, `subordinates` (role to function), `escalates` or a `flow` with `carries: information` (function to role); the case behind it is the
|
|
131
|
+
- AI on the boards (gate ИИ1 Б, the case owner 31.10: "should flows include 'intelligence'? when AI is used", answered Б). AI is not a new `carries` value: an AI agent is an actor in `fillers`, and what it produces moves as information or product. Roles (kinds a profile flags `role`; a gap only with `of: position`) and functions take an optional `ai`: `assists` («ИИ помогает») or `performs` («выполняет ИИ»); anywhere else it is an error. A function's effective `ai` is its own, else that of the role in its `performed_by`. Elements take an optional `red_line: true` (agreed by the case owner, 31.10; refused on kinds flagged `light_off`: notes, and facts and signals on the default profile); its value, a threshold or yes/no, goes in `threshold`, now allowed on any red-line element, and the new hint `red-line-without-value` (all profiles, → functional-plan.md §4) names one without. An `algedonic_channel` with a `threshold` is a red line without it. `escalates` gains a second use: from a function to the role that answers for it at a red line. New hint `ai-decision-unanswered` (all three profiles, → functional-plan.md §3; new `validate/ai.py`): a function AI performs, linked to a red line (itself one, `in` one, performed by a red-line role, or joined to one by a relation of any kind), for which no role without `ai: performs` answers by `performed_by`, `subordinates` (role to function), `escalates` or a `flow` with `carries: information` (function to role); the case behind it is a hypothesis of the first case. `smd status` (counts) and `smd index` (top of the page) print «функции: выполняет ИИ n, ИИ помогает k, из m» when any element has `ai`, nothing otherwise. The page, the digest, the index, the graph details and the frames details show `ai` and `red_line` in words (`LABELS`). `fn-dough` in `bakeries-c2` and `pekarni-c2` has `ai: assists` (the night's volume planned with an AI demand forecast; the organiser decides); `--strict` stays 0/0. The first case has no `ai` and gets no new finding (0 errors, 150 warnings). `functional-plan` 0.2.7 (section 3) and `positional-construction` 0.2.8 (section 2) say where `ai` goes; `docs/method/roles-and-actors.md` gains "AI as an actor"; `docs/data-model.md`, `docs/checks.md`, `docs/commands.md`.
|
|
124
132
|
|
|
125
133
|
- Example cases draw a clean functional plan. The hint `function-flows` fired on every function of `f-new` in `bakeries-c1`, `bakeries-c2`, `two-boards-c1`, `pekarni-c1`, `pekarni-c2` and the golden record `bakeries-c2-expected` (found by running `smd validate --hints` on every record under `cases/`; the two management-profile records do not enable it). `bakeries-c2` and `pekarni-c2` now draw the `flow` relations the story states (mills supply flour into the dough, the owner pays per tonne and receives the dough, dough goes to logistics, the owner pays inside the dough price for now and receives it before four in the morning); `two-boards-c1` draws flour, the dough and the delivery to the owner and links the open `gap-payer` to both functions. `bakeries-c1` and `pekarni-c1` are cycle 1, where K2 says nobody yet performs or pays: they draw the flour and the chain dough, quality standard, logistics, and leave the payer and the receiver as gaps (`gap-payer`, and a new `gap-receiver`, `of: position`) linked to each function by `refers`. `function-flows` and `unlinked-functions` are silent on all five; the hints left in cycle 1 (`performed_by`, `idle-positions`) are K2 itself. The golden record is unchanged, and its README says why. `tests/test_procedure_checks.py` checks the five records.
|
|
126
|
-
- Relations of kind `flow` take an optional `carries` (`money`, `material`, `product`, `information`; schema additive, old records stay valid; words in both languages in `LABELS`, shown in the Markdown digest). `function-flows` reads a payer as an incoming flow of `money` from a position or place, an input as an incoming flow of anything but money, and a receiver as an outgoing flow of anything but money to a position or place, so a supplier (mills with flour) is no longer a payer. A receiver is also a non-money flow to a later function of the same frame that has one (followed along the chain, cycles walked once), so a middle function needs no direct line; on the
|
|
134
|
+
- Relations of kind `flow` take an optional `carries` (`money`, `material`, `product`, `information`; schema additive, old records stay valid; words in both languages in `LABELS`, shown in the Markdown digest). `function-flows` reads a payer as an incoming flow of `money` from a position or place, an input as an incoming flow of anything but money, and a receiver as an outgoing flow of anything but money to a position or place, so a supplier (mills with flour) is no longer a payer. A receiver is also a non-money flow to a later function of the same frame that has one (followed along the chain, cycles walked once), so a middle function needs no direct line; on the first case's cycle 5 the function-flow hints go from 10 to 7. A flow with no `carries` is read as before for payer and input; the hint's wording names `carries: money`. All flows of the example cases set `carries`. `functional-plan` 0.2.6 asks for it (section 4). `docs/checks.md`, `docs/data-model.md`.
|
|
127
135
|
- `bakeries-c2` and `pekarni-c2` draw the owner's and the organiser's `flow` to and from `coop-plant` (what each gives or takes), so the `cooperation-flows` hint is silent on the examples (the plant pays the organiser: `carries: money`, "paid by use against the pledged volume"). The direct `fn-dough` to owner lines are dropped from `bakeries-c2`, `pekarni-c2` and `two-boards-c1`: the dough reaches the owner through logistics.
|
|
128
136
|
- An `untested` hypothesis with `observed` gets no verdict proposal, in `smd validate`, `smd status` or the SessionFlow export; the hint `verdict` says "observed data recorded but status is untested: set testing". Only a `testing` one is read by its rule.
|
|
129
137
|
- `smd next` reads the hint pointers. Every hint finding contributes its procedure and section (`HINT_PROCEDURES`) as a candidate with the hint's message as the reason; a hint on a document (`board-dense`) is printed as a note. The conditions that no hint reports stay rules (`RULES`: gate 0, unplaced theses when no hint covers them, no K, a first cycle with no theses, a hypothesis in testing, closing the cycle when no hint of steps 1 to 6 is open). All candidates are sorted by one documented order (`ORDER`: gate 0; then the step-2 procedures `ingest-transcript`, `theses-to-board`, `field-result`, which lay information on the board; then the steps of `solo-session` section 3; then `reflexive-protocol` and `solo-session`). The closing rule waits for a hint at any procedure before `reflexive-protocol`, and the unplaced-theses rule is silenced only by a hint at `theses-to-board` section 2. A first cycle with no theses therefore gets `ingest-transcript` before `small-situation`, each procedure once with the sections of all its candidates; the output prints them (`functional-plan §3, §4`). The rules that re-derived hints (empty halves, incomplete positional set, new frame, gaps without a scheme block, closing by hint) are gone; the hints say the same, with the right section. `docs/commands.md` gives the table and the order.
|
|
@@ -131,16 +139,16 @@ Follow-ups of the 0.6.0 reviews. The schema gains one optional field, `carries`
|
|
|
131
139
|
- `docs/commands.md`: `sources --refresh` writes `lines` only into an entry that already has a `lines:` line; its report prints the file's line count for every refreshed entry. The doc said the report carried a count only where `lines` is present; the behaviour (a count on every line of the report, the manifest touched only where `lines` exists) is kept and now described.
|
|
132
140
|
- `docs/release.md`: the tag example is `v<version>`, not `v0.3.6`; the public commit is authored as the organisation's GitHub noreply identity with `git -c user.name=... -c user.email=... commit` and checked with `git log -1 --format='%an <%ae>'` before the push.
|
|
133
141
|
- `small-situation` 0.2.4 and `field-result` 0.3.1 gain the "Record the run" line, in the words of the other procedures.
|
|
134
|
-
- `voice` of a K, a hypothesis, a relation and a transition is free text, and `AI`, `ai` and `ИИ` already read as an AI voice everywhere (`is_ai`). `smd migrate` and the validator leave them as written: a warning would add one per item (the
|
|
142
|
+
- `voice` of a K, a hypothesis, a relation and a transition is free text, and `AI`, `ai` and `ИИ` already read as an AI voice everywhere (`is_ai`). `smd migrate` and the validator leave them as written: a warning would add one per item (the first case's cycle 5 has 158 `voice: AI` values, 7 of them on hypotheses) for a spelling that changes no result. `docs/data-model.md` and the schema description say so.
|
|
135
143
|
|
|
136
144
|
## 0.6.0 - 2026-10-31
|
|
137
145
|
|
|
138
146
|
Method review of 31.10 (gates М1 В, Ф В, У В): reproducible runs, deterministic checks for rules the procedures asked a model to check by hand, a typed standard for hypotheses with a pre-registered decision rule, and a shorter path for new users. Schema 0.3 stays; every new field is optional and old records stay valid.
|
|
139
147
|
|
|
140
|
-
- Hypothesis standard (method review 31.10, gates М1 В and Ф В, formal audit proposal 6). Three optional hypothesis fields, additive (schema stays 0.3, old records stay valid): `type` (`core`, `product`, `claim`, `estimate`, `probe`, `design`: how the hypothesis is read), `rule` (`{metric, op, threshold, n_min, basis}`: the pre-registered decision rule, a structured `revise_if`; `op` states the refutation condition) and `observed` (`{k, n, artefact}`). New `src/smd_engine/verdict.py`: the 95% Wilson score interval of k/n (Wilson 1927; reproduces 0.2553-0.3662 for 81/263, Newcombe 1998) and a proposed verdict for an untested or testing hypothesis when the threshold is a share strictly between 0 and 1 (`op` is `<`, `<=`, `>` or `>=`): too few (n below `n_min`), refuted, confirmed, or inconclusive (the interval straddles the threshold). The proposal is a hint (`verdict`) and a section of `smd status`; the sign-off stays human. New error: k greater than n; new warnings: a recorded result opposite to the proposal, and (with a manifest) an `observed.artefact` that is not of kind `field_artefact`; `validate_record` takes the manifest's kinds as `source_kinds`. New hints `hypothesis-type`, `hypothesis-rule`, `rule-basis`, `rule-n-min`, `type-status` (`docs/checks.md`), enabled on all three profiles; `revise-if` accepts a `rule` and leaves out claims and estimates (they get `hypothesis-rule`) and cores, designs and probes. The
|
|
148
|
+
- Hypothesis standard (method review 31.10, gates М1 В and Ф В, formal audit proposal 6). Three optional hypothesis fields, additive (schema stays 0.3, old records stay valid): `type` (`core`, `product`, `claim`, `estimate`, `probe`, `design`: how the hypothesis is read), `rule` (`{metric, op, threshold, n_min, basis}`: the pre-registered decision rule, a structured `revise_if`; `op` states the refutation condition) and `observed` (`{k, n, artefact}`). New `src/smd_engine/verdict.py`: the 95% Wilson score interval of k/n (Wilson 1927; reproduces 0.2553-0.3662 for 81/263, Newcombe 1998) and a proposed verdict for an untested or testing hypothesis when the threshold is a share strictly between 0 and 1 (`op` is `<`, `<=`, `>` or `>=`): too few (n below `n_min`), refuted, confirmed, or inconclusive (the interval straddles the threshold). The proposal is a hint (`verdict`) and a section of `smd status`; the sign-off stays human. New error: k greater than n; new warnings: a recorded result opposite to the proposal, and (with a manifest) an `observed.artefact` that is not of kind `field_artefact`; `validate_record` takes the manifest's kinds as `source_kinds`. New hints `hypothesis-type`, `hypothesis-rule`, `rule-basis`, `rule-n-min`, `type-status` (`docs/checks.md`), enabled on all three profiles; `revise-if` accepts a `rule` and leaves out claims and estimates (they get `hypothesis-rule`) and cores, designs and probes. The first case has no typed hypothesis and gets no new finding. Labels of the fields and of the six types in both languages; the page, the digest, the index and the graph show them under the hypothesis. `field-result` 0.3.0 gains section 0 (the six types and how each is read; the decision rule and the interval) and reads the proposal in section 3; `small-situation` 0.2.3 (section 4) gives each new H a `type`, and a claim or estimate a `rule` with its `basis`.
|
|
141
149
|
- `smd agree <record> <record> [...] [--fields ...] [--json]` (the audit of 31.10, proposal 4, gate Ф В): how stable are the labels a procedure writes. Takes N runs of one procedure on one input; warns, and goes on, when `run.procedure`, `run.pack_sha256` or `run.inputs` differ or are missing. Theses are matched across runs by the address they cite (the matching of `smd eval`, generalised to N runs); elements of the first record are matched in the other runs as `smd compare` matches them. For `belt`, `kind`, `status`, `voice`, `of` and the move `op` of theses, and `kind`, `of` and `op` of elements, it prints Krippendorff's alpha (nominal, any number of runs, missing values allowed; written in the new `agree.py` from the coincidence matrix, no new dependency; `n/a` with the reason when only one value occurs), the share of cite addresses found by all, some or one run with the one-run-only addresses, and a reading by Krippendorff's conventional cut-offs (0.800, 0.667), stated as a convention; a field with fewer than five pairable units shows its alpha with "few units" and is left out of the reading line. The alpha code reproduces the 0.743 of Krippendorff's 2011 worked example. `eval` is unchanged. `docs/commands.md` and the golden README describe it.
|
|
142
150
|
- `smd new <folder> [--profile] [--lang] [--case] [--title]` (UX audit of 31.10, gate У В): scaffolds a case folder that validates at once, `smd validate --strict` giving 0 errors and 0 warnings on every profile: `<case>-c1.board.yaml` (required fields, `profile`, an entry where the profile has the kind, one position to rename, empty lists), a `sources.yaml` skeleton with one entry, and a README naming the first procedure (`small-situation` on the default profile, `positional-construction` on the others). It refuses, writing nothing, if a file exists. `docs/first-board.md` starts from it.
|
|
143
|
-
- `smd status <record> [--lang] [-o file.md]`: the core view of a board set on one page of Markdown (46 lines for the
|
|
151
|
+
- `smd status <record> [--lang] [-o file.md]`: the core view of a board set on one page of Markdown (46 lines for the first case's cycle 5): state line, K not closed, hypotheses in testing and untested ones in leverage order, AI-voiced items waiting for a sign-off, transitions, counts per board and kind; lists are cut with "and N more". New `LABELS[...]["core"]` words in both languages.
|
|
144
152
|
- `smd next <record>`: the procedure to run next with one line why and at most two alternatives, by the rule table `RULES` in `src/smd_engine/nextstep.py` (written out in `docs/commands.md`); procedures of another profile are skipped; "no rule fires" is an answer.
|
|
145
153
|
- Hypothesis leverage (formal audit, section 4 row 5): for each untested hypothesis the size of what a refutation would reach (targets, K, ontology records testing it, theses on its targets, elements one relation away); a proposal, the group chooses. Listed by `smd status`, and a column "reach (proposal)" in the hypotheses table of `smd index`.
|
|
146
154
|
- Run stamp v2 (the audit of 31.10, formal section 3): the record's `run` takes four optional fields, `pack_sha256` (sha256 of the `smd pack` output the run used), `inputs` (source id to the sha256 of the input file the run read), `temperature` (a number) and `sample` (the run index, when a procedure is run several times on one input). Additive: the schema stays 0.3 and old records stay valid. The schema checks the types (a 64-character lowercase hex for a hash, an integer from 1 for `sample`); `docs/data-model.md`, `run`, describes the fields.
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.5
|
|
2
2
|
Name: smd-engine
|
|
3
|
-
Version: 0.7.
|
|
3
|
+
Version: 0.7.5
|
|
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
|
|
@@ -1,5 +1,5 @@
|
|
|
1
|
-
# Значения тегов вымышленного дела: шесть уровней OST, те же id, что в
|
|
2
|
-
#
|
|
1
|
+
# Значения тегов вымышленного дела: шесть уровней OST, те же id, что в первом
|
|
2
|
+
# реальном деле (замысел -> организация). Уровни OST и слои L0-L5 публичной
|
|
3
3
|
# спецификации не совпадают: соответствие в README.md этой папки.
|
|
4
4
|
record: taxonomies
|
|
5
5
|
schema_version: "0.1"
|
|
@@ -116,7 +116,7 @@ Follow-ups; no change to the schema or the records.
|
|
|
116
116
|
- `tests/test_export_public.py` covers the scan of `scripts/export_public.py` (one planted leak of each pattern; a clean tree) and its argument checks.
|
|
117
117
|
- `docs/plan.md` and `docs/stages.md` give the release tags of the steps of the 2026-10-29 update (v0.2.1 to v0.5.0) and say that a release tag is not a schema version.
|
|
118
118
|
- `smd graph`: the height of each plane comes from `render/graph.py` (`LAYER`) in the model as `planes`; `graph.js` no longer repeats the spacing (260, 520). The planes stand where they stood; the graph pages differ only by that key and those lines.
|
|
119
|
-
- Screen: a relation label stands above the middle of its link unless it covers a label placed before it, an element box (of a frame, its heading; of a figure, its icon and caption), a board or half heading or a K badge. Then it takes the nearest spot that covers nothing, at most 4 lines (60 px) up or down and half its width sideways, in one line or wrapped to 220 px; with none free, the spot that covers least, its own spot winning ties, so no label moves to a worse place. Spots are computed on the whole record, so frames and cut screens keep them. On
|
|
119
|
+
- Screen: a relation label stands above the middle of its link unless it covers a label placed before it, an element box (of a frame, its heading; of a figure, its icon and caption), a board or half heading or a K badge. Then it takes the nearest spot that covers nothing, at most 4 lines (60 px) up or down and half its width sideways, in one line or wrapped to 220 px; with none free, the spot that covers least, its own spot winning ties, so no label moves to a worse place. Spots are computed on the whole record, so frames and cut screens keep them. On the first case's cycle-5 board the overlapping pairs go from 122 to 53 between labels and from 163 to 135 between labels and boxes. Labels that cover nothing keep their spot; in the examples three labels move one line (`two-boards-c1`: «looks back at», «dough»; `pekarni-oru-c1`: «усилить»), whose spot covered an element.
|
|
120
120
|
- `smd publish --strict` fails on warnings of the published record only; warnings of the earlier cycles it `revises` are printed with "(earlier cycle: not failing)". Errors anywhere in the chain still fail.
|
|
121
121
|
- `smd publish` writes the index with links relative to `--out` (`render_index(..., base=)`): the record file and `--archive` files by relative path, a file that shares only the root with `--out` without a link, and `YAML:N` as a line number, so no absolute path of the building machine is in the bundle. `smd index` keeps its absolute `file://` and `vscode://` links.
|
|
122
122
|
|
|
@@ -21,16 +21,16 @@ The checks are in `src/smd_engine/validate/`, one module per subject, run in the
|
|
|
21
21
|
- **Warnings (method review 31.10.2026):** an ontology position of `valid_for` with no line in `subjects` (positional-construction.md §5; the reverse of the warning of step 3).
|
|
22
22
|
- **Hints (functional plan, functional-plan.md §4; `validate/graph.py`):** over the functions `in` a new frame: a function with no payer (no `flow` into it from a position or place for others), no input (no `flow` into it) or no receiver (no `flow` from it to a position or place for others), each slot met as well by a gap linked to the function by a relation, with `of: position` for the payer, `material` or `means` for the input, `position`, `product` or `function` for the receiver (`function-flows`); functions of a frame with two or more linked by no `flow` (only `flow`) to another of them (`unlinked-functions`); positions, other than the cycle's reflexive one (`reflected_from`, `stance: reflexive`), that perform, pay for and receive nothing in the plan (`idle-positions`; places for others are left out). Enabled on `program-three-boards` and `classic-two-boards`; the management profile draws its functions on process boards, not in frames. With `carries` on a `flow` (`money`, `material`, `product`, `information`), the payer is an incoming flow of `money` from a position or place, an input an incoming flow of anything else, and a receiver an outgoing flow of anything but money to a position or place, or to another function of the same frame that has a receiver (followed along the chain, a cycle of functions walked once), so a middle function needs no line of its own to the receiver and only the end of the chain must reach a position or place; a supplier's `material` is an input and not a payer. A flow with no `carries` is read as before (any flow from a position or place pays, any flow in is an input, any flow out to a position or place receives), so records that never set it report what they did.
|
|
23
23
|
- **Errors (AI on the boards, gate ИИ1 Б):** `ai` on an element that is neither a function nor a role (a kind the profile flags `role`), or on a gap whose `of` is not `position`; `red_line` on a kind the profile flags `light_off` ("'red_line' is not for notes"; facts and signals on the default profile). `threshold` is allowed on any element with `red_line: true`, as the red line's free-text value. The schema refuses an `ai` other than `assists` or `performs` and a `red_line` that is not a boolean.
|
|
24
|
-
- **Hint `ai-decision-unanswered`** (functional-plan.md §3; `validate/ai.py`; all three profiles): a function whose effective `ai` (its own, else that of the role in `performed_by`) is `performs`, that is linked to a red line, and for which no role without `ai: performs` answers. A red line is an element with `red_line: true`, or an `algedonic_channel` with a `threshold` or a `line` (the management profile's carrier of a stakeholder's red line). Linked (`validate/redlines.py`, `linked`): the function is a red line itself, it is `in` one or one is `in` it, the role in its `performed_by` is one, or a relation of any kind, either way, joins it to one. A role answers when it is of a kind the profile flags `role`, not a gap (a missing role answers for nothing), has no `ai: performs`, and is the function's `performed_by`, or `subordinates` the function (role to function), or receives its `escalates` or a `flow` with `carries: information` (function to role). `subordinates` and `escalates` exist on the management profile only; elsewhere `performed_by` and the information flow back remain. A function with its own `ai: performs` whose `performed_by` is a role without `ai: performs` is answered by that role and gets no hint: the role answers for what AI does in it. The case behind it is the
|
|
24
|
+
- **Hint `ai-decision-unanswered`** (functional-plan.md §3; `validate/ai.py`; all three profiles): a function whose effective `ai` (its own, else that of the role in `performed_by`) is `performs`, that is linked to a red line, and for which no role without `ai: performs` answers. A red line is an element with `red_line: true`, or an `algedonic_channel` with a `threshold` or a `line` (the management profile's carrier of a stakeholder's red line). Linked (`validate/redlines.py`, `linked`): the function is a red line itself, it is `in` one or one is `in` it, the role in its `performed_by` is one, or a relation of any kind, either way, joins it to one. A role answers when it is of a kind the profile flags `role`, not a gap (a missing role answers for nothing), has no `ai: performs`, and is the function's `performed_by`, or `subordinates` the function (role to function), or receives its `escalates` or a `flow` with `carries: information` (function to role). `subordinates` and `escalates` exist on the management profile only; elsewhere `performed_by` and the information flow back remain. A function with its own `ai: performs` whose `performed_by` is a role without `ai: performs` is answered by that role and gets no hint: the role answers for what AI does in it. The case behind it is a hypothesis of the first case: some decisions cannot be passed on, to a model or to a new manager, without people of a certain role, and the owner records each as a yes/no red line. With no `ai` on the record the hint is silent.
|
|
25
25
|
- **Hint `red-line-without-value`** (functional-plan.md §4; all three profiles): an element with `red_line: true` and neither a `line` nor a `threshold`. A red line is an absolute value, a threshold or yes/no that data check (the case owner 26.10); the hint asks to name it. It is a hint, not an error: the group may mark a line before it has the value.
|
|
26
26
|
- **Errors (red line values, gate КЛ1 В; `validate/redlines.py`, `docs/red-lines.md`):** `line` on an element that is neither `red_line: true` nor an `algedonic_channel`; a `line` with both a corridor (`min`, `max`) and `expect`, or with neither; `min` not below `max`; `until` not after `since` (or after the record's `date` when there is no `since`); `line.recovery_days` and the channel's `recovery_time` both set and different; `observed` on an element with no `line`; an observed value of the wrong type (a boolean for a yes/no line, a number for a corridor); with a manifest, an unknown `observed` source. The schema refuses a `line` without `until`, and an observation without `value`, `date` or `source`. The schema also refuses `expect` without `metric`. **Warnings:** with a manifest, an observation whose source is not of kind `field_artefact`; observations dated before the line takes force (`since`, else the record's `date`), which are not read; two observations with the same date ("one observation per date").
|
|
27
|
-
- **Hints (red line values):** `red-line-breach` (field-result.md §5): the breaches of a line by its observations, each with its dates, by the rule of `src/smd_engine/redline.py` (observations from the line's start to `until`, sorted by date; a run of outside values spans from its first date to the next inside value, or, still open, to the later of the last observation and the record's `date`, never past `until`; it is a breach when longer than `line.recovery_days`, else `recovery_time`; any run when neither is set). `red-line-expired` (field-result.md §5): observations dated after `until`, or a record dated after it ("the line ended on <until>: renew or drop"). `red-line-outlives-pace` (functional-plan.md §4): a line in force (`until` minus `since`, or minus the record's `date`) more years than the `pace` of an element it is linked to (as above, itself included), the analogue of `ontology-outlives-pace`: a line is in force for a term matched to the pace of its tier (the case owner 26.10
|
|
27
|
+
- **Hints (red line values):** `red-line-breach` (field-result.md §5): the breaches of a line by its observations, each with its dates, by the rule of `src/smd_engine/redline.py` (observations from the line's start to `until`, sorted by date; a run of outside values spans from its first date to the next inside value, or, still open, to the later of the last observation and the record's `date`, never past `until`; it is a breach when longer than `line.recovery_days`, else `recovery_time`; any run when neither is set). `red-line-expired` (field-result.md §5): observations dated after `until`, or a record dated after it ("the line ended on <until>: renew or drop"). `red-line-outlives-pace` (functional-plan.md §4): a line in force (`until` minus `since`, or minus the record's `date`) more years than the `pace` of an element it is linked to (as above, itself included), the analogue of `ontology-outlives-pace`: a line is in force for a term matched to the pace of its tier (the case owner 26.10).
|
|
28
28
|
- **Hints (typical errors of a group screen, qualification-pass.md §3.2; `program-three-boards`):** positions, other than the reflexive one, with no `shift` or `flow` to another position, place or cooperation (`positions-unlinked`, E2); object-board content, gaps and notes aside, linked by no relation, transition, `in`, `performed_by` or move, however indirectly, to an element of another board (`object-isolated`, E3; an ontology's `cooperation` counts as linked to its `valid_for` positions; `seen_from` does not count, since E3 asks for a link besides it); facts with no relation, transition, `in`, `feeds` or `about` (`isolated-facts`, E6, E11); the starting position of a `shift`, other than the reflexive one, with nothing seen from it on a board with halves while a new frame is drawn (`jump-to-frame`, E12; the engine's reading: the order of the transitions is not read); a transition with no end that is a position, a place for others or seen from a position (`transition-unanchored`, E14). E1, E7 and the rest of E14 are the hints on halves, entry and `seen_from` above; the other rows need reading.
|
|
29
29
|
- **Hints (self-checks of the procedures):** an AI-drafted `cooperation` that no K targets (`ai-cooperation`, positional-construction.md §5); an ontology whose `valid_for` positions have no `flow` to or from its `cooperation` (`cooperation-flows`); a `detail` table with a column «что теряется» or "what is lost" whose cell is empty or says none (`нет`, `none`, `-`, `—`, `n/a`) in a row (`translation-loss`, stakeholder-ontology.md §5); on `program-three-boards`, a `garland` with fewer than two `belongs` relations into it, or whose events all cite one source ("one witness") (`garland`, visionary-tract.md §3); a bridge, a `situation` on the big half with a `respecify` move, whose move is not from a `model` and a `garland` (`bridge-from`, §5); a candidate move of the tract (`glue` on a model, `respecify` or `rescale` on a situation, `adjoin` on a goal) with no `via`; a move the group made in its talk needs none (`move-via`, §1); an `adjoin` element, a candidate, accepted or with no status, with no `return` (the way back: what it changes in the old terms and what is lost; `move-return`, visionary-tract.md §7; dz02#l=11; thesis moves are not read). Not checked: that a stakeholder ontology names exactly one position (no field marks a record as one; several positions with no cooperation get the `ontology` hint), "one witness" by actor (signals carry no actor field), and three cycles in a row without a new scheme (the validator compares a record with its previous one only).
|
|
30
30
|
- **Errors (hypothesis standard, gates М1 В and Ф В; `validate/hypotheses.py`):** `observed` with k greater than n; the schema refuses an unknown `type`, a `rule` without `metric`, `op` or `threshold` or with another `op`, an `n_min` below 1, and an `observed` without `k`, `n` or `artefact`. `observed.artefact` is checked against the manifest like `artefacts`. The schema refuses `==` as an `op`: equality is no refutation condition.
|
|
31
31
|
- **Warnings (hypothesis standard):** a recorded `confirmed` while the whole Wilson interval of `observed` lies on the refuting side of the rule's threshold, or `refuted` while it lies on the holding side; with a manifest, an `observed.artefact` whose source is not of kind `field_artefact`.
|
|
32
|
-
- **Hints (hypothesis standard, `procedures/field-result.md` §0):** an untyped hypothesis whose `raised_in` cycle has typed hypotheses (`hypothesis-type`; records with none typed, like the
|
|
33
|
-
- **Hint `board-dense`:** a board, record boards included, with more elements than the profile's `board_dense` (default 15; `docs/profiles.md`), worded as advice to fold what is settled or split a part off, never an error; it points here, since no procedure folds a board. The default is low on purpose and tunable: working memory holds about four chunks when rehearsal and chunking are blocked (Cowan, N. (2001). The magical number 4 in short-term memory: a reconsideration of mental storage capacity. *Behavioral and Brain Sciences*, 24(1), 87-114). That figure is about what one keeps in mind at once, not about a screen, and no study gives a number of elements per diagram, so 15 is a heuristic to be tuned on the case (the
|
|
32
|
+
- **Hints (hypothesis standard, `procedures/field-result.md` §0):** an untyped hypothesis whose `raised_in` cycle has typed hypotheses (`hypothesis-type`; records with none typed, like the first case's, get none); a `claim` or `estimate` with neither `rule` nor `revise_if` (`hypothesis-rule`; such a hypothesis gets no `revise-if` hint, nor does a `core`, `design` or `probe`, and a `rule` stands in for `revise_if`); a `rule` with no `basis` (`rule-basis`); an `estimate` whose `rule` has no `n_min` (`rule-n-min`); a `probe` confirmed or refuted, or a `core` or `design` not `untested` (`type-status`); for each `testing` hypothesis with `observed`, the verdict its rule proposes (an `untested` one with `observed` gets the hint "observed data recorded but status is untested: set testing" instead), by the 95% Wilson score interval of k/n when the threshold is a share strictly between 0 and 1 (`verdict`, field-result.md §3: too few, refuted, confirmed, or inconclusive and stays testing; the group signs `accept_result`).
|
|
33
|
+
- **Hint `board-dense`:** a board, record boards included, with more elements than the profile's `board_dense` (default 15; `docs/profiles.md`), worded as advice to fold what is settled or split a part off, never an error; it points here, since no procedure folds a board. The default is low on purpose and tunable: working memory holds about four chunks when rehearsal and chunking are blocked (Cowan, N. (2001). The magical number 4 in short-term memory: a reconsideration of mental storage capacity. *Behavioral and Brain Sciences*, 24(1), 87-114). That figure is about what one keeps in mind at once, not about a screen, and no study gives a number of elements per diagram, so 15 is a heuristic to be tuned on the case (the first case's second cycle carried 33 elements on three boards, about 11 per board).
|
|
34
34
|
- **Errors (record boards):** reported with the schema errors: a record board of an unknown template, with an id of a profile board or template or `records`/`sources`, or twice; an element of a known kind its record board's template does not take. Later: a record board id that is also an element id, a `seen_from` that is neither a position nor a reflexive position, an unknown `unfolds` or one of a kind outside the template's `unfolds`. **Warnings:** a record board with no `seen_from` when its template sets `needs_position`; a kind whose `home` is a template, on another board ("usually lies on a board of template 'process'").
|
|
35
35
|
- **Errors (v0.3):** `scheme` on an element that is not a gap or on a thesis that is not a problem; a `detail.keys` column that is not among `columns`; with a taxonomy file, an unknown taxonomy or value in `tags` or in a bound column.
|
|
36
36
|
- **Warnings (v0.3):** `tags` or `detail.keys` used and no taxonomy file given.
|
|
@@ -81,7 +81,7 @@ uv run smd apply cases/example/bakeries-c2.board.yaml cases/example/patches/bake
|
|
|
81
81
|
- the transitions;
|
|
82
82
|
- the counts of elements per board (halves of the situation board apart) and per kind; when any element has `ai` (gate ИИ1 Б), one more line, «функции: выполняет ИИ n, ИИ помогает k, из m» ("functions: AI performs n, AI assists k, of m"): the functions by their effective `ai` (`docs/data-model.md`, Elements) and all functions. `smd index` prints the same line at the top of the page; neither prints it for a record with no `ai`.
|
|
83
83
|
|
|
84
|
-
Lists are cut to a fixed length and end in "and N more" (8 K, 5 hypotheses in testing, 8 verdicts, 5 untested, 5 transitions, 6 ids per waiting item, 8 kinds), one line per item. The page for the
|
|
84
|
+
Lists are cut to a fixed length and end in "and N more" (8 K, 5 hypotheses in testing, 8 verdicts, 5 untested, 5 transitions, 6 ids per waiting item, 8 kinds), one line per item. The page for the first case's cycle 5 (132 elements, 19 K, 40 hypotheses) is 46 lines. The labels come from the same `LABELS` tables as the other pages; `--lang ru` is the default.
|
|
85
85
|
|
|
86
86
|
**Hypothesis leverage (a proposal).** For each untested hypothesis the engine collects what a refutation would reach: its `targets`; its `qualifications` (K); the ontology records whose `test` is this hypothesis; the theses whose `feeds` or `about` hold one of its targets; and the elements one relation away from a target (either end of a relation, a target not counted twice). The score is the size of that set, the order is by score and then by id with numbers read as numbers (H2 before H10). It is the same for the same record. It is not a probability and carries no weight: a hypothesis can be worth testing for a reason the board does not show. The group chooses which to test; the order only saves it from counting by hand. `smd status` lists it, and `smd index` shows the score in the hypotheses table (column "reach (proposal)", the parts of the count as the tooltip).
|
|
87
87
|
|
|
@@ -91,4 +91,4 @@ A story as readable Markdown: the title, the audience and form, the sentences by
|
|
|
91
91
|
|
|
92
92
|
A story that passes has no sentence without a board id, no figure the board does not hold, no sentence stronger than its weakest source and no dropped opposition. It can still be a bad story: the walk may be the wrong one, the allow-list too wide, the wording too sure. Those are for the игротехник and the client.
|
|
93
93
|
|
|
94
|
-
The first use of `paths` on a real board is the list of gaps (`--gaps`): where the record has no typed link between two items a story would need. On the
|
|
94
|
+
The first use of `paths` on a real board is the list of gaps (`--gaps`): where the record has no typed link between two items a story would need. On the first case's cycle 5 only one of five hand-drawn story skeletons followed typed links (research note of 01.11.2026).
|
|
@@ -8,7 +8,7 @@ A function's effective `ai` is its own `ai`, else the `ai` of the role in its
|
|
|
8
8
|
`performed_by`. The hint `ai-decision-unanswered` names a function AI
|
|
9
9
|
performs that is linked to a red line while no role without `ai: performs`
|
|
10
10
|
answers for it: a decision that cannot be passed on without people of a
|
|
11
|
-
certain role
|
|
11
|
+
certain role. Which elements are red lines, and what
|
|
12
12
|
an element is linked to, is in validate/redlines.py."""
|
|
13
13
|
|
|
14
14
|
from __future__ import annotations
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|