smd-engine 0.5.2__tar.gz → 0.5.3__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.3}/CHANGELOG.md +11 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/PKG-INFO +1 -1
- {smd_engine-0.5.2 → smd_engine-0.5.3}/docs/commands.md +1 -1
- {smd_engine-0.5.2 → smd_engine-0.5.3}/docs/data-model.md +8 -3
- {smd_engine-0.5.2 → smd_engine-0.5.3}/lenses/README.md +4 -4
- {smd_engine-0.5.2 → smd_engine-0.5.3}/lenses/khaprov-ontology.md +50 -8
- {smd_engine-0.5.2 → smd_engine-0.5.3}/profiles/classic-two-boards.yaml +1 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/profiles/management-four-boards.yaml +1 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/profiles/program-three-boards.yaml +1 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/pyproject.toml +1 -1
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/apply.py +11 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/compare.py +27 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/render/graph.py +25 -1
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/render/html.py +19 -3
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/render/index.py +19 -2
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/render/markdown.py +9 -1
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/render/text.py +68 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/schemas/board_set.schema.json +37 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/validate/__init__.py +2 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/validate/hints.py +42 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/validate/ontology.py +20 -0
- smd_engine-0.5.3/tests/test_ontology_continuum.py +203 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/uv.lock +1 -1
- {smd_engine-0.5.2 → smd_engine-0.5.3}/.claude/agents/smd-game-technician.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/.claude/agents/smd-methodologist.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/.claude/agents/smd-visionary.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/.claude/commands/procedure.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/.flake8 +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/.github/workflows/ci.yml +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/.github/workflows/release.yml +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/.gitignore +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/.python-version +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/CONTRIBUTING.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/LICENSE +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/README.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/README_ru.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/cases/example/bakeries-c1.board.yaml +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/cases/example/bakeries-c2.board.yaml +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/cases/example/golden/README.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/cases/example/golden/bakeries-c2-expected.board.yaml +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/cases/example/golden/s3_transcript.txt +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/cases/example/patches/bakeries-c2-1.patch.yaml +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/cases/example/sources.yaml +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/cases/example/two-boards-c1.board.yaml +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/cases/example_ru/pekarni-c1.board.yaml +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/cases/example_ru/pekarni-c2.board.yaml +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/cases/example_ru/pekarni-oru-c1.board.yaml +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/cases/example_ru/sources.yaml +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/docs/README.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/docs/method/README.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/docs/method/encodable.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/docs/method/odi-problematization.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/docs/method/reconciliation.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/docs/method/roles-and-actors.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/docs/method/smd-classic.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/docs/method/sources.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/docs/method/structural-moves.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/docs/method/triz-systems.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/docs/plan.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/docs/profiles.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/docs/stages.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/lenses/design-chain.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/lenses/fliamer-diamond.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/lenses/khaprov-levels.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/lenses/scamper-check.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/lenses/schukin-boundaries.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/lenses/schukin-interface-tax.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/lenses/three-positions.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/lenses/triz-contradictions.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/procedures/README.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/procedures/field-result.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/procedures/functional-plan.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/procedures/ingest-transcript.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/procedures/positional-construction.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/procedures/problematization.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/procedures/qualification-pass.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/procedures/reflexive-protocol.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/procedures/small-situation.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/procedures/solo-session.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/procedures/theses-to-board.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/procedures/visionary-tract.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/roles/README.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/roles/actors.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/roles/game-technician.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/roles/methodologist.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/roles/researcher.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/roles/visionary.md +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/__init__.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/cli.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/eval.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/migrate.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/pack.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/profile.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/records.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/render/__init__.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/render/assets/frames.css +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/render/assets/frames.js +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/render/assets/graph.css +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/render/assets/graph.js +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/render/frames.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/render/frames_page.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/render/frames_text.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/render/graph_ui.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/render/layout.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/render/light.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/render/mermaid.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/render/sessionflow.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/render/svg.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/render/vault.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/revise.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/schemas/__init__.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/schemas/board_patch.schema.json +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/schemas/source_manifest.schema.json +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/schemas/taxonomies.schema.json +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/screen.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/sources.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/validate/context.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/validate/hypotheses.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/validate/management.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/validate/manifest.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/validate/signoffs.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/validate/structure.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/validate/taxonomies.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/src/smd_engine/validate/theses.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/tests/conftest.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/tests/test_action_program.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/tests/test_apply.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/tests/test_compare.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/tests/test_eval.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/tests/test_export.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/tests/test_frames.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/tests/test_graph.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/tests/test_ingestion.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/tests/test_lenses.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/tests/test_management.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/tests/test_migrate.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/tests/test_procedures.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/tests/test_profile.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/tests/test_publish.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/tests/test_record_boards.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/tests/test_render_and_cli.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/tests/test_revise.py +0 -0
- {smd_engine-0.5.2 → smd_engine-0.5.3}/tests/test_validate.py +0 -0
|
@@ -2,6 +2,17 @@
|
|
|
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.3 - 2026-10-29
|
|
6
|
+
|
|
7
|
+
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.
|
|
8
|
+
|
|
9
|
+
- 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.
|
|
10
|
+
- Elements take `pace`: years, the characteristic period of change of what the element stands for.
|
|
11
|
+
- 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.
|
|
12
|
+
- `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.
|
|
13
|
+
- `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 лет).
|
|
14
|
+
- 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.
|
|
15
|
+
|
|
5
16
|
## 0.5.2 - 2026-10-29
|
|
6
17
|
|
|
7
18
|
- 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.
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.5
|
|
2
2
|
Name: smd-engine
|
|
3
|
-
Version: 0.5.
|
|
3
|
+
Version: 0.5.3
|
|
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
|
|
@@ -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,7 @@ 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` |
|
|
61
62
|
| `modality` | `fact` or `ought` (модальность фактического и должного, GP-Guide11 ¶7); theses carry it too |
|
|
62
63
|
| `nature` | elements of an object board only: `natural`, `artificial` or `both` (естественное, искусственное; GP-STS; GP-T5 p. 252) |
|
|
63
64
|
| `performed_by` | functions only: the position or place for others that performs the function; the viewpoint stays in `seen_from` |
|
|
@@ -177,6 +178,10 @@ An ontological picture is valid for a chosen set of positions, and is checked fo
|
|
|
177
178
|
| `competes` | what competes with what (Khaprov's ontology test) |
|
|
178
179
|
| `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
180
|
| `test` | the hypothesis that tests realizability |
|
|
181
|
+
| `lives_in` | what the system lives in and must fit into, no entry twice: `{id: <element id>}` (must exist) or `{text: "..."}` |
|
|
182
|
+
| `tempos` | the tempos the ontology assumes: `{id, years}` or `{text, years}`, e.g. `{text: "business models", years: 5}` |
|
|
183
|
+
| `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`) |
|
|
184
|
+
| `covers` | element ids the picture covers besides those in `lives_in`, no id twice; the hint `ontology-outlives-pace` reads both |
|
|
180
185
|
|
|
181
186
|
### Sign-offs (interface tax)
|
|
182
187
|
|
|
@@ -248,7 +253,7 @@ Top level: `id`, `case`, `applies_to` (the board's id), `version` (the board's n
|
|
|
248
253
|
- `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
254
|
- `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
255
|
- `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.
|
|
256
|
+
- `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
257
|
- `state`: `accepted` and `open` entries are appended, `remove_open` entries dropped from `open`, `next_move` and `difficulty` replaced.
|
|
253
258
|
|
|
254
259
|
`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.
|
|
@@ -281,8 +286,8 @@ The checks are in `src/smd_engine/validate/`, one module per subject, run in the
|
|
|
281
286
|
- **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
287
|
- **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
288
|
- **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).
|
|
289
|
+
- **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.
|
|
290
|
+
- **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).
|
|
286
291
|
- **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
292
|
- **Warnings (G.P.'s «Программа действий»):** `reflected_from` naming a position with `stance: inside`.
|
|
288
293
|
- **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.
|
|
@@ -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
|
|
|
@@ -38,7 +38,7 @@ Elements, theses, hypotheses and ontology records carry `lens: <id>`; `smd compa
|
|
|
38
38
|
| Lens | Route | Source | What it asks |
|
|
39
39
|
|---|---|---|---|
|
|
40
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 |
|
|
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 |
|
|
@@ -63,7 +63,7 @@ Rows are procedure and step. "Q" is the question number in the lens file. Where
|
|
|
63
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
64
|
| `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 |
|
|
65
65
|
| `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` |
|
|
66
|
+
| `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` |
|
|
67
67
|
| `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
68
|
| `functional-plan` | 3 Performs, pays, receives | `design-chain` | Q6, Q9 | Instruments with performer and payer; empty links of the chain |
|
|
69
69
|
| `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 |
|
|
@@ -72,7 +72,7 @@ Rows are procedure and step. "Q" is the question number in the lens file. Where
|
|
|
72
72
|
| `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
73
|
| `functional-plan` | 7 Hypotheses | `schukin-boundaries` | Q9-Q13 | Capability probes are ready-made hypotheses `assumes`, `action`, `observe`, `revise_if` |
|
|
74
74
|
| `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 |
|
|
75
|
+
| `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
76
|
| `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
77
|
| `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
78
|
| `qualification-pass` | 6 Hand over | `schukin-interface-tax` | Q11 | As above |
|
|
@@ -1,24 +1,26 @@
|
|
|
1
1
|
---
|
|
2
2
|
id: khaprov-ontology
|
|
3
3
|
title: Three scales, the ontology test and managing not-knowing
|
|
4
|
-
version: 0.
|
|
5
|
-
source:
|
|
4
|
+
version: 0.2.0
|
|
5
|
+
source:
|
|
6
|
+
- "Khaprov, expert lecture on the entrepreneur as organizer of complexity, program day 4, read through a local digest of the automatic transcript and the Q&A file (digest sections 2.4, 3, 4 items 3-4 and 11, Q&A 6, 8 and 9; the digest is not in the repo); reconciliation of the test with the classic method: docs/method/reconciliation.md section 2 (GP1981)"
|
|
7
|
+
- "Khaprov, podcast on ontology, his Telegram channel, 28.10.2026 (https://t.me/sergeykhaprov/339), read through its automatic transcript (202 lines; the transcript is not in the repo); l.N = line N of that transcript"
|
|
6
8
|
route: smd
|
|
7
9
|
offered_by: [small-situation, visionary-tract, positional-construction, problematization, qualification-pass]
|
|
8
10
|
---
|
|
9
11
|
|
|
10
12
|
# Khaprov: scales, ontology test, not-knowing
|
|
11
13
|
|
|
12
|
-
A lens for the step "view of oneself" and for the ontology records of a case. It asks at which scale the group works and which scale its target needs, what the group says it makes and what competes with it, and what the group does not know. Output goes to the `ontology` list of the record (fields `object`, `valid_for`, `subjects`, `competes`, `test`) and to a few elements.
|
|
14
|
+
A lens for the step "view of oneself" and for the ontology records of a case. It asks at which scale the group works and which scale its target needs, what the group says it makes and what competes with it, and what the group does not know. Since 0.2.0 it also asks in what space and time the system is to live, from the podcast: which systems and coming events it must fit into, at which tempos, and for how long the picture holds. Output goes to the `ontology` list of the record (fields `object`, `valid_for`, `subjects`, `competes`, `test`, `lives_in`, `tempos`, `horizon`, `covers`), to the element field `pace` and to a few elements.
|
|
13
15
|
|
|
14
|
-
Terms are Khaprov's, from a lecture
|
|
16
|
+
Terms are Khaprov's, from a lecture and a podcast, both read through automatic transcripts. Items marked **[unverified]** must be checked against the recording or slides before being quoted.
|
|
15
17
|
|
|
16
18
|
## When to use
|
|
17
19
|
|
|
18
20
|
- At step 5, "view of oneself", of `visionary-tract`, as the grain options of the `rescale` move (questions 1-4).
|
|
19
|
-
- In `positional-construction` section 5, when two or more positions describe one object differently and the group wants one record of what is built and for whom (questions 5-11). The procedure already names the ontology test for `competes`.
|
|
21
|
+
- In `positional-construction` section 5, when two or more positions describe one object differently and the group wants one record of what is built and for whom (questions 5-11). The procedure already names the ontology test for `competes`. Questions 16-21 follow when the picture is meant to hold for a period, or when the case buys or takes over objects (equipment, software, a firm).
|
|
20
22
|
- In `small-situation` section 2, only question 1 (the scale the group works at), and only if the human is unsure of it. The answer goes into the label of the fragment element; the procedure writes no other element from this lens.
|
|
21
|
-
- In `problematization` section 2, questions 12-14, when a difficulty may be a wrongly posed problem. The output is a thesis, not new board elements.
|
|
23
|
+
- In `problematization` section 2, questions 12-14, when a difficulty may be a wrongly posed problem; question 18 when the group keeps rearranging objects and nothing changes. The output is a thesis, not new board elements.
|
|
22
24
|
- In `qualification-pass`, as questions behind a K, with no elements written: criterion C7 (scale and the reason for the concept) takes questions 1-4; the realizability row takes questions 9-11. The K text names the lens id.
|
|
23
25
|
- When the group says "our competitors" without saying what competes.
|
|
24
26
|
- Do not use it to decide which ontology is true. The engine's reading, from the classic method, is that a picture is checked for realizability in activity, not for truth (docs/method/reconciliation.md section 2). Khaprov's own position is stronger: a wrong ontology is fatal. Reading "fatal" as "fails the realizability test" reconciles them, but that is the engine's reading **(own extrapolation)**; Khaprov does not say it.
|
|
@@ -54,6 +56,15 @@ Terms are Khaprov's, from a lecture heard through an automatic transcript. Items
|
|
|
54
56
|
|
|
55
57
|
**Managing not-knowing (управление незнанием).** A stage zero before knowledge management: "Do I have knowledge of all the levels of complexity I need? Maybe I formulate the problem wrongly?" The source says ontology-level thinking is hard for adults to learn, suggests a bridge through technical and mathematical language, and mentions AI simulators in which a founder loads projects, staff and tasks and gets variants of decisions. It gives no further method.
|
|
56
58
|
|
|
59
|
+
**Podcast: the space-time continuum (пространственно-временной континуум).** Points the podcast makes, by transcript line:
|
|
60
|
+
- ontology is the seventh, top level of his complexity pyramid, made a tool of management rather than of philosophy (l.168, 180-182);
|
|
61
|
+
- one level of an ontology is "the space-time continuum in which the system will live" (l.172); an ontology covers the space and the continuum "of its exhaustion" (l.158-161, a garbled passage) **[unverified]**;
|
|
62
|
+
- the education example (l.154-166): a firm's life cycle fell from 100-200 to 30 years, technologies live about 15 years, business models built on them change 80% in 5 years; yet a course takes years to write and approve, five years to teach, and is planned for 11 cycles, as if the technology lived 60-90 years. His verdict: the continuum no longer fits; "however you rearrange the objects, nothing will change" (l.158); what must change is the continuum. The figures are from the automatic transcript **[unverified]**;
|
|
63
|
+
- an ontology must be fitted into the ontologies of other systems and of coming events: the iPhone fitted its ontology into that of coming events (l.64); aircraft built by the thousand must fit airports and the rest (l.70); the ontology of one object is a building block for the next level (l.92);
|
|
64
|
+
- the cost of an ontology error: decisions worth tens of billions to trillions of dollars (l.14-16, 24); an error costs hundreds of millions times thousands of person-hours, "when you make something and it is not needed" (l.170); the typical error is buying objects into an old ontology: imported numerically controlled machines of the 1970s stood in their crates because nobody held the ontology of programmed machining (l.26-34); people defend themselves by the industrial ontology while fraudsters live in the networked one (l.50-56);
|
|
65
|
+
- an ontology "decides 100% of uncertainty": the world will be this way, so investment, retraining and suppliers move together (l.48);
|
|
66
|
+
- horizontal specialization (l.100-148): firms that held thinking, communication and activity in one vertical gave way to platforms (App Store, Google Play, Amazon) that take the communication layer (payments, deal tracking, logistics) for hundreds of millions of people, and technoparks below that produce to order; the platform passes the risk of guessing a product's ontology to many developers (l.126-130). He reads Gosplan and Gossnab as such platforms, Soviet enterprises as technoparks (l.144-148).
|
|
67
|
+
|
|
57
68
|
## Questions
|
|
58
69
|
|
|
59
70
|
Scale (view of oneself):
|
|
@@ -77,6 +88,14 @@ Not-knowing (stage zero):
|
|
|
77
88
|
14. Which ontology is the group acting in without having named it? Is any management system or tool in the case taken from another picture?
|
|
78
89
|
15. What is the next step that reduces not-knowing the most, and who takes it?
|
|
79
90
|
|
|
91
|
+
Continuum (from the podcast; the wording is the engine's **(own extrapolation)**):
|
|
92
|
+
16. What world does the system live in? Name the systems, infrastructures and coming events it must fit into. Which of them are already on the boards?
|
|
93
|
+
17. Which tempos does the picture assume? How long do the technologies, business models, tiers or rules it rests on last, and how long is the system's own cycle (to build, launch and pay back)?
|
|
94
|
+
18. For how many years should the picture hold? Is any tempo from 17 shorter? If so, does the group rearrange objects, or change the continuum, and which would the next tempo change undo?
|
|
95
|
+
19. Which objects (equipment, software, staff, a firm) does the case buy or take over? Does the picture they need exist in the case, and who would run them in it?
|
|
96
|
+
20. What would an error in this picture cost: money, person-hours, a lost market window or generation? Who bears it?
|
|
97
|
+
21. Which layer would a platform take here: communication (sales, payments, logistics, deal tracking), production, or none? What stays the group's own, and under whose rules?
|
|
98
|
+
|
|
80
99
|
## Output slots
|
|
81
100
|
|
|
82
101
|
Every element, thesis, hypothesis and ontology record it produces carries `lens: khaprov-ontology`; `smd compare` reads all four. The table applies where the procedure writes elements (`visionary-tract`, `positional-construction`). In `small-situation`, `problematization` and `qualification-pass` see "When to use".
|
|
@@ -96,8 +115,27 @@ Every element, thesis, hypothesis and ontology record it produces carries `lens:
|
|
|
96
115
|
| Not-knowing (Q12, Q13) | thesis with `kind: question` or `problem`, `belt: m`, `lens: khaprov-ontology`; the hypothesis behind it, if testable, as an `H` |
|
|
97
116
|
| What is not known and where (Q12, Q14) | `gap` with `of` set; or `note` with `epistemic: unverified` when no scheme block fits |
|
|
98
117
|
| The next step against not-knowing (Q15) | `goal` on `od`, `seen_from` the position that takes it |
|
|
99
|
-
|
|
100
|
-
|
|
118
|
+
| What the system lives in and must fit into (Q16) | `ontology.lives_in`: `{id: <element>}` for what is on the boards (a big `situation`, a `place_for_others`, a `position`), `{text: "..."}` for the rest |
|
|
119
|
+
| Tempos (Q17) | `ontology.tempos`: `{id: <element>, years}` or `{text: "...", years}`; on an element that stands for the changing thing (a tier, a technology), also `pace` in years |
|
|
120
|
+
| Horizon (Q18) | `ontology.horizon` in years; `ontology.covers` for elements the picture covers besides those `lives_in` names. The hint `ontology-outlives-pace` then names every pace (of the elements in `lives_in` and `covers`) or tempo shorter than the horizon |
|
|
121
|
+
| Rearranging objects instead of changing the continuum (Q18) | thesis `kind: problem`, `belt: m`, `lens: khaprov-ontology` |
|
|
122
|
+
| An object without its picture (Q19) | `gap` with `of: method` (no one knows how to run it) or `of: position` (no one to run it); a hypothesis `H` if the group can test whether the object is used |
|
|
123
|
+
| Cost of an error (Q20) | `ontology.note`; a figure with no source goes into a `note` on `oo` with `epistemic: unverified` |
|
|
124
|
+
| The platform's layer (Q21) | `place_for_others` on `od` for the platform, with `fillers`; the `function` it takes, `performed_by` that place; the place in `ontology.lives_in` as `{id: <place>}` |
|
|
125
|
+
|
|
126
|
+
Example for the invented bakeries case (`cases/example/`): the record `O1` there has object "shared production as an asset owned by the bakeries that use it", `valid_for` the owner and the organiser, one subject per position, a cooperation element, a `competes` statement and the test `H1`. Use it as the shape of a finished record. With the continuum it might read (invented figures):
|
|
127
|
+
|
|
128
|
+
```yaml
|
|
129
|
+
- {id: fn-logistics, board: oo, kind: function, label: "night logistics, run by the plant", pace: 5}
|
|
130
|
+
ontology:
|
|
131
|
+
- id: O1
|
|
132
|
+
lives_in: [{id: s-big}, {text: "Региональные сети и мельницы"}]
|
|
133
|
+
tempos: [{text: "delivery business models", years: 5}]
|
|
134
|
+
horizon: 10
|
|
135
|
+
covers: [fn-dough, fn-logistics]
|
|
136
|
+
```
|
|
137
|
+
|
|
138
|
+
`smd validate --hints` then gives two hints on `O1`: `fn-logistics` and the delivery business models change every 5 years, before the 10-year horizon.
|
|
101
139
|
|
|
102
140
|
## Limits
|
|
103
141
|
|
|
@@ -108,3 +146,7 @@ Example for the invented bakeries case (`cases/example/`): the record `O1` there
|
|
|
108
146
|
- Scale is read from the evidence the group brings. The lens gives no thresholds.
|
|
109
147
|
- Managing not-knowing is a title and a first question in the source, not a method. The questions in the third group above are the engine's way of using it **(own extrapolation)**.
|
|
110
148
|
- Figures and company data in the lecture come from an automatic transcript and are not to be quoted without the recording.
|
|
149
|
+
- The podcast gives no method for naming tempos or setting a horizon. The fields `lives_in`, `tempos`, `horizon`, `covers` and `pace`, and the rule of the hint (a pace or tempo shorter than the horizon), are the engine's reading of "the continuum is exhausted" **(own extrapolation)**.
|
|
150
|
+
- "An ontology decides 100% of uncertainty" (l.48) is the podcast's claim. The engine still records a picture as valid for positions and tested for realizability, and reads the claim as a projective decision, not a forecast **(own extrapolation)**.
|
|
151
|
+
- Horizontal specialization is given through examples. Mapping a platform to a `place_for_others` that performs a function is the engine's reading **(own extrapolation)**.
|
|
152
|
+
- Names and figures of the podcast come from an automatic transcript and are not to be quoted without the recording.
|
|
@@ -30,6 +30,7 @@ OPTIONAL_LISTS = (
|
|
|
30
30
|
"raises",
|
|
31
31
|
"qualifications",
|
|
32
32
|
"arises_from",
|
|
33
|
+
"covers",
|
|
33
34
|
)
|
|
34
35
|
# ...lists the schema requires to be non-empty, left empty for the validator to
|
|
35
36
|
# report, so that a removal never deletes a decision silently...
|
|
@@ -276,6 +277,16 @@ def _unlink(item: dict[str, Any], gone: set[str]) -> None:
|
|
|
276
277
|
]
|
|
277
278
|
if not item["subjects"]:
|
|
278
279
|
del item["subjects"]
|
|
280
|
+
# Entries of an ontology's continuum that name the item by id.
|
|
281
|
+
for key in ("lives_in", "tempos"):
|
|
282
|
+
if isinstance(item.get(key), list):
|
|
283
|
+
item[key] = [
|
|
284
|
+
x
|
|
285
|
+
for x in item[key]
|
|
286
|
+
if not (isinstance(x, dict) and _gone(x.get("id"), gone))
|
|
287
|
+
]
|
|
288
|
+
if not item[key]:
|
|
289
|
+
del item[key]
|
|
279
290
|
move = item.get("move")
|
|
280
291
|
if isinstance(move, dict) and isinstance(move.get("from"), list):
|
|
281
292
|
# An empty `from` stays for the validator to report.
|
|
@@ -20,6 +20,7 @@ from difflib import SequenceMatcher
|
|
|
20
20
|
from typing import Any
|
|
21
21
|
|
|
22
22
|
from smd_engine.profile import ProfileError, profile_of
|
|
23
|
+
from smd_engine.render.text import CONTINUUM, continuum_parts
|
|
23
24
|
|
|
24
25
|
MATCH = 0.55 # below this, two labels are not the same element
|
|
25
26
|
SAME = 0.85 # at or above this, two labels say the same thing
|
|
@@ -217,6 +218,29 @@ def compare_boards(a: dict[str, Any], b: dict[str, Any]) -> list[str]:
|
|
|
217
218
|
return out
|
|
218
219
|
|
|
219
220
|
|
|
221
|
+
def compare_continuum(a: dict[str, Any], b: dict[str, Any]) -> list[str]:
|
|
222
|
+
"""Ontology records matched by id, with `lives_in`, `tempos`, `horizon`
|
|
223
|
+
and `covers` in A and in B: one line each for a record that has any of
|
|
224
|
+
them on either side. Empty when no ontology record of either has them."""
|
|
225
|
+
in_a = {o["id"]: o for o in a.get("ontology", [])}
|
|
226
|
+
in_b = {o["id"]: o for o in b.get("ontology", [])}
|
|
227
|
+
out = []
|
|
228
|
+
for oid in [*in_a, *(i for i in in_b if i not in in_a)]:
|
|
229
|
+
x, y = in_a.get(oid), in_b.get(oid)
|
|
230
|
+
px, py = continuum_parts(x or {}), continuum_parts(y or {})
|
|
231
|
+
if not (px or py):
|
|
232
|
+
continue
|
|
233
|
+
side = "both" if x and y else "only A" if x else "only B"
|
|
234
|
+
line = f"- {side} `{oid}` {(y or x or {})['object']}"
|
|
235
|
+
for key in CONTINUUM:
|
|
236
|
+
if x and y and (key in px or key in py):
|
|
237
|
+
line += f"; {key} {px.get(key, '-')} / {py.get(key, '-')}"
|
|
238
|
+
elif key in px or key in py:
|
|
239
|
+
line += f"; {key} {px.get(key) or py.get(key)}"
|
|
240
|
+
out.append(line)
|
|
241
|
+
return out
|
|
242
|
+
|
|
243
|
+
|
|
220
244
|
def lenses(record: dict[str, Any]) -> set[str]:
|
|
221
245
|
"""Lenses a board set used, read from elements, theses, hypotheses, ontology."""
|
|
222
246
|
items = (
|
|
@@ -265,6 +289,9 @@ def report(a: dict[str, Any], b: dict[str, Any]) -> str:
|
|
|
265
289
|
boards = compare_boards(a, b)
|
|
266
290
|
if boards:
|
|
267
291
|
out += ["## boards", ""] + boards + [""]
|
|
292
|
+
continuum = compare_continuum(a, b)
|
|
293
|
+
if continuum:
|
|
294
|
+
out += ["## ontology: continuum", ""] + continuum + [""]
|
|
268
295
|
lenses_a, lenses_b = lenses(a), lenses(b)
|
|
269
296
|
if lenses_a | lenses_b:
|
|
270
297
|
out += [
|
|
@@ -16,7 +16,13 @@ from smd_engine.profile import Profile, profile_of
|
|
|
16
16
|
from smd_engine.render import asset_text
|
|
17
17
|
from smd_engine.render.graph_ui import UI
|
|
18
18
|
from smd_engine.render.layout import plan, region_of
|
|
19
|
-
from smd_engine.render.text import
|
|
19
|
+
from smd_engine.render.text import (
|
|
20
|
+
continuum_parts,
|
|
21
|
+
cut,
|
|
22
|
+
esc,
|
|
23
|
+
screen_label,
|
|
24
|
+
pace_text,
|
|
25
|
+
)
|
|
20
26
|
|
|
21
27
|
SPAN = 1000.0 # width of a board plane in graph units
|
|
22
28
|
LAYER = 260.0 # distance between planes
|
|
@@ -75,6 +81,12 @@ EDGE_KINDS: dict[str, dict[str, str]] = {
|
|
|
75
81
|
"cites": "source",
|
|
76
82
|
},
|
|
77
83
|
}
|
|
84
|
+
# Links of an ontology record's continuum, listed in edge_kinds only when a
|
|
85
|
+
# record draws them, so a record without them gives the same page.
|
|
86
|
+
CONTINUUM_EDGE_KINDS: dict[str, dict[str, str]] = {
|
|
87
|
+
"ru": {"lives_in": "живёт в", "covers": "охватывает"},
|
|
88
|
+
"en": {"lives_in": "lives in", "covers": "covers"},
|
|
89
|
+
}
|
|
78
90
|
# Kinds shown by the "flows and shifts" view.
|
|
79
91
|
FLOW_KINDS = ["flow", "shift", "opposes", "produces", "uses", "transition"]
|
|
80
92
|
GROUP_LABELS = {
|
|
@@ -185,6 +197,8 @@ def graph_model(
|
|
|
185
197
|
"z": z,
|
|
186
198
|
}
|
|
187
199
|
)
|
|
200
|
+
if "pace" in e:
|
|
201
|
+
nodes[-1]["extra"] = {"pace": pace_text(e, lang)}
|
|
188
202
|
for parent in e.get("in", []):
|
|
189
203
|
if parent in by_id:
|
|
190
204
|
edge(e["id"], parent, "in")
|
|
@@ -237,6 +251,8 @@ def graph_model(
|
|
|
237
251
|
for key in ("action", "observe", "revise_if", "competes", "test")
|
|
238
252
|
if rec.get(key)
|
|
239
253
|
}
|
|
254
|
+
if group == "ontology":
|
|
255
|
+
extra |= continuum_parts(rec, lang)
|
|
240
256
|
nodes.append(
|
|
241
257
|
{
|
|
242
258
|
"id": rec["id"],
|
|
@@ -263,6 +279,12 @@ def graph_model(
|
|
|
263
279
|
edge(rec["id"], rec["cooperation"], "cooperation")
|
|
264
280
|
if rec.get("test"):
|
|
265
281
|
edge(rec["id"], rec["test"], "tested_by")
|
|
282
|
+
for entry in rec.get("lives_in", []):
|
|
283
|
+
if entry.get("id") in by_id:
|
|
284
|
+
edge(rec["id"], entry["id"], "lives_in")
|
|
285
|
+
for ref in rec.get("covers", []):
|
|
286
|
+
if ref in by_id:
|
|
287
|
+
edge(rec["id"], ref, "covers")
|
|
266
288
|
|
|
267
289
|
# Sources below the boards, under the items that cite them.
|
|
268
290
|
titles = {s["id"]: s for s in (manifest or {}).get("sources", [])}
|
|
@@ -300,6 +322,7 @@ def graph_model(
|
|
|
300
322
|
|
|
301
323
|
present = {node["id"] for node in nodes}
|
|
302
324
|
edges = [e for e in edges if e["s"] in present and e["t"] in present]
|
|
325
|
+
drawn = {e["k"] for e in edges}
|
|
303
326
|
return {
|
|
304
327
|
"title": data.get("title", data.get("id", "")),
|
|
305
328
|
"id": data.get("id", ""),
|
|
@@ -311,6 +334,7 @@ def graph_model(
|
|
|
311
334
|
"board_colours": {b: profile.board(b).colour[1] for b in boards},
|
|
312
335
|
# the engine's link kinds, then the relation kinds the profile labels
|
|
313
336
|
"edge_kinds": EDGE_KINDS[lang]
|
|
337
|
+
| {k: v for k, v in CONTINUUM_EDGE_KINDS[lang].items() if k in drawn}
|
|
314
338
|
| {k: label[lang] for k, label in profile.relation_labels.items()},
|
|
315
339
|
"flow_kinds": FLOW_KINDS,
|
|
316
340
|
"nodes": nodes,
|
|
@@ -6,7 +6,12 @@ from __future__ import annotations
|
|
|
6
6
|
from typing import Any
|
|
7
7
|
|
|
8
8
|
from smd_engine.render.svg import render_svg
|
|
9
|
-
from smd_engine.render.text import
|
|
9
|
+
from smd_engine.render.text import (
|
|
10
|
+
LABELS,
|
|
11
|
+
continuum_lines,
|
|
12
|
+
esc,
|
|
13
|
+
pace_text,
|
|
14
|
+
)
|
|
10
15
|
|
|
11
16
|
CSS = """
|
|
12
17
|
:root{--bg:#fff;--ink:#1d1d1f;--muted:#5b5b60;--line:#e3e3e8;--navy:#12235a}
|
|
@@ -32,6 +37,17 @@ def _fillers(el: dict[str, Any], lab: dict[str, Any]) -> str:
|
|
|
32
37
|
return f"<br><small>{esc(lab['fillers'])}: {esc(', '.join(el['fillers']))}</small>"
|
|
33
38
|
|
|
34
39
|
|
|
40
|
+
def _pace(el: dict[str, Any], lang: str) -> str:
|
|
41
|
+
text = pace_text(el, lang)
|
|
42
|
+
return f"<br><small>{esc(text)}</small>" if text else ""
|
|
43
|
+
|
|
44
|
+
|
|
45
|
+
def _continuum(o: dict[str, Any], lang: str) -> str:
|
|
46
|
+
"""Lives in, tempos, horizon and covers of an ontology record."""
|
|
47
|
+
shown = continuum_lines(o, lang)
|
|
48
|
+
return f"<br><small>{esc('; '.join(shown))}</small>" if shown else ""
|
|
49
|
+
|
|
50
|
+
|
|
35
51
|
def _table(title: str, cols: list[str], rows: list[list[str]]) -> str:
|
|
36
52
|
"""A titled table; cells are already escaped. Empty when there are no rows."""
|
|
37
53
|
if not rows:
|
|
@@ -55,7 +71,7 @@ def render_html(
|
|
|
55
71
|
rows_e = "".join(
|
|
56
72
|
f"<tr><td><code>{esc(e['id'])}</code></td><td>{esc(e['board'])}"
|
|
57
73
|
f"{'/' + esc(e['half']) if e.get('half') else ''}</td><td>{esc(e['kind'])}</td>"
|
|
58
|
-
f"<td>{esc(e['label'])}{_fillers(e, lab)}</td>"
|
|
74
|
+
f"<td>{esc(e['label'])}{_fillers(e, lab)}{_pace(e, lang)}</td>"
|
|
59
75
|
f"<td><code>{esc(', '.join(e.get('cites', [])))}</code></td></tr>"
|
|
60
76
|
for e in data["elements"]
|
|
61
77
|
)
|
|
@@ -107,7 +123,7 @@ def render_html(
|
|
|
107
123
|
[
|
|
108
124
|
[
|
|
109
125
|
f"<b>{esc(o['id'])}</b>",
|
|
110
|
-
esc(o["object"]),
|
|
126
|
+
esc(o["object"]) + _continuum(o, lang),
|
|
111
127
|
f"<code>{esc(', '.join(o['valid_for']))}</code>",
|
|
112
128
|
f"<code>{esc(o.get('cooperation', ''))}</code>",
|
|
113
129
|
esc(o.get("test", "")),
|
|
@@ -17,7 +17,13 @@ from typing import Any
|
|
|
17
17
|
from urllib.parse import quote
|
|
18
18
|
|
|
19
19
|
from smd_engine.profile import profile_of
|
|
20
|
-
from smd_engine.render.text import
|
|
20
|
+
from smd_engine.render.text import (
|
|
21
|
+
LABELS,
|
|
22
|
+
continuum_lines,
|
|
23
|
+
esc,
|
|
24
|
+
pace_text,
|
|
25
|
+
title_line,
|
|
26
|
+
)
|
|
21
27
|
|
|
22
28
|
CSS = """body{font:14px/1.45 -apple-system,Helvetica,Arial,sans-serif;margin:0;color:#1d2433;background:#fff}
|
|
23
29
|
header{position:sticky;top:0;background:#fff;border-bottom:1px solid #ddd;padding:10px 16px;z-index:1}
|
|
@@ -151,6 +157,12 @@ class _Index:
|
|
|
151
157
|
def _refs(self, items: list[str | None] | None) -> str:
|
|
152
158
|
return ", ".join(f'<a href="#{esc(x)}">{esc(x)}</a>' for x in items or [] if x)
|
|
153
159
|
|
|
160
|
+
def _continuum(self, o: dict[str, Any]) -> str:
|
|
161
|
+
"""Lives in, tempos, horizon and covers of an ontology record, under its
|
|
162
|
+
object; empty when it has none of them."""
|
|
163
|
+
lines = continuum_lines(o, self.lang)
|
|
164
|
+
return f"<br><small>{esc('; '.join(lines))}</small>" if lines else ""
|
|
165
|
+
|
|
154
166
|
def _where(self, sid: str) -> str:
|
|
155
167
|
source = self.sources.get(sid)
|
|
156
168
|
if source is None:
|
|
@@ -228,7 +240,7 @@ class _Index:
|
|
|
228
240
|
ontology = [
|
|
229
241
|
[
|
|
230
242
|
anchor(o["id"]),
|
|
231
|
-
e(o["object"]),
|
|
243
|
+
e(o["object"]) + self._continuum(o),
|
|
232
244
|
refs(o.get("valid_for")),
|
|
233
245
|
refs([o.get("cooperation")]) + " · " + refs([o.get("test")]),
|
|
234
246
|
e(o.get("note", "")),
|
|
@@ -260,6 +272,11 @@ class _Index:
|
|
|
260
272
|
f"<br><small>{e(x['label_note'])}</small>"
|
|
261
273
|
if x.get("label_note")
|
|
262
274
|
else ""
|
|
275
|
+
)
|
|
276
|
+
+ (
|
|
277
|
+
f"<br><small>{e(pace_text(x, self.lang))}</small>"
|
|
278
|
+
if "pace" in x
|
|
279
|
+
else ""
|
|
263
280
|
),
|
|
264
281
|
e(", ".join(x.get("fillers", []))),
|
|
265
282
|
cites(x.get("cites")),
|
|
@@ -5,7 +5,12 @@ from __future__ import annotations
|
|
|
5
5
|
from typing import Any
|
|
6
6
|
|
|
7
7
|
from smd_engine.profile import profile_of
|
|
8
|
-
from smd_engine.render.text import
|
|
8
|
+
from smd_engine.render.text import (
|
|
9
|
+
LABELS,
|
|
10
|
+
MOVE_NAMES,
|
|
11
|
+
continuum_lines,
|
|
12
|
+
years_text,
|
|
13
|
+
)
|
|
9
14
|
|
|
10
15
|
|
|
11
16
|
def _line(el: dict[str, Any]) -> str:
|
|
@@ -16,6 +21,8 @@ def _line(el: dict[str, Any]) -> str:
|
|
|
16
21
|
bits.append("in " + ", ".join(f"`{i}`" for i in el["in"]))
|
|
17
22
|
if el.get("fillers"):
|
|
18
23
|
bits.append("fillers: " + ", ".join(el["fillers"]))
|
|
24
|
+
if "pace" in el:
|
|
25
|
+
bits.append(f"pace: {years_text(el['pace'], 'en')}")
|
|
19
26
|
if el.get("seen_from"):
|
|
20
27
|
bits.append(f"seen from `{el['seen_from']}`")
|
|
21
28
|
if el.get("epistemic"):
|
|
@@ -148,6 +155,7 @@ def render_markdown(data: dict[str, Any], lang: str = "ru") -> str:
|
|
|
148
155
|
out.append(f" - `{sub['position']}`: {sub['subject']}")
|
|
149
156
|
if o.get("competes"):
|
|
150
157
|
out.append(f" - competes: {o['competes']}")
|
|
158
|
+
out += [f" - {line}" for line in continuum_lines(o, lang)]
|
|
151
159
|
out.append("")
|
|
152
160
|
if data.get("signoffs"):
|
|
153
161
|
out += [f"## {lab['signoffs']}", ""]
|