Skip to content

Method, version 0.5

Version
0.5, draft
Dated
November 6, 2026
Dashed numbers
Proposed defaults, to be set before the first prediction

These are the rules SOVRINT holds itself to. Most of them are about how a judgment gets written down, because that has to be right before any software is. There are four cases so far. The first file uses the status words and the rules for copies, and its draft prediction was declined under section 5. File 2, File 3 and File 4 use them too and make no prediction. The trend rules have their first series on Trends, which counts topics. File 2 has the first series for a narrative, a thin one: 15 items in 13 of 175 weeks. File 4 has another thin one: 32 items in 29 of 810 weeks.

A rule in the present tense binds SOVRINT now. Anything written with “would” is still only a plan. Drafts of this page were produced with AI agents, and SOVRINT is responsible for all of it.

  1. Find

    2.1

    Search dated public text for the words and write down the earliest line observed.

    On August 17, 2019, The Post Newspaper reported a Texas City rule under the line “From bell to bell there is no cell.” That is the earliest phone use found in the first file. Earliest observed source does not establish original authorship.

  2. Audit

    2.2

    Go back to every item and merge the copies. Eight pages running one story are one source.

    In the first file, one AP story on three sites and one ABC News story on eight pages count as two sources. No person has made that audit.

  3. Analyze

    2.3

    Read the audited items for how the wording changed and, where there is a weekly count, how it moved.

    In the first file, Pennsylvania’s heading and its rule use different words. See the 26 texts.

  4. Predict

    2.4

    Write the prediction down in advance, with its date and the rule that decides it, and keep it on the Record whichever way it goes.

    The first file has one draft prediction, declined. It is on the Record.

1Defined terms

1.1Narrative

A narrative is a claim about something in the world that can be written as one sentence and quoted, in some wording, from dated public text.

Daylight saving time is a topic. “Changing the clocks makes people sick” is a narrative. Both lines were written for this page.

Two texts carry the same narrative when they make the same claim about the same subject, even if the wording differs. The Method tracks the claim. Whether it is true is a separate question.

1.2Series

A series is the count behind a narrative or a topic: distinct items per calendar week, from a written search of one named public source. An item is one published text. A publisher is whoever put it out.

Copies are folded first. A wire story run by forty papers is one item with forty publishers.

A series counts what was published, which is a different thing from what people think.

1.3Trend

A narrative or a topic becomes a trend here when it has a series and the series changes. A topic trend shows a subject being written about more or less. It says nothing about any claim in those texts.

A micro trend has risen for 3 weeks running and is still small enough to list on one page: fewer than 10 publishers, or one place, or one language, or one community.

A macro trend has held a weekly count for at least 12 weeks and is carried by 10 or more publishers, under different owners, in at least 3 regions or communities. It must also do this among two kinds of publisher, each tested on its own. On Trends that means passing in both company filings (rule 1.6) and state bills (rule 1.7), each in its own latest window. The counts are never added together.

A trend that meets neither definition is unclassed until it meets one. Micro and macro describe reach alone. They are also the first two trend classes, which are the groups any error rate would be reported by.

How often a micro trend becomes a macro trend is still unmeasured. Getting that figure is part of why this project exists.

1.4Outcome words

These six terms have a fixed meaning on this site. Window A is the last four full weeks before a prediction’s issue date. Window B is the four full weeks ending on its resolution date.

Grow
The count in B is at least 25 percent above the count in A
Hold
The count in B is less than 25 percent above or below the count in A
Fade
The count in B is at least 25 percent below the count in A
Resurface
The series stayed at or under 10 percent of its peak for at least 8 weeks, then a single week reached 50 percent of that peak
Spread further
B holds items from 3 or more publishers that carried nothing in the prior 12 weeks
National coverage
3 or more outlets on the prediction’s written list of national outlets publish a distinct item inside the horizon, the days between issue and resolution. The list is fixed on the issue date

“Peak” stays off this list, because a peak can only be seen afterward. If any of these six is used loosely on this site, that is an error for the Record.

1.5Reading a count

Trends borrows Grow, Hold and Fade from rule 1.4 and reads them over longer windows, because a weekly count of federal documents jumps around. It adds up the last 12 full weeks and the 12 before them. At least 25 percent up is Grow, at least 25 percent down is Fade, and anything between is Hold. For a prediction, the windows in rule 1.4 still decide.

Under 24 items across both windows, about one a week, the reading is Too few to read and no percentage is shown. A rise from one item to three is not a finding. The twelve-week window was set before the first run of the full list and the floor after it. Both numbers are proposed.

