Ultrasafe

When

When

You're about to put out a small fix. Only a little bit of the code changed, and the previous version was already safe.

Right before a patch release (semver Z bump, hotfix, or quick critical patch). Narrow diff, tight schedule, stable prior release, small change footprint.

What happens

How to activate

1. When you say 'release this version', Ultrasafe starts on its own.
2. 3 or 4 AI helpers look at the new code at the same time, checking it from different angles.
3. They repeat 3 to 5 rounds. Each round, they look at more than half the changed code.
4. If two rounds in a row find nothing new and everything is improving, the release is OK to go out.
5. A short report is saved for you to look at if you want.

1. Tag your patch branch: git tag v2.5.41-patch1 && git push --tags.
2. The PreToolUse hook auto-fires on git push --tags, or invoke explicitly: /ultrasafe --tier=1.
3. Tier 1 dispatches 3-4 agents in parallel, weighted toward static analysis (SAST + linting + dep-advisory scan).
4. Iteration loop: min 3, max 5. Per-iter coverage ≥50% over diff scope; skipped equivalence classes recorded in untested_classes[].
5. Clean-signal AND gate: regression-free + monotonic + coverage + 2-iter-consecutive. Pass → release proceeds (v0.1 advisory).
6. Output: OSCAL Assessment Result + Hyperbrief IR card written to reports/ultrasafe-iterations/v2.5.41-patch1/iter-N/.

When

When

You're about to release a big new version to a lot of users. The change list is long, or you need to give your users a written safety promise.

Right before a major release. Breaks backward compat, new public API, long changelog, Tier 3, compliance attestation needed, or RC round.

What happens

How to activate

1. When you say 'release this big version', Ultrasafe starts on its own.
2. All 8 AI helpers look at the new version at the same time. Each one is a different kind of attacker.
3. They repeat at least 5 rounds (up to 10). They have to look at 90% or more of the code, and at least two helpers have to agree on each finding.
4. If two rounds in a row find nothing new, the release gets a sealed safety certificate that you can share with your users.
5. Ultrasafe also writes down what it learned, so you can turn the lessons into permanent rules later.

1. Explicit: /ultrasafe --tier=3. Or PreToolUse hook on gh release create vX.Y.Z + semver X-bump.
2. Full 8-agent fan-out (AI/LLM + Web/API + Supply + Crypto + Social + Method/Comp + TM/Lifecycle + Synthesizer). §4 Finding contract + Synthesizer cross-axis correlation + BFT 2f+1 quorum.
3. Tier 3: min 5 max 10 iter. Coverage ≥90%. Cross-axis confirmation ≥0.5. Agent-diversity ≥50% × 3 dims.
4. Strict AND-gate: regression-free (3-component) + EWMA monotone + coverage met + 2-iter-consec with ≥50% diversity.
5. Pass → OSCAL signed (cosign + Rekor proof + Sigstore TSA). Attestation: e.g. 'coverage 90% under OWASP LLM Top 10 v2025.11 + MITRE ATT&CK v15 as of 2026-06-06'.
6. 3-level Greatpractice tree (macro/mezzo/micro) auto-drafted for human curation.

When

When

You're about to use a new outside part in your project, or change to a different version of one you already use. Want to make sure it's real and safe before bringing it in.

Bumping a transitive-critical dep or adding a new one. SBOM delta, typosquatting risk, maintainer anomaly, reproducible-build verify, Sigstore attestation check needed.

What happens

How to activate

1. You change your project to use the new outside part.
2. An AI helper specialized in outside parts checks five things at once — like 'is this the real version?' and 'is the maker acting strangely?'
3. Two other helpers (encryption + web) double-check the answers.
4. Clearly fake or tampered → warns you right away. Maker just looks a little odd → a human reviews. The system never blocks a maker by itself.
5. A small lesson is saved, like 'always check the part-name spelling before installing'.

1. Update your dep manifest (package.json / go.mod / Cargo.toml / requirements.txt / Gemfile) to the new pin.
2. Targeted invocation: /ultrasafe --axis=supply-chain. Or PreToolUse hook fires on dep-manifest push.
3. SCS runs 5 parallel checks: build tampering · maintainer compromise · typosquatting · transitive path · reproducibility. Emits PURL + attestation chain + maintainer_anomaly_flag.
4. Cross-axis: Crypto verifies Sigstore sig; Web queries OSV/GHSA. Maintainer anomaly → human (§2.1.3) — system never autonomously blocks a maintainer.
5. Auto-block on cosign-mismatch / SLSA L0 / OSV CVE exact-match IFF signature-based + FP<1% + fully reversible. Else → Hyperbrief.
6. Iter: 3 fixed (scan / SBOM rebuild / supply-chain regression). Coverage ≥75% of 5 SCS classes; skips with reason in untested_classes[].
7. Output: Greatpractice micro-rule candidate. Artefacts at reports/ultrasafe-iterations/pkg:npm/foo@v2-upgrade-2026-06-06/iter-{1..3}/.

When

When

Right after you fix a problem Ultrasafe found earlier. 3 things to confirm: (1) original problem really gone, (2) same problem not lurking next door, (3) fix didn't break something else.

Post-fix verification after prior Ultrasafe finding. Verify: (1) PoC no longer triggers, (2) no neighbor exposes same vuln class, (3) no unrelated-invariant regression.

What happens

How to activate

1. The next round starts on its own as soon as the fix is in.
2. A fresh AI helper tries the original attack one more time. This time it should fail.
3. Another helper looks at the nearby code to check for the same kind of weak spot sneaking in from a different direction.
4. A third helper checks that the fix didn't accidentally break some other rule that was already protecting you.
5. All 3 checks pass → fix confirmed. Any fails → human review requested (recurring problems usually need a deeper change, not another quick fix).

1. Iter N+1 auto-fires on fix-commit landing. Baseline pinned to iter N's commit SHA + catalog versions.
2. §6.2(a) 3-component: (a) PoC retest MUST fail; (b) neighborhood scan via call-graph 1-2 hop; (c) invariant widening via mutation testing.
3. All 3 pass → regression_check.all_pass = true ✓. Strict: no new HIGH-severity from the fix.
4. Any fail → §6.5 meta-defect oscillation. Hyperbrief IR auto-strips defer, forces escalate.
5. Example: SQL injection → parameterized-query fix; iter 2 PoC blocked + neighbor sites covered + input-validation invariant held; iter 3 no new XSS surface. Clean ✓.
6. Output: Greatpractice micro-rule (e.g. 'parameterized-query acceptance test for new endpoints'). Path: reports/ultrasafe-iterations/<tag>/iter-{N..N+3}/.