Name: Shared Sapience Progress & Claims Tracker
Creator: Ben Linford
Published: 2026-08-07T21:16:20Z
License: https://creativecommons.org/licenses/by/4.0/

The knowledge chain

From a daily edition to a public evidence record

The Century Report records developments as they happen and supplies the wider context and source trail. The tracker carries qualifying developments forward so patterns can be examined across weeks and months.

Publish the source record

Each tracker cycle begins with a published edition at its canonical URL. The edition contains the reporting context and categorized source list.

Update continuing arcs

Developments that materially advance a defined arc enter its timeline. One development can advance several arcs and appear in each relevant record.

Evaluate published claims

The complete claims ledger is checked for developments that support, complicate, narrow, or place pressure on a published claim.

Promote one coherent release

The arc and claim files pass validation together. A manifest then publishes their exact locations, byte lengths, and SHA-256 hashes.

Selection and evaluation

What qualifies for the tracker

An arc entry records a meaningful development inside the arc's published scope. A new paper, announcement, or article qualifies when its substance advances the tracked story. Repeated coverage can enter when it adds a material fact, threshold, reversal, deployment, policy action, or change in direction.

Claim evidence is written relative to a specific published claim:

Supporting evidence: A development that increases confidence in the claim's direction, mechanism, or stated conditions.
Complicating evidence: A counterexample, delay, constraint, alternative pathway, or boundary condition that changes how the claim should be understood.
Potential falsifier: A stated observation or condition that would place direct pressure on the claim or show that it has failed.
Editorial status: A separate judgment that considers relevance, evidentiary strength, claim type, time horizon, assumptions, and potential falsifiers.

Counts describe placements in the record.

An event may advance several arcs or bear on several claims. Evidence totals provide context for review. Their meaning depends on relevance, quality, independence, timing, and relationship to the claim.

Collaboration and accountability

AI assistance and human editorial judgment

AI partners contribute to source triage, synthesis, drafting, pattern mapping, claim evaluation, metadata, and technical checks. This collaboration expands the attention available to a daily publication and makes consistent longitudinal review possible.

AI output can introduce errors, missing context, flawed links, and false confidence. Validation checks reduce those risks. Ben Linford makes the final editorial decisions about selection, framing, interpretation, claim status, publication, and corrections.

The broader sourcing, uncertainty, correction, and disclosure standards appear in Editorial Standards.

Freshness without ambiguity

How to read the dates

Field	Meaning
`published_at`	The UTC instant when the verified file pair was promoted.
`promoted_at`	An optional UTC instant added when an earlier verified release is restored as current. The original `published_at` remains in place.
`edition_date`	The newest edition completed across the claim evaluation. It matches `evaluated_through`.
`evaluated_through`	The newest published edition evaluated across the complete claims ledger, including an edition that yields no qualifying evidence.
`claims.last_updated`	The latest date when public claim or evidence content changed. A no-change evaluation leaves this date in place.
`arcs.last_updated`	The release-coherence date for the arc file. The publication gate aligns it with the completed claim-evaluation horizon.
`taxonomy_updated`	The latest date when arc identity, scope, or lifecycle metadata changed.
Row `date`	The date of the Century Report edition carrying that tracker entry. Event and external-source publication dates can differ.
`last_covered`	The newest development date inside one arc.

A staged edition leaves all public freshness signals on the preceding validated release. An edition published later in the day produces a tracker update later in the day.

Plain-language schema guide

Data dictionary

current.json - release entry point

This small mutable file identifies the current verified release. Deliberate machine clients should begin here and follow the immutable URLs it supplies.

schema: Manifest format version.
release_id: Edition date plus a 12-character content-derived identifier.
edition_date: Completed claim-evaluation horizon for the release.
published_at: UTC promotion timestamp.
promoted_at: Optional UTC restoration timestamp for a previously published release.
data: Summary of arc, claim, and evaluation freshness.
files: Immutable file URLs, byte lengths, and SHA-256 hashes.

arcs.json - story arcs and developments

The top level records its schema, release-coherence date, taxonomy date, counts, active arcs, and archived arcs.

