Epistemedia

Research Program

Falsifiable questions, benchmarks, experiments, and unresolved design tradeoffs for collective epistemic systems.

Lens: encyclopedia — A coherent general overview with explicit provenance and disagreement.

Included objects

Epistemedia Documentation

Agent Operations

This directory contains repeatable operating recipes. AGENTS.md remains the root authority contract.

Contributor Agent Recipe

1. Orient: make orient. 2. Select: python -m epistemedia repo next. 3. Read the root contract, selected task contract, execution plan, scoped authority, schemas, policies, and tests. 4. Claim through an append-only proposal. 5. Work in one bounded branch and preserve negative results. 6. Rebuild all derived surface

API, MCP, and CLI

All integrations read the same disclosure-safe public catalog. Preserve the returned catalog_id, frontier, commit, compiler, policy IDs, object IDs, and content digests when storing or citing results.

Public API and MCP deployment contract

The API and MCP gateway is a read-only projection service. It receives an accepted repository snapshot and exposes no GitHub, contribution, deployment, package-publishing, signing, or arbitrary network-fetch authority.

Epistemedia Architecture

Epistemedia is not an autonomous wiki whose canonical object is a page. Its canonical substrate is an append-only, provenance-preserving epistemic history. Pages and agent responses are reproducible projections over that history.

Brand Architecture

Knowledge that can show its work.

Validation workflow

Epistemedia's contribution CI is defined in .github/workflows/ci.yml and appears in GitHub Actions as Validate.

Autonomous Governance

Epistemedia governance controls procedure, authority, admission, resources, disclosure, and interoperability. It does not vote propositions into universal truth.

Human and Agent Interface Contract

Epistemedia does not maintain separate editorial truths for people, API clients, MCP agents, and local tools. Each interface adapts one disclosure-safe catalog and projection manifest.

Launching and Engaging with Epistemedia

Start at the human site and choose a topic. A topic page is a reproducible projection, not an anonymously edited canonical article. Inspect its lens, realm, frontier, policy, source objects, and manifest. Switch lenses to compare a coherent overview with evidence-first, skeptical, frontier, historical, pedagogical, or

Pre-public owner handoff

Archived bootstrap handoff. The repository-publication and protected-contribution steps below are complete. The default-hostname Pages bootstrap is also live. Use ops/activation/2026-08-22-pages-bootstrap.md for current evidence and remaining owner boundaries.

Epistemedia Roadmap

Compile the repository’s own architecture, governance, tasks, code, tests, and releases through the same public catalog used by every interface. Establish deterministic identity, disclosure safety, and agent-native operation.

Research Program

Epistemedia research is preregistered, event-sourced, reproducible, and explicit about dependence. Definitions, sourced upstream results, proofs, exact computations, observations, simulations, estimates, conjectures, hypotheses, negative results, and editorial synthesis must remain distinguishable.

Research Hypotheses

These are research claims to test, not accepted facts.

Epistemedia Tasks

tasks/contracts/ contains immutable accepted work contracts. A material change begins with a task contract or a narrowly authorized maintenance operation.

Em 0001

