Ergon Rule Target Planning
Materialize only the internal FND-12 technical plan. Let
$ergon-rule-migration-orchestration decide phase admission and use
$ergon-rule-executor-selection for the executor classification.
Step Zero: Readiness
Read docs/migracao/rule-migration/factory-contracts/part2-foundation-readiness-v2.json
before opening inputs. Resolve the active profile, environment, authority,
allowed stages/actions and blocking gaps. Continue only when the requested work
is admitted as MATERIALIZE_TECHNICAL_DRAFT; never translate corporate
NOT_READY into a global development block or reuse development admission in
another environment.
Required Inputs
- exact screen, operation, canonical decision identity and environment;
- RF-01 source manifest, RF-03 decision proposal, RF-04 materialized profile
and RF-05 semantic-gap report with verified lineage;
- reconciled Parte 1 evidence and explicit unresolved conflicts;
- an evidence-backed executor selection or explicit
UNKNOWN/review question;
- canonical FND-12 schemas, matrix, checker, materializer and toolchain from the
active migration repository.
Read references/contract-and-forward-tests.md before creating or reviewing a
plan.
Workflow
- Freeze evidence revisions, hashes and canonical decision identity.
- Confirm every requested target surface is admitted by the total surface
matrix; reject any unlisted combination.
- Copy only governed facts. Preserve order, dependencies, reason-code
semantics, cardinality, aggregation and executor details as explicit
unknown envelopes when evidence is insufficient.
- Produce exactly one
RULE_TARGET_BINDING_PLAN with
MATERIALIZED_UNCHECKED. Do not embed checker or admission results.
- Run the independent checker. Accept only a separate
TECHNICAL_PLAN_VERIFIED result bound to the exact plan digest.
- When local admission is requested, use the official admission command from
a clean revision and the fixed-local-disk store capability. Accept only a
separate
TECHNICAL_PLAN_ADMITTED receipt.
- Update traceability and stage blockers. Do not close a migration phase from
FND-12 status alone.
Hard Boundary
Never create JSON Logic expressions, Java classes, RuleSetDefinition, Config
materialization, executable snapshots, runtime bindings, publication,
activation, shadow authorization or legacy containment. KEEP_DB_BACKED is an
authority hold, not an engine executor. Technical admission is not business
homologation.
Fail closed on evidence drift, unknown target surface, ungoverned default,
secret/source/SQL leakage, dirty producer revision, checker mismatch, remote
store, forged capability or partial batch.
1---2name: ergon-rule-target-planning3description: Build, check and technically admit non-executable FND-12 TargetBindingPlan drafts for Ergon rule migration. Use after evidence-bound decomposition and semantic-gap reporting when Codex must project a selected decision into governed JSON Logic, Java, host or DB-backed target surfaces, preserve unknowns and blockers, run the canonical checker/admission chain, or prepare target-planning evidence without generating code, Config records, runtime definitions, business approval or authority.4metadata:5 source: https://skillmd.com/skills/codexrodrigues/ergon-rule-target-planning6---78# Ergon Rule Target Planning910Materialize only the internal FND-12 technical plan. Let11`$ergon-rule-migration-orchestration` decide phase admission and use12`$ergon-rule-executor-selection` for the executor classification.1314## Step Zero: Readiness1516Read `docs/migracao/rule-migration/factory-contracts/part2-foundation-readiness-v2.json`17before opening inputs. Resolve the active profile, environment, authority,18allowed stages/actions and blocking gaps. Continue only when the requested work19is admitted as `MATERIALIZE_TECHNICAL_DRAFT`; never translate corporate20`NOT_READY` into a global development block or reuse development admission in21another environment.2223## Required Inputs2425- exact screen, operation, canonical decision identity and environment;26- RF-01 source manifest, RF-03 decision proposal, RF-04 materialized profile27 and RF-05 semantic-gap report with verified lineage;28- reconciled Parte 1 evidence and explicit unresolved conflicts;29- an evidence-backed executor selection or explicit `UNKNOWN`/review question;30- canonical FND-12 schemas, matrix, checker, materializer and toolchain from the31 active migration repository.3233Read `references/contract-and-forward-tests.md` before creating or reviewing a34plan.3536## Workflow37381. Freeze evidence revisions, hashes and canonical decision identity.392. Confirm every requested target surface is admitted by the total surface40 matrix; reject any unlisted combination.413. Copy only governed facts. Preserve order, dependencies, reason-code42 semantics, cardinality, aggregation and executor details as explicit43 unknown envelopes when evidence is insufficient.444. Produce exactly one `RULE_TARGET_BINDING_PLAN` with45 `MATERIALIZED_UNCHECKED`. Do not embed checker or admission results.465. Run the independent checker. Accept only a separate47 `TECHNICAL_PLAN_VERIFIED` result bound to the exact plan digest.486. When local admission is requested, use the official admission command from49 a clean revision and the fixed-local-disk store capability. Accept only a50 separate `TECHNICAL_PLAN_ADMITTED` receipt.517. Update traceability and stage blockers. Do not close a migration phase from52 FND-12 status alone.5354## Hard Boundary5556Never create JSON Logic expressions, Java classes, `RuleSetDefinition`, Config57materialization, executable snapshots, runtime bindings, publication,58activation, shadow authorization or legacy containment. `KEEP_DB_BACKED` is an59authority hold, not an engine executor. Technical admission is not business60homologation.6162Fail closed on evidence drift, unknown target surface, ungoverned default,63secret/source/SQL leakage, dirty producer revision, checker mismatch, remote64store, forged capability or partial batch.