A reading describes the window just ended. It says nothing about what comes next, and it does not adjust for the time of year. Trends also gives a longer comparison, the last 52 weeks against the 52 before, which holds every season on both sides. Under 104 items across those two windows, it gives no percentage. That comparison and its floor were set after the first counts were seen. Once or twice a year the government’s regulatory agenda mentions many topics at once, and a reading moves when such a day enters or leaves a window.

In the Federal Register, a publisher is a top-level agency with at least one item in the window, and a bureau or office is folded into its department, following the source’s own list. Nearly every publisher belongs to one government, and all of them publish through one federal journal. So a Federal Register series cannot be a macro trend, however wide it runs, and Trends says which parts of the test it passes. For a micro trend, only the publisher limit in rule 1.3 is applied, because this source is one language and one place.

Trends counts each document as the source returns it. No copy check is run and no item is audited, so these counts have not been through stage 2.2.

A topic stays on the list once it is there. A search can be corrected, with the date and the reason written on Trends.

1.6Company filings

The second source on Trends is SEC EDGAR full-text search, limited to six report forms: 10-K, 10-Q, 8-K, 20-F, 40-F and 6-K. Amended versions count too. Each topic has its own series there, under the same fixed list. The sources are never added together. The form list was set after test counts were seen, and it is proposed.

An item here is a document, by filing date, so a report and each attachment count separately. A publisher is a filer, one number in the SEC’s list. Filers under one parent are not folded, so owners can be fewer than filers. A region is one of the four US Census regions, or outside the 50 states, by the filer’s principal office. That grouping is proposed.

Companies file around their reporting dates, so a short window mostly shows the calendar. The reading in rule 1.5 and the micro test are not run on this source. Only the comparison of the last 52 weeks with the 52 before is given.

A topic passes the test in company filings when it has a document in each of the last 12 weeks, from 10 or more filers, in at least 3 regions. Passing here alone is not a macro trend. Every publisher here is a company reporting under one law through one federal system, so it shows reach among companies only. A macro trend must also pass in state bills, under rule 1.3.

These counts have not been through stage 2.2 either. Each one can be checked against the source’s own search page, which gives the same number.

1.7State bills

The third source on Trends is the monthly database file from Open States, which holds the bills of every state legislature, from 2017 in full. Each topic has its own series there, under the same fixed list. The sources are never added together.

An item here is a bill or resolution, by the date of its first action. It counts when one of the topic’s phrases is in its title or summary. Full bill text is not used, because too much of it is missing from the file. A publisher is one legislature, of the 50 states, the District of Columbia and Puerto Rico, and its owner is that government. Congress is left out. A region is one of the four US Census regions, or Puerto Rico. That grouping is proposed.

Most legislatures sit for part of the year, and more bills are filed in odd years. So the reading in rule 1.5 and the micro test are not run on this source, and a count of the last 52 weeks is compared with the 52 before only as a share of all bills.

A topic passes the test in state bills when it has a bill in each of the last 12 weeks, from 10 or more legislatures, in at least 3 regions. Passing here alone is not a macro trend. These owners differ, but they are one kind of publisher. A macro trend must also pass in company filings, under rule 1.3.

The file has no public search, so a count here cannot be checked with one link. It is checked another way: the dated file, a hash of what was read, the published script and the list of bills behind every count. The bills of one state, Washington, are also compared with that state’s own list on every run. These counts have not been through stage 2.2.

2The four stages

The stages are Find, Audit, Analyze and Predict. Cases are carried out one at a time. Trends counts topics by script.

2.1Find

Oklahoma Senate Bill 139, 1st Session of the 60th Legislature (2025), as introduced. Page 1, lines 22 to 24: subsection A, ending the rule with from bell to bell.
Students may not use cell phones on campus “from bell to bell.” Oklahoma Legislature, SB 139 as introduced, first reading, February 3, 2025. Highlight added. Source

Find is reading public text to locate a narrative. The place and date of the first sighting here get written down.

That records a sighting. Earliest observed source does not establish original authorship. Some content is never public, and some is removed before anyone sees it. Closed groups, private messages and anything behind a login are out of bounds.

2.2Audit

Audit is going back to each item and confirming it against the original or an archived copy. Copies are folded. Changed wording is marked. Each claim gets a status word.

Audit records what each item says and leaves true and false to fact-checkers. Forty papers running one wire story are one source, because repetition is not corroboration.

2.3Analyze

