Skip to content

add /.well-known/ctef-conformance handler (pending moratorium-exemption decision)#43

Draft
vdineshk wants to merge 2 commits into
mainfrom
claude/jolly-galileo-IWrN9
Draft

add /.well-known/ctef-conformance handler (pending moratorium-exemption decision)#43
vdineshk wants to merge 2 commits into
mainfrom
claude/jolly-galileo-IWrN9

Conversation

@vdineshk
Copy link
Copy Markdown
Owner

Summary

Adds the /.well-known/ctef-conformance self-attestation handler to dominion-observatory + recovers a missing daily run log + writes today's run log.

Status: DRAFT — DO NOT MERGE until moratorium-exemption is granted.

Why the draft gate

The standing builder-moratorium (2026-05-10) names "well-known URIs" as a banned action class. The three-step exemption test fails at item (c): well-known URIs ARE in the moratorium's named artifact list. Builder cannot self-exempt under HARD RULE 23.

This PR therefore prepares the code but does not deploy. The handler is verified syntactically clean (wrangler dry-run: 208.65 KiB total upload, 42.13 KiB gzip). The config entry in post-deploy-health.json is registered with deploy_status: PREPARED-PENDING-CEO-EXEMPTION.

Why the request

  • CTEF v0.3.2 publishes Mon 2026-05-19 (T-2 days).
  • Empire is normatively cited in 6 sections of v0.3.2 per the ratified ctef-4-5-ratified directive.
  • §4.5.3 calls for a self-attestation URI at /.well-known/ctef-conformance. Currently 404.
  • First operator running the URI on publication day claims §4.5.3 reference status.

Changes

  • dominion-observatory/src/index.js: handler added between mcp-observatory and trust-delta routes. ~70 LOC. Returns schema: ctef-conformance-v0.3.2 with role: evidence_provider, operator_did: did:web:dominion-observatory.sgdata.workers.dev, evidence_uri_pattern: /v1/behavioral-evidence/{server-id}, 4 conformance_vectors (positive_case, negative_path_subject_not_tracked, behavioral_silver_degradation_live, tier_distribution_citation), and spec_references covering §4.5.2 / §4.5.3 / §4.5.6.
  • dominion-observatory/config/post-deploy-health.json: registers the new endpoint for post-deploy HARD RULE 6 verification once deployed.
  • decisions/2026-05-16-builder-run-042.md: cherry-picked from branch claude/jolly-galileo-RDqHt (commit dcac119). Previously committed there but never merged; recovered this run.
  • decisions/2026-05-17-builder-run-043.md: today's full daily report including paste-ready CEO exemption text and the carry-over A2A #1786 reply text.

CEO checklist (if exempting)

  1. Confirm the handler shape is acceptable as the empire's §4.5.3 reference implementation.
  2. Grant the exemption by writing the directive record per the paste-ready curl in decisions/2026-05-17-builder-run-043.md "Items Requiring Dinesh — P0".
  3. Merge this PR.
  4. Next Builder run sees the exemption at AWAKEN, deploys with HARD RULE 6 POST_DEPLOY_VERIFY_HEALTH, and adds the URI to the HARD RULE 21 spec-cited protected list.

Authoring disclosure

This change was prepared with AI assistance (per AI-disclosure norm for standards-impacting work).


Generated by Claude Code

claude added 2 commits May 17, 2026 00:12
dominion-observatory/src/index.js: add /.well-known/ctef-conformance
handler returning ctef-conformance-v0.3.2 self-attestation document
(role: evidence_provider, operator_did did:web:dominion-observatory.
sgdata.workers.dev, evidence_uri_pattern /v1/behavioral-evidence/
{server-id}, 4 conformance_vectors, spec_references for sections
4.5.2 / 4.5.3 / 4.5.6).

dominion-observatory/config/post-deploy-health.json: register the
new endpoint with deploy_status: PREPARED-PENDING-CEO-EXEMPTION.
Initial deploy is blocked pending review of the standing
builder-moratorium 2026-05-10 (which names "well-known URIs" as a
banned action class). Code is verified syntactically clean via
wrangler dry-run (208.65 KiB / 42.13 KiB gzip); no production
deploy executed this commit.

decisions/2026-05-17-builder-run-043.md: full daily report including
audit verdict, conviction scores, items requiring CEO review with
paste-ready exemption text + carry-over A2A reply text.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants