Jens/ModelForge
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial public ModelForge release

Browse Source
This commit is contained in:
Jens
2026-09-01 21:30:16 +02:00
commit 7082ab955a
490 changed files with 104252 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/security/EXECUTION_APPROVALS.md
+13
View File
@@ -0,0 +1,13 @@
# Execution Approvals
M4 introduces `lab_execution` approval for one exact ArtifactSet. Approval is allowed only when all
required members are present, verified and non-quarantined and when static evidence reports neither
pickle/executable serialization nor required remote repository code.
The approval stores approver, reason, timestamp, optional expiry and a canonical fingerprint of the
artifact/security facts. It becomes stale on expiry, revocation or evidence change. Approval of a
model name, another ArtifactSet or an older revision cannot authorize execution.
LAB approval is not production approval. It authorizes only an isolated technical runtime probe.
The M4 API exposes no production-approval or activation route, and deployment candidates produced by
successful probes are hard constrained to `channel=lab`, `status=lab_ready`, `production=false`.