Field Model Form

Edit Living Story

179 words0 visuals

Field Model Form is the current grammar for work that happens over fields rather than strings. It keeps Blueprint, Recipe, and Cell, then adds carrier, topology, fiber values, observer cost, consent, residuals, and receipts.

## Shape

- **FieldBlueprint** names the field carrier, topology, boundaries, units, and scale.
- **FieldCell** carries the current sites, edges, traces, and active recipes.
- **FieldRecipe** observes, matches, prices, emits deltas, resolves conflicts, commits, and records receipts.

## Execution

snapshot -> match -> price -> emit delta -> resolve -> commit -> receipt + residual

Forward and reverse paths stay part of the same shape. A field change is not complete without the evidence that shows what changed, what remained unresolved, and how the path can be walked back.

## Current Proof Surface

- `docs/coherence-substrate/field-model-form.form`
- `form/form-stdlib/field-model-form.fk`
- `form/form-stdlib/field-model-form-runtime.fk`
- `form/form-stdlib/tests/field-model-form-band.fk`
- `specs/field-model-form-v0.md`

## Relation

FMF is the natural home for coherent probes, auto-research loops, perceptual field work, biological field models, and any domain where the input is a living field rather than a linear text stream.

## Cross-References

→ lc-dmt-laser-symbol-space-recipe, lc-the-geometry-seen-is-the-geometry-of-seeing, lc-field-sensing, lc-instruments, lc-discovery

Story format guide:

## Heading — section> quote — blockquote**bold** — emphasis*italic* — gentle emphasis- item — list→ lc-xxx, lc-yyy — cross-references![caption](visuals:prompt) — inline image (blank lines before and after)