Swarmchasing Report a swarm

Docs

On this page
  1. Guides
  2. Reference
  3. Method and policy
  4. Specs
  5. Elsewhere

Every committed doc, by what it is for. The CLI's commands are in the CLI README; each crate has its own README.

Guides#

Task-oriented: how to do one job end to end.

DocCovers
Admin workflowThe admin's day: watch digest, review, case, contacts, drafts, send, notice, updates.
AI assistanceWhere a model helps (suggestions, triage, rule upkeep, drafting, monitoring), what it may see, what stays human.
Evaluating leadsLabelling leads well: what each label means, deciding a group, the traps, worked examples.
For operatorsFor a site that received a report: what it means, telling it is genuine, checking logs, sending logs back, replies, verifying a bundle, private contact.
For providersFor an AI provider that received a report: what it holds, checking the bundle, STIX and MISP exports, the publication clock, how it is named, replies.
For researchersFor outside researchers: the workbench on your own exports, rules and tactics, citing the manual, reproducing the evaluation, what is never shared.
Writing rulesAdding or changing a rule: fields, weights, links, hard negatives, the evaluation and the gate.

Reference#

What each part does and how it is configured.

DocCovers
Watch runs and reviewThe data directory, incremental collection, the digest, retention, reviewing leads.
Case filesCase files: case.toml, every case subcommand, contacts, drafts, bundles, pinned rules, STIX and MISP exports, incident drafts, operator evidence.
The inboxOutside submissions: transports, inbox commands, storage, other formats, intake caps, verification by id, triage and its settings, promotion.
NoticesDrafting, adding and updating notices; what they withhold; lint and build.
Declared agent identityDeclared agent identity: the catalog, identity refresh and check, the classes, report lines and suggested claims.
Evaluationswarmchase eval, the CI eval gate and its floors, the held-out measurement.
Browser toolkitThe Pages site: how it is built, each page, the workbench, and how it keeps payloads inert.
Configurationenv.list, environment variables, the urlquery.net key and terms.
CI on a self-hosted runnerThe workflows, secrets and variables, caches outside the checkout, runner requirements.

Method and policy#

DocCovers
MethodologyHow records become tiers, clusters, hints and claims, and the known limits.
PoliciesCollection, attribution, reporting and publication.
Swarmchasing Field Manual (SC-FM 1.1)The Swarmchasing Field Manual (SC-FM): the method as a citable standard, with stable section ids.

Specs#

Formats other groups can implement, each with a JSON Schema under schemas/.

DocCovers
SpecsIndex of the specs and their versions.
SC-Rules v1: indicator rules formatSC-Rules v1: the indicator rules file, scoring semantics and conformance vectors.
SC-Incident v1: incident interchange formatSC-Incident v1: one JSON document per published incident.
SC-Sightings v1: sharing what a swarm left in your logsSC-Sightings v1: an operator's sightings of a swarm, shared without its logs, and matching across operators.
SC-Submission v1: outside swarm reportsSC-Submission v1: an outside report of agent activity, evidence typed by how it can be checked.
Adopting the methodHow another group adopts the method and states conformance.
schemas/sc-bench-v1.jsonSC-Bench v1: a labelled set, by record id, that other detectors are scored against (evaluation).

Elsewhere#

DocCovers
CONTRIBUTING.mdThe hard rule, the gates, conventions, contributing a rule.
scripts/README.mdEvery script and gate, and where each runs.
samples/eval/README.mdThe labelled evaluation set and the held-out Transluce steps.
samples/showcase/README.mdThe synthetic set the landing page walks through.
samples/submissions/README.mdSynthetic SC-Submission, STIX, X-ARF and IODEF reports.

Source: docs/README.md