Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions PRIMER.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,11 +48,17 @@ Four required files:

**`IDENTITY.md`** — the machine-readable identity record. Name, pronouns, creature type, Coven membership (if any), emoji. Minimal structured data that a validator can check.

<<<<<<< Updated upstream
**`MEMORY.md`** — the familiar's persistent memory surface. It is required for structural conformance and must also appear on the Ward's protected surface.

**`ward.toml`** — the governance document. Protected files, editable files, approval tiers. This is what tells the self-improvement loop what it cannot touch. See [`schemas/ward.schema.json`](schemas/ward.schema.json).

Start from [`examples/minimal/`](examples/minimal/) — that's the floor. [`examples/sage/`](examples/sage/) shows a richer structurally conformant familiar directory. Sage's runtime enforcement lives outside this repo fixture.
=======
**`ward.toml`** — the governance document. Protected files, editable files, approval tiers. This is what tells the self-improvement loop what it cannot touch. See [`schemas/ward.schema.json`](schemas/ward.schema.json).

Start from [`examples/minimal/`](examples/minimal/) — that's the floor. [`examples/sage/`](examples/sage/) shows a full compliant familiar (Sage is a real familiar running on OpenCoven's infrastructure).
>>>>>>> Stashed changes
Comment on lines +51 to +61

---

Expand Down Expand Up @@ -94,10 +100,18 @@ You do not need to use OpenCoven's infrastructure to implement familiar-contract

## Where to go next

<<<<<<< Updated upstream
- [`rfcs/RFC-0001-familiar-contract.md`](rfcs/RFC-0001-familiar-contract.md) — the normative specification (v0.7.0)
- [`examples/minimal/`](examples/minimal/) — the minimal structurally conformant familiar directory (Lumen)
- [`examples/sage/`](examples/sage/) — a richer structurally conformant familiar directory (Sage)
- `node validators/validate.js ./your-directory` — validate your claimant directory
- `bash tests/conformance/run-conformance.sh` — verify the bundled reference validator + fixtures for the same contract version
- [`docs/faq.md`](docs/faq.md) — common questions
=======
- [`SPEC.md`](SPEC.md) — the normative specification
- [`examples/minimal/`](examples/minimal/) — the minimal compliant familiar (Lumen)
- [`examples/sage/`](examples/sage/) — a full compliant familiar (Sage)
- `node validators/validate.js ./your-directory` — validate your familiar
- [`FAQ.md`](FAQ.md) — common questions
>>>>>>> Stashed changes
- [`docs/comparison.md`](docs/comparison.md) — how this relates to other approaches
8 changes: 1 addition & 7 deletions schemas/role.schema.json
Original file line number Diff line number Diff line change
Expand Up @@ -69,11 +69,5 @@
}
},
"additionalProperties": true,
"notes": [
"Roles are additive. A familiar with a role satisfies all five Familiar Contract properties as its baseline; the role adds narrowing constraints.",
"A role cannot override or weaken the familiar's core identity (SOUL.md, IDENTITY.md).",
"A role cannot expand authority — only restrict it.",
"Roles are scoped to a project or context. They are not permanent identity changes.",
"For the full Roles Architecture, see the OpenCoven roles specification."
]
"$comment": "Roles are additive. A familiar with a role satisfies all five Familiar Contract properties as its baseline; the role adds narrowing constraints. A role cannot override or weaken SOUL.md or IDENTITY.md, cannot expand authority, and is scoped to a project or context rather than a permanent identity change."
}