Activate immutable ESKA core 0.2.0 W3ID routes

[GerhardBalz-Admin]

Status

UPSTREAM W3ID PR SUBMITTED.

The governed eska-v0.2.0 release exists, the tagged core backend is verified, PR #92 recorded the release-published / route-pending state on main, and the minimal W3ID contribution has now been submitted upstream as:

perma-id/w3id.org#6543

Goal

Activate immutable W3ID routes for ESKA core 0.2.0 only against the governed eska-v0.2.0 release.

Required routes

https://w3id.org/eska/model/core/0.2.0
https://w3id.org/eska/dist/0.2.0/eska-core.ttl

Both must resolve exclusively to the immutable eska-v0.2.0 release tag, never to main.

Prerequisites

• ESKA Publish governed ESKA v0.2.0 release #86 completed: eska-v0.2.0 exists;
• release tag points to exact governed commit a6ce0b9e795d271dce8a2b7be93d44932e8448d4;
• tagged model/eska-core.ttl is publicly fetchable and verified as core 0.2.0;
• tagged core contains eska:SemanticModel owl:equivalentClass smo:SemanticModel;
• tagged core retains dcterms:requires <https://w3id.org/smo/0.1.0> and the non-deprecated ESKA compatibility term;
• PR Record ESKA v0.2.0 release evidence #92 recorded release evidence on governed main as af35a390a181c86263edbff24bc22b01d7f6520e;
• post-merge focused contract verification passed;
• full Pizza/ESKA regression passed on unchanged rerun after one transient downstream RemoteDisconnected.

Upstream contribution

W3ID PR:

perma-id/w3id.org#6543

Source branch/head:

GerhardBalz/w3id.org:eska-core-0.2.0-routes
0a213385a247adcf3293c1077e9c58e64fda9308

Base:

perma-id/w3id.org:master
84d541d959006ea6df14014e880020223c3c059b

Verified upstream submission state at creation:

• open;
• non-draft;
• mergeable;
• exactly one commit;
• exactly two changed files: eska/.htaccess and eska/README.md;
• .htaccess adds exactly five lines;
• no change to existing current or immutable routes;
• every new immutable backend target uses eska-v0.2.0, never main;
• no maintainer comments yet;
• no commit-status checks reported yet.

Remaining sequence

1. wait for upstream #6543 merge or maintainer feedback;
2. verify the actual merged head and upstream merge commit;
3. externally verify current + all immutable ESKA routes, including core 0.2.0;
4. synchronize the repository-owned W3ID mirror with the active upstream state;
5. record upstream merge/live verification evidence in ESKA publication metadata;
6. close Activate immutable ESKA core 0.2.0 W3ID routes #87 and then close parent Align ESKA SemanticModel with published SMO in the next core minor version #84 / downstream SMO Add a third executable-semantic mode #11 if all acceptance criteria are fulfilled.

Non-goals

Do not:

• change core semantics while adding routes;
• modify existing core 0.1.0 or other module routes;
• retag eska-v0.1.0 or eska-v0.2.0;
• point any immutable route to mutable main;
• mark core 0.2.0 W3ID routing active before upstream merge plus successful external live verification.

Completion rule

Close only when both core 0.2.0 routes are upstream-active and externally verified against eska-v0.2.0.

Refs #84, completed #86/#88, merged PRs #85/#89/#92, upstream perma-id/w3id.org#6543.

[GerhardBalz-Admin]

Preparation update — no route has been activated or submitted upstream yet.

All release prerequisites are objectively satisfied by eska-v0.2.0 at commit a6ce0b9e795d271dce8a2b7be93d44932e8448d4, and the tagged core backend is verified.

A minimal W3ID fork branch has therefore been prepared safely:

• fork: GerhardBalz/w3id.org
• branch: eska-core-0.2.0-routes
• base synchronized to upstream perma-id/w3id.org:master at 84d541d959006ea6df14014e880020223c3c059b
• head: 0a213385a247adcf3293c1077e9c58e64fda9308
• exactly 1 commit ahead, 0 behind
• exactly 2 changed files: eska/.htaccess, eska/README.md

The only redirect behavior added is:

• HTML/Turtle model/core/0.2.0 → immutable eska-v0.2.0/model/eska-core.ttl;
• dist/0.2.0/eska-core.ttl → immutable eska-v0.2.0/model/eska-core.ttl.

No new immutable route targets main, and all existing routes are preserved. Upstream PR submission remains intentionally deferred until the release-evidence state in PR #92 is reviewed/merged.

[GerhardBalz-Admin]

Post-merge verification note: the first full Pizza ESKA reference run (31676893328, attempt 1) passed all seven executable modes, release/tag evidence, tagged core verification, and the first live W3ID checks, then failed on a transient downstream HTTPS RemoteDisconnected. The unchanged job was rerun and attempt 2 completed successfully end-to-end. No code or publication-state change was required.

#87 remains READY FOR UPSTREAM W3ID SUBMISSION.

[GerhardBalz-Admin]

Upstream merge observed

perma-id/w3id.org#6543 was merged on 13 August 2026.

Verified upstream PR evidence:

upstream PR          perma-id/w3id.org#6543
state                closed / merged
merged head          0a213385a247adcf3293c1077e9c58e64fda9308
upstream merge SHA   1230ac37c2100f752e2071606103b81f445d5d5c
merged at            2026-08-13T08:44:27Z

This satisfies the upstream-merge prerequisite but does not by itself close #87. The completion rule still requires external verification that both immutable core 0.2.0 routes resolve against eska-v0.2.0, followed by repository publication-state synchronization/evidence.

Next action: run the governed external route verification and record the resulting live evidence before marking the routes active.

[GerhardBalz-Admin]

Upstream merge and live verification complete

perma-id/w3id.org#6543 merged successfully.

Verified upstream evidence:

source head
0a213385a247adcf3293c1077e9c58e64fda9308

upstream merge commit
1230ac37c2100f752e2071606103b81f445d5d5c

The repository follow-up is PR #93.

A dedicated GitHub-hosted live verification run completed successfully:

31694481671 — SUCCESS

It verifies all three public representations:

• https://w3id.org/eska/model/core/0.2.0 with Accept: text/html;
• the same version IRI with Accept: text/turtle;
• https://w3id.org/eska/dist/0.2.0/eska-core.ttl with Accept: text/turtle.

The checks require an HTTP 303 redirect and final immutable backends under eska-v0.2.0.

PR #93 now synchronizes the repository-owned W3ID mirror and advances the governed publication contract/backend metadata from route-pending to active. The updated SMO/publication contract workflow is also green on head 713f59f457c84afcdc61f623908af972c121d408.

Issue #87 should close when PR #93 is reviewed and merged; parent #84 can then be closed if no other acceptance item remains.