smd-engine 0.5.2__tar.gz → 0.5.4__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.5.2 → smd_engine-0.5.4}/CHANGELOG.md +23 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/CONTRIBUTING.md +2 -2
- {smd_engine-0.5.2 → smd_engine-0.5.4}/PKG-INFO +2 -2
- {smd_engine-0.5.2 → smd_engine-0.5.4}/README.md +1 -1
- {smd_engine-0.5.2 → smd_engine-0.5.4}/README_ru.md +1 -1
- smd_engine-0.5.4/cases/example_ru/pekarnya-holding-c1.board.yaml +86 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/docs/README.md +3 -2
- smd_engine-0.5.4/docs/checks.md +23 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/docs/commands.md +1 -1
- {smd_engine-0.5.2 → smd_engine-0.5.4}/docs/data-model.md +11 -19
- {smd_engine-0.5.2 → smd_engine-0.5.4}/docs/method/README.md +1 -1
- {smd_engine-0.5.2 → smd_engine-0.5.4}/docs/method/sources.md +1 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/docs/profiles.md +17 -3
- {smd_engine-0.5.2 → smd_engine-0.5.4}/docs/stages.md +1 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/lenses/README.md +10 -6
- smd_engine-0.5.4/lenses/beer-viable-system.md +67 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/lenses/khaprov-levels.md +24 -1
- {smd_engine-0.5.2 → smd_engine-0.5.4}/lenses/khaprov-ontology.md +50 -8
- {smd_engine-0.5.2 → smd_engine-0.5.4}/procedures/functional-plan.md +4 -2
- {smd_engine-0.5.2 → smd_engine-0.5.4}/procedures/positional-construction.md +5 -2
- {smd_engine-0.5.2 → smd_engine-0.5.4}/profiles/classic-two-boards.yaml +1 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/profiles/management-four-boards.yaml +29 -4
- {smd_engine-0.5.2 → smd_engine-0.5.4}/profiles/program-three-boards.yaml +1 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/pyproject.toml +2 -1
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/apply.py +11 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/compare.py +27 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/pack.py +5 -4
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/profile.py +11 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/render/graph.py +25 -1
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/render/html.py +19 -3
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/render/index.py +19 -2
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/render/markdown.py +9 -1
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/render/text.py +68 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/schemas/board_set.schema.json +40 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/validate/__init__.py +8 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/validate/hints.py +42 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/validate/management.py +152 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/validate/ontology.py +20 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/validate/structure.py +20 -1
- smd_engine-0.5.4/tests/test_beer_layer.py +293 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/tests/test_export.py +13 -0
- smd_engine-0.5.4/tests/test_ontology_continuum.py +203 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/uv.lock +1 -1
- {smd_engine-0.5.2 → smd_engine-0.5.4}/.claude/agents/smd-game-technician.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/.claude/agents/smd-methodologist.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/.claude/agents/smd-visionary.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/.claude/commands/procedure.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/.flake8 +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/.github/workflows/ci.yml +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/.github/workflows/release.yml +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/.gitignore +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/.python-version +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/LICENSE +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/cases/example/bakeries-c1.board.yaml +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/cases/example/bakeries-c2.board.yaml +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/cases/example/golden/README.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/cases/example/golden/bakeries-c2-expected.board.yaml +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/cases/example/golden/s3_transcript.txt +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/cases/example/patches/bakeries-c2-1.patch.yaml +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/cases/example/sources.yaml +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/cases/example/two-boards-c1.board.yaml +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/cases/example_ru/pekarni-c1.board.yaml +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/cases/example_ru/pekarni-c2.board.yaml +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/cases/example_ru/pekarni-oru-c1.board.yaml +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/cases/example_ru/sources.yaml +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/docs/method/encodable.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/docs/method/odi-problematization.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/docs/method/reconciliation.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/docs/method/roles-and-actors.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/docs/method/smd-classic.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/docs/method/structural-moves.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/docs/method/triz-systems.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/docs/plan.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/lenses/design-chain.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/lenses/fliamer-diamond.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/lenses/scamper-check.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/lenses/schukin-boundaries.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/lenses/schukin-interface-tax.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/lenses/three-positions.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/lenses/triz-contradictions.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/procedures/README.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/procedures/field-result.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/procedures/ingest-transcript.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/procedures/problematization.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/procedures/qualification-pass.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/procedures/reflexive-protocol.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/procedures/small-situation.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/procedures/solo-session.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/procedures/theses-to-board.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/procedures/visionary-tract.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/roles/README.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/roles/actors.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/roles/game-technician.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/roles/methodologist.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/roles/researcher.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/roles/visionary.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/__init__.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/cli.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/eval.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/migrate.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/records.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/render/__init__.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/render/assets/frames.css +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/render/assets/frames.js +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/render/assets/graph.css +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/render/assets/graph.js +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/render/frames.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/render/frames_page.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/render/frames_text.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/render/graph_ui.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/render/layout.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/render/light.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/render/mermaid.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/render/sessionflow.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/render/svg.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/render/vault.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/revise.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/schemas/__init__.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/schemas/board_patch.schema.json +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/schemas/source_manifest.schema.json +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/schemas/taxonomies.schema.json +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/screen.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/sources.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/validate/context.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/validate/hypotheses.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/validate/manifest.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/validate/signoffs.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/validate/taxonomies.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/src/smd_engine/validate/theses.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/tests/conftest.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/tests/test_action_program.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/tests/test_apply.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/tests/test_compare.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/tests/test_eval.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/tests/test_frames.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/tests/test_graph.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/tests/test_ingestion.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/tests/test_lenses.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/tests/test_management.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/tests/test_migrate.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/tests/test_procedures.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/tests/test_profile.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/tests/test_publish.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/tests/test_record_boards.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/tests/test_render_and_cli.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/tests/test_revise.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.4}/tests/test_validate.py +0 -0
|
@@ -2,6 +2,29 @@
|
|
|
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.5.4 - 2026-10-29
|
|
6
|
+
|
|
7
|
+
A layer from Stafford Beer's viable system model in the profile `management-four-boards` (Beer, «Мозг фирмы», 1972; М., 1993; gate Бир3, option В). Schema 0.3 stays: every new field is optional, and records without them give the same output.
|
|
8
|
+
|
|
9
|
+
- Profiles: kind flag `vsm`; the kinds it is set on take the element field `vsm_system`, a non-empty list of distinct systems 1-5 (a list, because one person often fills several systems). `management-four-boards` sets it on `position` and `post`.
|
|
10
|
+
- `management-four-boards`, each item marked "Beer layer" in the profile file with its chapter: kind `algedonic_channel` on `ot` with the fields `threshold` (text) and `recovery_time` (days, > 0), the form in which a stakeholder's red line is recorded; relations `escalates` (from an algedonic channel to the place that must act once the recovery time has run out) and `filters` (what a place passes up); hints `single-node-metasystem` (one filler fills systems 3, 4 and 5), `line-without-recovery` (a channel with a threshold and no recovery time or no `escalates` to a post, position or place for others) and `absorbed-into-system-1` (a place filling system 5 `captures` places of the business that fill systems 4 and 5). Each off its kind is an error: `vsm_system` on a kind not flagged `vsm`, `threshold` or `recovery_time` off an `algedonic_channel`.
|
|
11
|
+
- Lens `beer-viable-system` 0.1.0, offered by `positional-construction` 0.2.5 (sections 2 and 5) and `functional-plan` 0.2.3 (section 4).
|
|
12
|
+
- Example `cases/example_ru/pekarnya-holding-c1.board.yaml`: an owner-run bakery sold to a holding, which gives each of the three hints once.
|
|
13
|
+
- Lens `khaprov-levels` 0.2.0: a section, marked as an AI draft, with the diagonal of Khaprov's seven levels and the six tiers of a business (ontology frames tier 1 as the ontology record, not a seventh tier; culture to tier 1; politics and strategy to tiers 2 and 3; programs to tier 4; projects to tier 5; objects to tiers 5 and 6; pace falls as the level rises), and questions 11 and 12 that use it.
|
|
14
|
+
- `docs/method/sources.md`: row BEER1972. `docs/profiles.md`: the Beer layer of the management profile.
|
|
15
|
+
- `docs/checks.md`: the checks section of `docs/data-model.md`, moved to a file of its own when the data model passed 300 lines. `smd pack` adds it after the data model (`# Checks: docs/checks.md`), and the wheel ships it beside `data-model.md`.
|
|
16
|
+
|
|
17
|
+
## 0.5.3 - 2026-10-29
|
|
18
|
+
|
|
19
|
+
The space-time continuum of an ontology (Khaprov, podcast on ontology, 28.10.2026; gate Х1, option В). Schema 0.3 stays: every new field is optional, and records without them give the same output.
|
|
20
|
+
|
|
21
|
+
- Ontology records take `lives_in` (what the system lives in and must fit into: entries `{id: <element id>}` or `{text: "..."}`, no entry twice), `tempos` (`{id, years}` or `{text, years}`), `horizon` (years the picture is expected to hold) and `covers` (element ids, no id twice). Every `id` entry and every id in `covers` must be an element of the record (error). The entries are explicit: an earlier draft of this change told an id from a text by its shape.
|
|
22
|
+
- Elements take `pace`: years, the characteristic period of change of what the element stands for.
|
|
23
|
+
- Hint `ontology-outlives-pace`, enabled in the three shipped profiles: an ontology with a `horizon` longer than the `pace` of an element in `lives_in` or `covers` (`covers` adds to `lives_in`) or than a `tempos` entry; the continuum is exhausted before the horizon. The message cites the transcript of 202 lines (l.154-172), which now opens with three header lines (link, date, blank line); every podcast citation in the lens moved by three lines.
|
|
24
|
+
- `smd apply` sets the fields by id; a removed element leaves `covers` and the `{id}` entries of `lives_in` and `tempos`. `smd revise` carries them. The Markdown digest and `smd index` show `lives_in`, `tempos` and `horizon`; `smd compare` adds a section `ontology: continuum` when a record has them.
|
|
25
|
+
- `smd graph`, `smd vault` and `smd render --format html` show `lives_in`, `tempos`, `horizon` and `covers` where they show `competes` and `test`, and an element's `pace` with its other fields (the Markdown digest and `smd index` too; `covers` is now also shown there). The graph draws `covers` and the element ids of `lives_in` as links `covers` and `lives_in` (grey: `graph.js` is unchanged, so pages without them stay byte for byte the same), and lists them as link kinds only when a record has them. `smd frames` does not show `pace`, which would need a change to `frames.js`. Russian pages and digests label the four fields in Russian (`covers` as «охватывает») and write years with their plural (1 год, 2 года, 5 лет).
|
|
26
|
+
- Lens `khaprov-ontology` 0.2.0: the podcast as a second source; questions 16-21 on what the system fits into, its tempos and horizon, objects bought into an old picture, the cost of an error and a platform's layer, with their output slots.
|
|
27
|
+
|
|
5
28
|
## 0.5.2 - 2026-10-29
|
|
6
29
|
|
|
7
30
|
- The public export leaves out `tests/test_export_public.py`, which tests the maintainer tool that the export also leaves out; 0.5.1 was not released publicly for this reason.
|
|
@@ -21,7 +21,7 @@ uv run black . && uv run flake8 && uv run mypy src && uv run pytest
|
|
|
21
21
|
|
|
22
22
|
3. CI (`.github/workflows/ci.yml`) runs black, flake8, mypy, pytest and a trivy scan. A pull request is merged after CI is green.
|
|
23
23
|
4. Commit messages are conventional: `feat(scope): ...`, `fix(scope): ...`, `docs(scope): ...`, `chore(scope): ...`.
|
|
24
|
-
5. Update the docs in the same change: `docs/data-model.md` for any record field
|
|
24
|
+
5. Update the docs in the same change: `docs/data-model.md` for any record field, `docs/checks.md` for any check, `docs/profiles.md` for the profile format, `docs/commands.md` and the table in `README.md` for a command, `CHANGELOG.md` for anything a user would notice.
|
|
25
25
|
|
|
26
26
|
Tests live in `tests/`, one file per area (`test_validate.py`, `test_profile.py`, `test_apply.py`, ...). The fixtures `board`, `board2` and `manifest` in `tests/conftest.py` load `cases/example/` and are deep-copied for each test, so a test may change them freely. Add one focused test per behaviour you add.
|
|
27
27
|
|
|
@@ -56,7 +56,7 @@ A check is a function that takes the context `Ctx` (`validate/context.py`) and r
|
|
|
56
56
|
1. Write the function in the module of its subject under `src/smd_engine/validate/` (`structure.py`, `theses.py`, `hints.py`, ...). Decorate a check that only applies to board sets with `@board_set`.
|
|
57
57
|
2. Add it to `REGISTRY` in `src/smd_engine/validate/__init__.py` (and its import). Findings come out in registry order.
|
|
58
58
|
3. A method hint is declared with `@hint("hint-id")` and runs only for a profile that lists the id under `hints`. Add the id to the `hints` list of each profile that should have it; an id that no check declares is an error of every record that names it.
|
|
59
|
-
4. Describe the check in
|
|
59
|
+
4. Describe the check in `docs/checks.md`.
|
|
60
60
|
5. Test it in `tests/test_validate.py`: take the `board` fixture, break one thing, assert on the finding.
|
|
61
61
|
|
|
62
62
|
## Add a profile
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.5
|
|
2
2
|
Name: smd-engine
|
|
3
|
-
Version: 0.5.
|
|
3
|
+
Version: 0.5.4
|
|
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
|
|
@@ -127,7 +127,7 @@ A profile (`profiles/*.yaml`) holds the boards, the element kinds, the relation
|
|
|
127
127
|
|---|---|
|
|
128
128
|
| `program-three-boards` (default) | org-activity `od`, object `oo`, situation `s` with a small and a big half |
|
|
129
129
|
| `classic-two-boards` | org-activity `od` and object-ontological `oo` side by side; no situation board |
|
|
130
|
-
| `management-four-boards` | G.P.'s scheme of organisation, leadership and management: org-activity `od` and the upper system `ot` on top, the apparatus of leadership `ap` and the managed polysystem `us` below |
|
|
130
|
+
| `management-four-boards` | G.P.'s scheme of organisation, leadership and management: org-activity `od` and the upper system `ot` on top, the apparatus of leadership `ap` and the managed polysystem `us` below; a labelled layer from Beer's viable system model (systems 1-5, red lines as algedonic channels) |
|
|
131
131
|
|
|
132
132
|
An unknown profile, board or kind is an error naming the element. Format and the keys of a profile: `docs/data-model.md`, section Profiles.
|
|
133
133
|
|
|
@@ -102,7 +102,7 @@ A profile (`profiles/*.yaml`) holds the boards, the element kinds, the relation
|
|
|
102
102
|
|---|---|
|
|
103
103
|
| `program-three-boards` (default) | org-activity `od`, object `oo`, situation `s` with a small and a big half |
|
|
104
104
|
| `classic-two-boards` | org-activity `od` and object-ontological `oo` side by side; no situation board |
|
|
105
|
-
| `management-four-boards` | G.P.'s scheme of organisation, leadership and management: org-activity `od` and the upper system `ot` on top, the apparatus of leadership `ap` and the managed polysystem `us` below |
|
|
105
|
+
| `management-four-boards` | G.P.'s scheme of organisation, leadership and management: org-activity `od` and the upper system `ot` on top, the apparatus of leadership `ap` and the managed polysystem `us` below; a labelled layer from Beer's viable system model (systems 1-5, red lines as algedonic channels) |
|
|
106
106
|
|
|
107
107
|
An unknown profile, board or kind is an error naming the element. Format and the keys of a profile: `docs/data-model.md`, section Profiles.
|
|
108
108
|
|
|
@@ -104,7 +104,7 @@ uv run smd frames cases/example_ru/pekarni-c2.board.yaml -o out/frames.html
|
|
|
104
104
|
|---|---|
|
|
105
105
|
| `program-three-boards` (по умолчанию) | оргдеятельностная `od`, объектная `oo`, ситуационная† `s` с малой† и большой† половинами |
|
|
106
106
|
| `classic-two-boards` | оргдеятельностная `od` и объектно-онтологическая `oo` рядом; ситуационной доски нет |
|
|
107
|
-
| `management-four-boards` | схема ОРУ Г.П. Щедровицкого: оргдеятельностная `od` и верхняя система ОРУ `ot` сверху, аппарат руководства `ap` и управляемая полисистема `us`
|
|
107
|
+
| `management-four-boards` | схема ОРУ Г.П. Щедровицкого: оргдеятельностная `od` и верхняя система ОРУ `ot` сверху, аппарат руководства `ap` и управляемая полисистема `us` снизу; отдельный слой из модели жизнеспособной системы Бира (системы 1-5, красные линии как алгедонические каналы) |
|
|
108
108
|
|
|
109
109
|
Неизвестный профиль, доска или вид элемента - ошибка с именем элемента. Формат и ключи профиля: `docs/data-model.md`, раздел Profiles.
|
|
110
110
|
|
|
@@ -0,0 +1,86 @@
|
|
|
1
|
+
# Выдуманный учебный пример на слое Бира профиля management-four-boards
|
|
2
|
+
# (С. Бир, «Мозг фирмы», 1972; пер. М. М. Лопухин, М., 1993): одну из трёх
|
|
3
|
+
# пекарен из cases/example_ru, которой управляет сам владелец, покупает
|
|
4
|
+
# региональный хлебный холдинг. Запись показывает три подсказки слоя:
|
|
5
|
+
# - single-node-metasystem: владелец один заполняет системы 3, 4 и 5 (место
|
|
6
|
+
# post-owner); при передаче метасистема уйдёт вместе с ним;
|
|
7
|
+
# - line-without-recovery: красная линия ch-orders (алгедонический канал) с
|
|
8
|
+
# порогом, но без времени восстановления и без адреса, куда идёт сигнал;
|
|
9
|
+
# ch-flour — та же линия, записанная полностью;
|
|
10
|
+
# - absorbed-into-system-1: сценарий «продажа холдингу» как строка на досках:
|
|
11
|
+
# место правления холдинга (система 5) захватывает (captures) системы 4 и 5
|
|
12
|
+
# пекарни (Бир, гл. 15: фирма становится частью системы 1 покупателя).
|
|
13
|
+
record: board_set
|
|
14
|
+
schema_version: "0.3"
|
|
15
|
+
id: pekarnya-holding-c1
|
|
16
|
+
case: example-pekarnya-holding
|
|
17
|
+
title: Пекарня владельца и холдинг-покупатель, слой Бира, экран после сессии 1
|
|
18
|
+
date: "2026-02-07"
|
|
19
|
+
cycle: 1
|
|
20
|
+
status: draft
|
|
21
|
+
profile: management-four-boards
|
|
22
|
+
elements:
|
|
23
|
+
# Оргдеятельностная доска: владелец, покупатель, группа карты
|
|
24
|
+
- {id: p-owner, board: od, kind: position, label: "владелец и директор пекарни",
|
|
25
|
+
acts_as: leader, stance: inside}
|
|
26
|
+
- {id: p-holding, board: od, kind: position, label: "правление хлебного холдинга",
|
|
27
|
+
acts_as: organiser, stance: external}
|
|
28
|
+
- {id: p-map, board: od, kind: position, label: "группа, которая составляет карту передачи",
|
|
29
|
+
stance: external}
|
|
30
|
+
- {id: place-heir, board: od, kind: place_for_others, label: "наёмный директор после продажи"}
|
|
31
|
+
- {id: gap-model, board: od, kind: gap,
|
|
32
|
+
label: "у кого будет модель пекарни (система 4), когда владелец уйдёт?",
|
|
33
|
+
short: "у кого модель пекарни после ухода владельца?", of: position}
|
|
34
|
+
# Система ОРУ: знание, идеал, программа, красные линии как алгедонические каналы
|
|
35
|
+
- {id: k-retro, board: ot, kind: knowledge_retro,
|
|
36
|
+
label: "журнал заказов и сбоев за три года", seen_from: p-map}
|
|
37
|
+
- {id: ideal, board: ot, kind: ideal_state,
|
|
38
|
+
label: "через три года после продажи пекарня печёт под своим именем", seen_from: p-map}
|
|
39
|
+
- {id: prog, board: ot, kind: programme,
|
|
40
|
+
label: "год передачи: владелец наставником при наёмном директоре", seen_from: p-map}
|
|
41
|
+
- {id: ch-flour, board: ot, kind: algedonic_channel,
|
|
42
|
+
label: "запас муки ниже нормы", threshold: "мука меньше чем на 4 дня выпечки",
|
|
43
|
+
recovery_time: 2, seen_from: p-map}
|
|
44
|
+
- {id: ch-orders, board: ot, kind: algedonic_channel,
|
|
45
|
+
label: "сорван срок поставки сетевому заказчику", threshold: "задержка больше 1 дня",
|
|
46
|
+
seen_from: p-map}
|
|
47
|
+
# Аппарат руководства: места и их наполнение, системы 1-5 по Биру
|
|
48
|
+
- {id: post-owner, board: ap, kind: post, label: "директор-владелец", fillers: [владелец],
|
|
49
|
+
vsm_system: [3, 4, 5]}
|
|
50
|
+
- {id: post-shift, board: ap, kind: post, label: "старший смены", fillers: [старший пекарь],
|
|
51
|
+
vsm_system: [1]}
|
|
52
|
+
- {id: post-holding, board: ap, kind: post, label: "правление холдинга",
|
|
53
|
+
fillers: [председатель, финансовый директор, директор по развитию], vsm_system: [4, 5]}
|
|
54
|
+
- {id: grp-bakers, board: ap, kind: group, label: "пекари, которые сами меняются сменами"}
|
|
55
|
+
# Управляемая полисистема: пекарня и её заказчики
|
|
56
|
+
- {id: mono-bakery, board: us, kind: monosystem, label: "пекарня: цех, смены, печи",
|
|
57
|
+
seen_from: p-map}
|
|
58
|
+
- {id: mono-clients, board: us, kind: monosystem, label: "постоянные заказчики пекарни",
|
|
59
|
+
seen_from: p-map}
|
|
60
|
+
- {id: wp-bake, board: us, kind: work_process, label: "ночная выпечка", in: [mono-bakery],
|
|
61
|
+
seen_from: p-map}
|
|
62
|
+
- {id: f-owner, board: us, kind: fact,
|
|
63
|
+
label: "о закупке муки и о сроках сетевых заказов решает только владелец",
|
|
64
|
+
short: "о муке и сроках заказов решает только владелец", seen_from: p-map,
|
|
65
|
+
epistemic: unverified}
|
|
66
|
+
relations:
|
|
67
|
+
- {from: p-owner, to: post-owner, kind: belongs}
|
|
68
|
+
- {from: p-owner, to: post-owner, kind: represents}
|
|
69
|
+
- {from: p-holding, to: post-holding, kind: belongs}
|
|
70
|
+
- {from: p-holding, to: post-holding, kind: represents}
|
|
71
|
+
- {from: post-owner, to: post-shift, kind: subordinates}
|
|
72
|
+
- {from: post-shift, to: post-owner, kind: filters, label: "только сбои дольше смены"}
|
|
73
|
+
- {from: grp-bakers, to: post-shift, kind: personal}
|
|
74
|
+
- {from: ch-flour, to: post-owner, kind: escalates, label: "через 2 дня"}
|
|
75
|
+
- {from: post-holding, to: post-owner, kind: captures, label: "сценарий: продажа холдингу"}
|
|
76
|
+
- {from: prog, to: mono-bakery, kind: captures}
|
|
77
|
+
- {from: k-retro, to: f-owner, kind: knows}
|
|
78
|
+
- {from: mono-bakery, to: mono-clients, kind: symbiotic}
|
|
79
|
+
transitions:
|
|
80
|
+
- {n: 1, from: p-map, to: f-owner, label: "кто решает сейчас"}
|
|
81
|
+
- {n: 2, from: f-owner, to: post-owner, label: "чьё это место"}
|
|
82
|
+
- {n: 3, from: post-owner, to: ideal, label: "что останется после продажи"}
|
|
83
|
+
state:
|
|
84
|
+
version: "0.1"
|
|
85
|
+
open: ["gap-model"]
|
|
86
|
+
next_move: "записать для каждой красной линии время восстановления и место, куда идёт сигнал"
|
|
@@ -6,7 +6,8 @@ Start with `README.md` in the repository root. This folder holds the reference d
|
|
|
6
6
|
|
|
7
7
|
| File | Content |
|
|
8
8
|
|---|---|
|
|
9
|
-
| `data-model.md` | the record format: board sets, source manifests, taxonomies, patches, the `profile` key, migration
|
|
9
|
+
| `data-model.md` | the record format: board sets, source manifests, taxonomies, patches, the `profile` key, migration |
|
|
10
|
+
| `checks.md` | the checks the validator runs: errors, warnings and hints, and the profile and source of each hint |
|
|
10
11
|
| `profiles.md` | the profile format: boards and their regions, kinds, the screen layout, the ids every profile defines, the checks of a profile file |
|
|
11
12
|
| `commands.md` | the commands of `smd` with examples, and the exit codes |
|
|
12
13
|
| `plan.md` | the build plan approved 2026-10-25 and the architecture of the repository |
|
|
@@ -30,7 +31,7 @@ Start with `README.md` in the repository root. This folder holds the reference d
|
|
|
30
31
|
| Folder | Content |
|
|
31
32
|
|---|---|
|
|
32
33
|
| `../cases/example/` | an invented case in English: two cycles, a patch, a classic-profile record, a golden run |
|
|
33
|
-
| `../cases/example_ru/` | the same case with Russian labels |
|
|
34
|
+
| `../cases/example_ru/` | the same case with Russian labels, and two records on the management profile: G.P.'s scheme of ОРУ (`pekarni-oru-c1`) and its Beer layer, one bakery sold to a holding (`pekarnya-holding-c1`) |
|
|
34
35
|
| `../cases/example/golden/README.md` | how to check a procedure run against a reference record with `smd eval` |
|
|
35
36
|
|
|
36
37
|
## Other files in the root
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
# Checks
|
|
2
|
+
|
|
3
|
+
The checks the validator runs on the records of `docs/data-model.md`. Section and field names refer to that file; the profile format is in `docs/profiles.md`.
|
|
4
|
+
|
|
5
|
+
The checks are in `src/smd_engine/validate/`, one module per subject, run in the order of its `REGISTRY`; hints run only when the record's profile enables them. An unknown profile, or a board, kind or relation kind outside the profile, is an error reported with the schema errors, and like them it stops the checks:
|
|
6
|
+
- **Errors:** duplicate ids; `fillers` on an element that is not a role; a `detail` row whose length differs from `columns`; dangling references in `seen_from`, `in`, relations, transitions, qualification targets, move sources and thesis `feeds`; `seen_from` or `reflected_from` that is not a position; `half` rules; containment cycles; transition numbering; a closed K without `closed_in`; a K raised after the record's cycle; a record revising itself; `verified` without a checker; unknown source ids when a manifest is given.
|
|
7
|
+
- **Errors (ingestion):** `of` on an element that is not a gap; `performed_by` on a non-function or not naming a position or place for others; a thesis that `raises` an unknown K; a hypothesis result without its text, field artefact or `resolved_in`; dangling hypothesis targets or K; a thesis status that does not fit its voice; an accepted move from an AI voice with no `accept_move` sign-off; a sign-off by an AI voice, without a target, or aimed at the wrong kind of target.
|
|
8
|
+
- **Warnings:** a screen label (`short`, or `label` when there is no `short`) over 60 characters, which the screen cuts; a kind off its usual board; a content item without a position; a transition inside one board; a `shift` between non-positions; a manifest entry with no file or url, or no clean-room decision.
|
|
9
|
+
- **Warnings (ingestion):** a revising cycle with no `reflected_from`; a thesis with no source address (except AI voice); an accepted move with neither a source nor a sign-off; a closed K, a `refined` thesis, a hypothesis result or a `verified` record with no matching sign-off; a hypothesis `testing` with no action; a sign-off that changes nothing, because its target is not in the state it licenses (only the latest K or move sign-off on a target is checked: `reopen_k` supersedes an earlier `close_k`).
|
|
10
|
+
- **Hints** (Girenko's criteria for a group screen, 17.10.2026): no entry; an empty board, or an empty half of a halved board (the program's small or big situation not laid out); one position and no places for others; a new frame without functions or with functions no one performs; open gaps; open qualifications; candidate moves, on elements and theses; AI variants awaiting the group.
|
|
11
|
+
- **Warnings (step 3):** subject-object talk ("we must", "our task", "мы должны", "наша задача") in a label on a board the profile flags `object` (the object board); `represents` not starting from a position; an ontology subject for a position outside `valid_for`.
|
|
12
|
+
- **Errors (step 3):** ontology `valid_for` that is not a position, `cooperation` that is not a cooperation element, `test` that is not a hypothesis, an id in `lives_in`, `covers` or `tempos` that is not an element.
|
|
13
|
+
- **Hints (classic method):** an ontology with no realizability test, or valid for several positions with no cooperation; an ontology whose `horizon` is longer than the `pace` of an element in `lives_in` or `covers`, or than a `tempos` entry: the continuum is exhausted before the horizon (`ontology-outlives-pace`, Khaprov, podcast 28.10.2026, l.154-172; no hint without `horizon`); a gap or a problem thesis with no scheme block; a new cycle with no `difficulty`; a hypothesis with no `revise_if`; degenerate belts (GP1987): mostly М-К theses and none in М ("play with words"), or М theses with none in мД (thinking cut off from the situation).
|
|
14
|
+
- **Errors (G.P.'s «Программа действий»):** `stance` or `acts_as` on an element that is not a position, `goal_source`, `arises_from` or `assigned_by` on one that is not a goal, `nature` off an object board; an `arises_from` id that is neither a gap, a fact, nor a `difficulty`, `problem` or factual thesis; `assigned_by` that is not a position or place for others.
|
|
15
|
+
- **Warnings (G.P.'s «Программа действий»):** `reflected_from` naming a position with `stance: inside`.
|
|
16
|
+
- **Hints (G.P.'s «Программа действий», GP-Guide11, read against GP-T5):** an object-board element seen from a position with `stance: inside` (`object-from-inside`, ¶36); a new cycle whose object board is seen from an `external` position with no `reflected_from` (`external-without-reflection`, ¶35, ¶47); a goal with no breakdown: no `goal_source`, `arises_from`, gap linked by a relation, `difficulty` or `problem` thesis naming it, or `state.difficulty` (`goal-without-breakdown`, ¶43; also an `assigned` goal with no `assigned_by` and a `breakdown` goal with no `arises_from`); a position with `acts_as` (not `functionary`) and no `represents` relation (`position-without-object`, GP-Guide10 ¶7, ¶19); an object-board element with `modality: ought` and no fact linked by a relation, `in`, or a factual thesis (`ought-without-fact`, GP-T5 p. 252); `ought` on a `natural` element (`design-the-natural`, GP-STS); theses, other than `open`, with neither `feeds` nor `about` (`information-without-cell`, ¶5). Where the 1981 and 1988 texts disagree the 1988 lectures win: GP-Guide5 ¶7 required a forecast ("Управлять без прогноза в принципе невозможно"); GP-T5 p. 251 calls forecasting in оргуправление a substitution by scientistic principles, so `ought-without-fact` asks for the natural processes, not a forecast.
|
|
17
|
+
- **Hints (G.P.'s management scheme, `management-four-boards`, GP-T5):** a `leads` relation to someone with goals `goal_source: own` (seen from the target or from a position that `belongs` to it) (`lead-vs-manage`, pp. 169-170); a `manages` relation with no element the source `produces` and the target `uses` (`manage-via-organizedness`, pp. 222-223); a position that `manages` with no retrospective or no projective knowledge seen from it or linked to it (`manage-without-knowledge`, p. 241); a `leads` relation whose ends hold no post (itself, or one it `belongs` to), or with no line of `subordinates` from the leader's post down to the other (`leads-outside-organisation`, pp. 242, 254); a `represents` target outside the kinds expected for the position's `acts_as`: organiser to `post`, `functional_place`, `mission`, `monosystem`; leader to `post` (not `group`: the informal group is outside the administrative structure, pp. 224-225, 254); manager to `work_process`, `trajectory`, `self_motion`; politician to `club`, `position`; functionary to none (`representation-fit`; the table is the engine's reading of GP-T5 pp. 170-175, 213, 223, 242-244, 253-254, not a table of G.P.'s); an upper board with content but no past of the object (a `factual` kind, `knowledge_retro`, or `modality: fact` on the managed board), no `ideal_state`, or no `captures` from the upper board to the managed one (`development-step`, «шаг развития», «минимальная единица», pp. 229, 232, 238); a managed board with fewer than two monosystems, or monosystems with no `parasitic`, `symbiotic` or `mechanism_of` relation (`polysystem`, pp. 206-213).
|
|
18
|
+
- **Errors (Beer layer of `management-four-boards`, gate Бир3 В):** `vsm_system` on a kind the profile does not flag `vsm`; `threshold` or `recovery_time` on an element that is not an `algedonic_channel`. The schema refuses a `vsm_system` that is not a non-empty list of distinct integers 1-5, an empty `threshold` and a `recovery_time` that is not a number > 0.
|
|
19
|
+
- **Hints (Beer layer of `management-four-boards`, BEER1972):** one filler fills systems 3, 4 and 5 across the posts and positions it fills (`single-node-metasystem`, Гл. 9, 13): the transfer will remove the metasystem with the person. The filler of a post or position is the one actor in its `fillers`; a post with no fillers is filled by the one position that `belongs` to it; a position with no fillers that belongs to posts with one and the same filler is that filler; an element with several fillers, or a post with several positions, is shared (a multinode, Гл. 14) and counts for nobody. An `algedonic_channel` with a `threshold` and no `recovery_time`, or with no `escalates` relation from it to a `post`, `position` or `place_for_others` (`line-without-recovery`, Гл. 17). A place filling system 5 that `captures` places of the business filling systems 4 and 5 between them (`absorbed-into-system-1`, Гл. 15): the business becomes part of the buyer's system 1, its name and identity at risk. The engine has no scenario table: a transfer scenario is laid out on the boards as the buyer's post and its `captures` relations (G.P.'s «захват», GP-T5 pp. 226-227).
|
|
20
|
+
- **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 not a 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'").
|
|
21
|
+
- **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.
|
|
22
|
+
- **Warnings (v0.3):** `tags` or `detail.keys` used and no taxonomy file given.
|
|
23
|
+
- **Across cycles:** when the revised record is among the files validated, a new cycle with no new or changed frame, function, model, concept, standard or cooperation gets the hint "reflection without a new scheme". A cycle run by `ingest-transcript` or `theses-to-board` whose new theses feed only elements the previous cycle did not have gets `cells-from-information`: the cells were drawn from the information, not before it (GP-Guide11 ¶5).
|
|
@@ -43,4 +43,4 @@ uv run smd apply cases/example/bakeries-c2.board.yaml cases/example/patches/bake
|
|
|
43
43
|
|
|
44
44
|
`sources --folder` checks that every listed file is present, has a sha256, and matches it. `--refresh` rewrites the sha256 instead, for logs that grow.
|
|
45
45
|
|
|
46
|
-
`compare` matches the elements of two board sets by kind group and wording and classifies each pair as agreement, refinement, conflict, or present in one set only. `--merge` writes a draft cycle on top of B: elements only in A are imported as hypotheses with a `from-<A>` lineage tag, and each conflict becomes an open K with the options lock, fork, rebase, merge. Matching by wording is a heuristic; the report is material for a qualification pass.
|
|
46
|
+
`compare` matches the elements of two board sets by kind group and wording and classifies each pair as agreement, refinement, conflict, or present in one set only. `--merge` writes a draft cycle on top of B: elements only in A are imported as hypotheses with a `from-<A>` lineage tag, and each conflict becomes an open K with the options lock, fork, rebase, merge. Matching by wording is a heuristic; the report is material for a qualification pass. When an ontology record of either set has `lives_in`, `tempos`, `horizon` or `covers`, the report adds a section `ontology: continuum`: the records matched by id, with those fields in A and in B.
|
|
@@ -58,6 +58,10 @@ Fields: `id` (no dot, since a dot separates a board from its half), `template`,
|
|
|
58
58
|
| `goal_source` | goals only: `breakdown` (set at a прокол, GP-Guide11 ¶43), `assigned` (passed down under руководство, GP-Guide4 ¶12), `own` (собственная цель of the `seen_from` position) |
|
|
59
59
|
| `arises_from` | goals only: what broke: ids of gaps, facts (a kind the profile flags `factual`, `fact` in the default profile, or `modality: fact`), and `difficulty`, `problem` or factual (`modality: fact`) theses |
|
|
60
60
|
| `assigned_by` | goals only: the position or place for others that passed the goal down |
|
|
61
|
+
| `pace` | years, a number > 0: the characteristic period of change of what the element stands for (a tier, a technology); any element. The hint `ontology-outlives-pace` compares it with an ontology's `horizon` |
|
|
62
|
+
| `vsm_system` | kinds the profile flags `vsm` only (`position` and `post` of `management-four-boards`): the systems 1-5 of Beer's viable system model that the place or position fills, a list of distinct numbers, e.g. `[3, 4, 5]`. A list, because one person often fills several systems (BEER1972 Гл. 9), and the hint `single-node-metasystem` reads them together |
|
|
63
|
+
| `threshold` | `algedonic_channel` only: the limit of the index past which the channel signals, as text. A stakeholder's red line is recorded as such a channel (BEER1972 Гл. 17) |
|
|
64
|
+
| `recovery_time` | `algedonic_channel` only: days, a number > 0, that the unit has to bring the index back before the signal goes up by `escalates` (BEER1972 Гл. 17) |
|
|
61
65
|
| `modality` | `fact` or `ought` (модальность фактического и должного, GP-Guide11 ¶7); theses carry it too |
|
|
62
66
|
| `nature` | elements of an object board only: `natural`, `artificial` or `both` (естественное, искусственное; GP-STS; GP-T5 p. 252) |
|
|
63
67
|
| `performed_by` | functions only: the position or place for others that performs the function; the viewpoint stays in `seen_from` |
|
|
@@ -177,6 +181,10 @@ An ontological picture is valid for a chosen set of positions, and is checked fo
|
|
|
177
181
|
| `competes` | what competes with what (Khaprov's ontology test) |
|
|
178
182
|
| `aspects` | the object taken apart, aspect name to text; the usual ones are `activity`, `carrier`, `ownership`, `management` and `separation` (how they come apart), others may be added |
|
|
179
183
|
| `test` | the hypothesis that tests realizability |
|
|
184
|
+
| `lives_in` | what the system lives in and must fit into, no entry twice: `{id: <element id>}` (must exist) or `{text: "..."}` |
|
|
185
|
+
| `tempos` | the tempos the ontology assumes: `{id, years}` or `{text, years}`, e.g. `{text: "business models", years: 5}` |
|
|
186
|
+
| `horizon` | years the ontology is expected to hold; with `pace` and `tempos`, the space-time continuum of the record (Khaprov, podcast 28.10.2026, `lenses/khaprov-ontology.md`) |
|
|
187
|
+
| `covers` | element ids the picture covers besides those in `lives_in`, no id twice; the hint `ontology-outlives-pace` reads both |
|
|
180
188
|
|
|
181
189
|
### Sign-offs (interface tax)
|
|
182
190
|
|
|
@@ -248,7 +256,7 @@ Top level: `id`, `case`, `applies_to` (the board's id), `version` (the board's n
|
|
|
248
256
|
- `add`: items appended to `boards` (record boards, placed before `elements` when the board had none), `elements`, `relations`, `transitions`, `qualifications`, `theses`, `hypotheses`, `ontology`, `signoffs`, in the board's shapes; `sources`: manifest ids added to the board's `sources`. The added items are checked by the board schema after application, not in the patch.
|
|
249
257
|
- `set`: `{id, <field>: value}` merged into the record board, element, K, thesis, hypothesis or ontology record of that id; `null` deletes the field. `{n, <field>: value}` does the same for the transition numbered `n` (`n` itself is not changed). When both the old and the new value are mappings (`detail`, `move`, `tags`, `aspects`), they merge one level deep, key by key, and `null` deletes that key; lists and scalars replace. So `{id: x, detail: {keys: {tier: tier}}}` keeps the table's `columns` and `rows`, and `{id: m, move: {from: [a, b]}}` keeps the move's `op`.
|
|
250
258
|
- `board_notes`: text appended to the board's `notes`, before the lines for removals.
|
|
251
|
-
- `remove`: `{id, reason}` or `{n, reason}`. `n` drops that transition (later ones renumbered 1..n) and notes `<patch id>: removed transition <n>: <reason>`. The item is dropped with every link that names it; each id and reason is appended to the board's `notes` as `<patch id>: removed <id>: <reason>`, followed by `; dropped sign-off <function> <id> (<by>, <date>)` for each sign-off dropped with it. A record board is removed with the elements on it, noted as `; with <ids>`. Links dropped: relations and transitions from or to it (the remaining transitions are renumbered 1..n), `reflected_from`, record board `seen_from` and `unfolds`, element `seen_from`, `performed_by` and `in`, qualification `targets`, thesis `feeds`, `about` and `raises`, hypothesis `targets` and `qualifications`, goal `arises_from` and `assigned_by`, ontology `valid_for`, `subjects` of that position, `cooperation` and `test`, sign-offs on it, and its entry in `state.open`. A list left empty is deleted, except `valid_for` and a move's `from`, which stay empty so that the validator reports them.
|
|
259
|
+
- `remove`: `{id, reason}` or `{n, reason}`. `n` drops that transition (later ones renumbered 1..n) and notes `<patch id>: removed transition <n>: <reason>`. The item is dropped with every link that names it; each id and reason is appended to the board's `notes` as `<patch id>: removed <id>: <reason>`, followed by `; dropped sign-off <function> <id> (<by>, <date>)` for each sign-off dropped with it. A record board is removed with the elements on it, noted as `; with <ids>`. Links dropped: relations and transitions from or to it (the remaining transitions are renumbered 1..n), `reflected_from`, record board `seen_from` and `unfolds`, element `seen_from`, `performed_by` and `in`, qualification `targets`, thesis `feeds`, `about` and `raises`, hypothesis `targets` and `qualifications`, goal `arises_from` and `assigned_by`, ontology `valid_for`, `covers` and the `{id}` entries of `lives_in` and `tempos`, `subjects` of that position, `cooperation` and `test`, sign-offs on it, and its entry in `state.open`. A list left empty is deleted, except `valid_for` and a move's `from`, which stay empty so that the validator reports them.
|
|
252
260
|
- `state`: `accepted` and `open` entries are appended, `remove_open` entries dropped from `open`, `next_move` and `difficulty` replaced.
|
|
253
261
|
|
|
254
262
|
`smd apply <board> <patch> -o <out> [--sources <manifest>] [--taxonomies <file>]` applies `add`, `set`, `board_notes`, `remove`, `sources`, `state` and `title` in that order, sets `state.version`, appends the patch id to `applied`, and validates the result, with the manifest and the taxonomy file when given; an error in an item names the item's id. A patch for another board, a `set` or `remove` naming an unknown id or transition number, or, with `--sources`, a patch `cites` entry that is not in the manifest exits 2. A transition `n` in `set` and `remove` is its number after `add`, before this patch renumbers; so `add` may give a transition and `set` may change it. The notes get `board_notes` (trailing whitespace dropped), then one line per removal, each joined to the notes by one newline. A patch already in `applied` exits 1: a patch applies once. A result with errors is not written and the command exits 1; `--force` writes it and still exits 1. The output is in the engine's YAML layout (`dump_record`), so a board written by the engine changes only in the patched lines; comments of a hand-written board are not kept. `smd revise` does not carry `applied` into the next cycle.
|
|
@@ -258,7 +266,7 @@ Top level: `id`, `case`, `applies_to` (the board's id), `version` (the board's n
|
|
|
258
266
|
A profile is a YAML file in `profiles/` of the install: the repository folder in a checkout, `smd_engine/assets/profiles` in the wheel. A record names its profile by id in `profile`; there is no per-case profile path, so a new profile is added to `profiles/` of the install. The schema leaves `board`, `kind` and the relation `kind` as strings; the validator checks them against the record's profile, and an unknown board or kind is an error naming the element and the value. Three profiles ship:
|
|
259
267
|
- `program-three-boards` (default): the program's screen (`screen: triangles`), boards `od`, `oo` and `s` (halves `small`, `big`), the 19 kinds above, every hint;
|
|
260
268
|
- `classic-two-boards`: boards `od` and `oo` side by side (`screen: regions`); no `entry` and no situation kinds, plus `reflexive_position` and `norm`; no `entry` or situation hints; no SessionFlow export. Example: `cases/example/two-boards-c1.board.yaml`.
|
|
261
|
-
- `management-four-boards`: G.P.'s scheme of ОРУ (gates Ш13 В, Ш15 В): `od` and the upper system `ot` on top, the apparatus `ap` and the managed polysystem `us` below (`screen: regions`); its kinds, relations and hints are in `docs/profiles.md`, The management profile.
|
|
269
|
+
- `management-four-boards`: G.P.'s scheme of ОРУ (gates Ш13 В, Ш15 В): `od` and the upper system `ot` on top, the apparatus `ap` and the managed polysystem `us` below (`screen: regions`), with a layer from Beer's viable system model (gate Бир3 В); its kinds, relations and hints are in `docs/profiles.md`, The management profile. Examples: `cases/example_ru/pekarni-oru-c1.board.yaml`; for the Beer layer, `cases/example_ru/pekarnya-holding-c1.board.yaml`.
|
|
262
270
|
|
|
263
271
|
The file format, the layout of boards by their regions and the checks of a profile file are in `docs/profiles.md`. Two sets of ids are fixed by the engine:
|
|
264
272
|
- **Kinds every profile defines:** `position`, `place_for_others`, `function`, `cooperation`, `gap`, `note`; also `entry` when the profile enables the hint `entry`, and `goal` when it enables `goal-without-breakdown`. The checks, the frames switches and the fold counter name these ids; other meanings come from kind attributes (`shape: frame`, `light_off`, `stance`, `factual`) and the board flag `object`. No board id is fixed; `records` and `sources` are refused (layers of `smd graph`).
|
|
@@ -274,20 +282,4 @@ From 0.2 to 0.3: `schema_version` becomes `"0.3"`; an element `voice` outside th
|
|
|
274
282
|
|
|
275
283
|
## Checks
|
|
276
284
|
|
|
277
|
-
The checks
|
|
278
|
-
- **Errors:** duplicate ids; `fillers` on an element that is not a role; a `detail` row whose length differs from `columns`; dangling references in `seen_from`, `in`, relations, transitions, qualification targets, move sources and thesis `feeds`; `seen_from` or `reflected_from` that is not a position; `half` rules; containment cycles; transition numbering; a closed K without `closed_in`; a K raised after the record's cycle; a record revising itself; `verified` without a checker; unknown source ids when a manifest is given.
|
|
279
|
-
- **Errors (ingestion):** `of` on an element that is not a gap; `performed_by` on a non-function or not naming a position or place for others; a thesis that `raises` an unknown K; a hypothesis result without its text, field artefact or `resolved_in`; dangling hypothesis targets or K; a thesis status that does not fit its voice; an accepted move from an AI voice with no `accept_move` sign-off; a sign-off by an AI voice, without a target, or aimed at the wrong kind of target.
|
|
280
|
-
- **Warnings:** a screen label (`short`, or `label` when there is no `short`) over 60 characters, which the screen cuts; a kind off its usual board; a content item without a position; a transition inside one board; a `shift` between non-positions; a manifest entry with no file or url, or no clean-room decision.
|
|
281
|
-
- **Warnings (ingestion):** a revising cycle with no `reflected_from`; a thesis with no source address (except AI voice); an accepted move with neither a source nor a sign-off; a closed K, a `refined` thesis, a hypothesis result or a `verified` record with no matching sign-off; a hypothesis `testing` with no action; a sign-off that changes nothing, because its target is not in the state it licenses (only the latest K or move sign-off on a target is checked: `reopen_k` supersedes an earlier `close_k`).
|
|
282
|
-
- **Hints** (Girenko's criteria for a group screen, 17.10.2026): no entry; an empty board, or an empty half of a halved board (the program's small or big situation not laid out); one position and no places for others; a new frame without functions or with functions no one performs; open gaps; open qualifications; candidate moves, on elements and theses; AI variants awaiting the group.
|
|
283
|
-
- **Warnings (step 3):** subject-object talk ("we must", "our task", "мы должны", "наша задача") in a label on a board the profile flags `object` (the object board); `represents` not starting from a position; an ontology subject for a position outside `valid_for`.
|
|
284
|
-
- **Errors (step 3):** ontology `valid_for` that is not a position, `cooperation` that is not a cooperation element, `test` that is not a hypothesis.
|
|
285
|
-
- **Hints (classic method):** an ontology with no realizability test, or valid for several positions with no cooperation; a gap or a problem thesis with no scheme block; a new cycle with no `difficulty`; a hypothesis with no `revise_if`; degenerate belts (GP1987): mostly М-К theses and none in М ("play with words"), or М theses with none in мД (thinking cut off from the situation).
|
|
286
|
-
- **Errors (G.P.'s «Программа действий»):** `stance` or `acts_as` on an element that is not a position, `goal_source`, `arises_from` or `assigned_by` on one that is not a goal, `nature` off an object board; an `arises_from` id that is neither a gap, a fact, nor a `difficulty`, `problem` or factual thesis; `assigned_by` that is not a position or place for others.
|
|
287
|
-
- **Warnings (G.P.'s «Программа действий»):** `reflected_from` naming a position with `stance: inside`.
|
|
288
|
-
- **Hints (G.P.'s «Программа действий», GP-Guide11, read against GP-T5):** an object-board element seen from a position with `stance: inside` (`object-from-inside`, ¶36); a new cycle whose object board is seen from an `external` position with no `reflected_from` (`external-without-reflection`, ¶35, ¶47); a goal with no breakdown: no `goal_source`, `arises_from`, gap linked by a relation, `difficulty` or `problem` thesis naming it, or `state.difficulty` (`goal-without-breakdown`, ¶43; also an `assigned` goal with no `assigned_by` and a `breakdown` goal with no `arises_from`); a position with `acts_as` (not `functionary`) and no `represents` relation (`position-without-object`, GP-Guide10 ¶7, ¶19); an object-board element with `modality: ought` and no fact linked by a relation, `in`, or a factual thesis (`ought-without-fact`, GP-T5 p. 252); `ought` on a `natural` element (`design-the-natural`, GP-STS); theses, other than `open`, with neither `feeds` nor `about` (`information-without-cell`, ¶5). Where the 1981 and 1988 texts disagree the 1988 lectures win: GP-Guide5 ¶7 required a forecast ("Управлять без прогноза в принципе невозможно"); GP-T5 p. 251 calls forecasting in оргуправление a substitution by scientistic principles, so `ought-without-fact` asks for the natural processes, not a forecast.
|
|
289
|
-
- **Hints (G.P.'s management scheme, `management-four-boards`, GP-T5):** a `leads` relation to someone with goals `goal_source: own` (seen from the target or from a position that `belongs` to it) (`lead-vs-manage`, pp. 169-170); a `manages` relation with no element the source `produces` and the target `uses` (`manage-via-organizedness`, pp. 222-223); a position that `manages` with no retrospective or no projective knowledge seen from it or linked to it (`manage-without-knowledge`, p. 241); a `leads` relation whose ends hold no post (itself, or one it `belongs` to), or with no line of `subordinates` from the leader's post down to the other (`leads-outside-organisation`, pp. 242, 254); a `represents` target outside the kinds expected for the position's `acts_as`: organiser to `post`, `functional_place`, `mission`, `monosystem`; leader to `post` (not `group`: the informal group is outside the administrative structure, pp. 224-225, 254); manager to `work_process`, `trajectory`, `self_motion`; politician to `club`, `position`; functionary to none (`representation-fit`; the table is the engine's reading of GP-T5 pp. 170-175, 213, 223, 242-244, 253-254, not a table of G.P.'s); an upper board with content but no past of the object (a `factual` kind, `knowledge_retro`, or `modality: fact` on the managed board), no `ideal_state`, or no `captures` from the upper board to the managed one (`development-step`, «шаг развития», «минимальная единица», pp. 229, 232, 238); a managed board with fewer than two monosystems, or monosystems with no `parasitic`, `symbiotic` or `mechanism_of` relation (`polysystem`, pp. 206-213).
|
|
290
|
-
- **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 not a 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'").
|
|
291
|
-
- **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.
|
|
292
|
-
- **Warnings (v0.3):** `tags` or `detail.keys` used and no taxonomy file given.
|
|
293
|
-
- **Across cycles:** when the revised record is among the files validated, a new cycle with no new or changed frame, function, model, concept, standard or cooperation gets the hint "reflection without a new scheme". A cycle run by `ingest-transcript` or `theses-to-board` whose new theses feed only elements the previous cycle did not have gets `cells-from-information`: the cells were drawn from the information, not before it (GP-Guide11 ¶5).
|
|
285
|
+
The checks the validator runs on these records (errors, warnings and hints, and which profile enables each hint) are in `docs/checks.md`.
|
|
@@ -13,6 +13,6 @@ The method from external primary sources, so that the engine does not rest on on
|
|
|
13
13
|
| `roles-and-actors.md` | boards hold roles; actors that can occupy them go in `fillers`; stakeholder as the term; a role with structure keeps a `detail` table (adopted 27.10.2026) |
|
|
14
14
|
| `structural-moves.md` | the preprint behind the `move` field: the four operations, the selection functional, its limits and the running demonstration |
|
|
15
15
|
|
|
16
|
-
Sources: the main texts are from G.P. Shchedrovitsky's *Избранные труды* (1995) and *Философия. Наука. Методология* (1997), read on gtmarket.ru, and Altshuller's texts on altshuller.ru.
|
|
16
|
+
Sources: the main texts are from G.P. Shchedrovitsky's *Избранные труды* (1995) and *Философия. Наука. Методология* (1997), read on gtmarket.ru, and Altshuller's texts on altshuller.ru. Stafford Beer's «Мозг фирмы» (BEER1972, read on gtmarket.ru) is the source of the Beer layer of the management profile (`docs/profiles.md`).
|
|
17
17
|
|
|
18
18
|
fondgp.ru refused automated access, and Blauberg, Sadovsky and Yudin could not be read; claims that depend on them are marked unverified. Three quotations were re-checked against the downloaded texts.
|
|
@@ -54,6 +54,7 @@ Access note: fondgp.ru returned HTTP 403 to the fetch tool and 404 for `/lib/mmk
|
|
|
54
54
|
| BSY1977 | Blauberg I.V., Sadovsky V.N., Yudin E.G. Systems Theory: Philosophical and Methodological Problems. Moscow: Progress, 1977 [S: library catalogues] | https://search.ub.tum.de/vufind/Record/DE-604.BV025107489 |
|
|
55
55
|
| BY1973 | Блауберг И.В., Юдин Э.Г. Становление и сущность системного подхода. М.: Наука, 1973 [S: НЭБ catalogue] | https://rusneb.ru/catalog/010003_000061_5af8ed87d829815e25f2eb27fafda447/ |
|
|
56
56
|
| ILE2013 | Ilevbare I.M., Probert D., Phaal R. A review of TRIZ, and its benefits and challenges in practice // Technovation 33 (2013) [S: abstracts only] | (not fetched) |
|
|
57
|
+
| BEER1972 | Бир С. Мозг фирмы / пер. с англ. М. М. Лопухин. М., 1993 (Stafford Beer, Brain of the Firm, 1972; translated from the second edition, which adds Part IV on Chile, chapters 16-20); electronic publication: Центр гуманитарных технологий, 18.03.2013. Cited by chapter, «Гл. N», and «Приложение» for the glossary. The source of the Beer layer of `management-four-boards` (gate Бир3 В) and of the lens `beer-viable-system`. The book has no System 3\* | https://gtmarket.ru/library/basis/5789 |
|
|
57
58
|
| CHK | Checkland P. Systems Thinking, Systems Practice (1981); Smyth D., Checkland P. (1976) root definitions; Checkland P., Poulter J. Learning for Action (2006) [S: secondary summaries only] | https://cci.drexel.edu/faculty/sgasson/SSM/Stage3b.html |
|
|
58
59
|
|
|
59
60
|
---
|
|
@@ -13,7 +13,7 @@ Profiles are files in `profiles/` of the install: the repository folder in a che
|
|
|
13
13
|
| `id`, `title` | the file name; `{ru, en}` |
|
|
14
14
|
| `screen` | `regions` (default) or `triangles`; see Screen and layout |
|
|
15
15
|
| `boards` | a board template among them: see Board templates. Otherwise in screen order: `id`, `label: {ru, en}`, `halves` (`[small, big]`, one of them, or `none`; each half at most once), `region: [x0, y0, x1, y1]` (screen units, width 1600), `colour: [background, ink]` (`#rrggbb`), `split` (only for a board with two halves: the x where they meet; the middle of the region by default), `object` (`true`: a board of objects, where subject-object talk is warned) |
|
|
16
|
-
| `kinds` | in layout order: `id`, `label: {ru, en}` (plural, for counters and tables), `home` (the board it usually lies on, a warning otherwise; or a template, see Board templates), `shape`, and the flags `needs_position`, `container`, `role` (takes `fillers`), `scheme` (counts for "reflection without a new scheme"), `skeleton` (kept by the folded overview; listed by `smd pack` as the cells a reading fills), `light_off` (left off the lighter screen, `--light`), `stance` (takes the element field `stance`: the positions, GP-Guide11 ¶35), `factual` (records a fact: a breakdown a goal may arise from, and the fact the hint `ought-without-fact` looks for). Flags left out are false |
|
|
16
|
+
| `kinds` | in layout order: `id`, `label: {ru, en}` (plural, for counters and tables), `home` (the board it usually lies on, a warning otherwise; or a template, see Board templates), `shape`, and the flags `needs_position`, `container`, `role` (takes `fillers`), `scheme` (counts for "reflection without a new scheme"), `skeleton` (kept by the folded overview; listed by `smd pack` as the cells a reading fills), `light_off` (left off the lighter screen, `--light`), `stance` (takes the element field `stance`: the positions, GP-Guide11 ¶35), `factual` (records a fact: a breakdown a goal may arise from, and the fact the hint `ought-without-fact` looks for), `vsm` (takes the element field `vsm_system`: Beer's systems 1-5, BEER1972). Flags left out are false |
|
|
17
17
|
| `relations` | relation kinds, each once, in order: an id of the engine's own (`shift`, `flow`, `produces`, `uses`, `belongs`, `opposes`, `refers`, `represents`, `other`), or a mapping `{id, label: {ru, en}}` for any other kind (an engine id takes no label). `smd graph` and `smd vault` name and filter links by these labels; a kind the engine does not colour is drawn grey |
|
|
18
18
|
| `hints` | ids of the hints enabled, each once, among the hints the engine has (`src/smd_engine/validate/hints.py`, `src/smd_engine/validate/management.py`). `situation-halves` reports an empty half as "small situation not laid out" or "big situation not laid out", the method's names for the halves, so a profile that halves a board without situations leaves it off |
|
|
19
19
|
| `compare_groups` | name to kinds matched against each other by `smd compare`; a kind in no group is matched in `other` |
|
|
@@ -67,7 +67,7 @@ The engine names a few kinds by id; the parser refuses a profile without them ("
|
|
|
67
67
|
| `goal` | only when the profile enables the hint `goal-without-breakdown`; takes `goal_source`, `arises_from` and `assigned_by` |
|
|
68
68
|
| others | a hint of one profile's scheme (`src/smd_engine/validate/management.py`) registers the kinds and relation kinds it names; a profile that enables it must define them ("missing kinds the engine names", "missing relation kinds the hints name") |
|
|
69
69
|
|
|
70
|
-
Other meanings come from attributes, so a profile can name these kinds as it likes: a kind drawn as `frame` takes `frame_state`, holds function chips, is found by the `old-frames` and `new-frames` picks and by the hint on new frames; `heading` draws the bold paragraph; `light_off` kinds leave the lighter screen; `stance` kinds take the field `stance`, and `factual` kinds count as facts for `arises_from` and `ought-without-fact`; a board flagged `object` gets the subject-object warning, which names the home boards of the `role` kinds as the place for such talk. No board id is fixed, but `records` and `sources` are refused for any board, template or record board: they are the layers `smd graph` draws above and below the board planes. The halves are `small` and `big` (the schema's enum for `half`).
|
|
70
|
+
Other meanings come from attributes, so a profile can name these kinds as it likes: a kind drawn as `frame` takes `frame_state`, holds function chips, is found by the `old-frames` and `new-frames` picks and by the hint on new frames; `heading` draws the bold paragraph; `light_off` kinds leave the lighter screen; `stance` kinds take the field `stance`, `vsm` kinds the field `vsm_system`, and `factual` kinds count as facts for `arises_from` and `ought-without-fact`; a board flagged `object` gets the subject-object warning, which names the home boards of the `role` kinds as the place for such talk. No board id is fixed, but `records` and `sources` are refused for any board, template or record board: they are the layers `smd graph` draws above and below the board planes. The halves are `small` and `big` (the schema's enum for `half`).
|
|
71
71
|
|
|
72
72
|
## The management profile
|
|
73
73
|
|
|
@@ -83,7 +83,21 @@ Other meanings come from attributes, so a profile can name these kinds as it lik
|
|
|
83
83
|
|
|
84
84
|
Relations: the engine's, plus `organises`, `leads`, `manages` (pp. 169-175, 241-244), `subordinates` (from the superior place to the subordinate one, pp. 169, 242), `personal` (pp. 166, 224-225), `captures` («захват», pp. 226-227, 236), `knows` (retrospective and projective knowledge of the lower system, p. 241; not «отражение», which p. 181 drops), `contends` (politics: rival systems of ОРУ in a struggle for the capture of the object, an activity built over управление, pp. 225-229, 253), and between monosystems `parasitic`, `symbiotic`, `mechanism_of` (p. 208). A position fills a post by `belongs`.
|
|
85
85
|
|
|
86
|
-
Hints: the classic set and those of gates Ш8-Ш12, plus the hints of this scheme (`docs/
|
|
86
|
+
Hints: the classic set and those of gates Ш8-Ш12, plus the hints of this scheme (`docs/checks.md`). There is no `forecast` kind and no hint on management without a forecast: GP-Guide5 ¶7 (1981) has «Управлять без прогноза в принципе невозможно», but GP-T5 p. 251 calls forecasting in оргуправление a substitution by scientistic principles. «Управлять вообще можно только развитием» is G.P.'s own «очень смелая гипотеза» (p. 174); the profile states it here as a hypothesis and checks nothing by it.
|
|
87
|
+
|
|
88
|
+
**Beer layer** (gate Бир3 В). Items from Stafford Beer, «Мозг фирмы» (1972; М., 1993; BEER1972 in `docs/method/sources.md`), marked "Beer layer" in the profile file with the chapter each rests on. Beer's viable system model is a model source for the profile, not a reading of G.P.; the profile carries both and does not merge them. The book has no System 3\*, so there is no kind for it. Example: `cases/example_ru/pekarnya-holding-c1.board.yaml`, an owner-run bakery sold to a holding.
|
|
89
|
+
|
|
90
|
+
| Item | What it is | Beer |
|
|
91
|
+
|---|---|---|
|
|
92
|
+
| flag `vsm` on `position` and `post`; field `vsm_system` | the systems 1-5 a position or place fills, a list | Гл. 9-15; one person can be the firm, Гл. 9 |
|
|
93
|
+
| kind `algedonic_channel` on `ot`, fields `threshold`, `recovery_time` (days) | an alarm path that bypasses the filters; a stakeholder's red line is recorded as one | Гл. 17 |
|
|
94
|
+
| relation `escalates` | from an algedonic channel to the place that must act once the recovery time has run out | Гл. 17 |
|
|
95
|
+
| relation `filters` | what a place passes up to the place above | Гл. 7 |
|
|
96
|
+
| hint `single-node-metasystem` | one filler fills systems 3, 4 and 5: the transfer will remove the metasystem with the person | Гл. 9, 13 |
|
|
97
|
+
| hint `line-without-recovery` | a red line with a threshold and no recovery time or no escalation address | Гл. 17 |
|
|
98
|
+
| hint `absorbed-into-system-1` | a place filling system 5 captures (`captures`) systems 4 and 5 of the business: it becomes part of the buyer's system 1, its name and identity at risk | Гл. 15 |
|
|
99
|
+
|
|
100
|
+
The lens `beer-viable-system` asks the questions whose answers fill these items.
|
|
87
101
|
|
|
88
102
|
G.P. asks that each working process be idealised «на отдельной доске» (GP-T5 p. 245). The template `process` gives each record as many process boards as it has working processes, each a board of its own below the four, labelled «Доска процесса: <label>», naming the `work_process` it `unfolds` and the position it is seen from; its functions lie on it. The reading step `process` follows `upper`, once per process board.
|
|
89
103
|
|
|
@@ -23,6 +23,7 @@ Plan approved 2026-10-25 (`docs/plan.md`). Each step is a branch and a PR. The s
|
|
|
23
23
|
| Ш8-Ш12 | Gates Ш8-Ш12 (G.P.'s «Программа действий» against т. 5): element fields, hints, the three-positions lens | done in v0.3.8 |
|
|
24
24
|
| Ш13 | G.P.'s management scheme as the profile `management-four-boards` | done in v0.4.0 |
|
|
25
25
|
| boards | Record boards from profile templates; process boards on their own boards in the management profile | done in v0.5.0 |
|
|
26
|
+
| Бир3 | Beer layer of the management profile (Beer, «Мозг фирмы»): `vsm_system`, `algedonic_channel`, `escalates`, `filters`, three hints, the lens `beer-viable-system`, the example `pekarnya-holding-c1` | done in v0.5.4 |
|
|
26
27
|
|
|
27
28
|
## Structural moves (Invention as a Structural Operation)
|
|
28
29
|
|
|
@@ -11,7 +11,7 @@ One Markdown file per lens, `lenses/<id>.md`. The checks are in `tests/test_lens
|
|
|
11
11
|
| `id` | the file name without `.md`, lowercase-hyphen; the value of `lens:` on elements and theses |
|
|
12
12
|
| `title` | one line |
|
|
13
13
|
| `version` | semver; bump on any change of the questions or the output slots |
|
|
14
|
-
| `source` | who and where: lecture or slides, or the primary-text keys of `docs/method/sources.md
|
|
14
|
+
| `source` | who and where: lecture or slides, or the primary-text keys of `docs/method/sources.md`; a list when the lens has more than one source |
|
|
15
15
|
| `route` | `smd`, `triz` or `both`: the way of thinking the lens belongs to (`docs/method/reconciliation.md` section 8) |
|
|
16
16
|
| `offered_by` | procedure ids that offer the lens; must agree with the selection table below |
|
|
17
17
|
|
|
@@ -37,8 +37,8 @@ Elements, theses, hypotheses and ontology records carry `lens: <id>`; `smd compa
|
|
|
37
37
|
|
|
38
38
|
| Lens | Route | Source | What it asks |
|
|
39
39
|
|---|---|---|---|
|
|
40
|
-
| `khaprov-levels` | smd | Khaprov, lecture | at which of seven levels of management complexity a problem is decided; the three kinds of complexity |
|
|
41
|
-
| `khaprov-ontology` | smd | Khaprov, lecture; GP1981 | three scales; the ontology test; managing not-knowing |
|
|
40
|
+
| `khaprov-levels` | smd | Khaprov, lecture | at which of seven levels of management complexity a problem is decided; the three kinds of complexity; the diagonal of the levels and the six tiers of a business, and their paces (AI draft) |
|
|
41
|
+
| `khaprov-ontology` | smd | Khaprov, lecture and podcast; GP1981 | three scales; the ontology test; managing not-knowing; the space-time continuum: what the system fits into, its tempos and horizon, objects bought into an old picture, a platform's layer |
|
|
42
42
|
| `schukin-boundaries` | smd | Schukin, written talk | five grounds of a cut between functions; four families of change; capability probes |
|
|
43
43
|
| `schukin-interface-tax` | smd | Schukin, written talk | the function of each human touchpoint; achievement and balancing metrics; the engine's own sign-offs |
|
|
44
44
|
| `fliamer-diamond` | smd | Fliamer, module-1 slides | complexes of the big situation: functions, products, consumption, new technical solutions |
|
|
@@ -46,6 +46,7 @@ Elements, theses, hypotheses and ontology records carry `lens: <id>`; `smd compa
|
|
|
46
46
|
| `triz-contradictions` | triz | ARIZ-85V, Altshuller | a contradiction inside one object: zone, time, resources, ideal result, separation |
|
|
47
47
|
| `scamper-check` | smd | Eberle, Osborn; Zharnikov | a cross-check of the four structural moves after the tract |
|
|
48
48
|
| `three-positions` | smd | G.P., «Программа действий» (GP-Guide11); т. 5 | from where a scheme is drawn: inside, reflexive, external; which structures stay conditions |
|
|
49
|
+
| `beer-viable-system` | smd | Beer, «Мозг фирмы» (BEER1972) | which of systems 1-5 the owner fills; where the model of the firm is; recovery time and escalation address of each red line; the business's recursion level after a transfer; organisation versus structure |
|
|
49
50
|
|
|
50
51
|
## Selection table
|
|
51
52
|
|
|
@@ -60,19 +61,22 @@ Rows are procedure and step. "Q" is the question number in the lens file. Where
|
|
|
60
61
|
| `visionary-tract` | 5 View of oneself (rescale) | `khaprov-ontology` | Q1-Q4 | The three scales are the grain options of the move |
|
|
61
62
|
| `visionary-tract` | after 6, before the hand-over | `scamper-check` | all | Looks for candidates the four-move pass missed |
|
|
62
63
|
| `visionary-tract` | 10 Hand over | `schukin-interface-tax` | Q11 | As above |
|
|
63
|
-
| `positional-construction` | 2 Positional set | `khaprov-levels` | Q1-Q3, Q10 | Asks whether a position acts at the level its task needs, and whether the missing one is a gap or missing knowledge |
|
|
64
|
+
| `positional-construction` | 2 Positional set | `khaprov-levels` | Q1-Q3, Q10-Q12 | Asks whether a position acts at the level its task needs, and whether the missing one is a gap or missing knowledge; on the diagonal (AI draft), whether a tier's change is decided at its level |
|
|
64
65
|
| `positional-construction` | 2 Positional set, 4 Representations | `three-positions` | Q1, Q2, Q5, Q6 | A position that draws the structure it works inside draws a condition, not an object (GP-Guide11 ¶36); `stance` on the positions |
|
|
66
|
+
| `positional-construction` | 2 Positional set | `beer-viable-system` | Q1, Q7 | On `management-four-boards`: which of Beer's systems 1-5 each post and position fills (`vsm_system`), and where system 5 really sits |
|
|
65
67
|
| `positional-construction` | 3 The construction | `design-chain` | Q1-Q5, Q9 | The `flow` relations label what passes, from whom, to whom; the chain asks what stays behind |
|
|
66
|
-
| `positional-construction` | 5 One common object | `khaprov-ontology` | Q5-Q11 | The ontology record's `subjects`, `valid_for`, `competes`, `cooperation` and `test` |
|
|
68
|
+
| `positional-construction` | 5 One common object | `khaprov-ontology` | Q5-Q11, Q16-Q21 | The ontology record's `subjects`, `valid_for`, `competes`, `cooperation` and `test`; when the picture is to hold for a period, `lives_in`, `tempos`, `horizon` and `covers` |
|
|
69
|
+
| `positional-construction` | 5 One common object | `beer-viable-system` | Q4, Q5 | On `management-four-boards`, in a case of transfer: does the business stay a viable system of its own or become part of the buyer's system 1; organisation versus structure |
|
|
67
70
|
| `functional-plan` | 2 Draft the chain, 5 Align | `fliamer-diamond` | Q3-Q5 | Functions in a chain, products, consumers; material on how the chain is arranged elsewhere |
|
|
68
71
|
| `functional-plan` | 3 Performs, pays, receives | `design-chain` | Q6, Q9 | Instruments with performer and payer; empty links of the chain |
|
|
69
72
|
| `functional-plan` | 4 Empty places | `khaprov-levels` | Q2, Q3 | A function with no performer: is the performer missing at a higher or lower level, or is knowledge missing |
|
|
73
|
+
| `functional-plan` | 4 Empty places | `beer-viable-system` | Q2, Q3, Q6 | On `management-four-boards`: who keeps the model of the firm, the recovery time and escalation address of each red line, what each place passes up |
|
|
70
74
|
| `functional-plan` | 6 Candidate moves | `schukin-boundaries` | Q1-Q8, Q14 optional | The four families and five grounds the procedure already names; grounds for `respecify` |
|
|
71
75
|
| `functional-plan` | 6, after the line above | `schukin-interface-tax` | Q1-Q10 | The human touchpoints that remain after a merge or shared state |
|
|
72
76
|
| `functional-plan` | 6 | `triz-contradictions` | Q0 first | Only when one function carries two opposed demands; Q0 sends a paradox between positions back to the SMD route |
|
|
73
77
|
| `functional-plan` | 7 Hypotheses | `schukin-boundaries` | Q9-Q13 | Capability probes are ready-made hypotheses `assumes`, `action`, `observe`, `revise_if` |
|
|
74
78
|
| `functional-plan` | 9 Hand over | `schukin-interface-tax` | Q11 | As above |
|
|
75
|
-
| `problematization` | 2 Sort what is on the table | `khaprov-ontology` | Q12-Q14 | A difficulty may be a wrongly posed problem; output is a thesis |
|
|
79
|
+
| `problematization` | 2 Sort what is on the table | `khaprov-ontology` | Q12-Q14, Q18 | A difficulty may be a wrongly posed problem, or objects rearranged where the continuum must change; output is a thesis |
|
|
76
80
|
| `problematization` | 6 Pointer to the other route | `triz-contradictions` | all | The procedure flags a contradiction inside the object and writes no TRIZ terms; the lens is a separate pass |
|
|
77
81
|
| `qualification-pass` | 3.1 C7, 3.3 realizability | `khaprov-ontology` | Q1-Q4, Q9-Q11 | Questions only: the scale and the stated reason; the test and the cooperation. No elements |
|
|
78
82
|
| `qualification-pass` | 6 Hand over | `schukin-interface-tax` | Q11 | As above |
|
|
@@ -0,0 +1,67 @@
|
|
|
1
|
+
---
|
|
2
|
+
id: beer-viable-system
|
|
3
|
+
title: Beer's viable system at a transfer of ownership, systems 1-5, red lines and recursion
|
|
4
|
+
version: 0.1.0
|
|
5
|
+
source: "Stafford Beer, «Мозг фирмы» (Brain of the Firm, 1972; translated from the second edition, with Part IV on Chile, by М. М. Лопухин, М., 1993), read on gtmarket.ru, https://gtmarket.ru/library/basis/5789 (BEER1972 in docs/method/sources.md); cited by chapter, «Гл. N», and «Приложение» for the glossary"
|
|
6
|
+
route: smd
|
|
7
|
+
offered_by: [positional-construction, functional-plan]
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
# Beer: viable system, red lines, recursion
|
|
11
|
+
|
|
12
|
+
A lens that reads a business about to change owner as Beer's viable system. It asks who fills systems 1-5 today, where the model of the firm is kept, what each red line does when it is crossed, and whether the business keeps its own metasystem after the transfer or becomes part of the buyer's system 1. The lens gives no answers. It gives the human questions whose answers fill the Beer layer of the profile `management-four-boards` (`docs/profiles.md`, The management profile).
|
|
13
|
+
|
|
14
|
+
Marks: **[V]** read in the book, quoted verbatim from the Russian translation (italic markers dropped); **[ANALYSIS]** the engine's reading, not a claim of the source.
|
|
15
|
+
|
|
16
|
+
## When to use
|
|
17
|
+
|
|
18
|
+
- In `positional-construction`, section 2 (the positional set), when the record follows `management-four-boards` and the case is a transfer of ownership or management: questions 1 and 7. Section 5 (one common object): questions 4 and 5.
|
|
19
|
+
- In `functional-plan`, section 4 (empty places become gaps): questions 2, 3 and 6.
|
|
20
|
+
- On another profile the fields `vsm_system`, `threshold` and `recovery_time`, the kind `algedonic_channel` and the relations `escalates` and `filters` do not exist: the answers go into theses (`kind: statement` or `problem`) and `note` elements, and the text names the lens id.
|
|
21
|
+
- Not as an organisation chart. Beer's systems are functions of control, and the metasystem is a logical level, «но не обязательно высший уровень иерархии в смысле командования» [V Приложение].
|
|
22
|
+
- Not as a theory of succession. Beer never discusses succession; his takeover passage (Гл. 15) is about loss of viability [ANALYSIS].
|
|
23
|
+
|
|
24
|
+
## What the source gives
|
|
25
|
+
|
|
26
|
+
- **Five systems** [V Гл. 9-15]. System 1: the autonomous operating units, each viable itself. System 2: damping of oscillation between units, mostly «либо совершенно не официальные, либо в основном непризнанные организации» (Гл. 12). System 3: internal stability now and the allocation of resources; it «является естественным управляющим во время сна или при отсутствии управления» (Гл. 10). System 4: the outside and the future, with a model of the firm: «Если бы такой модели не было, то высшее руководство не имело бы представления о том, какой фирмой оно управляет» (Гл. 13). System 5: policy and identity, a group of decision elements (multinode) whose members may hold no post: they «не занимают никакого официального положения в фирменной иерархии» (Гл. 14).
|
|
27
|
+
- **One person can be the firm** [V Гл. 9]: «Если один человек — это фирма, то он использует свою нервную систему, чтобы управлять такой фирмой».
|
|
28
|
+
- **Structure follows the person** [V Гл. 6]: «Реальные структурные схемы фирм сильно зависят от того, кто именно занимает ведущие посты, и когда такой человек уходит, часто приходится менять структуру».
|
|
29
|
+
- **Where system 5 is** [V Гл. 15]: «командный центр меняет своё местоположение от времени до времени».
|
|
30
|
+
- **Filters and the algedonic channel** [V Гл. 7, 17]. A filter is «фильтр как устройство для уменьшения разнообразия, сводящее многое к одному» (Гл. 7). A unit that cannot restore its index «в приемлемое время» sends an algedonic signal up a level; the time is set with the people of that level: «указать физиологически приемлемое время восстановления (приведения в норму) каждого индекса» (Гл. 17). When every level does its work, «алгедонический сигнал станет редкостью» (Гл. 17).
|
|
31
|
+
- **Recursion** [V Гл. 15]: «Если жизнеспособная система содержит в себе жизнеспособную систему, тогда их организационные структуры должны быть рекурсивны».
|
|
32
|
+
- **Death of a viable system and takeover** [V Гл. 15]: «Когда жизнеспособная система погибает, её физическое существование продолжается как наблюдаемое взаимодействие со смежными системами. Но она теряет свои отличительные признаки, а именно её связи как жизнеспособной системы.» Of the board of a firm taken over by a larger one: «Оно должно перестать быть директоратом и становится группой управления. Короче говоря, фирма становится одним из подразделений нового целого — частью системы 1.» The old name «через несколько лет исчезает совсем».
|
|
33
|
+
- **Organisation and structure** (Maturana, quoted by Beer) [V Гл. 19]: «Если организация системы изменится, то изменится и её индивидуальность»; «если организация системы останется инвариантной к изменению её структуры, то система останется той же и её индивидуальность сохранится».
|
|
34
|
+
- **No System 3\*.** The audit channel known as System 3\* is not in this book; the nearest is the inspection channel of system 3 (Гл. 12). The lens and the profile have no kind for it [V, by search of the text].
|
|
35
|
+
|
|
36
|
+
## Questions
|
|
37
|
+
|
|
38
|
+
1. **Systems 1-5.** Which of systems 1-5 does the owner fill, and which do other posts and positions fill? Where one person fills several, list them all. Is system 5 one person, or a group in which someone holds no post?
|
|
39
|
+
2. **Model of the firm.** Where is the system 4 model of the business (its environment, its model of itself, the plan as continuous revision)? In one head, spread over several people, or written down? Who will keep it after the transfer?
|
|
40
|
+
3. **Red lines.** For each red line: what is the index and its threshold, how long may the unit take to bring it back (recovery time), and which place must act when that time has run out (escalation address)? Who set the time?
|
|
41
|
+
4. **Recursion after the transfer.** After the transfer, will the business keep its own systems 1-5, or a system 4 and 5 that the buyer deliberately leaves to it, or will the buyer's system 5 take its 4 and 5, so that it becomes part of the buyer's system 1 (Гл. 15)?
|
|
42
|
+
5. **Organisation and structure.** Which relations make the business this business (its organisation, Гл. 19), and which parts can change without changing it (its structure: people, tools, places)? Does each red line guard the organisation? What is left is the free zone of the new owner.
|
|
43
|
+
6. **Filters.** What does each place pass up, and what does it hold back? Which signals must bypass the filters?
|
|
44
|
+
7. **Real system 5.** Where were the last decisions on the purpose and survival of the business made, and by whom? Is that the owner, or another group (Гл. 15)?
|
|
45
|
+
|
|
46
|
+
## Output slots
|
|
47
|
+
|
|
48
|
+
Every element and thesis carries `lens: beer-viable-system`. Kinds, fields and relations are those of `management-four-boards` (`docs/data-model.md`, `docs/profiles.md`). Wording the model writes is `voice: ai`, `epistemic: hypothesis`.
|
|
49
|
+
|
|
50
|
+
| Answer | Kind, board, field |
|
|
51
|
+
|---|---|
|
|
52
|
+
| Systems a place or position fills (Q1, Q7) | `vsm_system: [n, ...]` on the `post` (`ap`) or `position` (`od`); the people in `fillers`, or a position that `belongs` to the post. The hint `single-node-metasystem` names one filler of systems 3, 4 and 5 |
|
|
53
|
+
| System 5 as a group (Q1, Q7) | one `post` with several `fillers` and `vsm_system: [5]`; a member with no post is a `position` that `belongs` to it |
|
|
54
|
+
| The model of the firm (Q2) | `model` on `ot`, `seen_from` the position that keeps it; if nobody will keep it after the transfer, `gap` on `od` with `of: position` |
|
|
55
|
+
| A red line (Q3) | `algedonic_channel` on `ot` with `threshold` (text), `recovery_time` (days) and `seen_from`; a relation `escalates` from it to the `post`, `position` or `place_for_others` that must act. The hint `line-without-recovery` names a line with a threshold and no recovery time or no address |
|
|
56
|
+
| The buyer and the transfer scenario (Q4) | the buyer's `post` on `ap` with its `vsm_system`; a relation `captures` from it to each place of the business it takes. The hint `absorbed-into-system-1` fires when a place filling system 5 captures systems 4 and 5 of the business |
|
|
57
|
+
| Organisation and structure (Q5) | thesis `kind: statement`, `belt: m`, `about` the red lines (algedonic channels) it reads; what a line guards in the channel's `label` |
|
|
58
|
+
| What a place passes up (Q6) | relation `filters` from the lower place to the place above, its `label` saying what passes |
|
|
59
|
+
| The informal links of system 2 (Q1, Q6) | `group` on `ap` with a `personal` relation to the post it coordinates |
|
|
60
|
+
|
|
61
|
+
## Limits
|
|
62
|
+
|
|
63
|
+
- Beer's model is cybernetic regulation of a viable system toward survival; G.P.'s scheme of ОРУ is an activity that captures its object from a reflexive position. The profile carries both, with Beer's items labelled as a layer; it does not reconcile them [ANALYSIS].
|
|
64
|
+
- The checks are the engine's reading of Beer: the book gives no rule that 3, 4 and 5 in one person is a risk, no field for recovery time, and no test of absorption. The thresholds of the checks (3-4-5 in one filler; system 5 taking 4 and 5) are the engine's [ANALYSIS].
|
|
65
|
+
- `recovery_time` is in days. Beer gives no unit; Cybersyn read indices daily (Гл. 16-17) [ANALYSIS].
|
|
66
|
+
- A scenario of the transfer has no record of its own: it is laid out on the boards as the buyer's post and its `captures` relations. Two scenarios are two records, or two cycles [ANALYSIS].
|
|
67
|
+
- The book's figures on the multinode (Гл. 14) rest on Beer's assumed probabilities and are not quoted here.
|