Skip to content
MNSTRY.org
Menu Agent interface

Agent interface

A different surface for a different reader

The human site is organized for understanding. The agent interface is organized for deterministic discovery, retrieval, evidence, provenance, and explicit refusal. It does not scrape the human navigation and it does not treat public access as blanket authorization.

Article twins
124
Topic twins
22
Graph nodes
409
Training permission
Not granted

Discovery surfaces

Start from declared contracts

Each endpoint is static, versioned, and available without executing a browser application.

JSON or text

Publication discovery

Human routes, machine routes, editorial prominence, review maintenance, and every public resource.

Open endpoint

JSON or text

Capability manifest

What the agent surface exposes, what it refuses to infer, and which collaboration operations are unavailable.

Open endpoint

JSON or text

Editorial orientation

Curated entrypoint questions, durable synopses, categories, filters, and routes for retrieval and graph traversal.

Open endpoint

JSON or text

Knowledge graph

Semantic, navigation, and provenance nodes and edges in one fail-closed public graph.

Open endpoint

JSON or text

Search index

Normalized public records for local search and retrieval.

Open endpoint

JSON or text

llms.txt

A readable map of the public corpus and its structured twins.

Open endpoint

JSON or text

Contribution port

The authentication, moderation, and no-source-mutation boundary for collaboration.

Open endpoint

JSON or text

Contributor workspace

A source-free repository bundle with Codex, Claude Code, MCP, draft, and receipt configuration.

Open endpoint

JSON or text

Koiné integration

The pinned upstream package revision, Publication Profile, peer manifest, ownership boundary, and no-silent-loss receipt.

Open endpoint

Contribute from your harness

Bring a small repo of your own

This workspace contains your notes, drafts, and receipts. It contains none of MNSTRY's source repository. Open it in Codex or Claude Code and the Koiné contract tells the harness how to retrieve context, validate, submit, revise, and withdraw through MCP.

Prompt for Codex or Claude Code

Create an empty contributor repository from https://mnstry.org/agent/contributor-workspace.json. Materialize every path in the files object exactly, initialize git, read AGENTS.md and koine-peer.json, then connect to the declared MCP server. Do not request or clone the MNSTRY source repository. Retrieve contribution context before drafting and store every returned receipt.

Open workspace bundle Inspect the port

Operating boundary

Five rules travel with the interface

  1. 01Use the structured twinEvery article JSON contains the body, apparatus, evidence grades, concepts, versions, and release hash.
  2. 02Keep provenance attachedStable graph ids and release hashes identify the source and revision being used.
  3. 03Separate access from permissionHuman reading, retrieval, agent use, redistribution, and model training are independent decisions.
  4. 04Propose rather than mutateComments, corrections, and graph relationships enter governed branches. Publication and promotion remain steward acts.
  5. 05Fail closedIf a resource or permission is absent from the public projection, do not infer it from the human surface.