3 min read

Playbooks

A playbook is a named line of investigation. Instead of tuning an investigation tree (which transforms, how deep, how many entities), you pick the question you are asking and Viokit runs the tree that fits it. It then hands you the checklist of steps that stay with you: the ones no tool should do for you, with the source to use and the legal or ethical care each needs.

A playbook adds no new power. It is a saved choice of lookups and limits for the investigation tree, plus the manual steps.

The starter playbooks

Playbook id Question it answers Seed
who-is-behind-this-website Which company runs this site, who directs it, what else do they run? domain
who-is-behind-this-company Who are its officers, what else do they direct, who shares its address? organization
map-domain-infrastructure (web-dns pack) Which hostnames, addresses, registrar and hosting sit behind a domain? domain
what-has-happened-at-this-address Who owns it, who is registered there, what has been published about it? postal-address
corporate-due-diligence Is this company what it says, and is anything recorded against it or its people? organization
trace-a-vehicle-or-aircraft What is this vehicle, aircraft or ship, who is it registered to, is it sanctioned, and who stands behind the owner? vehicle, aircraft, vessel
shell-company-network Is this company part of a network of shells: shared registered office, officers and controllers, parents, offshore leaks? organization
sanctions-evasion-screen Is this company or person, or anyone who owns or runs it, on a sanctions or PEP list, in the offshore leaks, or holding aircraft? organization, person
phone-number-lead What does this phone number say from its own structure, and which case records hold it? phone-number
person-footprint (opt-in) What does a person's public footprint show? person

who-is-behind-this-website encodes reference investigation 01: domain, then the contacts on the site, Companies House, officers, appointments, and shared addresses. Its manual steps are the parts of that investigation that stay manual: LinkedIn staff, usernames, and a vehicle registration.

shell-company-network and sanctions-evasion-screen are wide rather than deep: they follow ownership, control and shared addresses and then screen what they find. A sanctions hit is a lead to check against the list entry, never a finding. The person-reaching lookups in both are held by the purpose gate until the case records a purpose. phone-number-lead runs one offline lookup on the number itself (country, line type, validity), which reveals nothing about a person and so is not behind the gate; everything about who holds the number is left as a manual step. See Follow a phone, email or bank-account lead.

Running one

Pick a playbook in the console, give it a seed (for example the domain example.com) and run it. You get back the tree summary (entities, runs, why it stopped); the parts of the playbook this deployment cannot run because a pack is not installed (for example no Companies House lookup), which are reported, not errors, while the rest still runs; and your checklist of manual steps. Read the tree afterwards. Run the manual steps by hand and record the results, so they carry provenance like everything else.

If a source is not installed, for example sanctions, due diligence still runs the registry and news parts and tells you screening was skipped. A skipped part means "not checked", never "checked and clear".

Manual steps

Each manual step names the source, how to record the result, and a note on the law or ethics. Examples: LinkedIn is manual because its terms forbid automated collection; the open electoral register is restricted in use; a vehicle registration can identify a private keeper. Read the note before you act.

Opt-in playbooks

person-footprint is for a named private person. A run needs the owner's go-ahead (data protection and proportionality). Viokit refuses until you confirm, and the refusal states why. Only confirm once the go-ahead exists. The playbook is also passive-only by default.

Limits and defaults

Each playbook carries its own depth and entity limits, and may restrict tool kinds (passive only). map-domain-infrastructure is passive only, so port scanning is listed as a manual step; scanning touches the target and needs authorisation.

Docs

↑↓ to moveEnter to openEsc to close