decapod 0.47.17

Decapod is the daemonless, local-first control plane that agents call on demand to align intent, enforce boundaries, and produce proof-backed completion across concurrent multi-agent work. 🦀
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75

# GLOSSARY.md - Loaded Terms (Normative)

**Authority:** interface (normative term definitions)
**Layer:** Interfaces
**Binding:** Yes
**Scope:** defines loaded terms used across the doc stack to prevent semantic drift
**Non-goals:** tutorials; this is a reference

This glossary is binding: if a term is defined here, other canonical docs MUST use it consistently.

---

## 1. Terms

- Canonical:
  - The repo-relative path in `**Canonical:** ...` identifies the authoritative location of a document.
  - Canonical does not imply binding; it implies "this path is the source-of-truth for the text."
- Binding:
  - `**Binding:** Yes` means the document defines requirements, invariants, or interfaces.
  - `**Binding:** No` means guidance only; if it conflicts with binding docs, it is wrong.
- Layer:
  - Constitution: authority and behavioral doctrine.
  - Interfaces: machine surfaces, schemas, invariants, safety gates.
  - Guides: operational advice; non-binding.
- Authority (header field):
  - A short statement describing what the document is allowed to define (e.g. routing vs interface vs constitution).
- Router (routing authority):
  - A document that routes readers to canonical sources.
  - A router does not create new behavioral requirements (see Delegation Charter in `core/DECAPOD.md`).
- Proof surface:
  - A named, runnable mechanism that can detect drift or validate invariants (e.g. `decapod validate`, schema checks).
- Claim:
  - A registered promise/guarantee/invariant with a stable claim-id, tracked in `interfaces/CLAIMS.md`.
- Enforcement:
  - Whether a claim is checked by a proof surface (`enforced`), partly checked (`partially_enforced`), or only documented (`not_enforced`).
- Store:
  - A state root that scopes reads/writes (see `interfaces/STORE_MODEL.md`).
  - User store: `~/.decapod`
  - Repo store: `<repo>/.decapod/project`
- Subsystem:
  - A first-class Decapod surface with a CLI group and schema/proof hooks (see `core/PLUGINS.md`).
- Plugin-grade:
  - Meets the thin-waist requirements in `core/PLUGINS.md` (stable CLI group, schema/discovery, store-awareness, proof hooks).
- Derived (artifact/state):
  - Computed output that must not be treated as source-of-truth (see `plugins/MANIFEST.md`).
- Validate:
  - The primary proof surface (`decapod validate`) that checks documented invariants and drift gates.
- Amendment:
  - A binding meaning change governed by `specs/AMENDMENTS.md`.
- Deprecation:
  - A non-binding marker on old meaning governed by `core/DEPRECATION.md`, with replacement + sunset.

---

## Links

### Core Router
- `core/DECAPOD.md` - **Router and navigation charter (START HERE)**

### Authority (Constitution Layer)
- `specs/INTENT.md` - **Methodology contract (READ FIRST)**
- `specs/SYSTEM.md` - System definition and authority doctrine
- `specs/AMENDMENTS.md` - Change control

### Registry (Core Indices)
- `core/PLUGINS.md` - Subsystem registry
- `core/INTERFACES.md` - Interface contracts index
- `core/DEPRECATION.md` - Deprecation contract

### Contracts (Interfaces Layer - This Document)
- `interfaces/DOC_RULES.md` - Doc compilation rules
- `interfaces/CLAIMS.md` - Promises ledger
- `interfaces/STORE_MODEL.md` - Store semantics
- `interfaces/CONTROL_PLANE.md` - Sequencing patterns
- `interfaces/TESTING.md` - Testing contract