{ "$schema": "https://epistemedia.com/schemas/task-contract-v1.json", "id": "EM-0001", "title": "Bootstrap the Epistemedia public interface", "status": "completed", "change_class": "ordinary-implementation", "objective": "Expose one disclosure-safe public catalog through deterministic HTML, Markdown, llms.txt, API, MCP

Em 0002

{ "$schema": "https://epistemedia.com/schemas/task-contract-v1.json", "id": "EM-0002", "title": "Specify and implement the normative event envelope v0.1", "status": "ready", "change_class": "protocol-normative", "objective": "Turn the draft event envelope into a canonical, replay-tested protocol object covering identit

Em 0003

{ "$schema": "https://epistemedia.com/schemas/task-contract-v1.json", "id": "EM-0003", "title": "Activate production domains and public service deployment", "status": "ready", "change_class": "ordinary-implementation", "objective": "Connect epistemedia.com, api.epistemedia.com, and mcp.epistemedia.com to deployments bu

Em 0004

{ "$schema": "https://epistemedia.com/schemas/task-contract-v1.json", "id": "EM-0004", "title": "Correct the production domain and activate public services", "status": "ready", "change_class": "ordinary-implementation", "objective": "Replace the incorrect deployment target with epistimedia.com, api.epistimedia.com, and

Em 0005

{ "$schema": "https://epistemedia.com/schemas/task-contract-v1.json", "id": "EM-0005", "title": "Govern the canonical identifier namespace migration", "status": "ready", "change_class": "protocol-normative", "objective": "Migrate active canonical schema, policy, discovery, and record identifier namespaces from the unow

Em 0006

{ "$schema": "https://epistemedia.com/schemas/task-contract-v1.json", "id": "EM-0006", "title": "Activate the owned episte.media production domain", "status": "ready", "change_class": "ordinary-implementation", "objective": "Replace superseded deployment targets with episte.media, api.episte.media, and mcp.episte.media

Em 0007

{ "$schema": "https://epistemedia.com/schemas/task-contract-v1.json", "id": "EM-0007", "title": "Govern the episte.media canonical identifier namespace", "status": "ready", "change_class": "protocol-normative", "objective": "Migrate active canonical schema, policy, discovery, and record identifier namespaces from the u

Em 0008

{ "$schema": "https://epistemedia.com/schemas/task-contract-v1.json", "id": "EM-0008", "title": "Activate epistemedia.org with an episte.media sharing redirect", "status": "ready", "change_class": "ordinary-implementation", "objective": "Activate epistemedia.org, api.epistemedia.org, and mcp.epistemedia.org as the cano

Em 0009

{ "$schema": "https://epistemedia.com/schemas/task-contract-v1.json", "id": "EM-0009", "title": "Govern the epistemedia.org canonical identifier namespace", "status": "ready", "change_class": "protocol-normative", "objective": "Migrate active canonical schema, policy, discovery, and record identifier namespaces from th

Em 0010

{ "$schema": "https://epistemedia.com/schemas/task-contract-v1.json", "id": "EM-0010", "title": "Make generated public state reproducible locally and in CI", "status": "ready", "change_class": "ordinary-implementation", "objective": "Make local and CI validation independently prove that the disposable public projection

Em 0011

{ "$schema": "https://epistemedia.com/schemas/task-contract-v1.json", "id": "EM-0011", "title": "Restore canonical Apache-2.0 licensing", "status": "ready", "change_class": "maintenance", "objective": "Replace the abbreviated license notice with the complete canonical Apache License 2.0 text and verify that repository,

Em 0012

{ "$schema": "https://epistemedia.com/schemas/task-contract-v1.json", "id": "EM-0012", "title": "Remove the legacy repository clock injection hook", "status": "ready", "change_class": "maintenance", "objective": "Remove the root-level CI-only usercustomize hook after EM-0010 makes reproducible timestamp semantics expli

Em 0013

{ "$schema": "https://epistemedia.com/schemas/task-contract-v1.json", "id": "EM-0013", "title": "Harden the public API and modern MCP transport", "status": "ready", "change_class": "ordinary-implementation", "objective": "Bring the read-only public gateway into explicit MCP 2026-07-28 Streamable HTTP conformance, expos

Em 0014

{ "$schema": "https://epistemedia.com/schemas/task-contract-v1.json", "id": "EM-0014", "title": "Bound the container context and preserve accepted release identity", "status": "ready", "change_class": "ordinary-implementation", "objective": "Prevent local, secret, VCS, cache, and disposable state from entering the cont

Em 0015

{ "$schema": "https://epistemedia.com/schemas/task-contract-v1.json", "id": "EM-0015", "title": "Make the installed wheel CLI self-contained", "status": "ready", "change_class": "ordinary-implementation", "objective": "Make a clean wheel installation import and execute the Epistemedia CLI without relying on checkout-le

Projection manifest