name: Current public display title.
slug: Stable machine identity and public fragment key.
aliases: Earlier public names preserved for continuity.
status: Editorial lifecycle marker such as active, watching, dormant, or resolved.
description: Defined scope of the arc.
where_it_stands: Current synthesis of momentum, constraints, and open questions.
developments: Newest-first timeline entries containing date, legacy raw_date, and summary text.
development_count: Total placements in the arc.
recent_count_30d: Placements inside the release's inclusive 30-day window.

claims.json - claims and evidence

The top level records its schema, content-change date, completed evaluation horizon, and claims array.

id: Stable public claim identifier.
claim_text: The claim as tracked.
claim_type: Controlled category for structural theses and forecasts.
time_horizon: Human-readable time window.
sources: Shared Sapience article or articles where the claim originated.
assumptions: Technical, economic, political, social, or other stated dependencies.
mechanism: The proposed causal pathway.
potential_falsifiers: Conditions that would challenge the claim.
related_arc_slugs: Stable identities of connected story arcs.
evidence_supporting: Chronological supporting evidence rows.
evidence_complicating: Chronological complicating evidence rows.
revision_notes: Reserved field for documented changes in scope or interpretation.

Evidence row - claim-relative provenance

date: Canonical edition date in ISO format.
text: A summary written for its relationship to the claim.
tcr_url: Canonical link to the edition supplying context and its source trail.

Source trail and limits

What each link can establish

Claim evidence carries an explicit tcr_url. Arc developments carry an edition date, and the public renderers construct the canonical edition URL from that date. The linked edition supplies the human-readable context and the categorized external source list.

The tracker text is a Shared Sapience synthesis of the covered development. External reporting, research papers, filings, and organizational materials retain their own authorship and terms.

Arc counts are placements across defined threads. Cross-listed developments contribute to each relevant arc.
Evidence can apply to several claims. Each placement expresses a claim-specific relationship.
Some historical arc entries contain several related developments in one row.
The server-rendered tracker overview includes the five newest developments for each evidenced arc. The immutable JSON contains the complete arc record.
Evidence rows currently have no permanent row-level identifier. Cite the claim ID, polarity, edition date, row text, and release ID.

Substantive corrections follow the process in Editorial Standards. A corrected live record enters a new verified release with a new version identifier.

Reproducible retrieval

How to verify a release

1
Fetch current.json and record its release_id.
2
Follow the two immutable file URLs under files.
3
Confirm the downloaded byte length equals the manifest's bytes value.
4
Compute SHA-256 for each file and compare it with the manifest's sha256 value.
5
Use the release directory's release.json when preserving the immutable manifest alongside the files.

Completed release directories are retained as public citation targets. The mutable compatibility aliases arcs.json and claims.json always reflect the current release and are unsuitable for version-specific citation.

Citation guidance

Cite the layer you used

Complete dataset: Cite this page, Ben Linford, Shared Sapience, the release ID, publication date, and immutable release.json. Include an access date when your style guide expects one.
Story arc: Cite the arc name and stable slug, the release ID, and immutable arcs.json. Link the matching tracker fragment for a reader-facing view.
Published claim: Cite the claim ID and text, its stable tracker fragment, the release ID, and immutable claims.json. Cite the listed source essay for the claim's original publication.
Development or evidence row: Cite the linked Century Report edition for context and sources. Add the arc slug or claim ID, row text, polarity when relevant, and release ID when reproducing the ledger state.

Reuse terms

An open record with attribution

The Shared Sapience-authored tracker summaries, metadata, selection and arrangement, and applicable database rights are licensed under Creative Commons Attribution 4.0 International.

Reuse requires appropriate credit to Shared Sapience and Ben Linford, a link to the license, and an indication of changes. A preferred credit line is: Shared Sapience Progress & Claims Tracker, by Ben Linford.

This license applies only to material Shared Sapience controls. Linked articles, research, reporting, filings, images, source publications, names, logos, and trademarks retain their existing rights and terms.

How the Tracker Works

The living record, as published

Verified manifest

Story arcs

Claims and evidence