You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 577b8dd
Browse filesBrowse the repository at this point in the historyBrowse files
0.84.0: schema-dist serial 86, a graph node's family is its type's colour word
Serial 86 keys presentation.json's colour groups by their colour words: each
type's family value is blue, green, pink or amber, colors.order and
colors.families are keyed by them (hexes unchanged), and _meta.families is
gone. Construct moves to pink and Ability to amber. The lens profile rules
that a graph node's family is that word and nothing else, and lens.fixture.json
asserts it; world_graph now gives it, and all 151 lens cases (37 graph) pass.
The generated map is renamed ELEMENT_GROUPS (private to the package, so no
alias), and the generator and the node's field comment call it a colour group.
The README's graph line says what family holds. address.md gains a sentence on
what a pin's, a marker's or a zone's address answers; nothing here restates it.
The tree is the tag's git archive (197 files); MANIFEST.json's sha256
(15200898...) matches the raw file served at the tag, whose ref resolves to
b0ca326. walk/ and schema.json did not move, so the vendored checker is
unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,11 @@ The package version runs on its own semver; the schema it is generated from is `
4
4
5
5
## Unreleased
6
6
7
+
## 0.84.0 (2026-10-29)
8
+
9
+
-**A graph node's `family` is its type's colour word**: `blue`, `green`, `pink` or `amber`, the value the schema distribution's `presentation.json` now gives each type, in place of `agents`, `world`, `abstract` or `temporal`. The key keeps its name, as the lens profile's node does; the word is a key for drawing the 22, never a classification or a label. Two types move group: **Construct is pink** (was `world`, green) and **Ability is amber** (was `abstract`, pink); the four hexes are unchanged. A tool that matched on the old words reads the new ones. The generated map behind it, private to the package, is renamed `ELEMENT_GROUPS` (was `ELEMENT_FAMILIES`).
10
+
-**Schema repinned to schema-dist `v0.33.0-dist.86`** (from dist.85; the same canonical 00.33.00, so `SCHEMA_VERSION` stays and no type or field moved; the folder lint and `FORMAT_VERSION` stay at 0.3.20). Serial 86 keys the presentation defaults' colour groups by their colour words, rules in the lens profile that a node's `family` is that word, and replays it in `lens.fixture.json`, whose 151 cases (37 graph) all pass. The address profile gains a sentence on what a pin's, a marker's or a zone's address answers on the site; nothing in this package restates it. Tests: the map against the vendored `presentation.json` for every type, Construct pink and Ability amber, and every node of every fixture graph case carrying its type's word.
11
+
7
12
## 0.83.2 (2026-10-29)
8
13
9
14
-**The doctor's flag 11 no longer reports an unmarked Law with supertype Charter.** The checks profile at schema-dist serial 85 rules that such a Law is lore, not a Charter and not a finding, house rules or not; the doctor followed the older reading and named one carrying `x_checks_rules` as a finding. Its rules are still never applied, on a folder and through the API (with `front_door.charter` null too); a marked Charter that is not the newest stays a finding. Tests: three, the unmarked Law newer than the Charter, a world with no marked Charter, and the API's null front door, now assert no finding and no rule applied from it.
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -324,7 +324,7 @@ The world holds the elements as the owner is served them; the reader's `rung` (`
324
324
325
325
`DATE_FIELD` is the profile's date table (each dated type's date field; the ten timeless types are not in it), and `date_of(el)` is an element's date as that table reads it: the whole number in its type's date field, else `None`. A timeline or a horizon dates elements exactly as the lens reader's fence does.
326
326
327
-
`world_graph(world, reader, *, lens=None, as_of=None, clock=None, rooms=False, hidden=False, proposed=False, map_space=False)` reads the same snapshot, for the same reader, as nodes and edges: `nodes` (`{id, type, name, family, icon}`, by id), `edges` (`{source, field, target, index}`, one per link, by source, field and index), `edges_cut` (links to elements that are not nodes, by reason; with a lens, `outside_lens` counts links to elements the reader sees that the lens left out), `cut` and `unreadable` (the `x_lens` key a lens could not be read by, else `None`). Room elements, hidden and proposed ones and map space are out unless a flag brings them back (`hidden` and `proposed` are the owner's alone, and a public reader takes no flag); the reading aids are out too, counted `reading_aid`, and no flag brings them back; with `lens` the nodes are exactly what the lens kept, an aid among them when the lens names its pair in `types`.
327
+
`world_graph(world, reader, *, lens=None, as_of=None, clock=None, rooms=False, hidden=False, proposed=False, map_space=False)` reads the same snapshot, for the same reader, as nodes and edges: `nodes` (`{id, type, name, family, icon}`, by id; `family` is the colour word the schema distribution's presentation defaults give the type, `blue`, `green`, `pink` or `amber`, a key for drawing the 22 and never a label), `edges` (`{source, field, target, index}`, one per link, by source, field and index), `edges_cut` (links to elements that are not nodes, by reason; with a lens, `outside_lens` counts links to elements the reader sees that the lens left out), `cut` and `unreadable` (the `x_lens` key a lens could not be read by, else `None`). Room elements, hidden and proposed ones and map space are out unless a flag brings them back (`hidden` and `proposed` are the owner's alone, and a public reader takes no flag); the reading aids are out too, counted `reading_aid`, and no flag brings them back; with `lens` the nodes are exactly what the lens kept, an aid among them when the lens names its pair in `types`.
Copy file name to clipboardExpand all lines: codegen/schema-dist/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ Each serial (one numbered publication of these files, tagged `v<schema version>-
14
14
|`schema/*.yaml`| the 22 element types, `base_properties` and `world`: the same content as the standard's YAML. The bytes differ (LF line endings, blank lines), the parsed data does not |
15
15
|`example/hyperion/`| Hyperion, the public example world, as a world folder. Every file in it passes the decoded schema |
16
16
|`example/world-export.json`| the world-export envelope (`format: onlyworlds-world-export`, the portal's one-file download) for one small fixed world: a single link, a multi-link, an extension field. It is the emitter's own output, pinned by a keel test, so a reader of the envelope tests against the real shape |
17
-
|`presentation.json`| default family and icon per type, and the four family 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 |
17
+
|`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 |
18
18
| `profiles/` | extension profiles: one page per named extension field 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 nine type-and-supertype pairs a parlor puts in a world, 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; `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, and the rule that a field holding one is public text, never resolved; `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). 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 |
19
19
|`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 |
20
20
|`walk/rulings.yaml`| rulings the YAML cannot carry (nullability, empty strings, extension fields). Code in any language should follow these rows |
0 commit comments