Repository navigation
ontology/ and ontology-kit/: shared option-4 classes on Pages, base URL in one place, immutability and catalog gate (#177) - #178
Merged
Conversation
Two top-level folders, per #177 §2.0 and Michiel's decision on question 12: ontology/ holds only the generated, published, immutable term files (v1, classes/<name>-v1, properties/<shortname>, extensionless JSON-AD); ontology-kit/ holds base.json (the one place the base URL is written), source.json, the build and check, the generated subject constants and the strict field resolver. - v1: event-v1, issue-v1, time-entry-v1 (with work-project-v1 and work-person-v1) and bank-transaction-v1, reusing the calendarFields, work-* and bank-* shortnames and referencing task/v1 and core `name` by their atomicdata.dev subjects. Declared, not verified. - `node ontology-kit/ontology.mjs check`: generated files equal a fresh build; no term file on origin/main changed or deleted except by a base move; the base literal only in base.json and generated/built files; and, while the base is on github.io, every catalog entry that uses it is `enabled: false`. - resolver.mjs: exact class and exact property subject only, with lens hooks for other shapes. No duck typing. - CI: the check, the kit's unit tests, and oxlint/oxfmt on ontology-kit/ in shared-checks; ontology/** and ontology-kit/** in the `any` filter and allowed in lane `paths`; ontology-published.yml checks Pages serves each term file at its subject after a build. - AGENTS.md: the two folders, and that they are approved shared code. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ne (#177) The dev-server serves the committed term files at /ontology/<path>, with their subjects moved from base.json's base to its own origin and GitHub Pages' headers (application/octet-stream, access-control-allow-origin *, a CORS preflight answered 405), as spike S1 imitated. The new tooling lane `ontology` (index 17, e2e only, runs when ontology/, ontology-kit/, the dev-server or the pin change) checks that the pinned host reads event-v1 from there and that atomic-server accepts a table of that class and a row with one of its properties. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #177. The groundwork for the option-4 design, following Michiel's decisions: a top-level
ontology/published at Pages/ontology/, the base URL kept in one place, and strict class matching with Devonian lenses. No plugin uses it yet.ontology/: only generated, immutable term files (extensionless JSON-AD):v1;event-v1,issue-v1,time-entry-v1,work-project-v1,work-person-v1,bank-transaction-v1;They reuse the
atomic-calendar-*,work-*,bank-*andmoney-*names, and referencetask/v1and core subjects on atomicdata.dev rather than copying them.ontology-kit/(name still open on Design: plugins sync into shared row classes, and plugin views work on any table of that class ("option 4") #177):base.json: the only place the base URL is written;source.json: the definitions;ontology.mjs build|check, generatingterms.mjssubject constants;resolver.mjs: exact class and exact property only, with lens hooks and no duck typing;CI
check --published origin/mainfails on:-v2; the only allowed in-place change is a base move.The gate: while the base is on
*.github.io, any catalog entry whose entry, published bundle or plugin code references the base or importsontology-kit/must beenabled: false. The base URL written literally outsidebase.jsonis refused.Pages:
ontology-published.ymlchecks that every term is served at its subject with the committed bytes.Dev-server: serves
/ontology/*with subjects rewritten to its own origin and Pages-like headers. A newontologye2e lane checks that the pinned host readsevent-v1and accepts a hand-made table of that class.Checks:
integrationsandontology-kit;tsc;Open: how a plugin's e2e reaches bundled github.io subjects while the dev-server serves them locally; and copying
integrations/alone now needsontology-kit/alongside it.🤖 Generated with Claude Code