Ergon Forms Target Handoff
Use this skill only at the convergence boundary defined by
docs/architecture/ADR-0001-separacao-das-fontes-legadas.md. The Forms
repository owns the source dossier; the target application owns later public
contracts and implementation.
Entry gate
Require all of the following before emitting a handoff:
- F6 classifies a functional capability without source UI/object names.
- F7 admits that same
functionalityId, resolves a real canonical owner and
consumer, and keeps implementation unauthorized.
- Every target incompatibility has a residual code and a return condition.
- The evidence files referenced by F6/F7 exist and their current hashes can be
calculated.
Fail closed if any condition is missing. Return to F4/F5/F6/F7 rather than
inventing target semantics.
Workflow
- Read the F6 semantic candidate and F7 admission.
- Classify target reuse as
REUSE, EXTEND, CREATE, BLOCK or DEFER.
- Run
scripts/Export-FormsTargetHandoff.ps1 with the admitted inputs.
- Run
scripts/Test-FormsTargetHandoff.ps1; a generated file that differs
from the versioned artifact is stale and cannot be consumed.
- Route the accepted intake to the canonical target owner for contract
discovery. Apply target API/UI skills only there and only after their entry
gates pass.
Handoff boundary
The intake may contain functional concepts, owner, consumer, reuse decisions,
invariants, residual codes, authority limits and opaque dossier hashes. It must
not contain or require:
- FMB/FMX, block, item, trigger, HWND or desktop-control identity;
.tp, XML, Cronos, Archon or browser-discovery artifacts;
sourceOrigin, V1/V2, aliases, origin modes or parallel target resources;
- SQL, schema, package,
ROWID or private session/credential values;
- authorization to change public contracts, Java, Angular, rules, DML,
publication, shadow, cutover or legacy authority.
The screen/functionality identifier may remain as opaque traceability. Source
paths stay in the origin dossier; the handoff carries only role, identifier and
SHA-256.
Completion
Completion requires a schema-valid, deterministic handoff, a passing boundary
checker and a gate that names the next target-owned contract step. Do not call
the target API implemented or verified from the handoff alone.
1---2name: ergon-forms-target-handoff3description: Validate an admitted Oracle Forms F7 capability and emit an origin-neutral intake for its real Ergon/Praxis target owner. Use only after F6 semantics and F7 admission are closed; do not use for Forms discovery, Cronos/Archon discovery, public API design, Java/Angular implementation or rule migration.4metadata:5 source: https://skillmd.com/skills/codexrodrigues/ergon-forms-target-handoff6---78# Ergon Forms Target Handoff910Use this skill only at the convergence boundary defined by11`docs/architecture/ADR-0001-separacao-das-fontes-legadas.md`. The Forms12repository owns the source dossier; the target application owns later public13contracts and implementation.1415## Entry gate1617Require all of the following before emitting a handoff:18191. F6 classifies a functional capability without source UI/object names.202. F7 admits that same `functionalityId`, resolves a real canonical owner and21 consumer, and keeps implementation unauthorized.223. Every target incompatibility has a residual code and a return condition.234. The evidence files referenced by F6/F7 exist and their current hashes can be24 calculated.2526Fail closed if any condition is missing. Return to F4/F5/F6/F7 rather than27inventing target semantics.2829## Workflow30311. Read the F6 semantic candidate and F7 admission.322. Classify target reuse as `REUSE`, `EXTEND`, `CREATE`, `BLOCK` or `DEFER`.333. Run `scripts/Export-FormsTargetHandoff.ps1` with the admitted inputs.344. Run `scripts/Test-FormsTargetHandoff.ps1`; a generated file that differs35 from the versioned artifact is stale and cannot be consumed.365. Route the accepted intake to the canonical target owner for contract37 discovery. Apply target API/UI skills only there and only after their entry38 gates pass.3940## Handoff boundary4142The intake may contain functional concepts, owner, consumer, reuse decisions,43invariants, residual codes, authority limits and opaque dossier hashes. It must44not contain or require:4546- FMB/FMX, block, item, trigger, HWND or desktop-control identity;47- `.tp`, XML, Cronos, Archon or browser-discovery artifacts;48- `sourceOrigin`, V1/V2, aliases, origin modes or parallel target resources;49- SQL, schema, package, `ROWID` or private session/credential values;50- authorization to change public contracts, Java, Angular, rules, DML,51 publication, shadow, cutover or legacy authority.5253The screen/functionality identifier may remain as opaque traceability. Source54paths stay in the origin dossier; the handoff carries only role, identifier and55SHA-256.5657## Completion5859Completion requires a schema-valid, deterministic handoff, a passing boundary60checker and a gate that names the next target-owned contract step. Do not call61the target API implemented or verified from the handoff alone.