K01

Roles & guides

Four roles. One namespace.

Owner, contributor, reviewer, consumer — each with how it works and how to use it. A single person often holds several. Everything here runs today with the knowledge CLI, the MCP server and this explorer.

Namespace owner

Controls the name: policy, reviewers, what gets published, which children exist.

how it works · how to use
Contributor

Proposes knowledge with sources. Researcher, lab, agent, community member.

how it works · how to use
Reviewer / curator

Reads the diff and the automated findings, approves or rejects, lands the next version.

how it works · how to use
Consumer

Resolves the name and reads the current version — with provenance.

how it works · how to use

Before the roles: install

Node 22+. The CLI and the MCP server are on npm and keep local copies of namespaces in ~/.recall.

  1. 01

    The CLI

    For owners, contributors and reviewers.
    npm i -g @knowledge01/cli
knowledge --help
  2. 02

    The MCP server

    For agents. Reads go through a Pinata gateway.
    claude mcp add knowledge \
  -e PINATA_GATEWAY=<gateway>.mypinata.cloud \
  -- npx -y @knowledge01/mcp

What ENS enforces

The policy says who may do what; ENS makes the important parts true on chain.

Roles live in the policy, and on the resolver

Every repository acting on a namespace enforces its published policy: contributors cannot commit to main, only reviewers approve, only the owner changes the policy. On chain, each namespace’s own resolver enforces who can write: the owner publishes and grants; a reviewer holds the right to publish that name alone; a named contributor can write one key, knowledge.proposal.<name>, to point the owner at a proposal — and nothing else.

knowledge policy keeps the two in step, and knowledge roles reads them back from ENS; each namespace’s Info page shows the same. More on what is proven versus claimed in the FAQ.