Diagnostic / platform systems

Field Contract Preview

show exactly what a recipe will register, measure, write, and render before enabling it

Running the actual pattern live via applyPattern() — switch the substrate, stack overlays, watch the signals, or reverse the dynamics. Not a mock.

"Field Contract Preview" — show exactly what a recipe will register, measure, write, and render before enabling it. It has a attract layer (draw matter into a focus / well). The active render stack is particles, dots.

A platform diagnostic, not a force: it reads the registries and lintPlatform to make field behavior auditable before enabling, with one minimal sample body so the contract itself stays inspectable.

Runtime tokens: attract draw matter into a focus / well
Concepts: contract
Metrics: scope a semantic lane — drive it with data-field-<metric> (or a domain model); without that its --field-<metric> stays inertimpact a semantic lane — drive it with data-field-<metric> (or a domain model); without that its --field-<metric> stays inertrisk written only when the host supplies it — the engine never invents confidence/risk scope, impact are host-supplied lanes — drive them with data-field-<metric> (or a domain model); without that, their --field-* stays inert.
Diagnostics: inspector topology causality
Render: particles · dots
Reduced motion: a static contract table listing what the recipe registers, measures, writes, and renders
Without motion: the preview is a plain table of registrations, measurements, writes, and announcements with no motion at all

Copy this pattern

<field-root></field-root>
  <div data-body="attract" data-strength="0.6" data-range="280" data-feedback></div>

<script type="module">
  import '@fundamental-engine/elements';
</script>

<field-root></field-root>
  <div data-body="attract" data-strength="0.6" data-range="280" data-feedback></div>

import { FieldField } from '@fundamental-engine/react';

export default function FieldContractPreview() {
  return (
    <FieldField>
      <div data-body="attract" data-strength="0.6" data-range="280" data-feedback />
    </FieldField>
  );
}

{
  "id": "field-contract-preview",
  "name": "Field Contract Preview",
  "intent": "show exactly what a recipe will register, measure, write, and render before enabling it",
  "primitives": [
    "attract"
  ],
  "bodies": [
    {
      "body": "attract",
      "strength": 0.6,
      "range": 280,
      "feedback": true
    }
  ],
  "render": [
    "particles",
    "dots"
  ],
  "metrics": [
    "scope",
    "impact",
    "risk"
  ],
  "diagnostics": [
    "inspector",
    "topology",
    "causality"
  ],
  "accessibility": {
    "reducedMotion": "a static contract table listing what the recipe registers, measures, writes, and renders",
    "meaningWithoutMotion": "the preview is a plain table of registrations, measurements, writes, and announcements with no motion at all"
  },
  "notes": "A platform diagnostic, not a force: it reads the registries and lintPlatform to make field behavior auditable before enabling, with one minimal sample body so the contract itself stays inspectable.",
  "tier": "systems",
  "status": "shipped",
  "concepts": [
    "contract"
  ]
}

Copy this pattern

See also