| Cross-type auto-pivot loop | Every selector type is a frontier node; metered spend stays behind one digest-bound approval | Typed nodes (selector_types + rungs.json owner/kit/neighbour) → case_state.propose → required Plan phase (PLAN_TOOLS, read-only) → auto free/urlscan pivots with ≤ N=25 hits, else proposal.json gated in audit.gate (harness approve · case_approve · TTY). Dispatcher ops propose + corpus-search (corpus_search tool). Assessment gains additive kit_siblings / neighbours / mentions — collected, never attributed. Rail: collecting ≠ attributing |
| MO-neighbour pivot | Reverse a non-CDN origin to its co-tenants — and only ever seed on a registrant join key | wp_mo_neighbours.discover reverses the estate's non-CDN origin IP (also the MX origin) through Netlas · Validin · urlscan, WHOIS-verifies each candidate apex, and classifies it same_registrant (current registrant e-mail/phone join key only — a proxied record contributes no phone) / same_mo (reference-data policy) / unrelated / unverifiable. Only same_registrant seeds the frontier; same-MO personas render as a rung-10 Related personas table in the report (--mask-personas to aggregate). A bulk-hosting guard fires before any spend; per-origin lock + disk cache + a per-run WhoisXML ledger hold across collector subprocesses, so an origin is bought once per case. RULE 5 rails intact: facts-only KB ingest, never an edge, never an operator_lead |
| WHOIS eras · urlscan Pro lifecycle | The timeline now knows who held the name before this operator | WHOIS history is an explicit --whois-history purchase scoped to seeds and cluster members (the render path never buys it); the house report renders a Registrant eras table (same-day flaps folded, registrar placeholders classed) and uses the current era's start as the archive-capture cutoff. urlscan Pro supplies the hostname lifecycle index — A/NS eras, CT and zonefile firsts, left-censored on a truncated walk — feeding the temporal view; verdict rows appear only on signal, and the API key is sent to urlscan.io only |
| Entitlement measured, not assumed | A key measured free skips the calls that would 403 | wp_capabilities.discover_plans probes each vendor's free account endpoint (urlscan quotas, Netlas plan, SecurityTrails/DNSLytics usage, IntelX /authenticate/info, Validin /api/paths) once per case into cases/<id>/capability_plans.json; enrich_live reads the store and gates only on a positive free verdict — unknown keeps the productive call as the probe. Censys search records its own verdict. A failed probe is reported this run and never frozen, so the next process re-measures |
| Netlas + the rest of the vendor wiring | Every registered key now has a pivot behind it | wp_netlas.py — Bearer client over the domains · responses · whois_domains · whois_ip · certs collections (search, count, facet, reverse-IP, plan), keyless query builder + web-UI links, ledgered, Cloudflare-safe UA; intel.py netlas ip|ns|spf|domain|san|title|plan|raw. Live-measured: domains a:<origin> returned 32 apexes on a 32-domain estate (15 members + same-MO siblings under other personas). Alongside: SecurityTrails DNS-history eras + DSL reverse-WHOIS (diffed against WhoisXML), DNSLytics reverse-IP under its own co-tenancy-routed key, GrayHatWarfare exposure lead + report section, Shodan cert/JARM search, once-per-case Censys cert search with a shared-cert fan-out guard, IntelX auto-fire in pipeline open (loop: --full only; role mailboxes excluded), and Validin wired natively (domain lookup, reputation, cert and favicon hosts). Frontier ranks owner-link candidates above lookalikes |
| The house report, composed deterministically | The editorial PDF/DOCX no longer needs a model to write it | intel.py house-report <CASE-ID> composes the IntelReport document from the case dir: sections I–XI, both confidence scales + the ICD-203 × Admiralty scatter, relationship graph + entity-relationship map, attribution inference chain, temporal view + registration heatmap + domain × shared-indicator matrix (which honours the §2.5 false-positive control and carries the WHOIS join keys), a landing-page capture per estate host (proxy-gated egress; a page that will not render falls back to the newest public web-scan, then a web-archive snapshot — captioned, dated by the archive, and labelled a previous owner's page when it predates the current registration), per-domain dossiers, a glossary, Appendices A–E. Rule 12 scrub of tool/vendor/path names; third parties masked through one gate (scripts/cti_third_party_mask.py). One figure source (scripts/cti_report_figures.py) feeds both the dashboard DOCX and the house PDF, so the two deliverables cannot disagree. --no-screenshots is fully offline; --no-archive-fallback forbids the stand-ins |
| ANY.RUN: the gate is real, and the docs now say so | Detonation exists — behind five gates, each of them code | SKILL.md, the README callouts, .env.example and the key registry claimed "no submit path". False since the gated layer landed. anyrun_submit is gated by: per-submission confirmation (a confirm=false briefing first — a data-driven approval_briefing exemption in tool_policy.json now lets that step through the MCP approval gate, fail-closed to fully gated if the file is unreadable); private by default, public refused unless ANYRUN_ALLOW_PUBLIC=1 grants a standing authorization, and then only as an explicit, recorded downgrade; a fail-closed plan check (/user private quota — zero is denied and no attestation overrides it — else a prior private task, else --i-have-a-paid-plan); a polled post-submit privacy read-back that withdraws and flags a task that still landed public (verify-privacy <uuid> finishes the check if the task outlives the wait); and the harness deny unless HARNESS_ALLOW_SUBMIT=1. 103 stubbed checks in test_intelx_anyrun §7b–7c; test_tool_gate §2 pins briefing-allowed / confirm-denied / fail-closed |
| Repo hygiene | The tree checks itself for pasted keys | audit.sh §5b greps every tracked file for vendor key shapes and KEY=value lines — proven to fire on a planted value and clean on the tree, so a key can only live in .env. AGENTS.md rewritten as the cross-agent Repository Guidelines. Key-alias registries reconciled with every tool's _secret() lookup and locked (tests/test_key_alias_registry.py); SecurityTrails / DNSLytics / CertSpotter registered so the capability banner stops going silent on keys it uses. The three workflow diagrams re-rendered from current sources — 79 @tools, 9 commands, Netlas, gated ANY.RUN |
| Every documented command is real | 26 SKILL.md commands that had no code behind them now resolve to a tool — or say what they are | 18 new keyless-first CLIs under scripts/osint/ (hash_id — MD5 vs NTLM before you submit, vuln_check, username_enum, phone_osint, github_osint, reputation_check, msft_recon, cn_recon, traffic_rank, sharelink_resolve, dork_builder, exposure_score, signature_scan, kb_crossref, case_drift, deep_profile, wifi_ssid …) plus 8 existing scripts/webpivot/ shims (cert_pivot, email_hygiene, wayback_fetch/harvest, rank_relations, sensitive_paths, pivot_suggest, crypto_balance) registered as @tools and intel.py ops; every SKILL.md command row now names its T2 CLI and T1 tool, or is labelled [model] / [unimplemented]. 79 @tools, and the SDK allowlists are locked to the decorated set (test_tool_registry.py). Clustering enforces the two-artifact rule: each cluster carries corroboration, and one shared artifact is flagged LEAD ONLY, never an attributed estate. The vendored engine's own tests now run in audit.sh §9–10 and CI — they ran nowhere before |
| ChongLuaDao in the pipeline · subdomains · one timeout ceiling | The first-party feeds grade every host, live subdomains join the case, and no call hangs a run | wp_cld.py runs per collected host inside enrich_live — denylist verdict + IoC analysis land as reputation facts (never a cluster edge) and CLD WHOIS is the primary source for .vn names. subdomain_enum unions subfinder (auto-keyed from .env), amass, assetfinder and findomain, DNS-verifies the names into cases/<id>/subenum/<apex>.json, and the frontier queues the live ones for the next round (hoster plumbing is a fact, not a seed). A single per-call ceiling — CTI_CALL_TIMEOUT, default 1800 s from WebPivot/references/timeouts.json — floors every fetch, vendor call, collector and renderer subprocess; raw DNS/TLS probes keep their fail-fast bounds, and a running MCP server keeps its value until restarted |
| Registrable apexes · landlord IPs · kit binders | The frontier and the KB agree on what an apex is and which IP is a landlord | A vendored Public Suffix List (public_suffix_list.json, wp_psl_update.py) drives one _registrable() reducer, so shop.id.vn and panel.co.uk fold to the right apex everywhere — frontier, ingest, report, Blueprint. shared_hosting_max_cohosts (12) is the one number that marks an IP as shared/bulk hosting: its hosted_on edges become facts, the cluster partition ignores them, and co-tenants are held back as leads. Expansion depth is anchored: a host owner-linked to a previous hop is related_hosts, never a member. Scraped social links resolve to the account — per-network reserved paths, second-segment routers and library/vendor credit accounts are reference data, and a bare platform apex (t.me, facebook.com) is never a handle |
| Blueprint folds to apex level | A hundred-host estate no longer silently drops the HTML report's architecture tab | Archify's architecture type draws ≤ 12 nodes · 18 edges, so cti_archify.py now collapses hosts under their registrable apex (Estate · N hosts), folds the long tail into +N more apexes, ranks finding-bearing apexes first and places the operator hub mid-row with spokes above and below. CTI_ARCHIFY=1 (auto: full graph if it fits, else the fold) · force (the widest 25-node grid) · 0; --plan prints both outcomes offline, and every HTML export now confirms the Blueprint mode first (Step C — --yolo keeps Auto). Locked by tests/test_archify_blueprint.py |
/cti on every coding agent | One registration step wires the commands into every agent on the machine, not only Claude Code | scripts/register_agents.py (run by register.sh) registers the 9 commands with omp · pi · OpenCode · Gemini CLI · Qwen Code · Factory droid · Windsurf and installs /cti as the shared ~/.agents/skills/cti skill for Cursor · Copilot CLI (/cti), Codex ($cti — Codex removed custom prompts in 0.117, so the old codex/cti-expert.md is gone) and the ChatGPT desktop app (@cti). Every file is a pointer stub to this clone, so a git pull updates all agents at once. Install and --uninstall touch only what they wrote — marked stubs, and ~/.claude symlinks that resolve into this repo — never a same-named command or skill of yours. Locked by tests/test_register_agents.py |