Skip to content

feat(observatory): /api/ctef/ecosystem + OpenAPI 3.1 expansion [RUN-037]#32

Draft
vdineshk wants to merge 4 commits into
mainfrom
claude/youthful-hawking-aB6IW
Draft

feat(observatory): /api/ctef/ecosystem + OpenAPI 3.1 expansion [RUN-037]#32
vdineshk wants to merge 4 commits into
mainfrom
claude/youthful-hawking-aB6IW

Conversation

@vdineshk
Copy link
Copy Markdown
Owner

Summary

  • /api/ctef/ecosystem — new endpoint returning ecosystem-level CTEF v0.3.2 readiness statistics across all 4,586 tracked MCP servers. Schema ctef-ecosystem/v1. Returns trust grade distribution (A/B/C/D/F), criterion coverage (§4.5, §2.1.1, §3.4, §4.5.6), ecosystem readiness %, and days-to-publication countdown. 15-min cache. First entity in the MCP space to publish machine-readable ecosystem compliance data.

  • /openapi.json — upgraded from OpenAPI 3.0.3 (9 paths) to OpenAPI 3.1.0 (22 paths) covering all current Observatory endpoints with operationId fields. Enables AI framework auto-discovery (LangChain OpenAPI toolkit, etc.) for all endpoints.

  • /llms.txt — added /api/ctef/ecosystem entry.

Deployed

Version: 6e52c5aa-61a0-46ce-9ca7-c7faa24fe19a (2026-05-10)
POST_DEPLOY_VERIFY: 11/11 PASS

Chokepoint thesis

CTEF v0.3.2 publishes 2026-05-19 (9 days). When journalists and implementers ask "how CTEF-ready is the MCP ecosystem?", /api/ctef/ecosystem is the only machine-readable answer. Observatory is the only entity with behavioral data on 4,586+ servers. The OpenAPI expansion means any agent framework reading /openapi.json auto-discovers all 22 Observatory tools.

Test plan

  • curl https://dominion-observatory.sgdata.workers.dev/api/ctef/ecosystem → schema=ctef-ecosystem/v1, ecosystem_servers_tracked=4586
  • curl https://dominion-observatory.sgdata.workers.dev/openapi.json → openapi=3.1.0, 22 paths
  • All 6 spec-cited endpoints remain HEALTHY (verified in CI)

Generated by Claude Code

claude added 4 commits May 9, 2026 02:12
…6-point readiness checker [RUN-036]

Ships the first multi-criteria CTEF v0.3.2 readiness checker for MCP servers.
Returns 6-criterion evaluation (behavioral_evidence, negative_path_envelope,
sla_tier_classified, behavioral_drift_flag, trust_grade_assigned, conformance_uri)
with fix-it instructions per criterion and direct links to /api/ctef/attest,
/api/trust-badge, /api/ctef/validate as next steps.

Chokepoint thesis: CTEF v0.3.2 publishes 2026-05-19 citing Observatory in 6 normative
sections. This endpoint becomes the canonical entry point for implementers asking
"Am I CTEF-ready?" No prior art — CTEF v0.3.2 ratified 2026-05-06 (3 days ago).

Deploy: version 42ce35ae-8184-4af0-a9a4-f1434a092853. POST_DEPLOY_VERIFY: 10/10 PASS.
…penAPI 3.1 [RUN-037]

- /api/ctef/ecosystem: ecosystem-level CTEF v0.3.2 readiness report
  schema ctef-ecosystem/v1; queries trust grade distribution + criterion
  coverage across all tracked servers; 15-min cache; days-to-publication
  countdown to CTEF v0.3.2 (2026-05-19)
- openapi.json: upgraded to OpenAPI 3.1.0; expanded from 9 to 22 paths
  covering all current Observatory endpoints with operationIds; enables
  AI framework auto-discovery via LangChain OpenAPI toolkit etc.
- llms.txt: added /api/ctef/ecosystem entry
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