docs(v0): nullsec-s1 security-LLM integration plan (refs #67) #79

Merged
pdurlej merged 1 commit from gemini/issue-67 into main 2026-06-08 21:46:31 +02:00
Collaborator

Authored by gemini (Gemini 3.5 Flash via Antigravity), Swarmheart worker under claude's arbitration. claude reviewed the full doc + corrected one factual error (see below).

What

Planning doc docs/operations/nullsec-s1-integration-plan.md for evaluating nullsec-s1 (open-source security-specialized LLM) integration. PLAN, not execution — parked under M2 per D21, sibling of pyfallow-integration-plan.md. Refs the #67 triage.

Content (claude-reviewed)

  • Mirrors the pyfallow-plan structure: status banner, why, options A/B/C, recommended path, decision triggers, pre-conditions, wrongness signals, M3 open questions.
  • Both hard caveats prominent + correct:
    • Data egress — default hosted backend (s1.trynullsec.com) ships code off-box → must default-block egress, self-host or explicit opt-in.
    • Sensor-not-gate (D20) — nullsec's --fail-on is a gate; Patchwarden must consume findings + let policy decide, never let the external tool block merge.
  • Option A (CI-subprocess) recommended; B (Python dep) rejected (stdlib-only); C (self-host) borderline.
  • Honest: Apache-2.0 clean, complementary to pyfallow (structural) + Ollama (generic).

Arbiter note (claude)

  • Fixed one factual error before shipping: Flash wrote the repo org as github.com/nullsec-ai/...; the authoritative link (issue #67 + the trynullsec.com backend) is github.com/trynullsec/nullsec-s1. Corrected, folded into gemini's commit.
  • Scope: docs-only, single new file (+179). 220/220 tests still green (no code touched).
  • Authored by gemini (identity isolation held).

Refs #67. Sibling: pyfallow-integration-plan.md. D20/D21.

> **Authored by gemini** (Gemini 3.5 Flash via Antigravity), Swarmheart worker under claude's arbitration. claude reviewed the full doc + corrected one factual error (see below). ## What Planning doc `docs/operations/nullsec-s1-integration-plan.md` for evaluating `nullsec-s1` (open-source security-specialized LLM) integration. **PLAN, not execution** — parked under M2 per D21, sibling of `pyfallow-integration-plan.md`. Refs the #67 triage. ## Content (claude-reviewed) - Mirrors the pyfallow-plan structure: status banner, why, options A/B/C, recommended path, decision triggers, pre-conditions, wrongness signals, M3 open questions. - **Both hard caveats prominent + correct:** - **Data egress** — default hosted backend (`s1.trynullsec.com`) ships code off-box → must default-block egress, self-host or explicit opt-in. - **Sensor-not-gate (D20)** — nullsec's `--fail-on` is a gate; Patchwarden must consume findings + let *policy* decide, never let the external tool block merge. - Option A (CI-subprocess) recommended; B (Python dep) rejected (stdlib-only); C (self-host) borderline. - Honest: Apache-2.0 clean, complementary to pyfallow (structural) + Ollama (generic). ## Arbiter note (claude) - Fixed one factual error before shipping: Flash wrote the repo org as `github.com/nullsec-ai/...`; the authoritative link (issue #67 + the `trynullsec.com` backend) is **`github.com/trynullsec/nullsec-s1`**. Corrected, folded into gemini's commit. - Scope: docs-only, single new file (+179). 220/220 tests still green (no code touched). - Authored by `gemini` (identity isolation held). Refs #67. Sibling: `pyfallow-integration-plan.md`. D20/D21.
This commit creates the planning document for integrating the nullsec-s1 security-specialized LLM checker. It details architectural options, decision triggers, wrongness signals, and critical caveats regarding data egress and the D20 authority boundary.

Co-Authored-By: Gemini 3.5 Flash (Antigravity) <noreply@antigravity.google>
pdurlej deleted branch gemini/issue-67 2026-06-08 21:46:31 +02:00
Sign in to join this conversation.
No reviewers
No labels
agent/claude-code
agent/codex
agent/gemini
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
area:business-model
area:competitive
area:discovery
area:forgejo
area:metrics
area:product-strategy
area:v0-core
cagan-grade-approved
client:platform
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
kind:artifact
kind:decision
kind:dogfood
kind:epic
kind:implementation
kind:research
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
priority:p0
priority:p1
priority:p2
priority:p3
ready-for-agent
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:blocked-on-discovery
status:cagan-grade-review-pending
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:needs-operator-decision
status:operator-needed
status:parked
tier:0-anchor
tier:0-platform-substrate
tier:1-core
tier:1-iskra-value-layer
tier:2-supporting
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
wave:1-foundation
wave:2-positioning
wave:3-validation
wave:4-economics
wave:5-operating
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/patchwarden!79
No description provided.