Ergon Rule Portfolio Catalog
Treat the catalog as the migration portfolio and navigation surface. It is not
an executable rule contract, business homologation, or runtime authority.
Step Zero: Readiness
- Locate the migration workspace and read its root
AGENTS.md.
- Read
docs/migracao/rule-migration/factory-contracts/part2-foundation-readiness-v2.json
before selecting, advancing, or presenting the next action for a rule.
- Require the active profile to admit the requested stage and action. A global
corporate blocker must not stop development discovery when the active
development profile explicitly admits it; development evidence must never
be reused as homologation or production admission.
- Read
docs/migracao/rule-migration/ergon-business-rule-catalog-and-cockpit-study-2026-07-21.md
when changing the catalog model or scope.
- Read
references/catalog-phase-forward-tests.md before changing state
projection, aliases, authority, or next-action logic.
Preserve these separate identities and state axes:
- documentary rules such as
RN-013;
- atomic decision proposals such as
regra-frequencia.periodo.ordem-valida;
- working aliases such as
RN-013a;
- legacy authority, target authority, semantic status and migration phase.
Never infer that an RN suffix is an ordinal of migrated work. Never promote a
technical proposal, description, draft, phase result or alias to
business-confirmed or target-authoritative state.
Canonical Sources
In the migration repository, use these sources rather than copying their
content into the skill:
docs/migracao/rule-migration/rule-canonical-decision-inventory.md for the
reconciled documentary RN slice;
docs/migracao/rule-migration/factory-contracts/goldens/*.rule-decision-profile.json
for atomic technical proposals;
- governed semantic packages for per-decision semantic status;
- governed phase state/evidence for the current migration position;
docs/migracao/rule-migration/factory-contracts/reference/ergon-rule-migration-portfolio-v1.json
as the generated internal portfolio;
docs/migracao/rule-migration/factory-contracts/reference/ergon-rule-domain-catalog-v0.2.json
as the sanitized Praxis projection;
docs/migracao/rule-migration/ergon-rule-migration-cockpit.html as the
generated read-only visual surface.
The canonical Domain Catalog contract belongs to praxis-config-starter. Do
not introduce an Ergon-specific public catalog API or redefine
praxis.domain-catalog/v0.2 in the migration repository.
Workflow
Audit or explain the portfolio
Run the repository checker before trusting generated artifacts:
tools/migration-factory/check-rule-portfolio-catalog.ps1
Report counts by artifact kind and state axis. Do not sum documentary rules
and atomic proposals as though they were the same population.
Explain aliases through their canonicalRuleId and decisionKey.
State semantic status, current legacy authority and target authority
separately.
Cite canonical source paths for claims about meaning, status or coverage.
Refresh the catalog
Change a canonical source only when new governed evidence actually changes
it.
Rebuild deterministically:
tools/migration-factory/build-rule-portfolio-catalog.ps1
tools/migration-factory/test-rule-portfolio-catalog.ps1
Review the generated portfolio, Domain Catalog projection and cockpit in
the same cycle.
Run tools/migration-factory/test-rule-migration-factory-contracts.ps1
when the change affects identities, states, mappings, schemas or the
assembler/checker.
Keep generated output byte-identical when inputs do not change.
Select work for Parte 2
- Filter candidates by bounded context, evidence coverage, semantic status,
legacy authority and current migration state.
- Record why the selected atomic decision is bounded enough for intake.
- Invoke
$ergon-rule-migration-orchestration for Phase 9 and later. This
skill does not open, close or approve a migration phase.
- After governed evidence or phase state changes, rebuild and recheck the
catalog so the cockpit cannot drift from the factory artifacts.
- If the phase is blocked, expose the blocker and its admissible recovery
action; do not present a later phase as the next action.
Fail-closed Rules
- Block refresh on duplicate RN IDs, duplicate decision keys, orphan
proposals, unresolved generated-source references, invalid aliases, schema
failure or non-deterministic output.
- Never copy an atomic phase/status onto its documentary parent or sibling.
- Block any generated promotion to target authority.
- Preserve
UNKNOWN, REVIEW_REQUIRED and KEEP_DB_BACKED; do not synthesize
missing business meaning, owner, effects, fact providers, outcomes, reason
codes or evidence.
- Keep business homologation deferred to its later process. A technical catalog
may guide development intake without pretending that domain specialists have
approved the semantics.
- Do not expose credentials, client data, SQL session context, HADES internals
or unsanitized source in the Domain Catalog projection or cockpit.
Expected Handoff
Return:
- catalog/check status;
- exact counts separated by documentary rules and atomic proposals;
- selected canonical rule, decision key and aliases;
- evidence and unresolved blockers;
- semantic status, current authorities and allowed next action;
- changed generated artifacts and validation commands.
1---2name: ergon-rule-portfolio-catalog3description: Build, audit, and consume the governed read-only portfolio of Ergon legacy rules and atomic decision proposals. Use when Codex must explain RN identities such as RN-013a, measure discovered versus proposed versus migrated rules, refresh the rule cockpit or Praxis Domain Catalog v0.2 projection, check catalog determinism, select a rule for Parte 2 intake, or reconcile catalog state after a migration phase.4metadata:5 source: https://skillmd.com/skills/codexrodrigues/ergon-rule-portfolio-catalog6---78# Ergon Rule Portfolio Catalog910Treat the catalog as the migration portfolio and navigation surface. It is not11an executable rule contract, business homologation, or runtime authority.1213## Step Zero: Readiness14151. Locate the migration workspace and read its root `AGENTS.md`.162. Read17 `docs/migracao/rule-migration/factory-contracts/part2-foundation-readiness-v2.json`18 before selecting, advancing, or presenting the next action for a rule.193. Require the active profile to admit the requested stage and action. A global20 corporate blocker must not stop development discovery when the active21 development profile explicitly admits it; development evidence must never22 be reused as homologation or production admission.234. Read24 `docs/migracao/rule-migration/ergon-business-rule-catalog-and-cockpit-study-2026-07-21.md`25 when changing the catalog model or scope.265. Read `references/catalog-phase-forward-tests.md` before changing state27 projection, aliases, authority, or next-action logic.2829Preserve these separate identities and state axes:3031- documentary rules such as `RN-013`;32- atomic decision proposals such as33 `regra-frequencia.periodo.ordem-valida`;34- working aliases such as `RN-013a`;35- legacy authority, target authority, semantic status and migration phase.3637Never infer that an RN suffix is an ordinal of migrated work. Never promote a38technical proposal, description, draft, phase result or alias to39business-confirmed or target-authoritative state.4041## Canonical Sources4243In the migration repository, use these sources rather than copying their44content into the skill:4546- `docs/migracao/rule-migration/rule-canonical-decision-inventory.md` for the47 reconciled documentary RN slice;48- `docs/migracao/rule-migration/factory-contracts/goldens/*.rule-decision-profile.json`49 for atomic technical proposals;50- governed semantic packages for per-decision semantic status;51- governed phase state/evidence for the current migration position;52- `docs/migracao/rule-migration/factory-contracts/reference/ergon-rule-migration-portfolio-v1.json`53 as the generated internal portfolio;54- `docs/migracao/rule-migration/factory-contracts/reference/ergon-rule-domain-catalog-v0.2.json`55 as the sanitized Praxis projection;56- `docs/migracao/rule-migration/ergon-rule-migration-cockpit.html` as the57 generated read-only visual surface.5859The canonical Domain Catalog contract belongs to `praxis-config-starter`. Do60not introduce an Ergon-specific public catalog API or redefine61`praxis.domain-catalog/v0.2` in the migration repository.6263## Workflow6465### Audit or explain the portfolio66671. Run the repository checker before trusting generated artifacts:6869 ```powershell70 tools/migration-factory/check-rule-portfolio-catalog.ps171 ```72732. Report counts by artifact kind and state axis. Do not sum documentary rules74 and atomic proposals as though they were the same population.753. Explain aliases through their `canonicalRuleId` and `decisionKey`.764. State semantic status, current legacy authority and target authority77 separately.785. Cite canonical source paths for claims about meaning, status or coverage.7980### Refresh the catalog81821. Change a canonical source only when new governed evidence actually changes83 it.842. Rebuild deterministically:8586 ```powershell87 tools/migration-factory/build-rule-portfolio-catalog.ps188 tools/migration-factory/test-rule-portfolio-catalog.ps189 ```90913. Review the generated portfolio, Domain Catalog projection and cockpit in92 the same cycle.934. Run `tools/migration-factory/test-rule-migration-factory-contracts.ps1`94 when the change affects identities, states, mappings, schemas or the95 assembler/checker.965. Keep generated output byte-identical when inputs do not change.9798### Select work for Parte 2991001. Filter candidates by bounded context, evidence coverage, semantic status,101 legacy authority and current migration state.1022. Record why the selected atomic decision is bounded enough for intake.1033. Invoke `$ergon-rule-migration-orchestration` for Phase 9 and later. This104 skill does not open, close or approve a migration phase.1054. After governed evidence or phase state changes, rebuild and recheck the106 catalog so the cockpit cannot drift from the factory artifacts.1075. If the phase is blocked, expose the blocker and its admissible recovery108 action; do not present a later phase as the next action.109110## Fail-closed Rules111112- Block refresh on duplicate RN IDs, duplicate decision keys, orphan113 proposals, unresolved generated-source references, invalid aliases, schema114 failure or non-deterministic output.115- Never copy an atomic phase/status onto its documentary parent or sibling.116- Block any generated promotion to target authority.117- Preserve `UNKNOWN`, `REVIEW_REQUIRED` and `KEEP_DB_BACKED`; do not synthesize118 missing business meaning, owner, effects, fact providers, outcomes, reason119 codes or evidence.120- Keep business homologation deferred to its later process. A technical catalog121 may guide development intake without pretending that domain specialists have122 approved the semantics.123- Do not expose credentials, client data, SQL session context, HADES internals124 or unsanitized source in the Domain Catalog projection or cockpit.125126## Expected Handoff127128Return:129130- catalog/check status;131- exact counts separated by documentary rules and atomic proposals;132- selected canonical rule, decision key and aliases;133- evidence and unresolved blockers;134- semantic status, current authorities and allowed next action;135- changed generated artifacts and validation commands.