agent-wiki
Menu

Portable protocols for agent memory and coordination.

agent-wiki is an agent-first, machine-readable knowledge base for memory, workspace, skill lifecycle, deliberation, and coordination. Start with one problem and the smallest useful binding.

Read the manifest Choose a protocol

Smallest reliable reading path

01 · Route

protocols.yaml

02 · Bind

one minimum level

03 · Calibrate

one matching use case, when available

  • 7 protocols
  • 5 guides
  • 12 documented use cases
  • CC BY 4.0
01 · Route by problem

Start with the constraint you actually have.

The Adoption Guide is the source for this routing table. Selection does not authorize environment changes, and adding a protocol is unnecessary when a simpler action already solves the problem.

  1. Useful context must survive sessionsMemory · memory:L0
  2. A user wants a failed run or prior conclusion to stop influencing future workMemory · memory:L0
  3. A corpus needs weak lateral explorationAuto-Walk · auto-walk:L0
  4. Imported or relationship-formed procedures need governed adoption and evolutionSkill Lifecycle · skill:L0
  5. The wrong information is active during a taskActive Workspace · active-workspace:L0
  6. An Agent needs a short self-guidance cueInner Speech · inner-speech:L0
  7. A decision needs inspectable competing viewsCouncil · council:L0
  8. One human wants one interface over many executorsSteward · steward:S1
  9. Several chosen protocols must cooperateComposition guide · composition:C1
  10. Several participants need governed shared standing over existing artifactsGoverned Shared Memory profile · No level; design-only guide
  11. Governed artifacts or a binding must be backed up, restored, or movedGoverned Artifact Portability and Recovery guide · No level; design-only guide
  12. Governed artifacts must remain available across independently usable bindings while updates continueGoverned Artifact Replication and Exchange guide · No level; design-only guide
02 · Protocol registry

Choose the smallest sufficient binding.

Levels are cumulative within one protocol and are not comparable across protocols. Versions below 1.0.0 may change incompatibly.

ProtocolVersionMaturityMinimumUsecase conformance
Agent-first MemoryUseful context must survive sessions0.2.0practicedmemory:L0mapped 3
Agent-first Auto-WalkA corpus needs weak lateral exploration0.1.0practicedauto-walk:L0proposed 3 · partially-verified 1
Agent-first Skill LifecycleImported or relationship-formed procedures need governed adoption and evolution0.1.0practicedskill:L0mapped 1
Agent-first Active WorkspaceThe wrong information is active during a task0.2.0design-onlyactive-workspace:L00 documented
Agent-first Inner SpeechAn Agent needs a short self-guidance cue0.1.0design-onlyinner-speech:L00 documented
Agent-first CouncilA decision needs inspectable competing views0.1.0practicedcouncil:L0mapped 3
Agent-first StewardOne human wants one interface over many executors0.1.0practicedsteward:S1partially-verified 1
03 · Evidence discipline

Three axes. No borrowed certainty.

Maturity describes the protocol, evidence describes an observation boundary, and conformance describes checks against a named protocol version. One does not silently upgrade another.

Maturity

How far a protocol has moved from bounded design into repeated operational feedback.

design-only · practiced · field-tested

design-only 2 · practiced 5 · field-tested 0

Evidence

What kind of source inspection, run report, reproduction, or field operation supports a use case.

design-example · source-inspected · run-reported · reproduced · field-tested

design-example 3 · source-inspected 1 · run-reported 2 · reproduced 0 · field-tested 6

Conformance

How directly the named requirements were mapped, inspected, or executed, with declared gaps preserved.

proposed · mapped · partially-verified · verified

proposed 3 · mapped 7 · partially-verified 2 · verified 0

12 manifest-listed use cases · 0 verified conformance claims. Read each evidence scope before reusing a conclusion.

04 · Authority

The website never becomes a second specification.

  • protocols.yaml is canonical for routing, ids, versions, maturity labels, and shared vocabularies.
  • Protocol documents define their own semantics, invariants, schemas, and conformance rules.
  • Use cases provide evidence and binding guidance; they do not redefine a protocol.
  • A conflict between the manifest and a document is a repository defect—surface it instead of guessing.
Open machine-readable authority
05 · Adopt

One protocol. One bounded attempt.

Partial and negative results are useful. Record the route, runtime, observed result, remaining gaps, and friction without upgrading the claim.

Read the Adoption Guide Report an adoption experience

  1. Read the manifest

    Read protocols.yaml for protocol ids, versions, maturity, dependencies, artifacts, and usecase evidence.

  2. Select by problem

    Select one protocol from the problem table below.

  3. Read the complete contract

    Read that protocol's metadata, Purpose, Non-goals, core artifact/schema, minimum binding, implementation levels, validation checklist, and Final rule.

  4. Calibrate with one use case

    Read one matching use case, when one exists, and calibrate claims from its Evidence and Validation scope fields.

  5. Compose only when required

    Read Composable Agent Cognition Protocols only when two or more protocols must exchange artifacts.