Things you would not find alone.

The first searches are written from it. Six cycles on one sharp question beat twelve on a vague one, which spends them decomposing instead of covering ground.

They land at priority 0.95 — right behind your primary at 1.0, ahead of pattern-born leads at 0.85 and routine decompositions at 0.7. Use them for the vectors you already know matter, not as a wish list.

The first run's searches are informed by what the record already holds. Someone arriving with a box of scans should choose “upload first” on the welcome card and run once the box is in.

A run asking for more cycles than your month has left is quietly clamped to the remainder, not refused — so a big first number can come back smaller than you asked.

After a pattern-born question the next pick is forced to be a plain one, so the slow loop's structure and the fast loop's coverage both get worked. Redirecting every cycle toward one starves the other.

Dates are never read from a bare year in the text (a 1996 article about 1976 mentions 1976 first); only a byline, a dateline, a URL or page metadata counts. Set the rest by hand in Sources, or they sit quarantined.

Anything not from a .gov or .mil host is presumed copyrighted, and a copyrighted source's text never leaves in a share, fork or export. Mark public-domain and government documents as such in Sources so their text travels.

Sources that share distinctive phrasing — a wire story reprinted five times — collapse into one lineage, and corroboration counts lineages, not pages. A break of kind “echo” is exactly this caught.

A fork carries the evidence, the claims and the frontier with a lineage entry back to the parent. Dig there; the main investigation's numbers stay clean, and you merge back only what proves out.

It is a union: the destination always wins, and a claim graded differently on the two sides is kept as-is and written to the merge report for a person. Read the confirmation before you click.

It is read in a 256-pixel tray, on cards, in the share email and in the tab title; past 48 the form warns you it will be cut somewhere. Rename any time from the investigation's Settings.

When a copy you take withholds copyrighted sources, the bring-your-own-copy card offers the list as a file: every withheld document, where to obtain it, and the content hash your copy must match.

Retract a wrong claim, promote a right one, close a dead lead, rule two names the same or different. Each survives the worker's later pushes and changes what the next cycle builds on.

The primary question is written to the frontier at priority 1.0; every line of the secondary box becomes a question at 0.95, worked right behind it, not as an afterthought.

Each sets a name and a question you can edit — the quickest way to see a real run before composing your own.

Private, unlisted or public can be changed any time from the investigation's own Settings; going public lists it in Community the moment you do.

The form warns rather than blocks — the name is read in the tray, on cards, in emails and in the tab title, and the long ones lose their ends there.

The welcome card asks whether to search now. “Begin” queues a breadth pass that lands the top pages at once, then the full run; “upload first” lets your own documents in before the web is searched.

Next moves is deterministic: little learned across the stop window with questions still open means the web has run dry on this angle. Upload your own documents, paste the links you know are good, or ask a different secondary question.

The suggested move there is to read the closing narrative; reopening a question in the Frontier is how the loop starts again.

Uploads, pasted links and scraper hits land without being read for structure. A survey is cheaper than a cycle: it clusters, corroborates and asks what is new.

Every break names its instrument — Lineage, Findings, Frontier, Knockout, Apophenia, Surfaces, Dynamics, Standing answers. That is the fastest way to learn what each one is for.

“seen — clear” acknowledges the breaks; the log below keeps everything by cycle.

An estimate marked “measured here” comes from this investigation's own cycle timings; “est.” is a default until it has some.

The ghosted text in the composer is Okusoko's own next question — one keystroke sends it.

/run 3 · /survey · /reverify · /add <url> · /q <secondary question> · /kill and /reopen <question id> · /promote, /contest, /retract <claim id> · /open <claim id> · /view findings.

A question for the frontier, a run or survey, a status change, a source by URL — each is a card. Dismiss hides it without acting.

A URL goes straight to add_source; a description becomes a research job that searches for it and digests what it finds.

Okusoko was under strain for this turn and answered with less care than usual — read it more skeptically, and ask again later for the same question.

Only the person who started a thread can delete it. Under a horizon, sources after the date are hidden from Okusoko, and it warns once that what it already knows of what came later can still colour emphasis.

Search matches by meaning: “were any drugs found in his system?” beats “drugs toxicology”. Re-asking the same thing in other words returns the same claims — vary the angle instead.

Each shows a live one-line reading of the record and whether anything changed since you last looked; the compact strip on the Overview sorts the fresh ones to the front.

Click it instead of hunting the case log. “what is this?” on a card opens the manual at exactly that instrument.

Yours land at 0.95, above pattern-born leads and routine decompositions, and are decomposed on first contact.

Ask opens a conversation on it: where the record stands, what is missing, and two or three angles worth digging — take one and the dig goes outside the record for the documents. What it finds is one click from being added. The button reads “continue in Ask” once a question has its conversation.

Instead of a generic run, the next cycle works exactly that question — the worker's own way of pursuing it. It is disabled while the worker holds another job on this investigation — one job at a time.

Where it came from, when it was first attested, what working it produced, its trajectory, and any children it spawned.

A killed question is dimmed and kept; reopen it any time and the loop's attention returns.

