Milestone: fail-closed artifact publication #6

New issue

Open

opened 2026-09-24 23:34:50 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-09-24 23:34:50 +00:00

(Migrated from github.com)

Source: https://github.com/lost-rob0t/zero-forge/blob/master/docs/architecture.md ("Fail-closed workflow")
Lineage: port-mapping milestone derived from ZeroForge

Scope

Port safe artifact publication:

Output paths reject unsafe CVE IDs, path traversal, escaping destinations,
and symlink escapes.
Validation is mandatory before persistence; every Smart repair is
revalidated before it may be written.
Persisted artifacts are recorded in the KB with provenance (validator
versions, digest, input evidence IDs).
Terminal failure states persist diagnostics; nothing is promoted on failure.

Acceptance criteria

Path-safety test fixtures: malicious CVE ID, traversal, symlink escape —
all rejected without filesystem side effects.
No code path persists an artifact without a passing validator record.
Publication is idempotent per (CVE ID, artifact type) or explicitly
versions, with superseded artifacts retained.

Dependencies

Validators + bounded repair milestone.

Non-goals

No deployment/packaging work (CI, release) in this milestone.
No unattended execution defaults; operator invokes the forge explicitly.

Implementation approval is not inferred from this issue.

**Source**: https://github.com/lost-rob0t/zero-forge/blob/master/docs/architecture.md ("Fail-closed workflow") **Lineage**: port-mapping milestone derived from ZeroForge ## Scope Port safe artifact publication: - Output paths reject unsafe CVE IDs, path traversal, escaping destinations, and symlink escapes. - Validation is mandatory before persistence; every Smart repair is revalidated before it may be written. - Persisted artifacts are recorded in the KB with provenance (validator versions, digest, input evidence IDs). - Terminal failure states persist diagnostics; nothing is promoted on failure. ## Acceptance criteria - Path-safety test fixtures: malicious CVE ID, traversal, symlink escape — all rejected without filesystem side effects. - No code path persists an artifact without a passing validator record. - Publication is idempotent per (CVE ID, artifact type) or explicitly versions, with superseded artifacts retained. ## Dependencies - Validators + bounded repair milestone. ## Non-goals - No deployment/packaging work (CI, release) in this milestone. - No unattended execution defaults; operator invokes the forge explicitly. Implementation approval is not inferred from this issue.