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 <noreply@anthropic.com>
This commit is contained in:
@@ -35,6 +35,8 @@ COPY policies/ ./policies/
|
|||||||
|
|
||||||
# Copy Compliance Execution Graph data (file-backed: Registry join-key copy + accepted control
|
# Copy Compliance Execution Graph data (file-backed: Registry join-key copy + accepted control
|
||||||
# mappings + evidence requirements) consumed by GET /sdk/v1/compliance/obligation-status.
|
# 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/control_mappings/ ./data/control_mappings/
|
||||||
COPY data/evidence_requirements/ ./data/evidence_requirements/
|
COPY data/evidence_requirements/ ./data/evidence_requirements/
|
||||||
COPY data/obligations/ ./data/obligations/
|
COPY data/obligations/ ./data/obligations/
|
||||||
|
|||||||
Reference in New Issue
Block a user