Surprise bits measure how improbable a claim's combination of entities is in this corpus — the structurally novel claims rise; newest is the default.

It appears only when copies inflate the count — five pages carrying one wire story. Corroboration counts lineages, not pages.

Counts recompute over pre-horizon or known-to-investigator sources, and a claim none of them support is not shown; the header says how many are beyond the horizon.

Corroborated, contested, retracted, provisional — set from the Inspector or with /promote, /contest, /retract. A later job push never undoes them.

“clear” resets it so the next date pass can re-infer. A hand-set date outlives the worker's later pushes.

Click the rights chip to review: public-domain, government, openly-circulated, licensed, copyrighted, unknown. The claims and quotes still travel with the content hash; a lawful copy on the other side restores the text.

It filters to the sources nobody has reviewed for rights — the ones whose text may travel when it should not, or be withheld when it need not.

Their own notes, a leak, an interview — with an optional reason, logged to the event feed.

A catalogue record, a reconstructed abstract, a finding aid: claims from it document what the work says about itself. “wayback” means the live page was dead and the text came from an archive snapshot.

A citation is the only edge that earns a direction on its own — the text named the other source. Kinship is shared distinctive phrasing with no direction asserted.

Toggle “isolated sources” to hide the ones with no textual relation to anything else.

It is drawn in its own colour so you never mistake it for a citation.

Claims another source also backs are kept. Only an admin or the person who added the source can delete it.

A failed page is the one to re-scan and re-upload; click a tag chip to open Findings filtered on it.

Images go through the same OCR as a scanned PDF page, rendered at the scan's own resolution.

“seen before” shows what happened to the earlier copy and lets you retry it — useful when the first read failed or degraded.

Split a very large PDF; nothing was queued.

When half or more of the readable pages are flagged handwritten, extraction takes one claim per line with verbatim quotes, names kept exactly as written.

The reading pile is a shared list of maybes that costs nothing until someone releases a link into the record or drops it.

Without one, searches use a shared default; on the Max plan your own keys mean uncapped cycles.

The ladder is scraper → http → readability → browser → Wayback. A learned scraper is validated on that page and shared to the tool library, so the next investigation meeting the site just uses it.

Or to the hold pile. The extension does the same with a picture of a scanned page.

The worker cannot reach it and there is no text to scrape; the picture goes through OCR like an upload.

It rides along as a margin note anchored to the page — whether or not you ingest the page at all.

A capture under about 900 pixels on its short side is flagged as small for newsprint; a full-window capture reads cleanly.

So it never travels on a share or a fork. If the document is public domain, mark it so in Sources afterwards.

It rides your okusoko.com session; signing out of the site signs it out too.

A plain click opens a dossier; double-click focuses on a node's neighbourhood; drag pins it in place; wheel zooms at the cursor.

Joint passages, independent lineages, a shuffle-null verdict, a percentile against random mention-matched selections — and a caution if the co-presence entered through one question's searches: built, not found.

Two entities sharing one Wikidata identity are never merged by the system — you rule. An entity with a contradiction on it is worth checking before trusting claims about it.

A rare but real entity may not render; the search box also matches by a co-occurring entity's name, which finds it anyway. Map-out shows any entity completely.

Standing, sources, relations, questions, gaps and every claim, structured — for your own notes or a colleague.

Where the coverage runs out becomes a secondary question for the next cycles in one click; twins get same/different rulings right there.

Claims that mention the name in text but were never linked by the resolver — the entity has more than the graph shows.

The whole trail is only as strong as that one account; find a second lineage before following it further.

A confirmed pattern sorts to the top and stays confirmed; a dismissed one leaves the list and the survey never brings it back — “show dismissed” restores one. Both outlive the worker's pushes.

“same entity” or “different” takes effect at the next resolver pass; nothing merges by itself.

Two entities that never meet in a corroborated passage yet keep sharing associates, places and years — with a shuffle-null verdict. Not a claim, not a node; a lead.

A deposition, a letter, a case number — its question is “go get this”. The interrogation ranks these to the director first.

Contest or retract the wrong side; a resolved contradiction becomes a break. The judge confirms real conflicts; lexical-only ones are marked unconfirmed.

It opens on the core period — the densest five years, with each source capped at three claims a year so one thick document cannot own the centre. The chip returns you there.

A claim about 1965 known only from a 2020 document sits at 1965 and disappears once the horizon predates 2020.

A dot is a full date; a band is a year only. Switch lanes by source, entity or epistemic grade.

An account whose wording strengthened by 0.15 or more across the years while every later telling drew on the same lineages as the first.

Independent corroboration, or a repetition of what was already known.

Drift needs corroboration links between claims and publication dates on their sources. Set dates in Sources, then run a survey.

Findings, Sources, Lineage and Chronoscope honour it. Entities, Patterns, Surfaces, Map, Narrative and the others are computed over the whole corpus and carry a banner saying so.

Sources you marked “known to” them count regardless of date; undated sources are quarantined, never silently in or out.

Today's corroborated claims whose independent support already existed inside the horizon.

This is the one deliberately full-knowledge comparison: today's statuses are the “now” side by design.

The “loudest gap” line on each axis is a ready-made next question.

