From 3a19affb674980af6bf8926ac2878109906fe950 Mon Sep 17 00:00:00 2001 From: Benjamin Admin Date: Fri, 26 Jun 2026 01:00:53 +0200 Subject: [PATCH] ci(compliance): re-trigger scoped ai-sdk build + doc synced join-keys copy Prior gitea push's build-ai-sdk failed on a transient registry push (arm64 built clean on macmini; amd64 cross-compile is green) and last-build/main got poisoned to that SHA, so a plain re-run scopes to nothing. A real touch in ai-compliance-sdk/ re-scopes the build. Also documents the synced-copy contract for data/obligations/obligation_join_keys.json. Co-Authored-By: Claude Opus 4.7 --- ai-compliance-sdk/Dockerfile | 2 ++ 1 file changed, 2 insertions(+) diff --git a/ai-compliance-sdk/Dockerfile b/ai-compliance-sdk/Dockerfile index 03c7384e..b87ea258 100644 --- a/ai-compliance-sdk/Dockerfile +++ b/ai-compliance-sdk/Dockerfile @@ -35,6 +35,8 @@ COPY policies/ ./policies/ # Copy Compliance Execution Graph data (file-backed: Registry join-key copy + accepted control # mappings + evidence requirements) consumed by GET /sdk/v1/compliance/obligation-status. +# data/obligations/obligation_join_keys.json is a synced copy of the repo-root Registry contract +# (the Obligation Registry owns the canonical file) — re-sync it when the Registry grows. COPY data/control_mappings/ ./data/control_mappings/ COPY data/evidence_requirements/ ./data/evidence_requirements/ COPY data/obligations/ ./data/obligations/