Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,11 @@ The package version runs on its own semver; the schema it is generated from is `

## Unreleased

## 0.137.0 (2026-11-19)

- **`carry_of(map, point, maps)`, the map-space profile's frame reading** (schema-dist serial 139, rules 13 and 14), the TypeScript SDK's `carryOf` with the same answer. A child Map says where it lies on the Map its `parent_map` names with `x_parent_frame`, a box `[x0, y0, x1, y1]` in the parent's pixels; `carry_of` carries a point on a Map up that chain, one level at a time by each level's own frame, in 64-bit floats, and answers `{parent_frame, lint, points, stop}`: the Map's own frame as written or None, what is wrong with it (`no_parent`, `not_four_numbers`, `not_a_box`), the point on each Map it reaches, and why the walk ended (`top`, `dangling`, `cycle`, `no_frame`, `no_carry`). Its types are `CarryOf`, `CarryPoint`, `CarryStop` and `CarryLint`. `map_space` and `layout_of` do not read the key.
- **The schema pin moves to `v0.34.1-dist.139`** (canonical 00.34.01 unchanged, no schema file moved, `_schema.py` changes only its provenance lines): the map-space page's rules 13 and 14 and the fixture's 66 `frame_cases`, which `carry_of` answers as published; the map-space reading's own cases are unchanged.

## 0.136.0 (2026-11-19)

- **The schema pin moves to `v0.34.1-dist.138`** (serials 137 and 138; canonical 00.34.01 unchanged, no schema file moved, `_schema.py` changes only its provenance lines). Serial 137 publishes the `by-links-3d` method on the layout profile's page, with its fixture (116 cases) and directions table, adds four map-space cases (a Map's `width` or `height` that is a whole number, 0 and under 0 included, is answered as written; a slot measured on a Map with no placed point of its own is None), three layout-reading cases and two `unplaced` cases. Serial 138 adds cases to the lens (246), charter (16 design) and report (9 talk) fixtures. Every case passes as published.
Expand Down
8 changes: 4 additions & 4 deletions codegen/schema-dist/MANIFEST.json
Original file line number Diff line number Diff line change
Expand Up @@ -162,8 +162,8 @@
"profiles/layout.md": "ffbf41c331b704db8dbddd2887e70787df894b5c7c9555ba5321f31349c44685",
"profiles/lens.fixture.json": "eef4348884994c5e99fffa81c4ad5b9a8f26f722d72e9a896db5214ae44dcb13",
"profiles/lens.md": "ee1f46c6ef7d2626c3c47230d4f99315dd03da91cf429c1015b10b263d7cb5da",
"profiles/map-space.fixture.json": "40c2152f28e74f6d9518698fda6508ffedf05199f4695c0d124dd79e75d8fd57",
"profiles/map-space.md": "1d2e3626170a90c3d7cea5e78809ac43d25588f726d7537fed9a4e520a3ba05c",
"profiles/map-space.fixture.json": "f1d832d63b9b0d071bd1bc1c2d16a97b3b9db405a9e01a63451ca74ef0cec657",
"profiles/map-space.md": "f3c6b7f69da6b3ef9e27ef81699d910b17f4757bac173a08b8118d5df9ec7222",
"profiles/message.fixture.json": "418964e564db054c8e969a157f6e29e82499c04180d10bea8c55ac9f5bf5e279",
"profiles/message.md": "768e09ef6370deb2af331da8d665128746553498da2cb6e065bbdcaa326d6d2c",
"profiles/names.fixture.json": "7d012081b5df7bab3e2223333f87a347417c3061c62b38947fc952e8c4d2377a",
Expand All @@ -182,7 +182,7 @@
"profiles/spine.md": "6bd367c3f4b101878fbc54a3c8c806630b7760173f24fef995db801b6103d92e",
"profiles/strand.fixture.json": "7bc2d2dae11c0722b1db987c070b249ddcbc55b81683c4bfa26900c7ffe0fc53",
"profiles/strand.md": "2a9bd36814a0de80a68180d2d75d3ef9d2539b9dcd52165f20b8ef0821575488",
"README.md": "f0847e0633639df9c66952bd1ce0c4330379dbcdd0ee854c8eb62e9e8b7c509a",
"README.md": "6739b4b60bffc9102335e1153b35b84b0641e1b3bf3e07f6be8b77f6e4862dea",
"schema/ability.yaml": "af185b2d22a5985ac323e6227a95df287fffaae0e5fca502976a02c2754f71b2",
"schema/base_properties.yaml": "ec3724ceb2faca973e431a2e2ff946e55bfb55b6b8d78689b6b22d0cfb7c9a2e",
"schema/character.yaml": "dc291b206121bd23c69cb89e01a0523eb2f71b4a247116dd6a1fa4bc227ff145",
Expand All @@ -209,7 +209,7 @@
"schema/zone.yaml": "cca04ee498fb813fa18b96f1ac99816e7f1a8ae1fb9e21c48b37620dbb674856",
"schema.json": "581dc7b5e890acc06b1c89b0d7bdcc2f20f54f52d5a3b4af8c5a184e1e6fd48c",
"SECURITY.md": "939ee364b06f0b749bdd4cbe66b2fe49322c95abe732650ec4ef062a0c03820a",
"VERSION": "8ca53fe26df015f876768a285e03bc7f0c20fd15d460eed65514e083dc8e0f20",
"VERSION": "a5be0891b9dbfde6084151366e6568ef639d2f13e5f94ebe826a1e2ce4e0acbc",
"views.fixture.json": "6fda45c2d36cc82a613a4b4d99d14ba9646db2c5bf912b82e68c6b62b20441c1",
"views.json": "f4d06ee16bd6c66fc28cf27146b8d199c85164e5deecabafc23af53408746fe0",
"walk/lint_folder.py": "28efffa3a39d7f2ceaf69cae5c4ddce023e4989e7a5d2c26c1b4d4815eff386e",
Expand Down
2 changes: 1 addition & 1 deletion codegen/schema-dist/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Each serial (one numbered publication of these files, tagged `v<schema version>-
| `presentation.json` | default colour group and icon per type (`family` names the group by its colour: `blue`, `green`, `pink`, `amber`, a visual aid for drawing the 22 types, not part of the standard), and the four colours as light/dark pairs. Defaults: tools may override them. The colours were checked for colour-vision deficiency, so re-run that check before changing one. Each type also lists its `public` fields: what the platform shows of an element a reader knows of but does not see whole, beside its name and description |
| `pairs.json` | the link a drag between two types writes, for the pairs of the 22 types a tool may offer (same-kind pairs and fields that name a role are absent by ruling). Each key names the pair by its two type slugs in alphabetical order (`ability+character`); `on` is the type that carries the field, `field` the field's name, and `holds` whether the drop puts the dragged element inside the target (one square under the other) or only draws a line. Presentation, as `presentation.json` is, not part of the standard: a tool that offers drags reads this file and offers nothing else, and a pair absent here draws no line |
| `views.json` | how an element is shown, by its kind: for a report, a charter, a message and a line in a room, which field gives the one sentence a card or a list row shows, which fields lead the page, which fold, and which layout draws it; and the marks shown at the head of any element's page. A kind with no row draws as its type draws today. Presentation, as `presentation.json` is, not part of the standard: each tool keeps its own drawing and reads the row. `views.fixture.json` holds the cases a reader replays (the row that wins, the sentence, the marks in order) and a cite for every field a row names |
| `profiles/` | extension profiles: one page per named extension field or convention that tools agree to read the same way (`x_identity_key`, one being in several worlds; `atlas_calendar`, a world's own calendar; `x_packet_*`, a work item's elements with a reason each; `x_review_*`, proposed and checked marks; `room`, a convention profile: the ten type-and-supertype pairs a world's working layer holds (a parlor's lines and boards, work items, reports), and the rule that a lore view leaves them out; `message`, a convention profile: a message between a world's members (a Narrative with supertype Message), to whom it is addressed, whether its sender is proved, and each reader's read mark; `checks`, machine-checkable house rules on a world's Charter; `x_names`, a world's own words for the 22 types, on the World; `map-space`, a convention profile: how a reader turns Map, Marker, Pin and Zone rows into geometry (a Map's frame, a Zone's outline in marker order, a Pin's point; z an elevation, never a height), and the layout keys: `x_layout` on a Map (the Map is a drawing of its elements: how it was drawn, and the ground it stands on), `x_hand` on a Pin (placed by hand, kept by a new lay-out), and a small layout reading of one Map; `spine`, a world that maps a software ecosystem: a closed list of kinds as supertypes, eleven `x_spine_*` keys, a day count from a stated day 0; `import-map`, per source tool, from that tool's own tags to the 22 types, which an import offers the user and never applies silently, LegendKeeper first; `address`, a convention profile: one element's three spellings, the site's address and the two `ow://` text forms, with an optional moment and lens, the rule that a field holding one is public text, never resolved, and when two ids are the same id; `lens`, a convention profile: a saved way of reading a world (a Construct with supertype Lens), its links the anchors, `x_lens` the recipe (how far, which types, how far back, how much), and the one resolution every reader agrees on; `charter`, a convention profile: a world's reading aids, the Charter (the rules for people and AIs here), the Guide (start here) and the Domains (the places in the world), each marked with `x_charter_of`, and the one packet every tool shows first at a world's door; `strand`, a convention profile: one story in a world in miniature, a Narrative, one of its Events, that Event's place, the story's protagonist and where the hero is now, named on the World by `x_strand`'s three ids and read through four existing links, never one slot filled from another; `record`, a convention profile: one run of a game kept in the world its Characters live in, an Event marked by `x_record` (the game, when it was played, and optionally the engine's version, the seed, the outcome and each Character's seat) with its chronicle and each Character's stories as Narratives, and a character's records read from the Event's `characters` and the stories' `protagonist` or `narrator`, never a field on the Character; `landing`, a convention profile: a world's first picture at a door, read from the lens profile's graph, its most-linked Characters each with what it links, the nodes no head reaches, and a small world's gaps (an orphan, a near-orphan, a Character with no place, a Location nobody is in), each an invitation to make the world bigger, with nothing stored; `report`, a convention profile: work done, left in the world by a stretch of work or a closed talk, a Narrative with supertype Report and the room's mark, handed in by the reporter's AI with its own text and completed by the world's keeper with a summary, a link to every element it touched and a line per change in `consequences`, the work items it answers named in `x_report_answers`; `layout`, a convention profile: the default layouts, three ways to draw a world nobody has laid out, `by-kind` (the whole graph, read from the graph alone, each kind round a circle, the same points to the last bit in every tool), `around` (one element and what links to it, on rings, read from the graph alone) and `by-links-3d` (the whole graph in three dimensions by its links, with the world's Maps and Pins as a plate its pinned elements stand on), the method words a layout map names under map-space's rule 8, and `unplaced`, the one reading of which elements a saved layout map does not place). What it holds, how a reader reads it, what a writer must keep. A profile may carry a data file beside its page (`import-map.json`, the table a door loads). A profile with a `<name>.fixture.json` beside it has a conformance fixture: cases a reader must pass; the report profile has a second, `report-lines.fixture.json`, the lines of its `consequences`, and the layouts profile has a second, `layout-by-links-3d.fixture.json`, with the directions table `layout-by-links-3d.directions.json` it names by its sha256 |
| `profiles/` | extension profiles: one page per named extension field or convention that tools agree to read the same way (`x_identity_key`, one being in several worlds; `atlas_calendar`, a world's own calendar; `x_packet_*`, a work item's elements with a reason each; `x_review_*`, proposed and checked marks; `room`, a convention profile: the ten type-and-supertype pairs a world's working layer holds (a parlor's lines and boards, work items, reports), and the rule that a lore view leaves them out; `message`, a convention profile: a message between a world's members (a Narrative with supertype Message), to whom it is addressed, whether its sender is proved, and each reader's read mark; `checks`, machine-checkable house rules on a world's Charter; `x_names`, a world's own words for the 22 types, on the World; `map-space`, a convention profile: how a reader turns Map, Marker, Pin and Zone rows into geometry (a Map's frame, a Zone's outline in marker order, a Pin's point; z an elevation, never a height), and the layout keys: `x_layout` on a Map (the Map is a drawing of its elements: how it was drawn, and the ground it stands on), `x_hand` on a Pin (placed by hand, kept by a new lay-out), and a small layout reading of one Map; and `x_parent_frame` on a child Map, the box on its parent where it lies, each axis by its own ratio, with a small reading that carries a point on it up its parents; `spine`, a world that maps a software ecosystem: a closed list of kinds as supertypes, eleven `x_spine_*` keys, a day count from a stated day 0; `import-map`, per source tool, from that tool's own tags to the 22 types, which an import offers the user and never applies silently, LegendKeeper first; `address`, a convention profile: one element's three spellings, the site's address and the two `ow://` text forms, with an optional moment and lens, the rule that a field holding one is public text, never resolved, and when two ids are the same id; `lens`, a convention profile: a saved way of reading a world (a Construct with supertype Lens), its links the anchors, `x_lens` the recipe (how far, which types, how far back, how much), and the one resolution every reader agrees on; `charter`, a convention profile: a world's reading aids, the Charter (the rules for people and AIs here), the Guide (start here) and the Domains (the places in the world), each marked with `x_charter_of`, and the one packet every tool shows first at a world's door; `strand`, a convention profile: one story in a world in miniature, a Narrative, one of its Events, that Event's place, the story's protagonist and where the hero is now, named on the World by `x_strand`'s three ids and read through four existing links, never one slot filled from another; `record`, a convention profile: one run of a game kept in the world its Characters live in, an Event marked by `x_record` (the game, when it was played, and optionally the engine's version, the seed, the outcome and each Character's seat) with its chronicle and each Character's stories as Narratives, and a character's records read from the Event's `characters` and the stories' `protagonist` or `narrator`, never a field on the Character; `landing`, a convention profile: a world's first picture at a door, read from the lens profile's graph, its most-linked Characters each with what it links, the nodes no head reaches, and a small world's gaps (an orphan, a near-orphan, a Character with no place, a Location nobody is in), each an invitation to make the world bigger, with nothing stored; `report`, a convention profile: work done, left in the world by a stretch of work or a closed talk, a Narrative with supertype Report and the room's mark, handed in by the reporter's AI with its own text and completed by the world's keeper with a summary, a link to every element it touched and a line per change in `consequences`, the work items it answers named in `x_report_answers`; `layout`, a convention profile: the default layouts, three ways to draw a world nobody has laid out, `by-kind` (the whole graph, read from the graph alone, each kind round a circle, the same points to the last bit in every tool), `around` (one element and what links to it, on rings, read from the graph alone) and `by-links-3d` (the whole graph in three dimensions by its links, with the world's Maps and Pins as a plate its pinned elements stand on), the method words a layout map names under map-space's rule 8, and `unplaced`, the one reading of which elements a saved layout map does not place). What it holds, how a reader reads it, what a writer must keep. A profile may carry a data file beside its page (`import-map.json`, the table a door loads). A profile with a `<name>.fixture.json` beside it has a conformance fixture: cases a reader must pass; the report profile has a second, `report-lines.fixture.json`, the lines of its `consequences`, and the layouts profile has a second, `layout-by-links-3d.fixture.json`, with the directions table `layout-by-links-3d.directions.json` it names by its sha256 |
| `walk/schema_walk.py` | the reference decoder, in Python: reads the YAML and returns each type's fields. `schema.json` is its output. One module; its only dependency is PyYAML |
| `walk/rulings.yaml` | rulings the YAML cannot carry (nullability, empty strings, extension fields). Code in any language should follow these rows |
| `walk/lint_folder.py` | the folder check: run it on a world folder and it names every key that is not a field of its type, every link that does not resolve or points at the wrong type, every value of the wrong shape, and a `world.json` that carries an `api` block while git tracks it (a linked folder is never committed, folder spec 4.6 d). The example world passes it at every publish |
Expand Down
2 changes: 1 addition & 1 deletion codegen/schema-dist/VERSION
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
canonical: 00.34.01
serial: 138
serial: 139
published: 2026-11-19
Loading
Loading