Analyze is reading the checked items as a series. It asks how the wording changed and when its reach widened, then which other explanations fit the same pattern. Trends runs a first, simple part of this on counts alone, under rule 1.5.

Intent, and who is behind a narrative, stay outside it. A pattern that looks coordinated may indicate coordination and requires corroboration. No account is called a bot. As a product stage this is scheduled, with software to come after item collection exists.

2.4Predict

Predict is writing down, in advance, how one measure of one narrative will move by a stated date, with the rule that decides it written first.

It is never about prices, demand, public confidence, votes or any other outcome outside the text. Nothing is predicted about a named person or organization. A case can end without a prediction. As a product stage this is scheduled.

3Status words

A quoted claim in a file carries one of three words. True and false are left out on purpose.

Observed
The text was seen at its source on the stated date, saying what is quoted. This describes the text. The claim inside it may still be wrong
Unverified
The claim appears in the text, and no primary record for or against it has been located
Not established
The material cannot settle the question. Cause, motive, scale and first author usually land here

If a court or a regulator has ruled on a claim, the page names the ruling and its date. That ruling is itself Observed, and the claim keeps its status word.

Each case also lists its search terms and dates, and what was left out. A line saying nothing turned up depends on the search behind it.

Quoted words are exact. Commas and periods follow US style, so one set inside a closing quotation mark may be an addition.

Parts of a file are marked by the kind of writing they hold. Observed means the same thing in both lists.

  • ObservedWhat the sources say.
  • AssessedA judgment about what they show now.
  • ProjectedA prediction about something still to come.

4Likelihood and confidence

Likelihood is the chance a target happens. Confidence is a grade on the material behind that judgment. The two can move apart: a prediction can say likely on thin material, or roughly even on very good material.

They never share a sentence. “Likely, with high confidence” is not allowed here. That rule, and the seven bands below, come from Intelligence Community Directive 203, a US standard signed January 2, 2015. The scale is borrowed because it is public and because it stops at 99 percent, and borrowing it implies no endorsement.

The seven likelihood bands of Intelligence Community Directive 203
BandPercentPosition on a scale of 0 to 100
Almost no chance1 to 5
Very unlikely5 to 20
Unlikely20 to 45
Roughly even chance45 to 55
Likely55 to 80
Very likely80 to 95
Almost certain95 to 99
The edges overlap in the source.

A prediction states one number and its band. That number is a judgment. It was not measured.

Low
The series is short, or the publishers are few, or much of it could not be audited
Moderate
The series is long enough and audited, and there is a known gap that could change the reading
High
At least 26 weeks of audited series, and no known gap that would change the reading

These three definitions are a first draft, and nobody outside has reviewed them.

5When there is no prediction

Declining is a recorded result, dated and counted on the Record.

A prediction is declined when any of these holds

  • Too few sources: fewer than 5 publishers in the series.
  • Too short a history: fewer than 12 weeks of series.
  • A coverage gap: the narrative lives in a language or region the named source cannot see.
  • A trend class with no measured error.
  • A horizon past 90 days.

These are declined whatever the evidence looks like

  • A ruling on whether a contested claim is true.
  • A label of bot, or of coordination, stated as fact.
  • A conclusion that media is synthetic, while no error rate for that test is published.
  • A statement of anyone’s intent.
  • A prediction about prices, demand, public confidence, votes or policy.
  • A prediction about a named person or organization. Counting text in a named source is a series, and that count is about the text.
  • Anything about private individuals. Cases quote institutions and published news only.
  • Flagging content to a site for removal, rating news outlets, or writing persuasion material for anyone.

Today every class is unmeasured, because no error rate exists. That is an absolute bar for clients. No prediction ships to a customer before its error rate is measured on held-out history, past data it was not built on, and published, per horizon and per trend class, with the sample size. That covers direction words and timing words as well as numbers.

A public prediction on the Record differs in who reads it: it is SOVRINT’s own judgment, dated in advance, that anyone can read and nobody buys. The conditions above apply to it all the same: no public prediction can be issued in a class until that class has a measured error. The one prediction drafted so far met three of them. It was declined and is the first entry on the Record.

6The ten fields of a prediction

Blank specimen

Method, version 0.5, section 6

Every prediction carries these fields, in this order. An empty field says “None.”

  1. 1The narrative, in one sentence.
  2. 2The series: search, named source, unit.
  3. 3The target: one statement that comes out yes or no.
  4. 4The issue date and the resolution date.
  5. 5The rule that decides it, which anyone can run without using judgment.
  6. 6Likelihood: a number and its band.
  7. 7Confidence: the grade and its basis, in a separate sentence.
  8. 8What would change this view.
  9. 9What a deliberately trivial prediction says about the same target.
  10. 10The author, who paid, and how it was made.

