Intervene

W10 · 5 h

Entities, authority, and source ecosystems

Essential question

How does a fact become corroborated beyond one owned page?

What you should be able to do

  1. Resolve ambiguous entity records.
  2. Distinguish primary, owned, and independent sources.
  3. Design a correction and refresh path.
PrerequisitesW02 evidence ceilings.One two-source contradiction or the supplied case.
Builds on

W02 evidence ceilings. · One two-source contradiction or the supplied case.

Investigates

How does a fact become corroborated beyond one owned page?

Feeds

L05 controlled intervention II.

Arrive with a prepared artifact

Reading route
Core PAPER-14/PAPER-35; PAPER-01 is time-provenance audit only.
Viewing route
Open the complete text-first lecture packageFive-minute source-dependence and syndication example. The current equivalent is notes, slide script, worked case, and no-video transcript; no recording is claimed.
Readiness check
List one primary, one owned, and one independent source for a supplied claim.
Bring
Draft entity dossier and conflict note.

Concepts, assumptions, and boundary

Entity identity precedes authority

Names, products, organizations, people, and locations can be ambiguous or change over time. An entity dossier records stable identifiers, aliases, jurisdiction, official records, owned publications, independent sources, and conflicts. Authority is then evaluated per claim. An owned page may be the primary source for product specifications; an independent source may be needed for comparative or reputation claims. Repetition across low-independence sites is not the same as corroboration.

Source ecosystems need correction loops

Facts propagate through press releases, documentation, databases, reporting, aggregators, and downstream summaries. A robust architecture records provenance and provides a correction owner, update date, and conflict note. The intervention is not to manufacture mentions or seed identical claims across nominally independent sites. It is to make authorized, verifiable primary information available and to route genuine errors through legitimate publication and correction channels.

Inspect the mechanism or evidence structure

Conceptual graphEntity–claim–publisher ecosystem
Entity–claim–publisher ecosystemA provenance graph distinguishes first-party origin, independent verification, syndication, and correction. Duplicate/syndicated branches share a pattern so their apparent source count is not mistaken for independence.EntityPrimary recordOwned sourceIndependent sourceSyndicationCorrection
Figure design. Entity and claim nodes connect to primary records, owned publications, independent corroboration, aggregators, and correction paths; edge labels state provenance and independence. Repeated publication does not automatically add independence.
Long description

A provenance graph distinguishes first-party origin, independent verification, syndication, and correction. Duplicate/syndicated branches share a pattern so their apparent source count is not mistaken for independence.

One action, one feedback state

Action

Resolve ambiguous entity cards and explain which evidence changed the decision.

Feedback

The system surfaces alias conflicts, publication dependence, stale dates, and insufficient authority.

Accessible alternative

A deterministic entity-resolution table contains every candidate and rationale.

Open the intervention-diff explorer

Produce a reviewable intermediate file

Task
Build a source-ecosystem map and correction workflow for one entity.
Inputs
Entity schema, source cards, provenance-edge legend, correction template.
Timebox
70 minutes
Intermediate file
entity-dossier.json and source-ecosystem.svg
Stop condition
Do not recommend fabricated third-party publication, undisclosed sponsorship, or mass duplication.

Why each controlled source is here

Complete, retrieve, and revise

Checkpoint
L05 controlled intervention II.
Reflection
Explain why source count can overstate independence.
Revision
Add owner, reviewed date, update trigger, and unresolved conflicts.
Low-compute route
Use supplied entity records and source cards; no external crawling is required.

Five retrieval questions

01Why is an owned source not automatically weak?

It may be the authoritative primary record for first-party facts, while remaining insufficient for independent comparative or reputation claims.

02How can apparent corroboration be false?

Syndicated, copied, or mutually dependent sources may repeat one origin without independent verification.

03What belongs in a correction path?

The disputed claim, source provenance, responsible owner, legitimate correction channel, date, status, and downstream refresh trigger.

04What is the evidence boundary for W10?

PAPER-01 is used only to demonstrate time-provenance failure because reported collection dates postdate this course freeze.

05What must you submit or revise after this week?

L05 controlled intervention II. Add owner, reviewed date, update trigger, and unresolved conflicts.

Continue in the practice package