anti
75af00c9c8
Runs the chained identity + campaign clustering pipeline against all seven fixtures via from_synthetic / from_synthetic_identity adapters and ratchets every YAML floor to 1.0 — the production clusterer (and the reference clusterers used in the per-fixture tests) all score perfectly across ARI / homogeneity / completeness / singleton_recall on each fixture. Three substrate fixes surfaced by the ratchet: - Tuning: shared_infra now Jaccards payload+C2 only; decky_set moved into cohort_weight to prevent fleet-scarcity false-merges (F1's shared_wordlist failure mode). Tier weight raised to 1.0 so shared payload+C2 alone crosses threshold (F5's intended pass). - Adapter: from_synthetic_identity now reads SyntheticSession started_at + duration_s for session_windows and per-decky timestamps (the production-row adapter still uses start_ts/end_ts when available). - Fixture data: paused_campaign.yaml's JA3 collided exactly with vpn_hopping.yaml's (same TLS extension list). The collision fused two unrelated campaigns under the chained identity layer in the noise_floor composite. Made paused's JA3 distinct. Also wires Campaign / CampaignsResponse into models/__init__.py's __all__ that was missed in the schema commit.
18 lines
538 B
YAML
18 lines
538 B
YAML
# Bounds for fixture 3 (lone_wolf).
|
|
#
|
|
# Every actor in this fixture is a singleton (the wolf itself, plus
|
|
# every background-noise scanner). A correct clusterer puts each in
|
|
# its own cluster; that's a perfect score.
|
|
#
|
|
# Bounds are deliberately loose at first — we ratchet them up as the
|
|
# algorithm matures. Loosening any bound to make CI pass requires
|
|
# justification in the PR description (per CAMPAIGN_CLUSTERING.md §2).
|
|
adjusted_rand_index:
|
|
min: 1.0
|
|
homogeneity:
|
|
min: 1.0
|
|
completeness:
|
|
min: 1.0
|
|
singleton_recall:
|
|
min: 1.0
|