Flatfile Agential Resource System Context Entry
What it is
A FlatfileAgentialResourceSystemContextEntry is the smallest indivisible entry in a locale context file. Each context file holds entries of one concrete form:
| File | Concrete form | Spec |
|---|---|---|
SOUL.md |
Principle | principle |
MEMORY.md |
MemoryEntry | flatfile-agential-resource-system-memory-entry |
INBOX.md |
Message | flatfile-agential-resource-system-message |
PLANS.md |
OperationItem | operation-item |
IDEAS.md |
Idea | flatfile-agential-resource-system-idea |
A FlatfileAgentialResourceSystemContextEntry is identified by its heading within its file.
OperationItems and Ideas use numeric identifiers (for example, ### WI-3:); Principles and MemoryEntries are identified by their heading text.
What every FlatfileAgentialResourceSystemContextEntry has
Every FlatfileAgentialResourceSystemContextEntry MUST have:
- A heading that identifies it uniquely within its file
- A body containing at least the required fields for its concrete form
Every FlatfileAgentialResourceSystemContextEntry MAY have:
- A status field — required for OperationItem and Idea; absent for Principle and MemoryEntry
- A why field — provenance or motivation
A FlatfileAgentialResourceSystemContextEntry CANNOT encode information derivable from its position or file: the locale it belongs to, its concrete form, or its numeric sequence position. Redundant encoding creates two sources of truth that can diverge.
Concrete forms
See the individual specs for required fields and canonical format:
- principle — a stable constraint on locale behavior
- flatfile-agential-resource-system-memory-entry — a dated learned fact; append-only
- flatfile-agential-resource-system-message — an inter-locale communication; has lifecycle status
- operation-item — a committed actionable task; has lifecycle status
- flatfile-agential-resource-system-idea — an uncommitted potential work item; has lifecycle status