A wire story on forty pages verifies perfectly and is one lineage; the axis exists to catch that. Redraw the zone thresholds with the sliders rather than trusting a fixed median.

Hover a bubble for momentum, velocity, acceleration, coherence, entropy and flags before you click.

Nothing is hidden for being slow. The “bridges” panel ranks claims by surprise — the fastest way to the structurally novel.

Arc weight is how many claims mention both places.

Places are geocoded when entities resolve; a place that could not be located also shows up as a surface gap.

Every factual sentence carries its claim; the Inspector shows the quote, the source and whether the bytes matched.

Material arrived since it was written; “rewrite narrative” queues the job. A section's basis is hashed, so an unchanged one is left alone and costs nothing.

It counts factual-sounding sentences with no claim marker behind them.

Clicking an outline entry scrolls to its section; old bodies are kept with their word counts and reasons.

Opening the Notebook turns it on by itself; the ink chip in the header does the same.

The browser's speech engine writes the note as you speak; the recording goes to Whisper in the background and replaces the wording when it lands. “⌁ whisper” or “⌁ browser” on the note says which one produced the final text.

A pinned note travels in every export and fork even when the margin is private; a held-back one never travels even when it does. Click the cycle control on the note.

The margin sits outside the record on purpose: no epistemic grade, never cited, never corroborated. If a note says something the record should hold, add it as a source or a question.

Notes on claims, sources, entities and clipped pages share one reverse-chronological feed; click any to jump to what it annotates.

Corroborated, contested, retracted, provisional — set on the claim while its quote, its source and the verification result are in front of you.

Unverified evidence is shown, not hidden; “re-verify” re-runs the matching over every unverified row, computed, not written.

Phases are colour-coded by stage and grouped by cycle marker.

A queued job is removed before a worker takes it; a running one stops at its next progress line, and a run keeps every cycle it finished.

Clearing is for the whole investigation. The row, its error and its log are kept.

The current cycle is assumed half done.

An unmatched address sends a real invitation. The owner can never be removed from here — transfer the investigation first.

Check it before deciding how much to trust material someone else added.

The root picker finds a claim, a source, an entity, a pattern or a question by a few letters; that is what separates this from a forum.

Closing a hole can end in something the record understands — a secondary question on the frontier, a link held in the reading pile — and the outcome stays on the closed card.

Like a private note, the argument stays with this investigation.

A pinned note always ships; a held-back one never does. A rigorous horizon fork strips every note regardless.

Review rights before you package or share; the manifest hash chip is what rsx verify checks a received copy against.

Visibility, the margin's travel, merging another investigation in, packaging as .rsx, and the size of the record follow.

You need not open an investigation to see it is mid-job; the meter on the card shows how many of its quotes are verified.

The cards look the same otherwise. Only an owner can delete an investigation; an editor can change it.

That is the one place on this page that says a record is a copy with parents rather than original work.

“N of M sources are copyrighted — you bring your own copies”: their claims, quotes and content hashes travel; their text does not.

Setting an investigation back to private removes it from Community; forks made while it was public stay with the people who made them.

The worker fills a fork in a minute or two; the activity bar shows it landing. Deleting a copy touches neither the original nor anyone else's.

One heart per person; a second click takes it back; nobody is ever listed, only how many.

Your public investigations are listed; the private and unlisted ones appear only as a number, and dates are months. Turn the page off in Settings and only your name shows anywhere.

It is the share of their quotes found byte-for-byte in their sources, across all their work — before you read any of it.

kind, status, space and cleared combine as query parameters, so /runs?kind=run&status=failed is a standing view of failed runs.

The row, its error and its log are kept behind “show cleared”; clearing takes it off the queue pages so an old bad scan stops greeting every new upload.

A run reports cycles, claims, patterns and why it stopped; a survey its corroborations; an ask its answer. Read the line before opening the job.

A job interrupted by a worker restart goes back to the queue and is picked up again from the start of its work, up to four times, before it counts as failed.

Google Books and the National Archives search only with a key; the National Archives cap is 10,000 queries a month, a budget to spend deliberately.

The site lets only a real browser in. Documents it finds land in the reading pile with the instruction: open it, download the PDF, drop it on Upload or send it from the extension.

A tertiary summary sits honestly at “now” under the horizon instead of leaking into the period it describes.

“used N times” and “validated” on a domain scraper tell you how battle-tested it is; a disabled one is disabled everywhere.

So a stolen session cannot disarm it. Enrolling again after an abandoned setup is fine — a stale unverified factor is cleaned up first.

The old inbox and the new one each get a link; the change lands only when both have been clicked.

It ends every session at once, unlike a plain sign-out, which ends only this one.

Pages, cycles and chat are metered by the month; storage is a standing total that only falls when something is deleted. The chat row also says roughly how many questions are left.

Write the line that says what you research; or turn the page off, and only your name is shown anywhere.

It reads that investigation's queue, its last jobs with their errors, and your role — ask “why is my run still queued?” and it looks before it answers.

Open a view, show a tutorial, a filled-in New investigation form, a job for the worker — each a card you click; nothing happens until you do.