Praxis Form AI Rules Validation
This praxis-form-* skill family is the canonical Codex skill surface for @praxisui/dynamic-form and projects/praxis-dynamic-form; do not create parallel praxis-dynamic-form-* guidance unless this family cannot express a proven contract gap.
Use this skill for Dynamic Form AI authoring, rules, and validation. Form AI must operate through declared semantic contracts: component authoring manifest, component edit plans, rule authoring context, diagnostics, allowed targets/properties, context packs, and registry ingestion. It must not route primary intent through local keyword matching.
For shared AI runtime, manifest, registry, or semantic intent work, pair this skill with praxis-ai-assistant-runtime, praxis-ai-authoring-manifests, praxis-ai-registry-ingestion, or praxis-ai-semantic-intent.
When a form rule is authored or previewed through @praxisui/visual-builder, pair with
praxis-visual-builder-jsonlogic-roundtrip for JSON Logic support and with
praxis-visual-builder-schemas-templates for field schemas, target/property schemas, context
variables, and template-compatible rules. Use praxis-visual-builder-ai-validation when the same
rule path is exposed through visual-builder AI operations.
When a rule is authored inside @praxisui/manual-form, pair with
praxis-manual-form-rules-agentic. Manual-form persists authorable rules in formRules, treats
formRulesState as visual-editor round-trip state, and must hand off shared business decisions to
governed domain/shared rule authoring before local materialization.
Source Audit
First resolve the Angular workspace root. In the platform monorepo the files may live under
praxis-ui-angular/projects/...; in a standalone Angular checkout they may live directly under
projects/.... Audit the active praxis-ui-angular workspace, not stale issue worktrees such as
praxis-ui-angular-issue*, unless the user explicitly targets one of those worktrees.
Inspect the AI/rules surface:
projects/praxis-dynamic-form/AGENTS.md
projects/praxis-dynamic-form/src/lib/ai/praxis-dynamic-form-authoring-manifest.ts
projects/praxis-dynamic-form/src/lib/ai/form-ai.adapter.ts
projects/praxis-dynamic-form/src/lib/ai/dynamic-form-ai.adapter.ts
projects/praxis-dynamic-form/src/lib/ai/form-ai-catalog.ts
projects/praxis-dynamic-form/src/lib/ai/form-ai-capabilities.ts
projects/praxis-dynamic-form/src/lib/ai/form-component-ai-capabilities.ts
projects/praxis-dynamic-form/src/lib/ai/dynamic-form-rule-authoring-context.ts
projects/praxis-dynamic-form/src/lib/ai/dynamic-form-agentic-authoring-turn-flow.ts
projects/praxis-dynamic-form/src/lib/ai/dynamic-form-context-pack.ts
projects/praxis-dynamic-form/src/lib/ai/filter-form-context-pack.ts
projects/praxis-dynamic-form/src/lib/ai/dynamic-form-ai-recipes.spec.ts
projects/praxis-dynamic-form/src/lib/utils/rule-authoring-diagnostics.ts
projects/praxis-dynamic-form/src/lib/utils/rule-property.utils.ts
projects/praxis-dynamic-form/src/lib/utils/rule-converters.ts
projects/praxis-dynamic-form/src/lib/utils/form-rule.utils.ts
projects/praxis-dynamic-form/src/lib/config-editor/rule-properties-panel.component.ts
projects/praxis-dynamic-form/src/lib/rules-editor/rules-editor.component.ts
projects/praxis-dynamic-form/src/lib/actions-editor/actions-editor.component.ts
projects/praxis-dynamic-form/src/lib/action-authoring/global-action-authoring.util.ts
projects/praxis-dynamic-form/src/lib/services/form-rules.service.ts
projects/praxis-dynamic-form/src/lib/services/domain-rule-form-rules.service.ts
projects/praxis-dynamic-form/src/lib/model/form-rules.model.ts
projects/praxis-dynamic-form/docs/dynamic-form-llm-rule-authoring-guide.md
projects/praxis-dynamic-form/docs/dynamic-form-rules-authoring-plan.md
projects/praxis-dynamic-form/src/lib/praxis-dynamic-form.json-api.md
projects/praxis-dynamic-form/src/lib/config-editor/praxis-dynamic-form-config-editor.json-api.md
projects/praxis-dynamic-form/test-dev/e2e/form-ai-assistant-live.playwright.spec.ts
Inspect tools/ai-registry/AGENTS.md when registry ingestion or component authoring catalog output changes.
When the platform monorepo is available, also inspect the decision-authoring readiness docs before
changing manifest, adapter, recipe, registry, or public docs involving componentEditPlan,
formRulesState, visualBlockGuidance, or rule.visualBlockGuidance.add:
docs/2026-04-final-surface-scan-readiness.md
docs/2026-04-release-readiness-decision-authoring-surface-cleanup.md
docs/2026-04-form-rules-state-despromocao-backlog.md
docs/2026-04-form-rules-state-inventario-superficies.md
docs/2026-04-routing-canonico-intencao-backlog.md
AI Contract Rules
- Use component edit plans only for Dynamic Form component authoring.
- Route business-rule, policy, eligibility, validation, compliance, and shared decision authoring to governed domain/shared rule authoring before projecting local form config.
- Treat
componentEditPlan as valid only for component/page authoring. If the prompt asks for
business rules, policy, eligibility, validation, compliance, or shared decisions, the correct
response is a governed domain-rules / shared_rule_authoring handoff or materialization path,
not a local Dynamic Form edit plan.
- In agentic flows, a shared business-rule prompt must reach the backend semantic resolver with
governed context hints instead of being short-circuited by the Dynamic Form adapter. The local
adapter may compile a returned
componentEditPlan only after the resolver has selected a
component-authoring operation; it must not decide primary business intent from words in the form.
field.local.add is for local form-only fields. Do not create backend DTO fields for local/transient UI needs.
- Never write
formRulesState directly; write formRules and let internals derive builder state.
- Use Json Logic only; do not generate JavaScript handlers or arbitrary functions.
- Do not assume every visual-builder node or value type is form-rule-ready. Context-variable and
custom-function operands require a canonical JSON Logic shape before they can be projected into
dynamic-form rules.
- Use allowed targets from rule authoring context: fields, sections, rows, columns, actions, messages, visual blocks.
- Use
RULE_PROPERTY_SCHEMA/diagnostics as the allowed property source.
- Visual block guidance writes only visual rules or
columns[].items[]; it must not create FormControl, fieldMetadata, or submit payload.
rule.visualBlockGuidance.add and visualBlockGuidance may remain as optional visual
materialization/projection of an already governed decision or a local visual request. Do not
promote them as the recommended operation for primary business-rule authoring.
- Mark LLM-authored rules for human review when the workflow expects review.
formCommandRules is the command/side-effect channel. Keep it separate from property formRules, validate GlobalActionRef, preserve structured payload, and treat payloadExpr as an advanced JSON escape hatch.
- Author command-rule conditions as canonical JSON Logic evaluated over stabilized
formData after formRules computed values have settled. Do not evaluate command-rule AI previews, diagnostics, or payloadExpr examples against raw form snapshots, local/transient fields, or textual expressions.
- Keep side effects out of
formRules[].effect.properties; commands such as alerts, confirmations, navigation, dialogs, workflow actions, or service calls belong in formCommandRules[].effects[].globalAction with a catalog-backed GlobalActionRef.
- In visual/editor authoring, prefer structured
effects[0].globalAction.payload for the primary effect. Preserve payloadExpr and secondary effects from advanced JSON round-trip, but do not promote them as the normal AI-authored path for new command rules.
domainRules materializations are shared/governed rule projections. Do not collapse them into local formRules as if the form were the primary business-rule owner.
- When a governed decision materializes to
form_config, preserve DomainRuleMaterialization
provenance (ruleDefinitionId, materializationKey, sourceHash, status,
decisionDiagnostics, target layer/type/key/pointer) through DomainRuleFormRulesService.
Do not re-author the same rule locally just because the visual effect is representable as
FormLayoutRule.
- Treat
propertiesWhenFalse as the Dynamic Form false-branch projection for UI/form state, not as a canonical business denial. If a governed materialization is unsupported, incomplete, invalid, or missing provenance, suppress that projection or surface diagnostics; do not backfill a local formRules denial, infer backend_validation, or turn the false branch into the source of policy.
- Context packs are grounding artifacts. Keep dynamic-form and filter-form context packs aligned with allowed targets, diagnostics, existing rules, actions, fields, visual blocks, and runtime/read-only evidence.
- Computed field values must use the canonical closed envelope when authoring structured values: exactly
{ "expression": <JSON Logic> } or exactly { "literal": <value> }.
- The visual property panel is a guided projection of the JSON/rule contract. Unsupported or JSON-only rule capabilities must remain visible as advanced/diagnostic state rather than being silently dropped.
Editor validation and rule diagnostics must use the host-injected PraxisJsonLogicService and its operator registry, matching FormRulesService runtime evaluation. Pass that instance into diagnoseFormRules/diagnoseFormRule; a standalone default validator must not shadow host-registered operators in an editor. A registered runtime-valid operator may remain runtime-only when the visual builder cannot represent it; preserve its inline JSON Logic and allow save/reopen. Prove a host-registered operator is accepted while an unknown operator and invalid arity remain rejected, using config-editor/praxis-dynamic-form-config-editor.spec.ts and utils/rule-authoring-diagnostics.spec.ts.
Intent Guardrail
Do not add keyword, regex, alias, or fuzzy matching as the primary intent router. Text matching is allowed only after a canonical intent/operation scope exists, for ranking declared fields/actions/targets or asking clarification.
When a required operation is missing, model or extend the canonical AI/tool contract. Do not replace the missing operation with local prompt parsing inside the form component.
Before accepting a manifest/adapter/registry change, ask whether it reduces the chance that a
business-rule prompt falls back to componentEditPlan, formRulesState, or
rule.visualBlockGuidance.add. If it only creates another local component route for a shared
decision, it is probably the wrong platform cut.
For Ergon-style migrations, treat a request such as "make CPF required when regime is X",
"block payment when status is Y", "show LGPD guidance for sensitive fields", or "validate a legal
command before submit" as a classification problem first: component-only presentation may stay in
Dynamic Form, but reusable policy, legal command, eligibility, validation, or compliance belongs to
domain-rules and only then projects into form_config, backend validation, workflow/action, or
another target. Do not turn the first migrated screen into the canonical rule owner.
Inventory Before New Contract
ja-suportado-so-ux: the manifest/context/rule contract supports the operation, but assistant UI, diagnostics, property panel, or explanation is incomplete.
ja-suportado-mal-nomeado-ou-mal-materializado: the value exists in formRules, formCommandRules, domainRules, context pack, or JSON editor, but is surfaced through a local label, prompt-only wording, or visual-builder state.
suportado-parcialmente: one path works while another path, such as JSON editor, visual property panel, AI assistant, diagnostics, runtime application, command-rule preview, domain-rule materialization, or reopen, drifts.
lacuna-real-de-contrato: no manifest operation, component edit plan, context pack, rule schema, diagnostics path, runtime rule service, or registry ingestion surface can represent the authoring decision.
Only lacuna-real-de-contrato justifies new AI/rule contract work. Otherwise, repair the missing projection, diagnostic, context pack, editor bridge, or validation gate.
Validation
- Manifest/catalog/capabilities:
npx ng test praxis-dynamic-form --watch=false --progress=false --include=projects/praxis-dynamic-form/src/lib/ai/praxis-dynamic-form-authoring-manifest.spec.ts --include=projects/praxis-dynamic-form/src/lib/ai/form-ai-catalog.spec.ts --include=projects/praxis-dynamic-form/src/lib/ai/dynamic-form-ai-recipes.spec.ts
- Context packs and AI flow:
npx ng test praxis-dynamic-form --watch=false --progress=false --include=projects/praxis-dynamic-form/src/lib/ai/dynamic-form-context-pack.spec.ts --include=projects/praxis-dynamic-form/src/lib/ai/dynamic-form-rule-authoring-context.spec.ts --include=projects/praxis-dynamic-form/src/lib/ai/form-ai.adapter.spec.ts --include=projects/praxis-dynamic-form/src/lib/ai/dynamic-form-agentic-authoring-turn-flow.spec.ts
- Rule runtime/diagnostics:
npx ng test praxis-dynamic-form --watch=false --progress=false --include=projects/praxis-dynamic-form/src/lib/services/form-rules.service.spec.ts --include=projects/praxis-dynamic-form/src/lib/services/domain-rule-form-rules.service.spec.ts --include=projects/praxis-dynamic-form/src/lib/utils/rule-authoring-diagnostics.spec.ts --include=projects/praxis-dynamic-form/src/lib/utils/form-rule.utils.spec.ts
- Rule conversion/property authoring:
npx ng test praxis-dynamic-form --watch=false --progress=false --include=projects/praxis-dynamic-form/src/lib/utils/rule-converters.spec.ts --include=projects/praxis-dynamic-form/src/lib/utils/rule-property.utils.spec.ts --include=projects/praxis-dynamic-form/src/lib/config-editor/rule-properties-panel.component.spec.ts --include=projects/praxis-dynamic-form/src/lib/rules-editor/rules-editor.component.spec.ts
- Actions/command rules: add
action-authoring/global-action-authoring.util.spec.ts, actions-editor/actions-editor.component.spec.ts, components/praxis-form-actions/praxis-form-actions.component.spec.ts, and command-rule editor specs when global actions or command rules change.
- Visual block rules: add
visual-block-rule-content-overrides.util.spec.ts and layout visual-block specs when AI/rules affect targetType: "visualBlock" or columns[].items[].
- Registry:
npm run generate:registry:ingestion, npm run validate:catalog, and npm run validate:authoring-contracts when manifest/catalog/capability/context-pack surfaces change.
- Decision-authoring cleanup regression: run a focused textual scan for
formRulesState|componentEditPlan|recommendedOperation|rule\\.visualBlockGuidance\\.add|visualBlockGuidance
across Dynamic Form manifests/docs/recipes and generated registry surfaces when changing AI
authoring guidance. Classify each hit as component authoring, visual materialization, internal
runtime state, historical doc, or canonical drift.
- Browser AI/rules: focused Playwrights for
form-ai-assistant-live, form-config-editor-rules, form-config-editor-command-rules, business-rules-form-demo, funcionarios-form-demo-rules, and funcionarios-form-demo-domain-rules when visible AI/rule behavior changes.
npm run build:praxis-dynamic-form when public AI/rule exports, services, docs-facing contracts, or editor APIs change.
State whether live AI E2E was skipped. Do not use GitHub Actions as exploratory validation.
Companion Skills
- Use
praxis-form-runtime-submit for runtime state, submit payload, field metadata, local/transient fields, and schema contracts.
- Use
praxis-form-schema-runtime-modes for runtime inputs, schema/read/submit URL grounding, mode/presentation rules, and metadata reconciliation used by AI context.
- Use
praxis-form-submit-payload-pipeline when AI-authored local fields, submitPolicy, entity lookup payloads, or nested arrays affect submit semantics.
- Use
praxis-form-actions-hooks-runtime when AI edits form actions, hooks, global action refs, shortcuts, or surface open payloads.
- Use
praxis-form-editor-document-roundtrip when AI output must become a DynamicFormAuthoringDocument, apply plan, Settings Panel save, or registry-ingested editor document.
- Use
praxis-form-layout-canvas for layout, visual blocks, canvas, and schema-driven materialization.
- Use
praxis-form-authoring-settings for Settings Panel and editor round-trip.
- Use
praxis-core-runtime-contracts and praxis-core-resource-runtime for shared AI contracts, schema/resource grounding, option sources, and global actions.
- Use
praxis-authoring-editors for cross-component authoring/persistence patterns.
1---2name: praxis-form-ai-rules-validation3description: "Use when Codex must inspect, change, or validate @praxisui/dynamic-form or praxis-dynamic-form package AI authoring: authoring manifests, component edit plans, form AI catalogs, dynamic form rules, visual block guidance, Json Logic, diagnostics, rule authoring context, context packs, agentic turn flow, AI registry ingestion, or assistant Playwright flows."4metadata:5 source: https://skillmd.com/skills/codexrodrigues/praxis-form-ai-rules-validation6---78# Praxis Form AI Rules Validation910This `praxis-form-*` skill family is the canonical Codex skill surface for `@praxisui/dynamic-form` and `projects/praxis-dynamic-form`; do not create parallel `praxis-dynamic-form-*` guidance unless this family cannot express a proven contract gap.1112Use this skill for Dynamic Form AI authoring, rules, and validation. Form AI must operate through declared semantic contracts: component authoring manifest, component edit plans, rule authoring context, diagnostics, allowed targets/properties, context packs, and registry ingestion. It must not route primary intent through local keyword matching.1314For shared AI runtime, manifest, registry, or semantic intent work, pair this skill with `praxis-ai-assistant-runtime`, `praxis-ai-authoring-manifests`, `praxis-ai-registry-ingestion`, or `praxis-ai-semantic-intent`.1516When a form rule is authored or previewed through `@praxisui/visual-builder`, pair with17`praxis-visual-builder-jsonlogic-roundtrip` for JSON Logic support and with18`praxis-visual-builder-schemas-templates` for field schemas, target/property schemas, context19variables, and template-compatible rules. Use `praxis-visual-builder-ai-validation` when the same20rule path is exposed through visual-builder AI operations.2122When a rule is authored inside `@praxisui/manual-form`, pair with23`praxis-manual-form-rules-agentic`. Manual-form persists authorable rules in `formRules`, treats24`formRulesState` as visual-editor round-trip state, and must hand off shared business decisions to25governed domain/shared rule authoring before local materialization.2627## Source Audit2829First resolve the Angular workspace root. In the platform monorepo the files may live under30`praxis-ui-angular/projects/...`; in a standalone Angular checkout they may live directly under31`projects/...`. Audit the active `praxis-ui-angular` workspace, not stale issue worktrees such as32`praxis-ui-angular-issue*`, unless the user explicitly targets one of those worktrees.3334Inspect the AI/rules surface:3536- `projects/praxis-dynamic-form/AGENTS.md`37- `projects/praxis-dynamic-form/src/lib/ai/praxis-dynamic-form-authoring-manifest.ts`38- `projects/praxis-dynamic-form/src/lib/ai/form-ai.adapter.ts`39- `projects/praxis-dynamic-form/src/lib/ai/dynamic-form-ai.adapter.ts`40- `projects/praxis-dynamic-form/src/lib/ai/form-ai-catalog.ts`41- `projects/praxis-dynamic-form/src/lib/ai/form-ai-capabilities.ts`42- `projects/praxis-dynamic-form/src/lib/ai/form-component-ai-capabilities.ts`43- `projects/praxis-dynamic-form/src/lib/ai/dynamic-form-rule-authoring-context.ts`44- `projects/praxis-dynamic-form/src/lib/ai/dynamic-form-agentic-authoring-turn-flow.ts`45- `projects/praxis-dynamic-form/src/lib/ai/dynamic-form-context-pack.ts`46- `projects/praxis-dynamic-form/src/lib/ai/filter-form-context-pack.ts`47- `projects/praxis-dynamic-form/src/lib/ai/dynamic-form-ai-recipes.spec.ts`48- `projects/praxis-dynamic-form/src/lib/utils/rule-authoring-diagnostics.ts`49- `projects/praxis-dynamic-form/src/lib/utils/rule-property.utils.ts`50- `projects/praxis-dynamic-form/src/lib/utils/rule-converters.ts`51- `projects/praxis-dynamic-form/src/lib/utils/form-rule.utils.ts`52- `projects/praxis-dynamic-form/src/lib/config-editor/rule-properties-panel.component.ts`53- `projects/praxis-dynamic-form/src/lib/rules-editor/rules-editor.component.ts`54- `projects/praxis-dynamic-form/src/lib/actions-editor/actions-editor.component.ts`55- `projects/praxis-dynamic-form/src/lib/action-authoring/global-action-authoring.util.ts`56- `projects/praxis-dynamic-form/src/lib/services/form-rules.service.ts`57- `projects/praxis-dynamic-form/src/lib/services/domain-rule-form-rules.service.ts`58- `projects/praxis-dynamic-form/src/lib/model/form-rules.model.ts`59- `projects/praxis-dynamic-form/docs/dynamic-form-llm-rule-authoring-guide.md`60- `projects/praxis-dynamic-form/docs/dynamic-form-rules-authoring-plan.md`61- `projects/praxis-dynamic-form/src/lib/praxis-dynamic-form.json-api.md`62- `projects/praxis-dynamic-form/src/lib/config-editor/praxis-dynamic-form-config-editor.json-api.md`63- `projects/praxis-dynamic-form/test-dev/e2e/form-ai-assistant-live.playwright.spec.ts`6465Inspect `tools/ai-registry/AGENTS.md` when registry ingestion or component authoring catalog output changes.6667When the platform monorepo is available, also inspect the decision-authoring readiness docs before68changing manifest, adapter, recipe, registry, or public docs involving `componentEditPlan`,69`formRulesState`, `visualBlockGuidance`, or `rule.visualBlockGuidance.add`:7071- `docs/2026-04-final-surface-scan-readiness.md`72- `docs/2026-04-release-readiness-decision-authoring-surface-cleanup.md`73- `docs/2026-04-form-rules-state-despromocao-backlog.md`74- `docs/2026-04-form-rules-state-inventario-superficies.md`75- `docs/2026-04-routing-canonico-intencao-backlog.md`7677## AI Contract Rules7879- Use component edit plans only for Dynamic Form component authoring.80- Route business-rule, policy, eligibility, validation, compliance, and shared decision authoring to governed domain/shared rule authoring before projecting local form config.81- Treat `componentEditPlan` as valid only for component/page authoring. If the prompt asks for82 business rules, policy, eligibility, validation, compliance, or shared decisions, the correct83 response is a governed `domain-rules` / `shared_rule_authoring` handoff or materialization path,84 not a local Dynamic Form edit plan.85- In agentic flows, a shared business-rule prompt must reach the backend semantic resolver with86 governed context hints instead of being short-circuited by the Dynamic Form adapter. The local87 adapter may compile a returned `componentEditPlan` only after the resolver has selected a88 component-authoring operation; it must not decide primary business intent from words in the form.89- `field.local.add` is for local form-only fields. Do not create backend DTO fields for local/transient UI needs.90- Never write `formRulesState` directly; write `formRules` and let internals derive builder state.91- Use Json Logic only; do not generate JavaScript handlers or arbitrary functions.92- Do not assume every visual-builder node or value type is form-rule-ready. Context-variable and93 custom-function operands require a canonical JSON Logic shape before they can be projected into94 dynamic-form rules.95- Use allowed targets from rule authoring context: fields, sections, rows, columns, actions, messages, visual blocks.96- Use `RULE_PROPERTY_SCHEMA`/diagnostics as the allowed property source.97- Visual block guidance writes only visual rules or `columns[].items[]`; it must not create `FormControl`, `fieldMetadata`, or submit payload.98- `rule.visualBlockGuidance.add` and `visualBlockGuidance` may remain as optional visual99 materialization/projection of an already governed decision or a local visual request. Do not100 promote them as the recommended operation for primary business-rule authoring.101- Mark LLM-authored rules for human review when the workflow expects review.102- `formCommandRules` is the command/side-effect channel. Keep it separate from property `formRules`, validate `GlobalActionRef`, preserve structured `payload`, and treat `payloadExpr` as an advanced JSON escape hatch.103- Author command-rule conditions as canonical JSON Logic evaluated over stabilized `formData` after `formRules` computed values have settled. Do not evaluate command-rule AI previews, diagnostics, or `payloadExpr` examples against raw form snapshots, local/transient fields, or textual expressions.104- Keep side effects out of `formRules[].effect.properties`; commands such as alerts, confirmations, navigation, dialogs, workflow actions, or service calls belong in `formCommandRules[].effects[].globalAction` with a catalog-backed `GlobalActionRef`.105- In visual/editor authoring, prefer structured `effects[0].globalAction.payload` for the primary effect. Preserve `payloadExpr` and secondary effects from advanced JSON round-trip, but do not promote them as the normal AI-authored path for new command rules.106- `domainRules` materializations are shared/governed rule projections. Do not collapse them into local `formRules` as if the form were the primary business-rule owner.107- When a governed decision materializes to `form_config`, preserve `DomainRuleMaterialization`108 provenance (`ruleDefinitionId`, `materializationKey`, `sourceHash`, `status`,109 `decisionDiagnostics`, target layer/type/key/pointer) through `DomainRuleFormRulesService`.110 Do not re-author the same rule locally just because the visual effect is representable as111 `FormLayoutRule`.112- Treat `propertiesWhenFalse` as the Dynamic Form false-branch projection for UI/form state, not as a canonical business denial. If a governed materialization is unsupported, incomplete, invalid, or missing provenance, suppress that projection or surface diagnostics; do not backfill a local `formRules` denial, infer `backend_validation`, or turn the false branch into the source of policy.113- Context packs are grounding artifacts. Keep dynamic-form and filter-form context packs aligned with allowed targets, diagnostics, existing rules, actions, fields, visual blocks, and runtime/read-only evidence.114- Computed field values must use the canonical closed envelope when authoring structured values: exactly `{ "expression": <JSON Logic> }` or exactly `{ "literal": <value> }`.115- The visual property panel is a guided projection of the JSON/rule contract. Unsupported or JSON-only rule capabilities must remain visible as advanced/diagnostic state rather than being silently dropped.116117Editor validation and rule diagnostics must use the host-injected `PraxisJsonLogicService` and its operator registry, matching `FormRulesService` runtime evaluation. Pass that instance into `diagnoseFormRules`/`diagnoseFormRule`; a standalone default validator must not shadow host-registered operators in an editor. A registered runtime-valid operator may remain `runtime-only` when the visual builder cannot represent it; preserve its inline JSON Logic and allow save/reopen. Prove a host-registered operator is accepted while an unknown operator and invalid arity remain rejected, using `config-editor/praxis-dynamic-form-config-editor.spec.ts` and `utils/rule-authoring-diagnostics.spec.ts`.118119## Intent Guardrail120121Do not add keyword, regex, alias, or fuzzy matching as the primary intent router. Text matching is allowed only after a canonical intent/operation scope exists, for ranking declared fields/actions/targets or asking clarification.122123When a required operation is missing, model or extend the canonical AI/tool contract. Do not replace the missing operation with local prompt parsing inside the form component.124125Before accepting a manifest/adapter/registry change, ask whether it reduces the chance that a126business-rule prompt falls back to `componentEditPlan`, `formRulesState`, or127`rule.visualBlockGuidance.add`. If it only creates another local component route for a shared128decision, it is probably the wrong platform cut.129130For Ergon-style migrations, treat a request such as "make CPF required when regime is X",131"block payment when status is Y", "show LGPD guidance for sensitive fields", or "validate a legal132command before submit" as a classification problem first: component-only presentation may stay in133Dynamic Form, but reusable policy, legal command, eligibility, validation, or compliance belongs to134`domain-rules` and only then projects into `form_config`, backend validation, workflow/action, or135another target. Do not turn the first migrated screen into the canonical rule owner.136137## Inventory Before New Contract138139- `ja-suportado-so-ux`: the manifest/context/rule contract supports the operation, but assistant UI, diagnostics, property panel, or explanation is incomplete.140- `ja-suportado-mal-nomeado-ou-mal-materializado`: the value exists in `formRules`, `formCommandRules`, `domainRules`, context pack, or JSON editor, but is surfaced through a local label, prompt-only wording, or visual-builder state.141- `suportado-parcialmente`: one path works while another path, such as JSON editor, visual property panel, AI assistant, diagnostics, runtime application, command-rule preview, domain-rule materialization, or reopen, drifts.142- `lacuna-real-de-contrato`: no manifest operation, component edit plan, context pack, rule schema, diagnostics path, runtime rule service, or registry ingestion surface can represent the authoring decision.143144Only `lacuna-real-de-contrato` justifies new AI/rule contract work. Otherwise, repair the missing projection, diagnostic, context pack, editor bridge, or validation gate.145146## Validation147148- Manifest/catalog/capabilities: `npx ng test praxis-dynamic-form --watch=false --progress=false --include=projects/praxis-dynamic-form/src/lib/ai/praxis-dynamic-form-authoring-manifest.spec.ts --include=projects/praxis-dynamic-form/src/lib/ai/form-ai-catalog.spec.ts --include=projects/praxis-dynamic-form/src/lib/ai/dynamic-form-ai-recipes.spec.ts`149- Context packs and AI flow: `npx ng test praxis-dynamic-form --watch=false --progress=false --include=projects/praxis-dynamic-form/src/lib/ai/dynamic-form-context-pack.spec.ts --include=projects/praxis-dynamic-form/src/lib/ai/dynamic-form-rule-authoring-context.spec.ts --include=projects/praxis-dynamic-form/src/lib/ai/form-ai.adapter.spec.ts --include=projects/praxis-dynamic-form/src/lib/ai/dynamic-form-agentic-authoring-turn-flow.spec.ts`150- Rule runtime/diagnostics: `npx ng test praxis-dynamic-form --watch=false --progress=false --include=projects/praxis-dynamic-form/src/lib/services/form-rules.service.spec.ts --include=projects/praxis-dynamic-form/src/lib/services/domain-rule-form-rules.service.spec.ts --include=projects/praxis-dynamic-form/src/lib/utils/rule-authoring-diagnostics.spec.ts --include=projects/praxis-dynamic-form/src/lib/utils/form-rule.utils.spec.ts`151- Rule conversion/property authoring: `npx ng test praxis-dynamic-form --watch=false --progress=false --include=projects/praxis-dynamic-form/src/lib/utils/rule-converters.spec.ts --include=projects/praxis-dynamic-form/src/lib/utils/rule-property.utils.spec.ts --include=projects/praxis-dynamic-form/src/lib/config-editor/rule-properties-panel.component.spec.ts --include=projects/praxis-dynamic-form/src/lib/rules-editor/rules-editor.component.spec.ts`152- Actions/command rules: add `action-authoring/global-action-authoring.util.spec.ts`, `actions-editor/actions-editor.component.spec.ts`, `components/praxis-form-actions/praxis-form-actions.component.spec.ts`, and command-rule editor specs when global actions or command rules change.153- Visual block rules: add `visual-block-rule-content-overrides.util.spec.ts` and layout visual-block specs when AI/rules affect `targetType: "visualBlock"` or `columns[].items[]`.154- Registry: `npm run generate:registry:ingestion`, `npm run validate:catalog`, and `npm run validate:authoring-contracts` when manifest/catalog/capability/context-pack surfaces change.155- Decision-authoring cleanup regression: run a focused textual scan for156 `formRulesState|componentEditPlan|recommendedOperation|rule\\.visualBlockGuidance\\.add|visualBlockGuidance`157 across Dynamic Form manifests/docs/recipes and generated registry surfaces when changing AI158 authoring guidance. Classify each hit as component authoring, visual materialization, internal159 runtime state, historical doc, or canonical drift.160- Browser AI/rules: focused Playwrights for `form-ai-assistant-live`, `form-config-editor-rules`, `form-config-editor-command-rules`, `business-rules-form-demo`, `funcionarios-form-demo-rules`, and `funcionarios-form-demo-domain-rules` when visible AI/rule behavior changes.161- `npm run build:praxis-dynamic-form` when public AI/rule exports, services, docs-facing contracts, or editor APIs change.162163State whether live AI E2E was skipped. Do not use GitHub Actions as exploratory validation.164165## Companion Skills166167- Use `praxis-form-runtime-submit` for runtime state, submit payload, field metadata, local/transient fields, and schema contracts.168- Use `praxis-form-schema-runtime-modes` for runtime inputs, schema/read/submit URL grounding, mode/presentation rules, and metadata reconciliation used by AI context.169- Use `praxis-form-submit-payload-pipeline` when AI-authored local fields, `submitPolicy`, entity lookup payloads, or nested arrays affect submit semantics.170- Use `praxis-form-actions-hooks-runtime` when AI edits form actions, hooks, global action refs, shortcuts, or surface open payloads.171- Use `praxis-form-editor-document-roundtrip` when AI output must become a `DynamicFormAuthoringDocument`, apply plan, Settings Panel save, or registry-ingested editor document.172- Use `praxis-form-layout-canvas` for layout, visual blocks, canvas, and schema-driven materialization.173- Use `praxis-form-authoring-settings` for Settings Panel and editor round-trip.174- Use `praxis-core-runtime-contracts` and `praxis-core-resource-runtime` for shared AI contracts, schema/resource grounding, option sources, and global actions.175- Use `praxis-authoring-editors` for cross-component authoring/persistence patterns.