smd-engine 0.6.1__tar.gz → 0.6.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.6.2/CHANGELOG.md +67 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/PKG-INFO +1 -1
- smd_engine-0.6.1/CHANGELOG.md → smd_engine-0.6.2/docs/changelog-0.2-0.5.md +3 -58
- {smd_engine-0.6.1 → smd_engine-0.6.2}/docs/data-model.md +1 -1
- {smd_engine-0.6.1 → smd_engine-0.6.2}/docs/stages.md +1 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/pyproject.toml +1 -1
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/schemas/board_patch.schema.json +1 -1
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/schemas/board_set.schema.json +2 -2
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_apply.py +19 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_hypothesis_standard.py +15 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/uv.lock +1 -1
- {smd_engine-0.6.1 → smd_engine-0.6.2}/.claude/agents/smd-game-technician.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/.claude/agents/smd-methodologist.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/.claude/agents/smd-visionary.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/.claude/commands/procedure.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/.flake8 +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/.github/workflows/ci.yml +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/.github/workflows/release.yml +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/.gitignore +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/.python-version +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/CONTRIBUTING.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/LICENSE +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/README.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/README_ru.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/cases/example/bakeries-c1.board.yaml +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/cases/example/bakeries-c2.board.yaml +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/cases/example/golden/README.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/cases/example/golden/bakeries-c2-expected.board.yaml +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/cases/example/golden/s3_transcript.txt +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/cases/example/patches/bakeries-c2-1.patch.yaml +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/cases/example/sources.yaml +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/cases/example/two-boards-c1.board.yaml +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/cases/example_ru/pekarni-c1.board.yaml +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/cases/example_ru/pekarni-c2.board.yaml +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/cases/example_ru/pekarni-oru-c1.board.yaml +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/cases/example_ru/pekarnya-holding-c1.board.yaml +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/cases/example_ru/sources.yaml +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/docs/README.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/docs/checks.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/docs/commands.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/docs/first-board.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/docs/glossary.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/docs/method/README.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/docs/method/encodable.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/docs/method/odi-problematization.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/docs/method/reconciliation.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/docs/method/roles-and-actors.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/docs/method/smd-classic.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/docs/method/sources.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/docs/method/structural-moves.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/docs/method/triz-systems.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/docs/plan.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/docs/profiles.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/docs/red-lines.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/lenses/README.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/lenses/beer-viable-system.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/lenses/design-chain.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/lenses/fliamer-diamond.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/lenses/khaprov-levels.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/lenses/khaprov-ontology.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/lenses/scamper-check.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/lenses/schukin-boundaries.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/lenses/schukin-interface-tax.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/lenses/three-positions.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/lenses/triz-contradictions.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/procedures/README.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/procedures/field-result.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/procedures/functional-plan.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/procedures/ingest-transcript.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/procedures/positional-construction.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/procedures/problematization.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/procedures/qualification-pass.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/procedures/reflexive-protocol.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/procedures/small-situation.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/procedures/solo-session.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/procedures/stakeholder-ontology.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/procedures/theses-to-board.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/procedures/visionary-tract.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/profiles/classic-two-boards.yaml +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/profiles/management-four-boards.yaml +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/profiles/program-three-boards.yaml +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/roles/README.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/roles/actors.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/roles/game-technician.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/roles/methodologist.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/roles/researcher.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/roles/visionary.md +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/__init__.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/agree.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/apply.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/cli.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/compare.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/eval.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/leverage.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/migrate.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/nextstep.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/pack.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/profile.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/records.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/redline.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/render/__init__.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/render/assets/frames.css +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/render/assets/frames.js +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/render/assets/graph.css +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/render/assets/graph.js +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/render/frames.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/render/frames_page.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/render/frames_text.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/render/graph.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/render/graph_ui.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/render/html.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/render/index.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/render/layout.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/render/light.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/render/markdown.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/render/mermaid.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/render/sessionflow.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/render/svg.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/render/text.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/render/vault.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/revise.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/scaffold.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/schemas/__init__.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/schemas/source_manifest.schema.json +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/schemas/taxonomies.schema.json +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/screen.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/sources.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/status.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/validate/__init__.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/validate/ai.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/validate/context.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/validate/graph.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/validate/hints.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/validate/hypotheses.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/validate/management.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/validate/manifest.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/validate/ontology.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/validate/redlines.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/validate/signoffs.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/validate/structure.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/validate/taxonomies.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/validate/theses.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/validate/tract.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/src/smd_engine/verdict.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/conftest.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_action_program.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_agree.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_ai_roles.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_beer_layer.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_beer_render.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_compare.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_eval.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_export.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_frames.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_graph.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_ingestion.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_lenses.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_management.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_migrate.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_nextstep.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_ontology_continuum.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_procedure_checks.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_procedures.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_profile.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_publish.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_record_boards.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_red_lines.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_render_and_cli.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_render_fields.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_render_ru_pages.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_render_ru_values.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_revise.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_scaffold.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_status.py +0 -0
- {smd_engine-0.6.1 → smd_engine-0.6.2}/tests/test_validate.py +0 -0
|
@@ -0,0 +1,67 @@
|
|
|
1
|
+
# Changelog
|
|
2
|
+
|
|
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
|
+
|
|
5
|
+
## Unreleased
|
|
6
|
+
|
|
7
|
+
## 0.6.2 - 2026-10-31
|
|
8
|
+
|
|
9
|
+
Gate ОТП1 В (the case owner, 31.10): a board carries the parts of a split hypothesis, as the group's hypothesis matrix does. Schema 0.3 stays; old records stay valid.
|
|
10
|
+
|
|
11
|
+
- A hypothesis split into parts keeps its number and adds one lowercase Latin letter: `H2a`, `H2b` (gate ОТП1 В, the case owner 31.10: the group's hypothesis matrix splits composite hypotheses into parts, each with one type). The board schema accepts `^H[0-9]+[a-z]?$` for a hypothesis `id` and an ontology record's `test`, and the patch schema accepts it for an item id, so a patch can remove `H2` and add `H2a` and `H2b`. Old records stay valid. `docs/data-model.md` gives the rule.
|
|
12
|
+
- The changelog of 0.2.0-0.5.9 moved to `docs/changelog-0.2-0.5.md` (this file had passed 300 lines).
|
|
13
|
+
|
|
14
|
+
## 0.6.1 - 2026-10-31
|
|
15
|
+
|
|
16
|
+
Follow-ups of 0.6.0 and two gates of 31.10: AI on roles and functions (ИИ1 Б) and structured red lines with observed values (КЛ1 В, with dates as decided 31.10). Schema 0.3 stays; every new field is optional and old records stay valid.
|
|
17
|
+
|
|
18
|
+
Follow-ups of the 0.6.0 reviews. The schema gains one optional field, `carries` on a `flow` (additive: old records stay valid), and `function-flows` reads it; a record that sets none reports as before. Gate ИИ1 Б adds two optional element fields, `ai` and `red_line`, and gate КЛ1 В two more, `line` and `observed` (additive, schema stays 0.3).
|
|
19
|
+
|
|
20
|
+
- 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`.
|
|
21
|
+
|
|
22
|
+
- 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 MIPT case's H64. `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 MIPT 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`.
|
|
23
|
+
|
|
24
|
+
- 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.
|
|
25
|
+
- 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 MIPT 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`.
|
|
26
|
+
- `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.
|
|
27
|
+
- 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.
|
|
28
|
+
- `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.
|
|
29
|
+
- The SessionFlow export shows the hypothesis fields of 0.6.0 under each hypothesis of section 1, in Russian: `type`, `rule` (metric, operator, threshold, `n_min`, basis), `observed` (k/n and the artefact) and, for an untested or a testing hypothesis, the verdict the rule proposes (`verdict.py`; the group signs).
|
|
30
|
+
- `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.
|
|
31
|
+
- `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.
|
|
32
|
+
- `small-situation` 0.2.4 and `field-result` 0.3.1 gain the "Record the run" line, in the words of the other procedures.
|
|
33
|
+
- `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 MIPT 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.
|
|
34
|
+
|
|
35
|
+
## 0.6.0 - 2026-10-31
|
|
36
|
+
|
|
37
|
+
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.
|
|
38
|
+
|
|
39
|
+
- 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 MIPT 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`.
|
|
40
|
+
- `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.
|
|
41
|
+
- `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.
|
|
42
|
+
- `smd status <record> [--lang] [-o file.md]`: the core view of a board set on one page of Markdown (46 lines for the MIPT 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.
|
|
43
|
+
- `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.
|
|
44
|
+
- 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`.
|
|
45
|
+
- 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.
|
|
46
|
+
- `smd pack` prints `pack sha256: <hex>` to stderr, the hash of the bytes it wrote (the file with `-o`, the text on stdout otherwise), so that a run can record it as `run.pack_sha256`.
|
|
47
|
+
- `smd revise` no longer copies the previous cycle's `run` into the next cycle: the new record is not the product of that run, and a carried `pack_sha256` would name a pack it was not made from. The next procedure writes its own stamp.
|
|
48
|
+
- `smd eval` prints the whole `run` stamp of both records, `inputs` as `{id: sha256, ...}`; until now a mapping showed as a Python dict.
|
|
49
|
+
- The "Record the run" line of `functional-plan` 0.2.5, `ingest-transcript` 0.3.1, `positional-construction` 0.2.7, `problematization` 0.2.3, `qualification-pass` 0.4.1, `reflexive-protocol` 0.3.2, `solo-session` 0.2.4, `stakeholder-ontology` 0.1.1, `theses-to-board` 0.3.6 and `visionary-tract` 0.2.3 names the new fields, in the same words: write what you know, omit the rest, invent nothing. `small-situation` and `field-result` have no such line and are unchanged.
|
|
50
|
+
- `docs/first-board.md`: a walkthrough from an empty folder to a first validated and drawn board (an invented family bakery handing over to a manager) and on to the first procedure. It lists the required top-level fields (`title` and `status` were not named in the README), which profile to choose when, which procedure comes first and next, and what to bring. Its commands were run as shown.
|
|
51
|
+
- `docs/glossary.md`: the terms a first-time user meets, one line each; linked from the README, `README_ru.md`, `docs/README.md` and the walkthrough.
|
|
52
|
+
- `README.md` and `README_ru.md`: the stale "Version 0.3.6" line and the `uvx` pin in the CI example now say 0.5.9 (schema 0.3); the two files link the walkthrough and the glossary near the top; the data-model table names the required top-level fields of a board set.
|
|
53
|
+
- Procedure `stakeholder-ontology` 0.1.0 (step 3, role игротехник, any profile): elicits the ontology of one stakeholder position, by default the owner, the tier-1 stakeholder (its stakeholder ontology is the Owner Ontology), in the position's own words, in a solo session with the holder or from an interview transcript; in proposal mode only from registered sources in which the holder speaks. Six parts with question forms: entities, definitions, absences, topology, time, causality, plus Khaprov's ontology test for `competes` and a question for the ontology-dependent records. Product: an ontology record with `valid_for` that one position, object and subject quoted with addresses, `tags` tier 1 for the owner (`{tier: [intent]}` in a case whose taxonomy names tier 1 so), and a `test` H (by default: does the shareable part work as a reading key); the shareable part (verbatim glossary of the position's terms as used in records, list of ontology-dependent records) as a separate file registered in the manifest and cited by the record; the private part (deliberate absences, causal beliefs, sources of the edge, values, judgement of people) kept off the board, the case repository and the registered log, the record's `note` saying only that it exists and who keeps it. The translation into the six-tier ontology is a separate step: an AI-voiced `concept` element whose `detail` table names, per term, the tier and what the translation loses. Typical errors include an ontology without a position, the analyst's words in the holder's mouth, the private part on the board, the owner set apart from the stakeholders, and a seventh tier. No schema or code change.
|
|
54
|
+
- `positional-construction` 0.2.6 (section 5) and `solo-session` 0.2.3 (section 3) point to it; `stakeholder-ontology` uses the full form "six-tier ontology of a business" at first use.
|
|
55
|
+
- `procedures/README.md`, `lenses/README.md` (selection table: no lens offered) and `docs/method/roles-and-actors.md` (where the role rule is applied) list the new procedure.
|
|
56
|
+
|
|
57
|
+
- Method review 31.10.2026 (gates Ф В and У В): rules the procedures asked the model to check by hand, which are exact graph or set conditions on the record, are now checks of the validator (`docs/checks.md`).
|
|
58
|
+
- New errors: a cycle of `belongs`, of `subordinates`, or of move sources (`move.from` of elements and theses). A cycle of `flow` is legitimate and is not checked.
|
|
59
|
+
- New warning: an ontology position of `valid_for` with no line in `subjects` (the reverse of the existing warning).
|
|
60
|
+
- New hints of the functional plan (functional-plan.md §4): `function-flows` (a function in a new frame with no payer, input or receiver `flow`, unless a gap with the matching `of` is linked to it), `unlinked-functions`, `idle-positions`.
|
|
61
|
+
- New hints of the typical errors of a group screen on `program-three-boards` (qualification-pass.md §3.2): `positions-unlinked` (E2), `object-isolated` (E3), `isolated-facts` (E6, E11), `jump-to-frame` (E12), `transition-unanchored` (E14). The hint `belts` also names theses that are all мД ("mechanical reproduction").
|
|
62
|
+
- New hints of the procedures' self-checks: `ai-cooperation` and `cooperation-flows` (positional-construction.md §5), `translation-loss` (stakeholder-ontology.md §5), `garland`, `bridge-from` and `move-via` (visionary-tract.md §1, §3, §5; `program-three-boards` only).
|
|
63
|
+
- New hint `board-dense`: a board with more elements than the profile's new optional key `board_dense` (default 15) gets advice to fold or split it.
|
|
64
|
+
- `smd validate --hints` prints after each hint the procedure and section that act on it, "→ procedures/functional-plan.md §4" (`Finding.procedure`, filled from `HINT_PROCEDURES` in `validate/context.py`; the field is not compared, so findings stay equal).
|
|
65
|
+
- The three profiles enable the new hints that their kinds allow. `functional-plan` 0.2.5, `qualification-pass` 0.4.1 and `visionary-tract` 0.2.3, with `positional-construction` and `stakeholder-ontology` in their unreleased versions, say which of their checks the validator now reports.
|
|
66
|
+
|
|
67
|
+
Older releases (0.2.0 to 0.5.9): [docs/changelog-0.2-0.5.md](docs/changelog-0.2-0.5.md).
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.5
|
|
2
2
|
Name: smd-engine
|
|
3
|
-
Version: 0.6.
|
|
3
|
+
Version: 0.6.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
|
|
@@ -1,61 +1,6 @@
|
|
|
1
|
-
# Changelog
|
|
2
|
-
|
|
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
|
-
|
|
5
|
-
## Unreleased
|
|
6
|
-
|
|
7
|
-
## 0.6.1 - 2026-10-31
|
|
8
|
-
|
|
9
|
-
Follow-ups of 0.6.0 and two gates of 31.10: AI on roles and functions (ИИ1 Б) and structured red lines with observed values (КЛ1 В, with dates as decided 31.10). Schema 0.3 stays; every new field is optional and old records stay valid.
|
|
10
|
-
|
|
11
|
-
Follow-ups of the 0.6.0 reviews. The schema gains one optional field, `carries` on a `flow` (additive: old records stay valid), and `function-flows` reads it; a record that sets none reports as before. Gate ИИ1 Б adds two optional element fields, `ai` and `red_line`, and gate КЛ1 В two more, `line` and `observed` (additive, schema stays 0.3).
|
|
12
|
-
|
|
13
|
-
- 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`.
|
|
14
|
-
|
|
15
|
-
- 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 MIPT case's H64. `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 MIPT 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`.
|
|
16
|
-
|
|
17
|
-
- 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.
|
|
18
|
-
- 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 MIPT 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`.
|
|
19
|
-
- `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.
|
|
20
|
-
- 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.
|
|
21
|
-
- `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.
|
|
22
|
-
- The SessionFlow export shows the hypothesis fields of 0.6.0 under each hypothesis of section 1, in Russian: `type`, `rule` (metric, operator, threshold, `n_min`, basis), `observed` (k/n and the artefact) and, for an untested or a testing hypothesis, the verdict the rule proposes (`verdict.py`; the group signs).
|
|
23
|
-
- `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.
|
|
24
|
-
- `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.
|
|
25
|
-
- `small-situation` 0.2.4 and `field-result` 0.3.1 gain the "Record the run" line, in the words of the other procedures.
|
|
26
|
-
- `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 MIPT 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.
|
|
27
|
-
|
|
28
|
-
## 0.6.0 - 2026-10-31
|
|
29
|
-
|
|
30
|
-
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.
|
|
31
|
-
|
|
32
|
-
- 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 MIPT 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`.
|
|
33
|
-
- `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.
|
|
34
|
-
- `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.
|
|
35
|
-
- `smd status <record> [--lang] [-o file.md]`: the core view of a board set on one page of Markdown (46 lines for the MIPT 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.
|
|
36
|
-
- `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.
|
|
37
|
-
- 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`.
|
|
38
|
-
- 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.
|
|
39
|
-
- `smd pack` prints `pack sha256: <hex>` to stderr, the hash of the bytes it wrote (the file with `-o`, the text on stdout otherwise), so that a run can record it as `run.pack_sha256`.
|
|
40
|
-
- `smd revise` no longer copies the previous cycle's `run` into the next cycle: the new record is not the product of that run, and a carried `pack_sha256` would name a pack it was not made from. The next procedure writes its own stamp.
|
|
41
|
-
- `smd eval` prints the whole `run` stamp of both records, `inputs` as `{id: sha256, ...}`; until now a mapping showed as a Python dict.
|
|
42
|
-
- The "Record the run" line of `functional-plan` 0.2.5, `ingest-transcript` 0.3.1, `positional-construction` 0.2.7, `problematization` 0.2.3, `qualification-pass` 0.4.1, `reflexive-protocol` 0.3.2, `solo-session` 0.2.4, `stakeholder-ontology` 0.1.1, `theses-to-board` 0.3.6 and `visionary-tract` 0.2.3 names the new fields, in the same words: write what you know, omit the rest, invent nothing. `small-situation` and `field-result` have no such line and are unchanged.
|
|
43
|
-
- `docs/first-board.md`: a walkthrough from an empty folder to a first validated and drawn board (an invented family bakery handing over to a manager) and on to the first procedure. It lists the required top-level fields (`title` and `status` were not named in the README), which profile to choose when, which procedure comes first and next, and what to bring. Its commands were run as shown.
|
|
44
|
-
- `docs/glossary.md`: the terms a first-time user meets, one line each; linked from the README, `README_ru.md`, `docs/README.md` and the walkthrough.
|
|
45
|
-
- `README.md` and `README_ru.md`: the stale "Version 0.3.6" line and the `uvx` pin in the CI example now say 0.5.9 (schema 0.3); the two files link the walkthrough and the glossary near the top; the data-model table names the required top-level fields of a board set.
|
|
46
|
-
- Procedure `stakeholder-ontology` 0.1.0 (step 3, role игротехник, any profile): elicits the ontology of one stakeholder position, by default the owner, the tier-1 stakeholder (its stakeholder ontology is the Owner Ontology), in the position's own words, in a solo session with the holder or from an interview transcript; in proposal mode only from registered sources in which the holder speaks. Six parts with question forms: entities, definitions, absences, topology, time, causality, plus Khaprov's ontology test for `competes` and a question for the ontology-dependent records. Product: an ontology record with `valid_for` that one position, object and subject quoted with addresses, `tags` tier 1 for the owner (`{tier: [intent]}` in a case whose taxonomy names tier 1 so), and a `test` H (by default: does the shareable part work as a reading key); the shareable part (verbatim glossary of the position's terms as used in records, list of ontology-dependent records) as a separate file registered in the manifest and cited by the record; the private part (deliberate absences, causal beliefs, sources of the edge, values, judgement of people) kept off the board, the case repository and the registered log, the record's `note` saying only that it exists and who keeps it. The translation into the six-tier ontology is a separate step: an AI-voiced `concept` element whose `detail` table names, per term, the tier and what the translation loses. Typical errors include an ontology without a position, the analyst's words in the holder's mouth, the private part on the board, the owner set apart from the stakeholders, and a seventh tier. No schema or code change.
|
|
47
|
-
- `positional-construction` 0.2.6 (section 5) and `solo-session` 0.2.3 (section 3) point to it; `stakeholder-ontology` uses the full form "six-tier ontology of a business" at first use.
|
|
48
|
-
- `procedures/README.md`, `lenses/README.md` (selection table: no lens offered) and `docs/method/roles-and-actors.md` (where the role rule is applied) list the new procedure.
|
|
49
|
-
|
|
50
|
-
- Method review 31.10.2026 (gates Ф В and У В): rules the procedures asked the model to check by hand, which are exact graph or set conditions on the record, are now checks of the validator (`docs/checks.md`).
|
|
51
|
-
- New errors: a cycle of `belongs`, of `subordinates`, or of move sources (`move.from` of elements and theses). A cycle of `flow` is legitimate and is not checked.
|
|
52
|
-
- New warning: an ontology position of `valid_for` with no line in `subjects` (the reverse of the existing warning).
|
|
53
|
-
- New hints of the functional plan (functional-plan.md §4): `function-flows` (a function in a new frame with no payer, input or receiver `flow`, unless a gap with the matching `of` is linked to it), `unlinked-functions`, `idle-positions`.
|
|
54
|
-
- New hints of the typical errors of a group screen on `program-three-boards` (qualification-pass.md §3.2): `positions-unlinked` (E2), `object-isolated` (E3), `isolated-facts` (E6, E11), `jump-to-frame` (E12), `transition-unanchored` (E14). The hint `belts` also names theses that are all мД ("mechanical reproduction").
|
|
55
|
-
- New hints of the procedures' self-checks: `ai-cooperation` and `cooperation-flows` (positional-construction.md §5), `translation-loss` (stakeholder-ontology.md §5), `garland`, `bridge-from` and `move-via` (visionary-tract.md §1, §3, §5; `program-three-boards` only).
|
|
56
|
-
- New hint `board-dense`: a board with more elements than the profile's new optional key `board_dense` (default 15) gets advice to fold or split it.
|
|
57
|
-
- `smd validate --hints` prints after each hint the procedure and section that act on it, "→ procedures/functional-plan.md §4" (`Finding.procedure`, filled from `HINT_PROCEDURES` in `validate/context.py`; the field is not compared, so findings stay equal).
|
|
58
|
-
- The three profiles enable the new hints that their kinds allow. `functional-plan` 0.2.5, `qualification-pass` 0.4.1 and `visionary-tract` 0.2.3, with `positional-construction` and `stakeholder-ontology` in their unreleased versions, say which of their checks the validator now reports.
|
|
1
|
+
# Changelog, releases 0.2.0 to 0.5.9
|
|
2
|
+
|
|
3
|
+
Moved from `CHANGELOG.md` on 2026-10-31; newer releases are there. 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.
|
|
59
4
|
|
|
60
5
|
## 0.5.9 - 2026-10-29
|
|
61
6
|
|
|
@@ -162,7 +162,7 @@ The inter-module form: what we assume, how we test it, what we got, what it chan
|
|
|
162
162
|
|
|
163
163
|
| Field | Meaning |
|
|
164
164
|
|---|---|
|
|
165
|
-
| `id` | `H1..Hn` |
|
|
165
|
+
| `id` | `H1..Hn`; a part of a split hypothesis adds one lowercase Latin letter: `H2a`, `H2b` |
|
|
166
166
|
| `assumes`, `action`, `observe`, `revise_if` | что предполагаем, каким действием проверяем, что будем наблюдать, какой результат заставит пересмотреть |
|
|
167
167
|
| `status` | `untested`, `testing`, `confirmed`, `refuted` |
|
|
168
168
|
| `result`, `changes` | what the test gave; what it changes on the boards |
|
|
@@ -48,6 +48,7 @@ Plan approved 2026-10-25 (`docs/plan.md`). Each step is a branch and a PR. The s
|
|
|
48
48
|
| 0.6.0 follow-ups | Example plans drawn; `carries` on `flow` and chain receivers; `smd next` from hint pointers; SessionFlow shows hypothesis fields | done in v0.6.1 |
|
|
49
49
|
| ИИ1 | `ai: assists / performs` on roles and functions; `red_line`; hint `ai-decision-unanswered`; AI share line in `smd status` and the index | done in v0.6.1 |
|
|
50
50
|
| КЛ1 | Structured red line `line` (corridor or yes/no, `since`/`until`, recovery) and `observed`; breach rule; hints for breach, expiry, pace; `docs/red-lines.md` | done in v0.6.1 |
|
|
51
|
+
| ОТП1 | Lettered part ids for split hypotheses (`H2a`, `H2b`) in the board and patch schemas | done in v0.6.2 |
|
|
51
52
|
|
|
52
53
|
## Structural moves (Invention as a Structural Operation)
|
|
53
54
|
|
|
@@ -73,7 +73,7 @@
|
|
|
73
73
|
},
|
|
74
74
|
"$defs": {
|
|
75
75
|
"id": {"type": "string", "pattern": "^[a-z0-9][a-z0-9._-]*$"},
|
|
76
|
-
"item_id": {"type": "string", "pattern": "^([a-z0-9][a-z0-9._-]*|[
|
|
76
|
+
"item_id": {"type": "string", "pattern": "^([a-z0-9][a-z0-9._-]*|[KTO][0-9]+|H[0-9]+[a-z]?)$", "description": "element id, or K, T, H, O id; a part of a split hypothesis is H2a, H2b"},
|
|
77
77
|
"n": {"type": "integer", "minimum": 1, "description": "transition number"},
|
|
78
78
|
"items": {"type": "array", "items": {"type": "object"}},
|
|
79
79
|
"cite": {"type": "string", "pattern": "^[a-z0-9][a-z0-9._-]*(#[a-z]+=[^\\s]+)?$"},
|
|
@@ -288,7 +288,7 @@
|
|
|
288
288
|
"additionalProperties": false,
|
|
289
289
|
"description": "inter-module hypothesis: what we assume, how we test it, what we got, what it changes",
|
|
290
290
|
"properties": {
|
|
291
|
-
"id": {"type": "string", "pattern": "^H[0-9]
|
|
291
|
+
"id": {"type": "string", "pattern": "^H[0-9]+[a-z]?$", "description": "H1..Hn; a part of a split hypothesis adds one lowercase Latin letter: H2a, H2b"},
|
|
292
292
|
"voice": {"type": "string", "description": "who formulated it: group, participant, AI (free text; AI, ai and ИИ all read as an AI voice)"},
|
|
293
293
|
"lens": {"$ref": "#/$defs/id", "description": "id of the lens behind the hypothesis"},
|
|
294
294
|
"tags": {"$ref": "#/$defs/taxonomy_tags"},
|
|
@@ -399,7 +399,7 @@
|
|
|
399
399
|
"description": "the object taken apart, aspect name to text, e.g. activity, carrier, ownership, management, separation"
|
|
400
400
|
},
|
|
401
401
|
"tags": {"$ref": "#/$defs/taxonomy_tags"},
|
|
402
|
-
"test": {"type": "string", "pattern": "^H[0-9]
|
|
402
|
+
"test": {"type": "string", "pattern": "^H[0-9]+[a-z]?$", "description": "hypothesis that tests realizability in activity"},
|
|
403
403
|
"lens": {"$ref": "#/$defs/id", "description": "id of the lens behind the ontology record"},
|
|
404
404
|
"voice": {"type": "string"},
|
|
405
405
|
"note": {"type": "string"},
|
|
@@ -253,3 +253,22 @@ def test_patch_with_both_is_deterministic(board2: dict[str, Any]) -> None:
|
|
|
253
253
|
{"n": 1, "from": "f-new", "to": "s-big", "label": "to the future"}
|
|
254
254
|
]
|
|
255
255
|
assert new["notes"].splitlines()[0] == "Decided after session 3."
|
|
256
|
+
|
|
257
|
+
|
|
258
|
+
def test_split_a_hypothesis_into_lettered_parts(board2: dict[str, Any]) -> None:
|
|
259
|
+
old = next(h for h in board2["hypotheses"] if h["id"] == "H2")
|
|
260
|
+
parts = [
|
|
261
|
+
{k: v for k, v in old.items() if k != "id"} | {"id": "H2a", "type": "claim"},
|
|
262
|
+
{"id": "H2b", "assumes": "second part", "status": "untested"},
|
|
263
|
+
]
|
|
264
|
+
p = patch(
|
|
265
|
+
add={"hypotheses": parts},
|
|
266
|
+
remove=[{"id": "H2", "reason": "split into H2a and H2b"}],
|
|
267
|
+
set=[{"id": "H2b", "type": "estimate"}],
|
|
268
|
+
)
|
|
269
|
+
assert errors(p) == []
|
|
270
|
+
new = apply_patch(board2, p)
|
|
271
|
+
hyps = {h["id"]: h for h in new["hypotheses"]}
|
|
272
|
+
assert "H2" not in hyps and hyps["H2a"]["type"] == "claim"
|
|
273
|
+
assert hyps["H2b"]["type"] == "estimate"
|
|
274
|
+
assert errors(new) == []
|
|
@@ -66,6 +66,21 @@ def test_schema_refuses(board2: dict[str, Any], fields: dict[str, Any]) -> None:
|
|
|
66
66
|
)
|
|
67
67
|
|
|
68
68
|
|
|
69
|
+
@pytest.mark.parametrize("hid", ["H2a", "H2b", "H12z"])
|
|
70
|
+
def test_split_hypothesis_part_ids_are_valid(board2: dict[str, Any], hid: str) -> None:
|
|
71
|
+
h2(board2)["id"] = hid
|
|
72
|
+
assert not [f for f in validate_record(board2) if f.level == "error"]
|
|
73
|
+
|
|
74
|
+
|
|
75
|
+
@pytest.mark.parametrize("hid", ["H2A", "H2ab", "H2\u0430", "Ha"])
|
|
76
|
+
def test_other_hypothesis_ids_are_refused(board2: dict[str, Any], hid: str) -> None:
|
|
77
|
+
h2(board2)["id"] = hid
|
|
78
|
+
assert any(
|
|
79
|
+
f.level == "error" and f.ref.startswith("hypotheses/1")
|
|
80
|
+
for f in validate_record(board2)
|
|
81
|
+
)
|
|
82
|
+
|
|
83
|
+
|
|
69
84
|
def test_k_above_n_is_an_error(board2: dict[str, Any]) -> None:
|
|
70
85
|
h2(board2).update(rule=RULE, observed={"k": 5, "n": 4, "artefact": "s4"})
|
|
71
86
|
assert found(board2, "error", "H2") == ["observed k=5 exceeds n=4"]
|
|
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
|
|
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
|