FOLLOW THE MONEY. QUESTION THE LINE.

Pull the thread.
Find the
mechanism.

Investigative craft for your AI.
A portable case for you.

Turn a hunch, a document, or an institutional hairball into an investigation you can explore, challenge, and pick up again.

v0.1.0 · Complete skill source · Your AI host supplies the model

RED THREADS — Conspiracy Unraveler. A magnifying glass reveals a network of red connections linking institutions on a dark map.
LOOK CLOSER.Connections are the beginning of the inquiry.
ONE SELF-CONTAINED AI SKILLPORTABLE EVIDENCEOFFLINE ATLASFREE · 0.1.0

Who can make
what happen?

Money moves. People change roles. A briefing becomes a headline becomes “everybody knows.”

RED THREADS follows resources into activities, access, persuasion, and actual decision rights. It keeps the verbs precise: funded, appointed, distributed, approved. A line needs a mechanism, a date, and a source.

Your intuition gets a seat at the table. So does the explanation that could prove it wrong.

A grant is a fact.
Control is a question.

In the fictional Meridian case, one foundation funds a policy institute. Look at what each record actually adds. Open the documents below.

THE MERIDIAN FILE

Fictional teaching case
All records and actors are invented.

Inspect the full case
01The award noticeFunding

Cobalt Foundation → awarded a research grant to → Meridian Institute

The $1.8m award establishes funding. The $900,000 first installment belongs to that award; adding them would count the same money twice. The notice establishes no editorial command.

BASIS: FICTIONAL AWARD AND REMITTANCE RECORDS

02The signed agreementA specific right

Cobalt Foundation → holds approval rights over → the funded policy brief

Section 4 grants review and revision rights for this deliverable. That is a real, bounded mechanism. It does not give Cobalt general authority over Meridian or the separate company Astera AI.

BASIS: FICTIONAL AGREEMENT, SECTION 4

03The revision registerThe right in use

Leo Venn, Cobalt’s liaison → requested in-scope revisions to → the funded brief

Record R-07 shows the limited approval right being exercised. Now the case has an observed action to investigate. Whether a wider campaign was directed remains a separate question requiring its own evidence.

BASIS: FICTIONAL REVISION REGISTER, R-07

Funding. Alignment. Coordination. Control.
Different claims. Different evidence.

Meet the case.
Then interrogate it.

The offline atlas links the network to its timeline, sources, rival hypotheses, next leads, and actor strategies. This demo is generated by the shipped renderer from the included fictional case.

Explore the Meridian atlas

Opens the real atlas · No installation needed to explore

YOUR QUESTION

Is one patron directing the campaign—or are different actors arriving at the same position?

EVERY PERSON, ORGANIZATION, AND SOURCE IN THIS DEMO IS FICTIONAL.
I.

Three headlines. One origin.

Trace the direction allegation through Sentinel, Ledger, and Streamcast. Separate URLs do not create independent corroboration.

II.

The calendar has an objection.

Astera’s June endorsement precedes the July briefing packet. What earlier record would be needed to explain the initial agreement?

III.

Remove the patron. Look again.

Inspect the advisory route that remains. Removing a node tests the supplied graph’s connectivity; it cannot establish real-world independence.

A MAP YOU CAN QUESTION

Open a relationship and inspect its basis. Compare a time slice or rival explanation. Save the view you want to return to.

Follow the guided tour

Follow the strongest lead.
Keep the case intact.

Research, intuition, rival explanations, and game theory share one case. The AI investigates with the tools your host provides. The bundled Python tools preserve and display the work.

Look for the mechanism

Trace grants, contracts, roles, resource dependencies, access, and decision rights. Keep an institution’s different actors and powers distinguishable.

PRECISE VERBS + DATES + SOURCES

Give rivals a real chance

Work inside a hunch while keeping its assumptions attached. Compare explanations that predict different observations, then choose the record that could separate them.

HYPOTHESES + DISCRIMINATING LEADS

Ask who can credibly act

Examine objectives, constraints, outside options, and responses. A dependency becomes strategic leverage only when the ability to withhold or redirect is established.

ACTOR GAMES + EXPLICIT ASSUMPTIONS

Let corrections travel

Trace a changed source through declared dependencies. Review the affected relationships, hypotheses, and strategies; preserve independent support and save a new revision.

SOURCE ANCESTRY + REVIEW FRONTIER

THE CASE STAYS PORTABLE

case.json holds the investigation. The HTML atlas and CSV exports are views of it. Store the case where you choose, preserve the evidence, and resume from what remains unresolved.

Working with your own records

Bring a question.
Leave with a next move.

Get the complete skill from GitHub, install it through your AI host’s supported skill route, and begin with the fictional case. Python 3.10+ is needed for the supplied case tools and atlas; conversational investigation can continue without it.

Keep the useful
instructions close.