SummaryThe Self-Audit Layer
Encode tracks the crystallization work itself. Every time oddkit_encode runs, it takes one or more DOLCHEO artifacts and structures them — producing a quality score, a persistence flag, and suggestions for improvement. Recording the Encode event as its own entry closes the loop between "discussed" and "captured." A ledger with five Decisions and zero Encodes says the decisions were mentioned but never formally processed. A ledger with Encodes but no corresponding saves says crystallization happened and the artifacts were lost in the response stream (see docs/oddkit/proactive/encode-does-not-persist.md). Both gaps are visible from the E entries alone.
Type Identity
| Field | Value |
|---|---|
| Letter | E |
| Name | Encode |
Field Schema
| Field | Recommended | Description |
|---|---|---|
| type | yes | Always E |
| title | yes | Short summary of what was crystallized |
| body | yes | What was encoded, the quality level returned, whether persistence was required, and what was done with the output |
Trigger Words (Fallback Classification)
encoded, crystallized, captured via encode, persisted, wrote to ledger, journaled, saved encode output, ran oddkit_encode