A prediction is judged under the version of this page in force on its issue date. It is never edited or removed after issue. A later change of view is a new dated note underneath it.

7Yes, No or Void

When the resolution date arrives, the rule is run against the named source and the raw count is posted beside the result.

The rule decides, whatever the author thinks is fair.

There are three results.

  • Yes
  • No
  • Void

Yes and No are what the rule returns.

Void means the named source stopped or changed so that the rule cannot be run, and the reason is published with the prediction still in place.

The grading rule was chosen in advance: the Brier scoring rule, which takes the stated probability, subtracts the outcome (1 for yes, 0 for no) and squares the result. Zero is a perfect prediction and 1 is the worst possible. Saying 50 percent every time gets 0.25. The same sum is shown for the trivial prediction, which assumes the coming window repeats the last one and says yes or no outright.

The Record keeps its own error rate, apart from the held-out rate in section 8. It counts resolved public predictions only, appears once 50 have resolved, and is split by horizon and trend class.

One target written two ways

Error rates are not yet published. Until they are, a prediction shown on this site is an illustration.

Bad. Made-up example. No such prediction exists.

The clock-change story will peak this winter.

“Peak” can only be seen in hindsight. “This winter” has no date. There is no source to count from, and the sentence has no way to lose.

Good. Made-up example. No such prediction exists.

The weekly count of distinct articles matching the search “changing the clocks” and health, in a named public news index, exceeds its trailing 12-week maximum at least once in a stated four-week window.

The likelihood is 30 percent, which the scale calls unlikely.

Confidence is low, because the series is 14 weeks long and the index holds English-language news only.

On the last day of the window anyone can run that search and compare the weeks. The answer is yes or no for anyone who asks.

8Eight planned steps

These steps are planned, and each depends on the one before it.

  1. Collection would store every item from one real source with the time it was seen, so a later test could use only what was known then. This has started for counts: Federal Register, company filing and state bill counts for the topics on Trends are stored with the time they were retrieved. The items themselves are not stored yet.
  2. At least two deliberately trivial baselines would be run, with their error measured on held-out history and published with sample sizes.
  3. A first backtest, a run over past data, would follow. It would split by time, and never at random.
  4. Calibration would be measured: does a stated 70 percent interval contain the outcome about 70 percent of the time. How narrow the intervals are would be reported beside it.
  5. An outside reviewer would check the protocol before any accuracy figure appears.
  6. The first error rate would be published per horizon and per trend class, with the baselines beside it and the rate of declined predictions.
  7. Clients would then see predictions, for those classes only.
  8. An independent party would re-run the numbers on stored history and publish its own figures, including where they differ.

Three rules hold across all of that. Every prediction must be reproducible from stored inputs and a recorded model version. A class that fails is withdrawn, and the withdrawal is published. If no class beats the baselines, SOVRINT publishes that finding and narrows the claim.

9Changes to this page

File 4, November 6, 2026
File 4 was added, and the opening now counts it and gives its thin series. No rule changed.
File 2, November 6, 2026
File 2 was added, and the opening now says a narrative has a thin series. No rule changed.
Layout, November 6, 2026
The four stages now open the page with their examples, and the page was set in a new design. No rule changed.
Version 0.5, November 6, 2026
Rule 1.3 now asks for two kinds of publisher, which on Trends means passing in both company filings and state bills. Rules 1.6 and 1.7 say so.
Version 0.4, November 6, 2026
Rule 1.7 is new: state bills are a third source, kept apart, checked by file and script instead of a search link, and passing their test is not called a macro trend yet. Section 8 records that their counts are stored too.
Version 0.3, November 6, 2026
Rule 1.6 is new: company filings are a second source, kept apart, and passing their test is not called a macro trend. Section 8 records that their counts are stored too.
Version 0.2, November 5, 2026
Topics can now have a series and be a trend (1.2, 1.3). Rule 1.5 is new. The opening and sections 2 and 2.3 mention Trends. Section 8 records that collection of counts has started.
Version 0.1, November 5, 2026
First written version.

Optional analytics

May SOVRINT use Google Analytics to count public-page visits and useful actions? It sets analytics cookies. Form answers and workspace activity are excluded. You can change your choice below at any time. About these cookies.