Ontology hosting: /ontology/v3.8/ IRIs 404 while public consumers already dereference them

[styk-tv]

Problem

Published ontology sets on this site stop at v3.7:

• https://conceptkernel.org/ontology/v3.7/core.ttl → 200
• https://conceptkernel.org/ontology/v3.8/core.ttl → 404

Meanwhile the protocol's reference implementation already dereferences the v3.8 IRI in its public quick-start (styk-tv/pgCK README):

const Task = 'https://conceptkernel.org/ontology/v3.8/core#Task';

Any consumer running that example resolves class IRIs against a 404. This site is named as the reference authority for CKP, so ontology IRI hosting is a contract, not a convenience.

Tasks

• Publish the v3.8 ontology TTL set under /ontology/v3.8/ so already-circulating IRIs resolve
• Publish the v3.9 ontology TTL set under /ontology/v3.9/, mirroring the public ontology/ directory of styk-tv/pgCK (core, affordance, delegation, delivery, goal, proof, task, validate)
• Treat published IRI sets as immutable — corrections go into the next version directory
• Extend the ontology browse index and sitemap.xml to cover the new versions

Acceptance

curl -s -o /dev/null -w '%{http_code}' returns 200 for /ontology/v3.8/core.ttl and /ontology/v3.9/core.ttl.

[styk-tv]

Scope correction + partial resolution, shipped in af10321:

The core vocabulary namespace is deliberately stable at /ontology/v3.8/core#. The governing specification pins the core IRI as a permanent handle — the vocabulary is versioned by the spec that governs it, not by churning its IRI. So the acceptance here changes: there is no /ontology/v3.9/ set to publish; the contract is that the v3.8 namespace resolves.

Now live:

• /ontology/v3.8/core.ttl — the runtime core exactly as shipped by styk-tv/pgCK (143 lines, 11 classes, 8 SHACL seal-gate shapes, including the governance plane: Proposal / Vote / QuorumLevel / Grant / Transition)
• /ontology/v3.8/ — index page documenting the namespace, its stability rule, and the urn:ckp: domain-kernel scheme
• sitemap.xml + llms.txt updated

Remaining for this issue: keep the published set in sync when pgCK ships a core.ttl change (governed, so rare and observable), and extend the ontology Browse index to include the v3.8 namespace.