Data System Authority Rules

Overview

The wiki has two overlapping systems that store structured entity data:

1. KB YAML (packages/kb/data/things/*.yaml) — the knowledge base package, with rich typed facts, time series, and cross-entity references
2. Old YAML facts (data/facts/*.yaml) — the legacy facts system, powering the <F> inline component and <Calc> expressions

Nine entities currently have entries in both KB YAML and old YAML facts. Without a clear rule, editors may update one system while the other goes stale. This document defines the authority hierarchy.

Note: The Postgres statements system was retired in March 2026 (PR #1908). The DB tables have been archived with a _archived_ prefix. This document now covers only the two remaining data systems.

Authority Hierarchy

Rule 1: KB YAML is authoritative for entities it covers

For any entity that has a packages/kb/data/things/<slug>.yaml file, KB YAML is the single source of truth for structured properties (revenue, valuation, headcount, founding date, legal structure, etc.).

• Do not update data/facts/<slug>.yaml for entities with KB entries
• When a number changes (new funding round, updated headcount), edit the KB YAML file only
• The old facts file for that entity should be treated as deprecated (see migration path below)

Rule 2: Old YAML facts remain authoritative for non-KB entities

For entities not yet in KB, data/facts/<slug>.yaml remains the authoritative source for structured properties. These facts power <F> and <Calc> components on wiki pages and should continue to be updated normally.

Current non-KB entities with old facts files:

• anthropic-government-standoff.yaml — event file, not an entity; no KB equivalent planned
• center-for-ai-safety.yaml
• chan-zuckerberg-initiative.yaml
• coefficient-giving.yaml
• google-deepmind.yaml
• jaan-tallinn.yaml
• manifund.yaml
• survival-and-flourishing-fund.yaml

Rule 3: Citations system is separate from structured facts

The citations system (citation quotes, accuracy checks) operates independently. It tracks which sources are cited on wiki pages and verifies their accuracy, but it is not a source of structured property values.

The 9 Overlapping Entities

These entities have entries in both data/facts/ and packages/kb/data/things/. KB YAML is authoritative for all of them.

Migration Path

When adding a new entity to KB:

1. Create packages/kb/data/things/<slug>.yaml with the entity's structured data

2. Migrate any facts from data/facts/<slug>.yaml that are still current into KB format

3. Delete or mark deprecated the old facts file — add a comment at the top:

   # DEPRECATED: This entity is now in packages/kb/data/things/<slug>.yaml.
   # KB YAML is authoritative. This file is kept only for any remaining <F> tag references.
   

4. Search for <F e="<slug>" in MDX pages — these will continue to render from the old facts file until they are updated to use KB data components (<KBFactTable>, <KBEntitySidebar>, etc.)

5. File an issue to migrate any remaining <F> tag usage on pages for that entity

Do not delete old facts files outright if there are still active <F> tags referencing them — the <F> component reads from data/facts/, not from KB YAML.

System Comparison

KB Cross-Entity Comparisons

The KBCompareTable component renders a single property across multiple KB entities side-by-side. Time-series properties (revenue, valuation, headcount) produce a year-columnar table; point-in-time properties produce a simple latest-value table.

{/* Compare revenue across all orgs that have it */}
<KBCompareTable property="revenue" />

{/* Filter to specific entities */}
<KBCompareTable property="headcount" entities={["anthropic", "openai", "deepmind", "meta-ai", "xai"]} />

{/* Force latest-only mode */}
<KBCompareTable property="valuation" mode="latest" title="AI Lab Valuations" />

Example — revenue run-rate for frontier AI labs:

Example — latest valuation across labs with KB data:

Related Documents

• content/docs/internal/fact-system-strategy.mdx — Strategy and phase plan for old YAML facts
• content/docs/internal/structured-data-architecture.mdx — Migration path from facts to claims
• packages/kb/EXPERIMENTAL.md — KB package status and roadmap