Launching and Engaging with Epistemedia

• Object ID: em:documentation:sha256:132c8bebe37109788249ab6278506f8ea9261ccd50946fc3405c9e62a947012f
• Kind: documentation
• Repository path: docs/launch.md
• Content digest: 68d97e21e55494fcb954bf02bc7cb81b68987a3cb60d6fb23deb59a71cf89c3a

Source content

Launching and Engaging with Epistemedia

For a reader

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 source-only views.

For an agent consuming knowledge

1. Retrieve /llms.txt or the nearest path-scoped llms.txt.

2. Select Markdown, JSON, API, MCP, CLI, or bundle access based on the task.

3. Preserve catalog, frontier, policy, compiler, object, and source identities.

4. Do not report a projection label as universal truth.

5. Inspect challenges, qualifications, dependence, and disclosure limitations before acting.

6. Cache immutable objects by digest; revalidate mutable aliases through status or release manifests.

For a person contributing through an agent

1. Point the agent to the repository or an open task URL.

2. Have it run make orient and python -m epistemedia repo next.

3. Select one bounded immutable task contract.

4. The agent creates a branch, implementation, tests, generated artifacts, and run receipt.

5. Untrusted CI validates without secrets.

6. An independently rooted trusted integrator applies accepted promotion predicates.

7. The accepted merge becomes a new repository and public-catalog frontier.

For a realm operator

A realm can remain private and local-first. It chooses its own constitution, ontologies, epistemic policies, disclosure, accepted imports, and exports. Sharing a bundle does not grant the receiver authority over its local state. Public Epistemedia is one realm and reference implementation, not the universal center of the network.

For an integration builder

Use OpenAPI for HTTP clients, MCP for agent clients, the CLI for local workflows, and downloadable release bundles for offline operation. Avoid scraping HTML when structured objects are available. Implement content-digest verification and surface manifest metadata to downstream users.

Current bootstrap corpus

Epistemedia initially dogfoods itself. The first public realm compiles the project’s constitution, architecture, policies, task contracts, implementation, tests, security model, governance, and release records. This keeps the launch useful and auditable before external knowledge realms are admitted.