add ctef-conformance-check composite GitHub Action#33
Draft
vdineshk wants to merge 2 commits into
Draft
Conversation
Composite action wraps GET /api/ctef/readiness/{server_id} on Dominion
Observatory and posts per-criterion remediation guidance to PRs. Surfaces
readiness_grade, readiness_score, trust_grade, evidence_uri, attestation_uri
as step outputs. Optional fail_on_non_compliant gates merges on the six
CTEF v0.3.2 §4.5 criteria.
Includes README + drop-in example workflow + prior-art search log under
decisions/.
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
2 participants
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.
Summary
actions/ctef-conformance-check/that wrapsGET /api/ctef/readiness/{server_id}on Dominion Observatory and posts per-criterion CTEF v0.3.2 §4.5 conformance status (with remediationfixtext per failed criterion) as a PR comment + job summary.readiness_grade,readiness_score,ready_for_ctef,trust_grade,trust_score,evidence_uri,attestation_uri,badge_markdown. Optionalfail_on_non_compliant: 'true'to gate merges.example-workflow.ymlso any MCP server repo can adopt withuses: vdineshk/daee-engine/actions/ctef-conformance-check@main.decisions/2026-05-11-novelty-hunt-ctef-conformance-action.md— 6 surfaces searched, no existing GitHub Action checks CTEF conformance or integrates with a behavioral-evidence registry.Why
CTEF v0.3.2 publishes 2026-05-19 (T-8 days). Empire has shipped 7 CTEF endpoints over runs 026–037 but external callers in their first 30d = 0 (DISTRIBUTION-BACKLOG state per audit). This action is a callability surface that propagates
/api/ctef/readinessinto MCP server maintainers' CI pipelines. Each adoption = recurring HTTP traffic to spec-cited endpoints (/v1/behavioral-evidence,/api/sla-tier,/api/trust-delta) referenced in the readiness response'sevidencefields.No worker deploy this run — pure no-deploy callability surface, zero risk to the 11 currently-healthy spec-cited + CTEF endpoints.
Test plan
https://dominion-observatory.sgdata.workers.dev/api/ctef/readiness/sg-cpf-calculator-mcp— parses VERSION, GRADE, SCORE, TRUST, EVIDENCE, ATTEST, BADGE correctly; per-criterionfixrendering verified..github/workflows/ctef-conformance.ymlcalling this action against a real Observatory-tracked server (deferred to follow-up PR).v1) is cut.BUILDER RUN-038 — DISTRIBUTION-BACKLOG callability ship.
Generated by Claude Code