smd-engine 0.3.7__tar.gz → 0.5.0__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.3.7 → smd_engine-0.5.0}/CHANGELOG.md +29 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/CONTRIBUTING.md +1 -1
- {smd_engine-0.3.7 → smd_engine-0.5.0}/PKG-INFO +3 -2
- {smd_engine-0.3.7 → smd_engine-0.5.0}/README.md +2 -1
- {smd_engine-0.3.7 → smd_engine-0.5.0}/README_ru.md +2 -1
- smd_engine-0.5.0/cases/example_ru/pekarni-oru-c1.board.yaml +121 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/docs/commands.md +2 -1
- {smd_engine-0.3.7 → smd_engine-0.5.0}/docs/data-model.md +37 -10
- {smd_engine-0.3.7 → smd_engine-0.5.0}/docs/method/sources.md +15 -2
- smd_engine-0.5.0/docs/profiles.md +109 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/lenses/README.md +4 -1
- smd_engine-0.5.0/lenses/three-positions.md +60 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/procedures/ingest-transcript.md +3 -2
- {smd_engine-0.3.7 → smd_engine-0.5.0}/procedures/positional-construction.md +5 -2
- {smd_engine-0.3.7 → smd_engine-0.5.0}/procedures/qualification-pass.md +4 -1
- {smd_engine-0.3.7 → smd_engine-0.5.0}/procedures/reflexive-protocol.md +13 -7
- {smd_engine-0.3.7 → smd_engine-0.5.0}/profiles/classic-two-boards.yaml +11 -2
- smd_engine-0.5.0/profiles/management-four-boards.yaml +175 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/profiles/program-three-boards.yaml +11 -2
- {smd_engine-0.3.7 → smd_engine-0.5.0}/pyproject.toml +1 -1
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/apply.py +55 -6
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/compare.py +86 -10
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/pack.py +67 -7
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/profile.py +292 -17
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/render/assets/graph.js +5 -3
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/render/frames.py +27 -7
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/render/frames_text.py +38 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/render/graph.py +3 -1
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/render/index.py +19 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/render/markdown.py +17 -2
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/render/svg.py +1 -1
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/render/text.py +11 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/render/vault.py +29 -3
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/schemas/board_patch.schema.json +3 -2
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/schemas/board_set.schema.json +26 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/screen.py +21 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/validate/__init__.py +93 -2
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/validate/context.py +15 -2
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/validate/hints.py +241 -1
- smd_engine-0.5.0/src/smd_engine/validate/management.py +336 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/validate/structure.py +127 -3
- smd_engine-0.5.0/tests/test_action_program.py +211 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/tests/test_apply.py +12 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/tests/test_compare.py +29 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/tests/test_export.py +31 -1
- smd_engine-0.5.0/tests/test_management.py +250 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/tests/test_procedures.py +8 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/tests/test_profile.py +75 -1
- smd_engine-0.5.0/tests/test_record_boards.py +377 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/tests/test_revise.py +16 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/uv.lock +1 -1
- smd_engine-0.3.7/docs/profiles.md +0 -82
- {smd_engine-0.3.7 → smd_engine-0.5.0}/.claude/agents/smd-game-technician.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/.claude/agents/smd-methodologist.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/.claude/agents/smd-visionary.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/.claude/commands/procedure.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/.flake8 +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/.github/workflows/ci.yml +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/.github/workflows/release.yml +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/.gitignore +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/.python-version +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/LICENSE +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/cases/example/bakeries-c1.board.yaml +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/cases/example/bakeries-c2.board.yaml +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/cases/example/golden/README.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/cases/example/golden/bakeries-c2-expected.board.yaml +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/cases/example/golden/s3_transcript.txt +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/cases/example/patches/bakeries-c2-1.patch.yaml +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/cases/example/sources.yaml +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/cases/example/two-boards-c1.board.yaml +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/cases/example_ru/pekarni-c1.board.yaml +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/cases/example_ru/pekarni-c2.board.yaml +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/cases/example_ru/sources.yaml +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/docs/README.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/docs/method/README.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/docs/method/encodable.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/docs/method/odi-problematization.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/docs/method/reconciliation.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/docs/method/roles-and-actors.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/docs/method/smd-classic.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/docs/method/structural-moves.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/docs/method/triz-systems.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/docs/plan.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/docs/stages.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/lenses/design-chain.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/lenses/fliamer-diamond.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/lenses/khaprov-levels.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/lenses/khaprov-ontology.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/lenses/scamper-check.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/lenses/schukin-boundaries.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/lenses/schukin-interface-tax.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/lenses/triz-contradictions.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/procedures/README.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/procedures/field-result.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/procedures/functional-plan.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/procedures/problematization.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/procedures/small-situation.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/procedures/solo-session.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/procedures/theses-to-board.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/procedures/visionary-tract.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/roles/README.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/roles/actors.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/roles/game-technician.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/roles/methodologist.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/roles/researcher.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/roles/visionary.md +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/__init__.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/cli.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/eval.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/migrate.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/records.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/render/__init__.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/render/assets/frames.css +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/render/assets/frames.js +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/render/assets/graph.css +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/render/frames_page.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/render/graph_ui.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/render/html.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/render/layout.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/render/light.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/render/mermaid.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/render/sessionflow.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/revise.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/schemas/__init__.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/schemas/source_manifest.schema.json +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/schemas/taxonomies.schema.json +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/sources.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/validate/hypotheses.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/validate/manifest.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/validate/ontology.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/validate/signoffs.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/validate/taxonomies.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/src/smd_engine/validate/theses.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/tests/conftest.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/tests/test_eval.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/tests/test_frames.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/tests/test_graph.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/tests/test_ingestion.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/tests/test_lenses.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/tests/test_migrate.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/tests/test_publish.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/tests/test_render_and_cli.py +0 -0
- {smd_engine-0.3.7 → smd_engine-0.5.0}/tests/test_validate.py +0 -0
|
@@ -2,6 +2,35 @@
|
|
|
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.0 - 2026-10-29
|
|
6
|
+
|
|
7
|
+
The first public release since 0.3.7; it also carries 0.3.8 and 0.4.0, which were tagged in the private repository only.
|
|
8
|
+
|
|
9
|
+
- `compare.merge` remaps `performed_by` of imported functions like `assigned_by` (kept only when the target exists in the result and is a position or place for others); before, a dangling reference was possible.
|
|
10
|
+
- Record boards: a profile may declare a board template (`per_record: true`, with its label, colour, the kinds it takes and, optionally, the kinds its boards may `unfold`); a record declares any number of boards of it in `boards` (`id`, `template`, `label`, optional `seen_from`, `unfolds`, `cites`), and every part of the engine handles each as a board: validation (unknown template, taken, reserved (`records`, `sources`: the layers of `smd graph`) or duplicate id, a kind the template does not take, `unfolds` of a kind the template does not unfold), the screen (placed below the profile's boards, rows as wide as its widest row), frames (a reading step on a template is read once per record board, `<step>-<board>`; zoom cuts to it), the index (a table of record boards), `smd compare` (boards matched by id, with their element counts; a merge carries A's boards that B lacks), `smd graph` (a plane each), `smd vault` (a folder each, unique and never named by the template alone), `smd pack` (record boards listed as cells), `smd revise` (carried) and `smd apply` (`add.boards`, `set` and `remove` by id; a removed record board takes its elements with it). `boards` is optional: schema 0.3 stays, and records without it give the same output byte for byte.
|
|
11
|
+
- `management-four-boards`: the kind `process_board` (a framed area of `ot`) is replaced by the template `process`, so each working process is idealised on a board of its own (GP-T5 p. 245) and unfolds a `work_process`; `function` lives on it, and `representation-fit` no longer lists `process_board` among a manager's targets. The reading step `process` follows `upper`. The example `pekarni-oru-c1` has two process boards.
|
|
12
|
+
- `scripts/export_public.py` reads its arguments with argparse: `-h/--help` prints the usage and exits 0 (before, it exported into a folder named `--help`); an output folder inside the repository, or one that exists and is not empty, is refused with exit 2.
|
|
13
|
+
|
|
14
|
+
## 0.4.0 - 2026-10-29
|
|
15
|
+
|
|
16
|
+
- Gate Ш13 В amended by Ш15 В: G.P.'s scheme of organisation, leadership and management as the profile `management-four-boards`, read against GP-T5 lectures 4-6 (1988; the latest text wins, the earlier view stays as a comment in the profile file). Schema 0.3 stays.
|
|
17
|
+
- Four boards on the `regions` screen: `od` and the upper system of ОРУ `ot` on top, the apparatus of leadership `ap` and the managed polysystem `us` below; `ot` and `us` flagged `object`. Kinds: knowledge (`knowledge_retro`, `knowledge_projective`) in place of a forecast, `ideal_state`, `programme`, `means`, `functional_place`, `process_board` (a working process idealised on its own board, drawn as a framed area of `ot`); `post`, `group`, `club`; `monosystem`, `mission`, `self_motion`, `trajectory`, `work_process` and the planes `functional_structure`, `link_structure`, `morphology`, `material`, and `fact`. Relations: `organises`, `leads`, `manages`, `subordinates`, `personal`, `captures` («захват»), `knows` (not «отражение»), `contends` (politics), `parasitic`, `symbiotic`, `mechanism_of`.
|
|
18
|
+
- Hints of this scheme, in `validate/management.py`: `lead-vs-manage`, `manage-via-organizedness`, `manage-without-knowledge`, `leads-outside-organisation`, `representation-fit` (the fit table revised by GP-T5: the working process is the object of управление), `development-step` («шаг развития»), `polysystem`.
|
|
19
|
+
- Profiles: a relation kind other than the engine's nine is written `{id, label: {ru, en}}`, and `smd graph` and `smd vault` name its links by the label; a hint may register the kinds and relation kinds it names, which a profile enabling it must define. Reading steps `upper`, `apparatus`, `managed`.
|
|
20
|
+
- Example `cases/example_ru/pekarni-oru-c1.board.yaml`.
|
|
21
|
+
- Fable review: an engine relation id with a label is refused; `leads-outside-organisation` names a leader and a led who hold the same place; the leader's fit is `post` only (GP-T5 pp. 224-225, 254).
|
|
22
|
+
- `docs/method/sources.md`: rows for the keys the new hints cite: GP1975a, GP-STS, IT1995, GP-Guide and its sections 4, 5, 8, 10, 11, GP-Guide2004, GP-T4, GP-T5.
|
|
23
|
+
|
|
24
|
+
## 0.3.8 - 2026-10-29
|
|
25
|
+
|
|
26
|
+
- `docs/method/sources.md`: the GP1983 row gives the Избранные труды key and explains the gtmarket page header; new row GP1983a for the single-author 1983 text; GP-Guide9 gets its edition (М.: Дело, 2003).
|
|
27
|
+
- Gates Ш8-Ш12, from G.P.'s «Программа действий» (GP-Guide11, 1981) read against т. 5 (GP-T5, 1988; the later text wins where they disagree). Schema 0.3 stays; every new field is optional and no hint fires on a record without the new fields, except `goal-without-breakdown`, `information-without-cell` and `cells-from-information`, which read existing fields.
|
|
28
|
+
- Element fields: `stance` (`inside`, `reflexive`, `external`) on the kinds a profile flags `stance` (the positions); `acts_as` (`organiser`, `leader`, `manager`, `politician`, `functionary`) on positions; `goal_source` (`breakdown`, `assigned`, `own`), `arises_from` and `assigned_by` on goals; `modality` (`fact`, `ought`) on elements and theses; `nature` (`natural`, `artificial`, `both`) on object-board elements. Each off its kind or board is an error, as are a dangling or wrong-kind `arises_from` and an `assigned_by` that is not a position or place for others; a `reflected_from` position with `stance: inside` is a warning. `arises_from` takes gaps, kinds flagged `factual`, elements and theses with `modality: fact`, and `difficulty` or `problem` theses.
|
|
29
|
+
- Profiles: kind flags `stance` and `factual` (`docs/profiles.md`); `goal` is a kind the engine names when a profile enables `goal-without-breakdown`.
|
|
30
|
+
- Hints, enabled in both profiles: `object-from-inside`, `external-without-reflection`, `goal-without-breakdown`, `position-without-object`, `ought-without-fact` (natural processes first, GP-T5 p. 252, in place of the 1981 forecast), `design-the-natural`, `information-without-cell`, and across cycles `cells-from-information`.
|
|
31
|
+
- Lens `three-positions`, offered by `reflexive-protocol` (section 2 gets a fourth question: from which external position, and in what language, the next object scheme is drawn) and `positional-construction` (records `stance` and `acts_as`). `ingest-transcript` 0.3.0: step 0.4 "Cells first". `qualification-pass` 0.4.0: a check row asks whether a representation fits the place the position has taken (Ш10 А), read with `position-without-object`.
|
|
32
|
+
- `smd pack`: with board sets among the records, a "Cells to fill" part lists the latest cycle's elements of the kinds the profile flags `skeleton`. `smd apply` drops `arises_from` and `assigned_by` links to a removed item; a `smd compare` merge remaps them on imported elements, as it does `seen_from` and `in`. `smd revise` carries `stance` and the other new fields with the elements.
|
|
33
|
+
|
|
5
34
|
## 0.3.7 - 2026-10-29
|
|
6
35
|
|
|
7
36
|
Docs after the code (update plan step 10); no change to records, schema or commands.
|
|
@@ -48,7 +48,7 @@ A kind is data. Edit the `kinds` list of the profile file, for example `profiles
|
|
|
48
48
|
- `docs/data-model.md`, the list of kinds;
|
|
49
49
|
- a test in `tests/test_profile.py`: a record using the kind validates, and one with a typo is an error.
|
|
50
50
|
|
|
51
|
-
Meanings come from attributes, not ids: `shape: frame` marks a kind that holds function chips and has a `frame_state`, `shape: heading` draws the bold situation paragraph, `light_off: true` leaves a kind off the lighter screen (`--light`). Only a few kinds are named by id in code, and every profile must define them: `position`, `place_for_others`, `function`, `cooperation`, `gap` and `note` (`REQUIRED_KINDS` in `src/smd_engine/profile.py`), and `entry` when the profile enables the hint `entry`; the parser refuses a profile without them. A kind that needs behaviour of its own is code in the checks or renderers; the ids and where the engine names each are in `docs/profiles.md`.
|
|
51
|
+
Meanings come from attributes, not ids: `shape: frame` marks a kind that holds function chips and has a `frame_state`, `shape: heading` draws the bold situation paragraph, `light_off: true` leaves a kind off the lighter screen (`--light`). Only a few kinds are named by id in code, and every profile must define them: `position`, `place_for_others`, `function`, `cooperation`, `gap` and `note` (`REQUIRED_KINDS` in `src/smd_engine/profile.py`), and `entry` when the profile enables the hint `entry`; the parser refuses a profile without them. A hint of one profile's scheme (`src/smd_engine/validate/management.py`) may name that profile's kinds and relation kinds: it registers them in `@hint(id, kinds=..., relations=...)`, and a profile that enables it must define them. A kind that needs behaviour of its own is code in the checks or renderers; the ids and where the engine names each are in `docs/profiles.md`.
|
|
52
52
|
|
|
53
53
|
## Add a check
|
|
54
54
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.5
|
|
2
2
|
Name: smd-engine
|
|
3
|
-
Version: 0.
|
|
3
|
+
Version: 0.5.0
|
|
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
|
|
@@ -92,7 +92,7 @@ Examples with options are in `docs/commands.md`; `smd <command> --help` lists th
|
|
|
92
92
|
| `eval` | Compares a procedure run with an expected record; exit 1 below the thresholds |
|
|
93
93
|
| `revise` | Opens the next cycle of a board set and applies the human's sign-offs |
|
|
94
94
|
| `apply` | Applies a patch (add, set and remove by id or by transition number `n`, `board_notes`, state) to a board set as its next sub-version, then validates |
|
|
95
|
-
| `pack` | One Markdown file with a procedure, its roles, lenses, the data model and the records, for any model |
|
|
95
|
+
| `pack` | One Markdown file with a procedure, its roles, lenses, the data model, the cells to fill and the records, for any model |
|
|
96
96
|
|
|
97
97
|
## Data model on one screen
|
|
98
98
|
|
|
@@ -127,6 +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
131
|
|
|
131
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.
|
|
132
133
|
|
|
@@ -67,7 +67,7 @@ Examples with options are in `docs/commands.md`; `smd <command> --help` lists th
|
|
|
67
67
|
| `eval` | Compares a procedure run with an expected record; exit 1 below the thresholds |
|
|
68
68
|
| `revise` | Opens the next cycle of a board set and applies the human's sign-offs |
|
|
69
69
|
| `apply` | Applies a patch (add, set and remove by id or by transition number `n`, `board_notes`, state) to a board set as its next sub-version, then validates |
|
|
70
|
-
| `pack` | One Markdown file with a procedure, its roles, lenses, the data model and the records, for any model |
|
|
70
|
+
| `pack` | One Markdown file with a procedure, its roles, lenses, the data model, the cells to fill and the records, for any model |
|
|
71
71
|
|
|
72
72
|
## Data model on one screen
|
|
73
73
|
|
|
@@ -102,6 +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
106
|
|
|
106
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.
|
|
107
108
|
|
|
@@ -69,7 +69,7 @@ uv run smd frames cases/example_ru/pekarni-c2.board.yaml -o out/frames.html
|
|
|
69
69
|
| `eval` | Сравнивает прогон процедуры с ожидаемой записью; код 1 ниже порогов |
|
|
70
70
|
| `revise` | Открывает следующий цикл записи и применяет подписи человека |
|
|
71
71
|
| `apply` | Применяет правку (add, set и remove по id или по номеру перехода `n`, `board_notes`, state) к записи как её следующую подверсию и проверяет результат |
|
|
72
|
-
| `pack` | Один файл Markdown с процедурой, её ролями, линзами, моделью
|
|
72
|
+
| `pack` | Один файл Markdown с процедурой, её ролями, линзами, моделью данных, ячейками для заполнения и записями, для любой модели |
|
|
73
73
|
|
|
74
74
|
## Модель данных на одном экране
|
|
75
75
|
|
|
@@ -104,6 +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
108
|
|
|
108
109
|
Неизвестный профиль, доска или вид элемента - ошибка с именем элемента. Формат и ключи профиля: `docs/data-model.md`, раздел Profiles.
|
|
109
110
|
|
|
@@ -0,0 +1,121 @@
|
|
|
1
|
+
# Выдуманный учебный пример на схеме ОРУ Г.П. Щедровицкого (профиль
|
|
2
|
+
# management-four-boards): пекарни из cases/example_ru, где организатор общего
|
|
3
|
+
# производства управляет ночным замесом теста. Все четыре доски заполнены;
|
|
4
|
+
# каждый рабочий процесс идеализирован на отдельной доске процесса (`boards`).
|
|
5
|
+
record: board_set
|
|
6
|
+
schema_version: "0.3"
|
|
7
|
+
id: pekarni-oru-c1
|
|
8
|
+
case: example-pekarni
|
|
9
|
+
title: Пекарни на схеме ОРУ, экран после сессии 1
|
|
10
|
+
date: "2026-01-10"
|
|
11
|
+
cycle: 1
|
|
12
|
+
status: draft
|
|
13
|
+
profile: management-four-boards
|
|
14
|
+
sources: [s1]
|
|
15
|
+
# Доски процессов: каждая — отдельная доска (шаблон process профиля), под четырьмя
|
|
16
|
+
boards:
|
|
17
|
+
- {id: pb-dough, template: process, label: "ночной замес теста", seen_from: p-organiser,
|
|
18
|
+
unfolds: wp-dough}
|
|
19
|
+
- {id: pb-delivery, template: process, label: "доставка теста в пекарни",
|
|
20
|
+
seen_from: p-organiser, unfolds: wp-delivery}
|
|
21
|
+
elements:
|
|
22
|
+
# Оргдеятельностная доска: позиции и их самоопределение
|
|
23
|
+
- {id: p-organiser, board: od, kind: position, label: "организатор общего производства",
|
|
24
|
+
acts_as: manager, stance: external}
|
|
25
|
+
- {id: p-owner, board: od, kind: position, label: "владелец трёх пекарен", acts_as: leader,
|
|
26
|
+
stance: inside}
|
|
27
|
+
- {id: p-founder, board: od, kind: position, label: "учредитель общего цеха", acts_as: organiser}
|
|
28
|
+
- {id: p-chair, board: od, kind: position, label: "председатель ассоциации пекарен",
|
|
29
|
+
acts_as: politician}
|
|
30
|
+
- {id: p-reflexive, board: od, kind: reflexive_position,
|
|
31
|
+
label: "группа, оглядывающаяся на свою сессию", stance: reflexive}
|
|
32
|
+
- {id: g-plant, board: od, kind: goal, label: "тесто из общего цеха к весне",
|
|
33
|
+
seen_from: p-organiser, goal_source: breakdown, arises_from: [f-night]}
|
|
34
|
+
- {id: place-mills, board: od, kind: place_for_others, label: "мельницы региона"}
|
|
35
|
+
- {id: gap-shares, board: od, kind: gap, label: "кто управляет цехом, если мельницы войдут в долю?",
|
|
36
|
+
of: position}
|
|
37
|
+
# Система ОРУ: знания, идеальное состояние, программа, средства
|
|
38
|
+
- {id: k-retro, board: ot, kind: knowledge_retro,
|
|
39
|
+
label: "как пекарни работали три года: смены, потери, закупки", seen_from: p-organiser}
|
|
40
|
+
- {id: k-proj, board: ot, kind: knowledge_projective,
|
|
41
|
+
label: "варианты общего цеха: смены, логистика, доли", seen_from: p-organiser}
|
|
42
|
+
- {id: ideal, board: ot, kind: ideal_state, label: "пекарни получают тесто к 5 утра",
|
|
43
|
+
seen_from: p-organiser, modality: ought}
|
|
44
|
+
- {id: prog, board: ot, kind: programme, label: "пилот с двумя пекарнями, затем остальные",
|
|
45
|
+
seen_from: p-organiser}
|
|
46
|
+
- {id: means-shares, board: ot, kind: means, label: "договор о долях в общем цехе",
|
|
47
|
+
seen_from: p-organiser}
|
|
48
|
+
# Доска процесса «ночной замес теста»: его функции
|
|
49
|
+
- {id: fn-mix, board: pb-dough, kind: function, label: "замес"}
|
|
50
|
+
- {id: fn-proof, board: pb-dough, kind: function, label: "расстойка"}
|
|
51
|
+
- {id: fn-hand-over, board: pb-dough, kind: function, label: "передача теста водителю"}
|
|
52
|
+
# Доска процесса «доставка теста в пекарни»: функции и кооперация
|
|
53
|
+
- {id: fn-load, board: pb-delivery, kind: function, label: "погрузка"}
|
|
54
|
+
- {id: fn-deliver, board: pb-delivery, kind: function, label: "развоз к 5 утра"}
|
|
55
|
+
- {id: coop-delivery, board: pb-delivery, kind: cooperation,
|
|
56
|
+
label: "пекарь общего цеха, водитель, старший смены пекарни"}
|
|
57
|
+
# Аппарат руководства: места, наполнение, группы, клуб
|
|
58
|
+
- {id: post-director, board: ap, kind: post, label: "директор пекарни", fillers: [владелец]}
|
|
59
|
+
- {id: post-shift, board: ap, kind: post, label: "старший ночной смены"}
|
|
60
|
+
- {id: grp-bakers, board: ap, kind: group, label: "пекари ночной смены"}
|
|
61
|
+
- {id: club-assoc, board: ap, kind: club, label: "клуб ассоциации пекарен"}
|
|
62
|
+
# Управляемая полисистема: моносистемы, миссия, процессы, траектории, факты
|
|
63
|
+
- {id: mono-people, board: us, kind: monosystem, label: "система людей: пекари трёх пекарен",
|
|
64
|
+
seen_from: p-organiser}
|
|
65
|
+
- {id: mono-tech, board: us, kind: monosystem, label: "система процессов: тесто и выпечка",
|
|
66
|
+
seen_from: p-organiser}
|
|
67
|
+
- {id: mission, board: us, kind: mission, label: "свежий хлеб в районе к утру",
|
|
68
|
+
in: [mono-people], seen_from: p-founder}
|
|
69
|
+
- {id: self-motion, board: us, kind: self_motion, label: "пекари сами ищут, как уйти с ночи",
|
|
70
|
+
in: [mono-people], seen_from: p-organiser}
|
|
71
|
+
- {id: tr-natural, board: us, kind: trajectory, label: "каждая пекарня сама сокращает ночь",
|
|
72
|
+
in: [mono-people], seen_from: p-organiser, modality: fact, nature: natural}
|
|
73
|
+
- {id: tr-ought, board: us, kind: trajectory, label: "ночной замес уходит в общий цех",
|
|
74
|
+
in: [mono-people], seen_from: p-organiser, modality: ought, nature: both}
|
|
75
|
+
- {id: wp-dough, board: us, kind: work_process, label: "ночной замес теста", in: [mono-tech],
|
|
76
|
+
seen_from: p-organiser}
|
|
77
|
+
- {id: wp-delivery, board: us, kind: work_process, label: "доставка теста в пекарни",
|
|
78
|
+
in: [mono-tech], seen_from: p-organiser}
|
|
79
|
+
- {id: pl-functions, board: us, kind: functional_structure, label: "смены и их участки",
|
|
80
|
+
in: [mono-tech], seen_from: p-organiser}
|
|
81
|
+
- {id: pl-links, board: us, kind: link_structure, label: "кто кому передаёт тесто",
|
|
82
|
+
in: [mono-tech], seen_from: p-organiser}
|
|
83
|
+
- {id: pl-morphology, board: us, kind: morphology, label: "печи и график смен", in: [mono-tech],
|
|
84
|
+
seen_from: p-organiser}
|
|
85
|
+
- {id: pl-material, board: us, kind: material, label: "мука, вода, дрожжи", in: [mono-tech],
|
|
86
|
+
seen_from: p-organiser}
|
|
87
|
+
- {id: f-night, board: us, kind: fact, label: "ночная смена стоит треть фонда оплаты труда",
|
|
88
|
+
seen_from: p-organiser, epistemic: unverified, cites: ["s1#t=00:12:40"]}
|
|
89
|
+
relations:
|
|
90
|
+
- {from: p-owner, to: p-organiser, kind: shift, label: "другая позиция"}
|
|
91
|
+
- {from: p-organiser, to: wp-dough, kind: represents}
|
|
92
|
+
- {from: p-owner, to: post-director, kind: represents}
|
|
93
|
+
- {from: p-founder, to: mission, kind: represents}
|
|
94
|
+
- {from: p-chair, to: club-assoc, kind: represents}
|
|
95
|
+
- {from: p-organiser, to: wp-dough, kind: manages, label: "через договор о долях"}
|
|
96
|
+
- {from: p-organiser, to: means-shares, kind: produces}
|
|
97
|
+
- {from: wp-dough, to: means-shares, kind: uses}
|
|
98
|
+
- {from: p-founder, to: mission, kind: organises}
|
|
99
|
+
- {from: p-chair, to: p-organiser, kind: contends, label: "чей цех"}
|
|
100
|
+
- {from: p-owner, to: post-director, kind: belongs}
|
|
101
|
+
- {from: p-owner, to: post-shift, kind: leads}
|
|
102
|
+
- {from: post-director, to: post-shift, kind: subordinates}
|
|
103
|
+
- {from: grp-bakers, to: post-shift, kind: personal}
|
|
104
|
+
- {from: prog, to: mono-tech, kind: captures}
|
|
105
|
+
- {from: k-retro, to: f-night, kind: knows}
|
|
106
|
+
- {from: ideal, to: f-night, kind: refers, label: "из прошлого"}
|
|
107
|
+
- {from: tr-natural, to: tr-ought, kind: refers, label: "усилить"}
|
|
108
|
+
- {from: mono-tech, to: mono-people, kind: mechanism_of}
|
|
109
|
+
- {from: fn-mix, to: fn-proof, kind: flow}
|
|
110
|
+
- {from: fn-proof, to: fn-hand-over, kind: flow}
|
|
111
|
+
- {from: fn-hand-over, to: fn-load, kind: flow, label: "между досками процессов"}
|
|
112
|
+
- {from: fn-load, to: fn-deliver, kind: flow}
|
|
113
|
+
transitions:
|
|
114
|
+
- {n: 1, from: p-organiser, to: f-night, label: "прошлое объекта", cites: ["s1#t=00:12:40"]}
|
|
115
|
+
- {n: 2, from: f-night, to: ideal, label: "идеал в будущем"}
|
|
116
|
+
- {n: 3, from: ideal, to: post-shift, label: "кто держит смену"}
|
|
117
|
+
- {n: 4, from: post-shift, to: fn-hand-over, label: "кто передаёт тесто"}
|
|
118
|
+
state:
|
|
119
|
+
version: "0.1"
|
|
120
|
+
open: ["gap-shares"]
|
|
121
|
+
next_move: "спросить мельницы, войдут ли они в долю общего цеха"
|
|
@@ -11,6 +11,7 @@ uv run smd validate path/to/case --taxonomies path/to/taxonomies.yaml # check
|
|
|
11
11
|
uv run smd migrate path/to/case # report what moving the records to schema v0.3 changes; --write edits the changed lines in place, comments kept
|
|
12
12
|
uv run smd render cases/example/bakeries-c1.board.yaml -o out/screen.svg
|
|
13
13
|
uv run smd render cases/example/two-boards-c1.board.yaml -o out/two-boards.svg # a record on the classic-two-boards profile: two boards side by side
|
|
14
|
+
uv run smd render cases/example_ru/pekarni-oru-c1.board.yaml -o out/oru.svg # a record on the management-four-boards profile: G.P.'s scheme of ОРУ on four boards
|
|
14
15
|
uv run smd render cases/example/bakeries-c1.board.yaml --format html -o out/screen.html
|
|
15
16
|
uv run smd render cases/example/bakeries-c1.board.yaml --format md --lang en
|
|
16
17
|
uv run smd render cases/example/bakeries-c1.board.yaml --format mermaid
|
|
@@ -23,7 +24,7 @@ uv run smd graph cases/example/bakeries-c2.board.yaml --sources cases/example/so
|
|
|
23
24
|
uv run smd index cases/example/bakeries-c2.board.yaml --sources cases/example/sources.yaml --archive /local/sources -o out/index.html # every K, thesis, hypothesis, O, sign-off and element with its YAML line; a cite links to its file only when the file is in --archive, otherwise the source title is shown
|
|
24
25
|
uv run smd publish cases/example/bakeries-c2.board.yaml --sources cases/example/sources.yaml --out out/pub # validate, then write <id>_frames, <id>_cycle_frames, <id>_index, <id>_graph and <id> as HTML; nothing is written if validation fails; takes --lang, --light, --zoom, --notes, --archive, --strict, --taxonomies
|
|
25
26
|
uv run smd vault cases/example/bakeries-c2.board.yaml out/vault --sources cases/example/sources.yaml # Obsidian vault: a note per element, thesis, hypothesis, K and source; links as typed properties; the screen as a canvas
|
|
26
|
-
uv run smd pack solo-session cases/example/bakeries-c2.board.yaml --sources cases/example/sources.yaml -o out/pack.md # attach to any model; --sources carries the manifest, --taxonomies the taxonomy file
|
|
27
|
+
uv run smd pack solo-session cases/example/bakeries-c2.board.yaml --sources cases/example/sources.yaml -o out/pack.md # attach to any model; --sources carries the manifest, --taxonomies the taxonomy file; with board sets, the skeleton of the latest cycle as "Cells to fill"
|
|
27
28
|
uv run smd sources cases/example/sources.yaml --clean-room --deny-lineage earlier-concept
|
|
28
29
|
uv run smd sources path/to/sources.yaml --folder /local/folder
|
|
29
30
|
uv run smd sources path/to/sources.yaml --folder /local/folder --refresh [ids] # recompute sha256 of the named sources (default: every decision_log) and edit only the sha256 lines of the manifest
|
|
@@ -6,7 +6,7 @@ The validator accepts only the current schema version. A record with another `sc
|
|
|
6
6
|
|
|
7
7
|
## board_set: one cycle of a three-board screen
|
|
8
8
|
|
|
9
|
-
Top level: `id`, `case`, `title`, `date`, `cycle` (1, 2, ...), `revises` (id of the previous cycle), `reflected_from`, `status` (`draft` | `extracted` | `verified`, the last needs `checked_by`), `sources` (manifest ids), `lineage`, `profile`, `run`, `applied`, `elements`, `relations`, `transitions`, `qualifications`, `theses`, `hypotheses`, `ontology`, `signoffs`, `state`.
|
|
9
|
+
Top level: `id`, `case`, `title`, `date`, `cycle` (1, 2, ...), `revises` (id of the previous cycle), `reflected_from`, `status` (`draft` | `extracted` | `verified`, the last needs `checked_by`), `sources` (manifest ids), `lineage`, `profile`, `run`, `applied`, `boards`, `elements`, `relations`, `transitions`, `qualifications`, `theses`, `hypotheses`, `ontology`, `signoffs`, `state`.
|
|
10
10
|
|
|
11
11
|
- `profile`: the method profile the record follows, a string; `program-three-boards` when absent. The profile sets the boards, kinds, relation kinds and hints (see Profiles below); an unknown profile is an error.
|
|
12
12
|
- `run`: the procedure run that produced the record: `{procedure, version, model, date}`; `procedure` (a procedure id) is required. `model` is free text, what the runner reports about itself. Each procedure writes it at hand-over and replaces an earlier one; `smd eval` compares two records (`cases/example/golden/README.md`).
|
|
@@ -16,7 +16,7 @@ Top level: `id`, `case`, `title`, `date`, `cycle` (1, 2, ...), `revises` (id of
|
|
|
16
16
|
|
|
17
17
|
### Boards
|
|
18
18
|
|
|
19
|
-
The boards of the default profile, `program-three-boards`; `classic-two-boards` has `od` and `oo` only.
|
|
19
|
+
The boards of the default profile, `program-three-boards`; `classic-two-boards` has `od` and `oo` only; `management-four-boards` has `od`, `ot`, `ap` and `us` (`docs/profiles.md`, The management profile).
|
|
20
20
|
|
|
21
21
|
| `board` | Board | Content |
|
|
22
22
|
|---|---|---|
|
|
@@ -24,6 +24,19 @@ The boards of the default profile, `program-three-boards`; `classic-two-boards`
|
|
|
24
24
|
| `oo` | object (объектная) | frames, functions, models, concepts, standards |
|
|
25
25
|
| `s` | situation (ситуационная), `half: small \| big` | the group's own practice; the wider system of activity |
|
|
26
26
|
|
|
27
|
+
### Record boards
|
|
28
|
+
|
|
29
|
+
A profile may declare a board template (`per_record: true`, `docs/profiles.md`); a record then makes any number of boards of it, listed once in `boards`, and its elements name such a board in `board` like any other. In `management-four-boards` the template is `process`: each working process idealised «на отдельной доске» (GP-T5 p. 245).
|
|
30
|
+
|
|
31
|
+
```yaml
|
|
32
|
+
boards:
|
|
33
|
+
- {id: pb-dough, template: process, label: "ночной замес теста", seen_from: p-organiser, unfolds: wp-dough}
|
|
34
|
+
elements:
|
|
35
|
+
- {id: fn-mix, board: pb-dough, kind: function, label: "замес"}
|
|
36
|
+
```
|
|
37
|
+
|
|
38
|
+
Fields: `id` (no dot, since a dot separates a board from its half), `template`, `label` (drawn as "<template label>: <label>", e.g. «Доска процесса: ночной замес теста»), and optional `seen_from` (a position), `unfolds` (the element the board unfolds, of a kind among the template's `unfolds` when it lists any: a `work_process` for a process board) and `cites`. The ids `records` and `sources` are refused (layers of `smd graph`). Every part of the engine handles a record board as a board: the screen draws it below the profile's boards, the frames read it in a step of its own (`process-pb-dough`) and cut a zoomed step to it, `smd graph` gives it a plane, `smd vault` a folder, `smd index` a table of record boards, `smd compare` matches record boards by id, `smd revise` carries them into the next cycle and a patch may add, change and remove them (see Patches). A record without `boards`, or on a profile without templates, is handled exactly as before; `boards` is optional, so the schema stays 0.3.
|
|
39
|
+
|
|
27
40
|
### Elements
|
|
28
41
|
|
|
29
42
|
`id`, `board`, `kind`, `label` (as said or written, verbatim) and optional fields:
|
|
@@ -40,6 +53,13 @@ The boards of the default profile, `program-three-boards`; `classic-two-boards`
|
|
|
40
53
|
| `route` | `smd` or `triz`: the line of work the item came from; theses carry it too |
|
|
41
54
|
| `tags` | taxonomy id to the values the item takes in it, `{tier: [t1, t2]}`; checked against the taxonomy file. Theses, hypotheses and ontology records carry it too |
|
|
42
55
|
| `seen_from` | element id of the position the item is seen from |
|
|
56
|
+
| `stance` | kinds the profile flags `stance` only (`position`; the classic `reflexive_position` too): `inside` (внутренняя, a place in the structure), `reflexive` (рефлексивная), `external` (внешняя: outside the structure, drawing it as an object) (GP-Guide11 ¶35-36). `smd revise` carries it with the element |
|
|
57
|
+
| `acts_as` | positions only: the place the position takes: `organiser` (организатор), `leader` (руководитель), `manager` (управляющий), `politician` (политик, a fourth level above управление, GP-T5 pp. 242-243), `functionary` (функционер) (GP-Guide10 ¶7) |
|
|
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
|
+
| `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
|
+
| `assigned_by` | goals only: the position or place for others that passed the goal down |
|
|
61
|
+
| `modality` | `fact` or `ought` (модальность фактического и должного, GP-Guide11 ¶7); theses carry it too |
|
|
62
|
+
| `nature` | elements of an object board only: `natural`, `artificial` or `both` (естественное, искусственное; GP-STS; GP-T5 p. 252) |
|
|
43
63
|
| `performed_by` | functions only: the position or place for others that performs the function; the viewpoint stays in `seen_from` |
|
|
44
64
|
| `in` | containers, e.g. a function inside a frame |
|
|
45
65
|
| `epistemic` | `stated`, `hypothesis`, `unverified`, `checked` |
|
|
@@ -80,7 +100,7 @@ A thesis can carry a move too; there `from` may name theses as well as elements.
|
|
|
80
100
|
|
|
81
101
|
### Relations, transitions, qualifications, state
|
|
82
102
|
|
|
83
|
-
- **Relations** (`shift`, `flow`, `produces`, `uses`, `belongs`, `opposes`, `refers`, `represents`, `other`, the `relations` of
|
|
103
|
+
- **Relations** (`shift`, `flow`, `produces`, `uses`, `belongs`, `opposes`, `refers`, `represents`, `other`, the `relations` of every profile; a profile may add its own, as the management profile does) link elements, normally within a board. `shift` links two positions; `represents` goes from a position to its representation of an object. Relations and transitions take an optional `voice` (e.g. AI), so links an AI drew stay visible as such.
|
|
84
104
|
- **Transitions** are numbered 1..n and move between boards. They draw the trajectory of the group's thinking.
|
|
85
105
|
- **Qualifications** `K1..Kn`: `targets`, `text`, `short` (the legend's text when given), `by`, `voice` (who wrote it, e.g. AI drafting for the methodologist), `status` (`open` | `partly` | `closed`), `raised_in`, `closed_in` (cycle numbers).
|
|
86
106
|
- **State** is the one-line state after a cycle: `version`, `difficulty` (what failed in the previous cycle), `accepted`, `open`, `next_move`.
|
|
@@ -109,6 +129,7 @@ A thesis is a SessionFlow thesis card (frame 03) with the belt and kind of the c
|
|
|
109
129
|
| `route`, `tags` | as on elements |
|
|
110
130
|
| `raises` | K ids the thesis raised, e.g. an organisers' remark that became a qualification |
|
|
111
131
|
| `about` | board elements the thesis reads or comments on without changing them (`feeds` is for elements it produced or changed) |
|
|
132
|
+
| `modality` | `fact` or `ought`, as on elements |
|
|
112
133
|
| `move` | the structural move the group made in its talk (`accepted`) or the model's reading of it (`candidate`) |
|
|
113
134
|
| `cites` | source address, `s3#t=00:08:10` (Источник) |
|
|
114
135
|
|
|
@@ -224,23 +245,24 @@ state:
|
|
|
224
245
|
```
|
|
225
246
|
|
|
226
247
|
Top level: `id`, `case`, `applies_to` (the board's id), `version` (the board's new `state.version`, kept as text; an unquoted `5.8` is read as `"5.8"`, but quote it, since YAML reads `5.10` as `5.1`), `date`, `cites`, `notes` (the patch's own note), `title` (replaces the board's title), `board_notes` (see below), and:
|
|
227
|
-
- `add`: items appended to `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.
|
|
228
|
-
- `set`: `{id, <field>: value}` merged into the 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`.
|
|
248
|
+
- `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
|
+
- `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`.
|
|
229
250
|
- `board_notes`: text appended to the board's `notes`, before the lines for removals.
|
|
230
|
-
- `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. Links dropped: relations and transitions from or to it (the remaining transitions are renumbered 1..n), `reflected_from`, element `seen_from`, `performed_by` and `in`, qualification `targets`, thesis `feeds`, `about` and `raises`, hypothesis `targets` and `qualifications`, 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.
|
|
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.
|
|
231
252
|
- `state`: `accepted` and `open` entries are appended, `remove_open` entries dropped from `open`, `next_move` and `difficulty` replaced.
|
|
232
253
|
|
|
233
254
|
`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.
|
|
234
255
|
|
|
235
256
|
## Profiles
|
|
236
257
|
|
|
237
|
-
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.
|
|
258
|
+
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:
|
|
238
259
|
- `program-three-boards` (default): the program's screen (`screen: triangles`), boards `od`, `oo` and `s` (halves `small`, `big`), the 19 kinds above, every hint;
|
|
239
260
|
- `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. Example: `cases/example_ru/pekarni-oru-c1.board.yaml`.
|
|
240
262
|
|
|
241
263
|
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:
|
|
242
|
-
- **Kinds every profile defines:** `position`, `place_for_others`, `function`, `cooperation`, `gap`, `note`; also `entry` when the profile enables the hint `entry`. The checks, the frames switches and the fold counter name these ids; other meanings come from kind attributes (`shape: frame`, `light_off`) and the board flag `object`. No board id is fixed.
|
|
243
|
-
- **Reading step ids:** `entry`, `positions`, `places`, `small`, `big`, `old-frame`, `new-frame`, `object`, each at most once: the steps `smd frames` has titles and texts for.
|
|
264
|
+
- **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`).
|
|
265
|
+
- **Reading step ids:** `entry`, `positions`, `places`, `small`, `big`, `old-frame`, `new-frame`, `object`, `upper`, `process`, `apparatus`, `managed`, each at most once: the steps `smd frames` has titles and texts for. A step on a template is read once per record board, as `<step>-<board id>`.
|
|
244
266
|
|
|
245
267
|
`smd pack` reads `profile` in a procedure's front matter (`any` or a profile id). A procedure for another profile than the records' is refused (exit 2, "procedure is for profile ..."); a procedure it names is left out. `smd compare`, `smd frames --by cycle` and the cycle frames of `smd publish` take records of one profile; records of two profiles exit 2 with a message naming both.
|
|
246
268
|
|
|
@@ -261,6 +283,11 @@ The checks are in `src/smd_engine/validate/`, one module per subject, run in the
|
|
|
261
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`.
|
|
262
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.
|
|
263
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'").
|
|
264
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.
|
|
265
292
|
- **Warnings (v0.3):** `tags` or `detail.keys` used and no taxonomy file given.
|
|
266
|
-
- **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".
|
|
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).
|
|
@@ -22,12 +22,25 @@ Access note: fondgp.ru returned HTTP 403 to the fetch tool and 404 for `/lib/mmk
|
|
|
22
22
|
| GP1974r | Щедровицкий Г.П. О рефлексии (fragment of a 1974 work). Избранные труды | https://gtmarket.ru/library/basis/3961/3991 |
|
|
23
23
|
| GP1975 | Щедровицкий Г.П. Исходные представления и категориальные средства теории деятельности (1975). Избранные труды | https://gtmarket.ru/library/basis/3961/3973 |
|
|
24
24
|
| GP1981 | Щедровицкий Г.П. Принципы и общая схема методологической организации системно-структурных исследований и разработок // Системные исследования. Ежегодник 1981. М.: Наука, 1981 | https://gtmarket.ru/library/basis/3961/3967 |
|
|
25
|
-
| GP1983 | Щедровицкий Г.П., Котельников С.И. Организационно-деятельностная игра как новая форма организации и метод развития коллективной мыследеятельности // Нововведения в организациях. ВНИИСИ, 1983 (also Вопросы психологии, 1985, №3) | https://gtmarket.ru/library/basis/3961/3968 |
|
|
25
|
+
| GP1983 | Щедровицкий Г.П., Котельников С.И. Организационно-деятельностная игра как новая форма организации и метод развития коллективной мыследеятельности // Нововведения в организациях. ВНИИСИ, 1983 (also Вопросы психологии, 1985, №3); Избранные труды (1995) key [1983 c*], pp. 115-142. The gtmarket page header names G.P. alone and shortens the title; its source note reads [1983 с] | https://gtmarket.ru/library/basis/3961/3968 |
|
|
26
|
+
| GP1983a | Щедровицкий Г.П. Организационно-деятельностная игра как новая форма организации коллективной мыследеятельности // Методы исследования, диагностики и развития международных трудовых коллективов. М., 1983; Избранные труды key [1983 a]. A different text from GP1983 | https://www.fondgp.ru/publications/организационно-деятельностная-игра-6/ |
|
|
26
27
|
| GP1987 | Щедровицкий Г.П. Схема мыследеятельности — системно-структурное строение, смысл и содержание // Системные исследования. Методологические проблемы. Ежегодник 1986. М., 1987 | https://gtmarket.ru/library/basis/3961/3974 |
|
|
27
28
|
| GP-PP | Щедровицкий Г.П. Проблемы и проблематизация в контексте программирования процессов решения задач // Философия. Наука. Методология, 1997, гл. 11 (symposium talk; original date [UNVERIFIED]) | https://gtmarket.ru/library/basis/5484/5494 |
|
|
28
29
|
| GP-SMD | Щедровицкий Г.П. Перспективы и программы развития СМД-методологии // Философия. Наука. Методология, гл. 14 (talk, late 1980s; date [UNVERIFIED]) | https://gtmarket.ru/library/basis/5484/5497 |
|
|
29
30
|
| GP-OP | Щедровицкий Г.П. Заметки о понятиях «объект» и «предмет» // Философия. Наука. Методология, Приложение (date [UNVERIFIED]) | https://gtmarket.ru/library/basis/5484/5498 |
|
|
30
|
-
| GP-Guide9 | Щедровицкий Г.П. Путеводитель по методологии организации, руководства и управления. Раздел 9 «Проблемы и проблематизация» (lecture text;
|
|
31
|
+
| GP-Guide9 | Щедровицкий Г.П. Путеводитель по методологии организации, руководства и управления. Раздел 9 «Проблемы и проблематизация» (lecture text; М.: Дело, 2003, ред. А.Г. Реус; full text: Из архива Г.П. Щедровицкого, т. 4, М., 2000) | https://gtmarket.ru/library/basis/3344/3354 |
|
|
32
|
+
| GP1975a | Щедровицкий Г.П. Автоматизация проектирования и задачи развития проектировочной деятельности // Разработка и внедрение автоматизированных систем в проектировании (теория и методология). М., 1975; IT1995 pp. 414-436 | https://gtmarket.ru/library/basis/3961 |
|
|
33
|
+
| GP-STS | Щедровицкий Г.П. «Естественное» и «искусственное» в социотехнических системах. Talk at the Институт проблем управления, 26.03.1975; first published 1992; IT1995 pp. 437-448 | https://gtmarket.ru/library/basis/3961 |
|
|
34
|
+
| IT1995 | Щедровицкий Г.П. Избранные труды / ред.-сост. А.А. Пископпель, Л.П. Щедровицкий. М.: Шк. Культ. Полит., 1995. "IT p. N" cites its page | https://gtmarket.ru/library/basis/3961 |
|
|
35
|
+
| GP-Guide | Щедровицкий Г.П. Путеводитель по методологии организации, руководства и управления. Хрестоматия. М.: Дело, 2003; ред. А.Г. Реус (an abridged edition of the 1981 lectures in GP-T4). "GP-GuideN ¶M" is section N, paragraph M counted from the section's first text block | https://gtmarket.ru/library/basis/3344 |
|
|
36
|
+
| GP-Guide4 | GP-Guide, Раздел 4 «Типологические характеристики организации, руководства и управления» | https://gtmarket.ru/library/basis/3344/3349 |
|
|
37
|
+
| GP-Guide5 | GP-Guide, Раздел 5 «Системно-объектная схема управления» | https://gtmarket.ru/library/basis/3344/3350 |
|
|
38
|
+
| GP-Guide8 | GP-Guide, Раздел 8 «Первое системное представление аппарата руководства» | https://gtmarket.ru/library/basis/3344/3353 |
|
|
39
|
+
| GP-Guide10 | GP-Guide, Раздел 10 «Процесс вхождения в место руководителя» | https://gtmarket.ru/library/basis/3344/3355 |
|
|
40
|
+
| GP-Guide11 | GP-Guide, Раздел 11 «Программа действий» | https://gtmarket.ru/library/basis/3344/3356 |
|
|
41
|
+
| GP-Guide2004 | Путеводитель по основным понятиям и схемам методологии организации, руководства и управления: Хрестоматия по работам Г.П. Щедровицкого / сост. А.П. Зинченко. М.: Дело, 2004. Cited by PDF page | - |
|
|
42
|
+
| GP-T4 | Щедровицкий Г.П. Оргуправленческое мышление: идеология, методология, технология. Курс лекций (1981). Из архива Г.П. Щедровицкого, т. 4. М., 2000. The full text behind GP-Guide; cited by book page | https://www.koob.ru/shchedrovitsky/ |
|
|
43
|
+
| GP-T5 | Щедровицкий Г.П. Организация, руководство, управление (2) = Методология и философия оргуправленческой деятельности. Lectures of 1988. Из архива Г.П. Щедровицкого, т. 5. М., 2002. Cited by book page; where it disagrees with GP-T4 or GP-Guide, the engine follows GP-T5 | https://www.koob.ru/shchedrovitsky/ |
|
|
31
44
|
| PG1987 | Щедровицкий П.Г. К анализу топики организационно-деятельностных игр. Пущино, 1987 | https://shchedrovitskiy.com/organizacionno-dejatelnostnaja-igra/ |
|
|
32
45
|
| PG2019 | Щедровицкий П.Г. Онтология мыследеятельности как общественный идеал. Ч. I (talk, 08.11.2019, 40 years of ОДИ) | https://shchedrovitskiy.com/ontolohiya-misledeyatelnosti-kak-obshchestvenniy-ideal/ |
|
|
33
46
|
| PG-GT | Щедровицкий П.Г. Эволюция игротехники организационно-деятельностных игр (lecture; date [UNVERIFIED]) | https://shchedrovitskiy.com/igrotehnika_organizacionno_deyatelnostnih_igr/ |
|
|
@@ -0,0 +1,109 @@
|
|
|
1
|
+
# Profiles: boards, kinds and the screen as data
|
|
2
|
+
|
|
3
|
+
A profile is one YAML file that sets what a record may hold and how the engine draws it: the boards and where they stand on the screen, the kinds of elements, the relation kinds, the hints, the groups `smd compare` matches, the reading order of `smd frames` and the SessionFlow picks. `src/smd_engine/profile.py` loads it. What a record does with its profile (the `profile` key, the two shipped profiles, the fixed ids) is in `docs/data-model.md`, section Profiles.
|
|
4
|
+
|
|
5
|
+
## Where profile files live
|
|
6
|
+
|
|
7
|
+
Profiles are files in `profiles/` of the install: the repository folder in a checkout, `smd_engine/assets/profiles` in the wheel (`profiles_dir()` takes the packaged folder when it exists). A record names a profile by its id, the file name without `.yaml`; there is no per-case profile path. A new profile is a new file in `profiles/` and, for a wheel, a rebuild.
|
|
8
|
+
|
|
9
|
+
## Format
|
|
10
|
+
|
|
11
|
+
| Key | Meaning |
|
|
12
|
+
|---|---|
|
|
13
|
+
| `id`, `title` | the file name; `{ru, en}` |
|
|
14
|
+
| `screen` | `regions` (default) or `triangles`; see Screen and layout |
|
|
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 |
|
|
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
|
+
| `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
|
+
| `compare_groups` | name to kinds matched against each other by `smd compare`; a kind in no group is matched in `other` |
|
|
20
|
+
| `compare_skip` | kinds `smd compare` leaves out (the program's: `entry`, `note`) |
|
|
21
|
+
| `reading` | reading steps of `smd frames`; see Reading steps |
|
|
22
|
+
| `sessionflow` | optional: the picks behind the first three SessionFlow questions (`who`, `where`, `what_for`); without it `--format sessionflow` is refused |
|
|
23
|
+
|
|
24
|
+
Flags are `true` or `false` and default to `false`.
|
|
25
|
+
|
|
26
|
+
`shape` is how the screen draws a kind: `marker` (entry), `figure` (position), `ellipse` (dashed, place for others), `question` (gap), `frame` (holds function chips; dashed when new), `heading` (bold text across the region on a board with halves, a box elsewhere; the program's situation), `paragraph` (text across the region on a board with halves, a box elsewhere), `box`.
|
|
27
|
+
|
|
28
|
+
The board colours are used everywhere a board is coloured: the screen (background and ink), the map of `smd frames --zoom`, the planes and points of `smd graph` and the folders and canvas cards of `smd vault` (ink), so the three agree.
|
|
29
|
+
|
|
30
|
+
## Screen and layout
|
|
31
|
+
|
|
32
|
+
Automatic layout places each element in the region of its board, or of its half, kind by kind in the order of `kinds`. The halves of a board are two regions, 10 units to each side of `split`.
|
|
33
|
+
|
|
34
|
+
Boards whose regions overlap vertically form a row. When a region's content runs past its bottom, the whole row grows downwards by the same amount, and every row below moves down by it. A region keeps its width: a dense board grows, it does not spread sideways.
|
|
35
|
+
|
|
36
|
+
`screen: regions` draws each board as a rectangle around its region (20 to each side, 50 above for the board's name, 10 below; `src/smd_engine/screen.py`), with its name at the top left. A board with two halves gets a dashed line at `split` and the names of its halves above it. A profile has at least one board. Any number of boards, with or without halves, can stand anywhere on the screen, within these rules:
|
|
37
|
+
- a board as drawn lies on the screen: `20 <= x0 < x1 <= 1580`, `150 <= y0 < y1`;
|
|
38
|
+
- no two boards overlap as drawn: regions side by side are at least 40 apart, one above the other at least 60 (touching rectangles are allowed, as the classic profile's at x 800);
|
|
39
|
+
- the boards of a row overlap vertically pairwise: a tall board beside two stacked boards would join them into one row, where the upper one could not push the lower one down, so the profile is refused;
|
|
40
|
+
- `split` lies inside the region, more than 10 from each edge (`x0 + 10 < split < x1 - 10`).
|
|
41
|
+
|
|
42
|
+
`screen: triangles` is the program's screen (Girenko, day 4, 17.10.2026): the first two boards without halves on top, the third below them, drawn as three triangles that meet at the apex (800, 440). It takes exactly three boards in that order, each drawn within its part of the screen: the first left of the apex and above it (`60 <= x0 < x1 <= 780`, `150 <= y0 < y1 <= 430`), the second right of it (`820 <= x0 < x1 <= 1540`, the same y), the third between the apex and the lower corners (`60 <= x0 < x1 <= 1540`, `490 <= y0 < y1 <= 850`). The top two parts lie inside their shapes; the third reaches past the slanted edges at its top corners, as the program's region does (its items start at y 625, under the names of the halves). The triangles are the screen's fixed geometry, and the regions place the items inside them. The top row grows as in `regions` and moves the apex down with it; the board below does not grow: when it overflows, it extends below its triangle into a band as wide as the screen, each half to its side of `split`. The program profile sets `split: 800`, so its halves meet under the apex (regions to 790 and from 810).
|
|
43
|
+
|
|
44
|
+
The map beside a step of `smd frames --zoom` follows the screen: the three triangles for `triangles`, the rectangles of the regions for `regions`. A board's count of elements in the step stands in its outline: centred in a rectangle, at a fixed point inside a triangle. A step cut to a board takes that board's rectangle, or to a half the part up to 10 past `split`.
|
|
45
|
+
|
|
46
|
+
## Board templates
|
|
47
|
+
|
|
48
|
+
A board with `per_record: true` is a template: it is not drawn itself, and each record makes its own boards of it (`boards` in the record, `docs/data-model.md`, Record boards). Keys: `id`, `label: {ru, en}`, `colour`, `kinds` (the kinds its boards take; an element of another kind on such a board is an error), `unfolds` (optional: the kinds of the element a record board of it may `unfold`; any kind when absent), and the flags `object` and `needs_position` (a record board with no `seen_from` is warned). It takes no `region`, `halves` or `split`. A kind whose `home` is the template must be among its `kinds`; on a record board the template's kinds are never warned off their home. The `triangles` screen takes no templates.
|
|
49
|
+
|
|
50
|
+
The record's boards stand below the profile's boards, in the record's order: rows of as many boards as the widest row of the profile, across the span of its boards, as close as the drawing margins allow (40 side by side, 60 one above the other), each region 300 tall (`screen.record_regions`). They grow like any row. A reading step whose `board` is the template (`{step: process, board: process, pick: {board: process}}`) is repeated for each record board of it, its filter narrowed to that board; the frame takes the id `<step>-<board id>` and the board's label as its title.
|
|
51
|
+
|
|
52
|
+
Limit: a screen shape other than rectangles around regions or the program's triangles needs a new `screen` value, drawn in `render/svg.py` and `render/frames_page.py`.
|
|
53
|
+
|
|
54
|
+
## Ids every profile defines
|
|
55
|
+
|
|
56
|
+
The engine names a few kinds by id; the parser refuses a profile without them ("missing kinds the engine names"):
|
|
57
|
+
|
|
58
|
+
| Kind | Where the engine names it |
|
|
59
|
+
|---|---|
|
|
60
|
+
| `position` | `seen_from`, `reflected_from`, `performed_by`, `shift` and `represents` links, ontology `valid_for` and `subjects`, the hint on positions, `seen_from` kept by a `smd compare` merge; `acts_as` and the hint `position-without-object`; `assigned_by` |
|
|
61
|
+
| `place_for_others` | `performed_by` and ontology `valid_for` may name it; the hint on positions; the frames switch "places" |
|
|
62
|
+
| `function` | `performed_by`; the hint on new frames; the frames switch "functions"; the performer line of SessionFlow |
|
|
63
|
+
| `cooperation` | ontology `cooperation` |
|
|
64
|
+
| `gap` | `of` and `scheme`; a breakdown in `arises_from` and for the hint `goal-without-breakdown`; the hint on gaps; the frames switch "places"; a board holding only gaps and notes counts as empty |
|
|
65
|
+
| `note` | the counter a folded region becomes (`smd frames --zoom`) |
|
|
66
|
+
| `entry` | only when the profile enables the hint `entry` |
|
|
67
|
+
| `goal` | only when the profile enables the hint `goal-without-breakdown`; takes `goal_source`, `arises_from` and `assigned_by` |
|
|
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
|
+
|
|
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`).
|
|
71
|
+
|
|
72
|
+
## The management profile
|
|
73
|
+
|
|
74
|
+
`management-four-boards` is G.P. Shchedrovitsky's scheme of organisation, leadership and management (ОРУ), gates Ш13 В and Ш15 В: the org-activity board `od` and the upper system of ОРУ `ot` on top, the apparatus of leadership `ap` and the managed polysystem `us` below, `ot` above `us` (GP-T5 p. 239: «Внизу идет естественный процесс изменения объекта, а вверху — процесс преобразования»). `ot` and `us` are flagged `object`. Example: `cases/example_ru/pekarni-oru-c1.board.yaml`. GP-T5 is т. 5 of the Archive (lectures of 1988); where G.P.'s texts of different periods disagree the latest wins, and the earlier view stays as a comment in the profile file, not as a kind or hint.
|
|
75
|
+
|
|
76
|
+
| Board | Kinds (G.P.'s terms; GP-T5 pages unless marked) |
|
|
77
|
+
|---|---|
|
|
78
|
+
| `od` org-activity | `position` (`acts_as`: организатор, руководитель, управляющий, политик, функционер; `stance`), `reflexive_position`, `goal`, `place_for_others` |
|
|
79
|
+
| `ot` system of ОРУ, upper | `knowledge_retro`, `knowledge_projective` («службы по организации знаний — как ретроспективных, так и прожективных», p. 241), `ideal_state` (the second state, the future, pp. 229, 238), `programme` (pp. 216, 245-246), `means` (рычаги, каналы; организованности, pp. 199, 222-223), `functional_place` (GP-Guide2004 pdf 138), `model` (конфигуратор, p. 151), `concept`, `cooperation` |
|
|
80
|
+
| `process` template: a process board per working process | `function` (its `home`), `cooperation`, `gap`, `note`; `unfolds: [work_process]`; flagged `object` and `needs_position` |
|
|
81
|
+
| `ap` apparatus of leadership | `post` (место; `fillers` = наполнение, pp. 177, 192-193; a role), `group` (неформальная группа, pp. 153-154, 224-225), `club` (where politics is done, p. 254) |
|
|
82
|
+
| `us` managed polysystem | `monosystem` (a container: «реально мы имеем дело с полисистемами», pp. 206-213), `mission` (p. 211, set by `organises`, p. 213), `self_motion` (p. 170), `trajectory` (with `modality`: the natural and the artificial-natural course, pp. 231, 244), `work_process` (рабочий процесс, the object of управление, p. 244), the five planes of the system (p. 201; four in GP-T4, five from p. 205): `work_process` for the processes, `functional_structure`, `link_structure`, `morphology` (организованности материала), `material`; `fact` (flagged `factual`) |
|
|
83
|
+
|
|
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
|
+
|
|
86
|
+
Hints: the classic set and those of gates Ш8-Ш12, plus the hints of this scheme (`docs/data-model.md`, Checks). 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
|
+
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
|
+
|
|
90
|
+
## Reading steps
|
|
91
|
+
|
|
92
|
+
`reading` lists the steps of `smd frames --by reading`, each `{step, board, pick}`:
|
|
93
|
+
- `step`: one of `entry`, `positions`, `places`, `small`, `big`, `old-frame`, `new-frame`, `object`, `upper`, `process`, `apparatus`, `managed` (the last four for the boards of G.P.'s management scheme), each at most once (the steps `smd frames` has titles and texts for, `render/frames_text.py`);
|
|
94
|
+
- `board`: the board, or the half (`s.small`), a zoomed step is cut to; or a template, for a step read once per record board of it;
|
|
95
|
+
- `pick`: what the step adds, either a filter or `old-frames` / `new-frames` (frames and their contents, by `frame_state`).
|
|
96
|
+
|
|
97
|
+
A filter is a mapping of at least one of `kinds` (a list of kind ids), `board`, `half` (a half of that board; of any board when `board` is absent) and `frame_state` (`old` or `new`). An element passes when it matches every key given. A step adds only what earlier steps did not show; an empty step is skipped. The SessionFlow picks are filters of the same form.
|
|
98
|
+
|
|
99
|
+
## Checks of a profile file
|
|
100
|
+
|
|
101
|
+
A malformed profile is an error of every record that names it (`error: profile: <id>: ...`), and like a schema error it stops the checks of that record:
|
|
102
|
+
- a section of the wrong type, a key outside the tables above (at the top, in a board, kind, reading step or filter), a flag other than `true` or `false`, `hints` other than a list of strings, `relations` other than a list of ids and `{id, label}` mappings;
|
|
103
|
+
- a duplicate board, kind or reading step id; a missing kind of the table above;
|
|
104
|
+
- no boards; `halves` other than `none` or a list of distinct halves; a board off the screen or overlapping another as drawn, a row whose boards do not overlap vertically, a `split` on a board without two halves or outside its region, a colour other than `#rrggbb`, a `screen` other than `regions` or `triangles`, a `triangles` screen with other than its three boards or with a board outside its part;
|
|
105
|
+
- a duplicate relation kind or hint id, a hint id the engine does not have, a relation kind outside the engine's without a label, a relation kind an enabled hint names and the profile lacks;
|
|
106
|
+
- a `home` that is neither a board nor a template; a `shape` outside the list;
|
|
107
|
+
- a template with a key outside its list (`region`, `halves`), `per_record` other than `true`, no kinds or an unknown kind in `kinds` or `unfolds`, a kind homed on it but not among its `kinds`, or on the `triangles` screen; a reading step on a template whose filter has `half` or another `board`; a board or template id `records` or `sources`; a kind in `compare_groups` or `compare_skip` that is not in `kinds`;
|
|
108
|
+
- a reading step other than the ids above, a step `board` that is neither a board nor a half of one, a filter with an unknown kind, board or half, `kinds` written as a string;
|
|
109
|
+
- a SessionFlow block other than `who`, `where`, `what_for`, or a pick that is not a valid filter; an empty filter `{}`, which would match every element.
|