Figments & frontmatter
ConceptsA Figment is one saved note — plain markdown with a few labeled fields at the top, readable by you and your agent. Formally, it is a markdown note with Lyt's eight-field frontmatter contract: prose stays readable while metadata gives people and agents dependable structure.
A structured markdown note
Figments live in a vault as plain markdown. The body is yours to write and edit. The frontmatter is a small, predictable contract that supports local indexing, filtering, and agent-readable records without moving knowledge out of the file.
The eight required fields
title,created,modified, andtagsare maintained as structural metadata.purposeandtopicare author-supplied: why the Figment matters and what it concerns.mesh-visibilitydefaults tolocal;weightdefaults to3on a 1–5 scale.
An optional meta container can hold extra key-value data outside the eight-field contract.
Capture with the contract
Capture creates a Figment through the contract rather than a separate opaque store. Legacy markdown can be reconciled and indexed while the original prose remains the durable record.
lyt capture "A durable note" --purpose "why this is worth keeping" --topic insightpurpose and topic are the two fields nothing can infer for you, so capture asks for them when you run it interactively and refuses to guess when it cannot. Add --vault <name> once your pod holds more than one vault.
Metadata serves the file
Frontmatter helps search and indexing interpret a Figment, but it does not replace the markdown as source of truth. Rebuilding local indexes reads the files again.