Public data API

The encyclopedia publishes a read-only static JSON API through GitHub Pages.

Base path:

https://conroy1988.github.io/Achievements/api/

Core discovery endpoints

Endpoint Purpose
index.json Core API version, endpoint discovery, and achievement slugs
achievements.json Complete nine-record achievement catalogue
achievements/{slug}.json One achievement record
schema.json JSON Schema draft 2020-12 achievement contract
status.json Generated repository health and workflow state

Evidence and research endpoints

Endpoint Purpose
evidence.json Privacy-safe evidence records and review state
timelines.json Verification timelines and page-level review dates
research-queue.json Bounded contributor research tasks
claims.json Atomic claims with evidence and task relationships
contradictions.json Competing interpretations and resolution criteria
coverage.json Claim and achievement coverage scores and ownership gaps
priorities.json Deterministically ranked research tasks with score components
change-impact.json Official-document changes mapped to claims, disputes, and tasks
public-observations.json Dated GitHub-owned profile, tier, and repository observations with explicit limitations
public-reconstructions.json Exact public event/profile pairs used to support broad trigger associations without overstating causality
official-achievement-fragments.json GitHub-owned live achievement criteria, linked history, fingerprints, and tier milestones

Evidence-operations endpoints

Endpoint Purpose
lab-protocols.json Ethical, privacy-safe reproduction protocols
auditor-rules.json Read-only public-signal rules and explicit limitations
submission-schema.json Structured general evidence-observation contract
mission-submission-schema.json Closed mission-packet contract with relationship, safeguard, and timing requirements
mission-review-queue.json Human-review queue and packet disposition state
mission-review-schema.json Closed review-record contract with conflict and promotion controls
promotion-plans.json Fail-closed canonical change plans generated from accepted promotion proposals
promotion-plan-schema.json Closed promotion-plan contract with impact, validation, approval, and rollback requirements
command-centre.json Static research metrics, targets, and public routes

Evidence-quality programme endpoints

Endpoint Purpose
event-linked-evidence.json Public GitHub events linked to claims, including negative and inconclusive observations
evidence-intelligence.json Deterministic per-achievement pressure scores and remaining release-gate gaps
acquisition-missions.json Ranked, ethical evidence missions with controls, stop conditions, and promotion targets
threshold-boundaries.json Proposed boundaries, current brackets, blockers, and required next evidence
adjudication.json Fail-closed promotion rules and current human-review decisions
contradiction-assessments.json One current resolution assessment for every open contradiction
release-readiness.json Immutable published v1.4.0 evidence and operational baseline
campaign-status.json Live v1.5.0 campaign lifecycle, task buckets, mission priority, gate distance, and archived release history

The discovery index now exposes 41 public JSON files: the aggregate catalogue, nine individual achievement records, schema, discovery, status, and twenty-five auxiliary endpoints.

Response obligations

Consumers must preserve uncertainty. Evidence level, reproduction state, reviewer decision, task state, dispute status, coverage score, observation scope, privacy status, and limitations are separate fields and must not be flattened into one confidence label.

Public observations establish only the platform state visible at the cited URL and date. They do not automatically prove causality, an exact threshold, a qualifying event, or an immutable historical count.

Event-linked records retain participant reports, negative results, processing-delay uncertainty, and public-event limitations. They do not modify canonical claim levels automatically.

Evidence-intelligence pressure scores prioritise unresolved work. They are not confidence scores and do not predict whether a community-reported claim is true.

Acquisition missions are bounded research instructions. They prohibit artificial activity, spam, false attribution, repository manipulation, and automatic claim promotion.

Mission intake packets must preserve the published mission, task, claim, contradiction, evidence-key, timing, safeguard, privacy, and human-review boundaries. Automated acceptance is not an evidence promotion.

Mission review records classify packets only. Promotion proposals require the mission’s published target, the applicable adjudication rule, two reviewers, one unconflicted reviewer, and a fully passing checklist. The queue always reports zero automatic canonical mutations.

Promotion plans are impact previews, not patches. They must preserve the source review, identify every affected source and generated file, require a separate maintainer-reviewed pull request, and report zero automatic applications.

The profile-auditor rules are expressly non-authoritative. They describe public signals, not badge detection.

Generation and drift control

python scripts/build_public_api.py
python scripts/build_evidence_register.py
python scripts/build_verification_timelines.py
python scripts/build_research_hub.py
python scripts/build_research_intelligence.py
python scripts/build_evidence_operations.py
python scripts/build_public_observations.py
python scripts/build_public_reconstructions.py
python scripts/build_official_achievement_fragments.py
python scripts/build_evidence_quality_programme.py
python scripts/build_research_campaign.py
python scripts/build_evidence_intelligence.py
python scripts/build_acquisition_missions.py
python scripts/build_mission_intake.py
python scripts/build_mission_review_queue.py
python scripts/build_promotion_plans.py

Generated endpoints must not be edited independently. Update the canonical source, run its builder, then commit the source and output together.

Versioning

Release baselines

The immutable v1.3.0 source baseline is commit 4869e71b392fc8a8f6d20835cdabe123c0c95e6f. The tag resolves exactly to that commit.

The immutable v1.4.0 source baseline is commit 98d478c7b73cff9c6e8fa5235640f12597544b67. The tag resolves exactly to that commit after release-readiness.json reported ready and merged-main operational health was verified at 100/100.