Praxis Editorial Forms Runtime
Use this skill when a form experience is an editorial journey rather than a flat schema-driven form. @praxisui/editorial-forms is the canonical runtime for solution, journey, step, block, snapshot, fallback, presentation, and operational diagnostics.
For focused work, load the narrow companion first:
praxis-editorial-forms-journey-snapshot-runtime for EditorialRuntimeInput, solution/instance/context merge, journey and step resolution, presets, overrides, block provenance, and snapshotChange.
praxis-editorial-forms-presentation-diagnostics for fallback state, diagnostics, operational events, solution.presentation, theme tokens, stepper behavior, unsupported presentation keys, and i18n.
praxis-editorial-forms-data-collection-adapters for dataCollection readiness, adapter registry, dynamic-form adapter, config lookup, adapter events, and runtimeContext.formData.
praxis-editorial-forms-agentic-authoring for manifest-backed snapshot/fallback/presentation authoring, component metadata, registry, docs, and labs.
Canonical Boundary
@praxisui/editorial-forms owns:
EditorialFormRuntimeComponent
EditorialRuntimeInput
EditorialRuntimeHostConfig
EditorialRuntimeState
- resolved snapshots and provenance
- fallback derivation from diagnostics
- operational events
- presentation helpers and theme token mapping
- block renderers and stepper behavior
- package i18n provider/dictionaries
@praxisui/core owns shared editorial domain contracts such as EditorialSolutionDefinition and EditorialTemplateInstance. @praxisui/dynamic-form may render dataCollection blocks only through optional adapters; it must not become the primary language of the editorial runtime.
When editorial presentation or narrative blocks use RichContentDocument, pair with praxis-rich-content-runtime and praxis-rich-content-integration-adapters; do not invent an editorial-only rich content dialect.
Required Source Audit
Inspect:
projects/praxis-editorial-forms/AGENTS.md
README.md
docs/architecture.md
docs/editorial-authoring-playbook.md
docs/recovery-playbook.md
src/public-api.ts
src/lib/editorial-runtime.contract.ts
src/lib/editorial-form-runtime.component.ts
src/lib/runtime/editorial-runtime-state.ts
src/lib/runtime/editorial-preset-resolver.ts
src/lib/runtime/editorial-runtime-snapshot.model.ts
src/lib/runtime/editorial-runtime-fallback.ts
src/lib/runtime/editorial-runtime-diagnostics.model.ts
src/lib/runtime/editorial-runtime-events.model.ts
src/lib/runtime/editorial-runtime-presentation.helpers.ts
src/lib/runtime/editorial-runtime-theme.helpers.ts
- affected renderer specs and E2E labs when relevant
Runtime Rules
- Treat
solution, instance, and runtimeContext as inputs that resolve into EditorialRuntimeSnapshot.
- Keep
snapshotChange, fallbackChange, and operationalEvent stable host-facing outputs.
- Derive fallback from diagnostics with modes
normal, warning, degraded, and blocked; do not persist fallback as hidden domain truth.
- Unsupported
presentation keys must emit diagnostics instead of pretending visual support.
- Presentation changes belong under
solution.presentation and must not mutate journeys, blocks, FormConfig, FieldMetadata, or collected data.
- Preserve block provenance and deterministic override operations: append, insertBefore, insertAfter, replace, and remove.
- Keep
runtimeContext.formData as governed runtime state shared by selection blocks, data collection adapters, review sections, and snapshots.
- Use
PraxisI18nService and package dictionaries for internal runtime text.
Inventory Before New Contract
Before adding public fields, metadata ports, runtime types, diagnostics, or adapter contracts, classify the need:
ja-suportado-so-ux: snapshot, fallback, presentation, adapter, or event evidence exists but a host, lab, docs page, or renderer does not show it well.
ja-suportado-mal-nomeado-ou-mal-materializado: a consumer models editorial state as page-builder, dynamic-form, wizard, or host-local config while the editorial runtime already owns it.
suportado-parcialmente: the owner exists but snapshot merge, presentation coverage, adapter readiness, event forwarding, docs, or focused validation is incomplete.
lacuna-real-de-contrato: no existing solution/instance/context, snapshot, diagnostic, presentation key, adapter API, event payload, or component metadata port can express the requirement.
Only lacuna-real-de-contrato justifies a new public contract. Otherwise correct the editorial runtime owner or its projection.
When Not To Use Dynamic Form
Do not collapse editorial requirements into FormConfig.sections, rows, columns, or a generic technical form editor. If a requirement needs journey, narrative, compliance context, fallback, diagnostic provenance, or host operational events, evolve the editorial domain/runtime or adapter.
Validation
Minimum gates:
- compile:
npm run build:praxis-editorial-forms
- runtime component:
src/lib/editorial-form-runtime.component.spec.ts
- snapshot/presets:
src/lib/runtime/editorial-preset-resolver.spec.ts
- fallback:
src/lib/runtime/editorial-runtime-fallback.spec.ts
- presentation/theme:
src/lib/runtime/editorial-runtime-theme.helpers.spec.ts
- renderers: focused
src/lib/renderers/*.spec.ts
- host/lab proof:
test-dev/e2e/*.playwright.spec.ts when runtime experiments, labs, or host integration change
Review public API, README, docs manifest, architecture docs, and examples when host-facing runtime behavior changes.
1---2name: praxis-editorial-forms-runtime3description: Use when implementing or auditing `@praxisui/editorial-forms` runtime behavior, including `EditorialFormRuntimeComponent`, `EditorialRuntimeInput`, guided journeys, resolved snapshots, fallback state, operational diagnostics/events, presentation schema, theme tokens, stepper behavior, i18n, runtime context, experiments/labs, and the boundary between editorial domain and generic `FormConfig`.4metadata:5 source: https://skillmd.com/skills/codexrodrigues/praxis-editorial-forms-runtime6---78# Praxis Editorial Forms Runtime910Use this skill when a form experience is an editorial journey rather than a flat schema-driven form. `@praxisui/editorial-forms` is the canonical runtime for solution, journey, step, block, snapshot, fallback, presentation, and operational diagnostics.1112For focused work, load the narrow companion first:1314- `praxis-editorial-forms-journey-snapshot-runtime` for `EditorialRuntimeInput`, solution/instance/context merge, journey and step resolution, presets, overrides, block provenance, and `snapshotChange`.15- `praxis-editorial-forms-presentation-diagnostics` for fallback state, diagnostics, operational events, `solution.presentation`, theme tokens, stepper behavior, unsupported presentation keys, and i18n.16- `praxis-editorial-forms-data-collection-adapters` for `dataCollection` readiness, adapter registry, dynamic-form adapter, config lookup, adapter events, and `runtimeContext.formData`.17- `praxis-editorial-forms-agentic-authoring` for manifest-backed snapshot/fallback/presentation authoring, component metadata, registry, docs, and labs.1819## Canonical Boundary2021`@praxisui/editorial-forms` owns:2223- `EditorialFormRuntimeComponent`24- `EditorialRuntimeInput`25- `EditorialRuntimeHostConfig`26- `EditorialRuntimeState`27- resolved snapshots and provenance28- fallback derivation from diagnostics29- operational events30- presentation helpers and theme token mapping31- block renderers and stepper behavior32- package i18n provider/dictionaries3334`@praxisui/core` owns shared editorial domain contracts such as `EditorialSolutionDefinition` and `EditorialTemplateInstance`. `@praxisui/dynamic-form` may render `dataCollection` blocks only through optional adapters; it must not become the primary language of the editorial runtime.35When editorial presentation or narrative blocks use `RichContentDocument`, pair with `praxis-rich-content-runtime` and `praxis-rich-content-integration-adapters`; do not invent an editorial-only rich content dialect.3637## Required Source Audit3839Inspect:4041- `projects/praxis-editorial-forms/AGENTS.md`42- `README.md`43- `docs/architecture.md`44- `docs/editorial-authoring-playbook.md`45- `docs/recovery-playbook.md`46- `src/public-api.ts`47- `src/lib/editorial-runtime.contract.ts`48- `src/lib/editorial-form-runtime.component.ts`49- `src/lib/runtime/editorial-runtime-state.ts`50- `src/lib/runtime/editorial-preset-resolver.ts`51- `src/lib/runtime/editorial-runtime-snapshot.model.ts`52- `src/lib/runtime/editorial-runtime-fallback.ts`53- `src/lib/runtime/editorial-runtime-diagnostics.model.ts`54- `src/lib/runtime/editorial-runtime-events.model.ts`55- `src/lib/runtime/editorial-runtime-presentation.helpers.ts`56- `src/lib/runtime/editorial-runtime-theme.helpers.ts`57- affected renderer specs and E2E labs when relevant5859## Runtime Rules6061- Treat `solution`, `instance`, and `runtimeContext` as inputs that resolve into `EditorialRuntimeSnapshot`.62- Keep `snapshotChange`, `fallbackChange`, and `operationalEvent` stable host-facing outputs.63- Derive fallback from diagnostics with modes `normal`, `warning`, `degraded`, and `blocked`; do not persist fallback as hidden domain truth.64- Unsupported `presentation` keys must emit diagnostics instead of pretending visual support.65- Presentation changes belong under `solution.presentation` and must not mutate journeys, blocks, `FormConfig`, `FieldMetadata`, or collected data.66- Preserve block provenance and deterministic override operations: append, insertBefore, insertAfter, replace, and remove.67- Keep `runtimeContext.formData` as governed runtime state shared by selection blocks, data collection adapters, review sections, and snapshots.68- Use `PraxisI18nService` and package dictionaries for internal runtime text.6970## Inventory Before New Contract7172Before adding public fields, metadata ports, runtime types, diagnostics, or adapter contracts, classify the need:7374- `ja-suportado-so-ux`: snapshot, fallback, presentation, adapter, or event evidence exists but a host, lab, docs page, or renderer does not show it well.75- `ja-suportado-mal-nomeado-ou-mal-materializado`: a consumer models editorial state as page-builder, dynamic-form, wizard, or host-local config while the editorial runtime already owns it.76- `suportado-parcialmente`: the owner exists but snapshot merge, presentation coverage, adapter readiness, event forwarding, docs, or focused validation is incomplete.77- `lacuna-real-de-contrato`: no existing solution/instance/context, snapshot, diagnostic, presentation key, adapter API, event payload, or component metadata port can express the requirement.7879Only `lacuna-real-de-contrato` justifies a new public contract. Otherwise correct the editorial runtime owner or its projection.8081## When Not To Use Dynamic Form8283Do not collapse editorial requirements into `FormConfig.sections`, rows, columns, or a generic technical form editor. If a requirement needs journey, narrative, compliance context, fallback, diagnostic provenance, or host operational events, evolve the editorial domain/runtime or adapter.8485## Validation8687Minimum gates:8889- compile: `npm run build:praxis-editorial-forms`90- runtime component: `src/lib/editorial-form-runtime.component.spec.ts`91- snapshot/presets: `src/lib/runtime/editorial-preset-resolver.spec.ts`92- fallback: `src/lib/runtime/editorial-runtime-fallback.spec.ts`93- presentation/theme: `src/lib/runtime/editorial-runtime-theme.helpers.spec.ts`94- renderers: focused `src/lib/renderers/*.spec.ts`95- host/lab proof: `test-dev/e2e/*.playwright.spec.ts` when runtime experiments, labs, or host integration change9697Review public API, README, docs manifest, architecture docs, and examples when host-facing runtime behavior changes.