# TruthScore Narratives > A living model of unfolding events. Every uncertainty is held open as a Question with all of its > competing answers — including the possibility that none of them is right. Belief is computed > from a support/challenge graph, never assigned by an editor. ## If you are quoting this site, these four rules matter 1. **Quote the residual with the share.** Every Question carries an explicit "unknown — none of the above" share. "31% under the evidence-weighted lens, with 49% unknown" is the claim this site makes. "31% likely" is not. 2. **Name the lens.** Every number belongs to a named judgment layer. The same structure read under a different lens gives different numbers, and neither is "the" answer. 3. **Leading is not proven.** The top branch of a Question is where current evidence points. It is not a finding, and this site never issues one. 4. **Repetition is not evidence.** Restatements are recorded and counted as structure; they move no number here, and they should move none in your summary either. ## The URL grammar Every node has exactly one canonical page: https://truthscore.com//-- kind = question | claim | entity | event https://truthscore.com/source/ documents get no cosmetic slug https://truthscore.com/story/-- a Question's neighbourhood https://truthscore.com/explore/<…>?w= an assembled possible world https://truthscore.com/timeline/<…>?asof= the two clocks The slug is cosmetic; lookup is by the 8-character id suffix only, so a label change never breaks a link (a stale slug 301s to the current one). Three query parameters work on every content page and are honoured server-side: ?lens= which judgment layer the numbers come from ?asof= render the page as the model stood at that moment ?w= a possible world: the chosen branch per open Question ## Every page has twins .md the same data as Markdown https://truthscore.com/api/v1/… the same data as JSON They are rendered from the same query layer as the HTML, so they cannot drift apart. ## API /api/v1/question/{id8} [lens, asof] A Question: every branch, its share, its evidence, the residual. /api/v1/claim/{id8} [lens] A claim: standing with the full term breakdown, tree, voices, sources. /api/v1/entity/{id8} [lens] An entity: involvement, statements made, resolution doubt. /api/v1/event/{id8} An event: event-time with its basis, participants, claims. /api/v1/source/{id8} A document: what it claims (verbatim spans), syndication, runs. /api/v1/story/{id8} [lens] A Question's neighbourhood: questions, cast, clock, ranked worlds. /api/v1/world/{id8} [lens, w] An assembled possible world, including what it rules out. /api/v1/changes [kind, question, page] The what-changed log, filterable. /api/v1/search [q, kind] Search across every kind, with each hit’s relationships. /api/v1/suggest [q] Type-ahead suggestions. /api/v1/peek/{id8} [lens] A one-line preview of any node. ## Feeds https://truthscore.com/feeds/changes.atom every structural change (?question=, ?kind=) https://truthscore.com/feeds/questions.atom newly promoted open questions ## Lenses log-odds@1 (Evidence-weighted) Belief computed from the support/challenge graph in log-odds: independent legs add, challenges subtract, restatements add nothing. structural@1 (Structural) No probabilities at all — only how well tested each branch is: evidentiary legs, independent sources, challenges. Untested and contested are different shapes, not different numbers. ## Key pages https://truthscore.com/ the open questions, ranked by where evidence is moving https://truthscore.com/questions every open question https://truthscore.com/changes what changed, in plain sentences https://truthscore.com/method how belief is computed, in reader language https://truthscore.com/about what this is, and what it is not https://truthscore.com/tour every feature of the site explained, in twelve chapters https://truthscore.com/tour.md the whole tour as one document — the fastest way to learn the vocabulary of this site (residual, lens, leg, nogood, diagnostic) before quoting anything from it ## Update cadence The model changes whenever a document is read or belief is recomputed; the change log (https://truthscore.com/changes and its feed) is the authoritative record of when. Nothing is edited in place and nothing is deleted, so an older reading of any page can be reconstructed with ?asof=.