Milestone: hard validators + bounded repair loop (MSF/ZAP/Nuclei) #5

New issue

Open

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

lost-rob0t commented

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

(Migrated from github.com)

Source: https://github.com/lost-rob0t/zero-forge/blob/master/docs/architecture.md ("Hard validators", fail-closed workflow) and ZeroForge README artifact table
Lineage: port-mapping milestone derived from ZeroForge

Scope

Port the hard artifact validators and the bounded Smart repair loop:

Metasploit exploit (Ruby): syntax + structural contract; validator runtime
preflight before generation so an unavailable runtime fails at startup.
ZAP active scan rule (JavaScript): bounded, non-destructive probe; alerts
must be evidence-backed.
ZAP passive scan rule (JavaScript): passive only; network calls and request
mutation are rejected.
Nuclei template (YAML): single document, required metadata/protocol
structure, matcher/extractor evidence; optional native nuclei -validate.
Validators are deterministic Prolog/effect code; model output is never
trusted by default.
Every repair attempt is revalidated; repair budget is bounded and owned by
the workflow.

Acceptance criteria

Each validator has reject fixtures (bad syntax, contract violation, policy
violation) and accept fixtures; both exercised by tests.
Repair budget exhaustion yields failed terminal status with the validator
diagnostics attached to the trace.
Validator preflight failures abort before consuming repair attempts.

Dependencies

Role separation milestone (Smart Agent performs repairs).

Non-goals

No softening of validation to raise accept rates.
No artifact types beyond the ZeroForge v1 set.

Implementation approval is not inferred from this issue.

**Source**: https://github.com/lost-rob0t/zero-forge/blob/master/docs/architecture.md ("Hard validators", fail-closed workflow) and ZeroForge README artifact table **Lineage**: port-mapping milestone derived from ZeroForge ## Scope Port the hard artifact validators and the bounded Smart repair loop: - Metasploit exploit (Ruby): syntax + structural contract; validator runtime preflight before generation so an unavailable runtime fails at startup. - ZAP active scan rule (JavaScript): bounded, non-destructive probe; alerts must be evidence-backed. - ZAP passive scan rule (JavaScript): passive only; network calls and request mutation are rejected. - Nuclei template (YAML): single document, required metadata/protocol structure, matcher/extractor evidence; optional native `nuclei -validate`. - Validators are deterministic Prolog/effect code; model output is never trusted by default. - Every repair attempt is revalidated; repair budget is bounded and owned by the workflow. ## Acceptance criteria - Each validator has reject fixtures (bad syntax, contract violation, policy violation) and accept fixtures; both exercised by tests. - Repair budget exhaustion yields failed terminal status with the validator diagnostics attached to the trace. - Validator preflight failures abort before consuming repair attempts. ## Dependencies - Role separation milestone (Smart Agent performs repairs). ## Non-goals - No softening of validation to raise accept rates. - No artifact types beyond the ZeroForge v1 set. Implementation approval is not inferred from this issue.