Manage Job Roles
Purpose
Provide a controlled, cross-pillar method to create, update, redesign and
process deletion requests for individual custom roles, and to export, validate
and approval-gate the import of the Manage Job Roles FSM setup task. Delegate
transport and live import execution to the declared shared and core
dependencies. Prepare user-specified role values only against a verified FSM
CSV template, retaining its headers, metadata and supported operations.
Export and move the FSM setup task Manage Job Roles only through the
declared dependency workflows. The catalog identity is task code
ASXS_MANAGE_JOB_ROLES; require a current catalog or live-task lookup to
confirm that its export/import flags remain supported before execution.
Scope and boundaries
- Accept creation, update, redesign and deletion requests for individual custom
roles. Prepare only operations supported by the current FSM CSV contract;
execute supported changes through
core.data-loader.
- Support task-level FSM CSV export and import of an exported, supplied or
template-conformant candidate archive.
- Honor the user's role design and explicit changes in this skill. Preserve
unrelated fields and memberships; do not substitute another skill's missing
execution classification for this declared FSM/Data Loader route.
- Do not call Fusion, OAuth, UCM, REST, FSM, or loader commands directly.
shared.setup-export.task-level-export owns export; core.data-loader
owns every import preflight, upload, initiation, and monitoring route.
- Treat a changed archive, source scope, target environment, or validation
result as a new request that must pass all gates again.
Required preflight
- Resolve the project workspace, requested operation, source and target
environments, and the exact job-role scope. Require source and target to be
distinct for a migration request; require explicit confirmation for a
same-environment restore.
- Confirm the exact task name and code with
shared.setup-export.task-level-export and verify its current
CSVExportImportSupportedFlag is Y. If the task is ambiguous, unavailable,
or unsupported, record a catalog-mismatch diagnostic and stop.
- Confirm the operator has Functional Setup Manager export access in the
source and Data Loader import privileges in the target. Do not request or
expose credentials, access tokens, or tenant secrets.
- Record the source/target identities, task code, scope, and a redacted
execution plan in the project workspace before any side effect.
Individual custom-role operations
| Requested operation |
Preparation and execution boundary |
| Create |
Prepare a custom-role definition and explicit hierarchy or privilege membership rows using the verified template. |
| Update |
Identify the existing custom role by exact code; change only the requested supported definition fields or memberships. |
| Redesign |
Prepare an explicit before/after plan for the requested role, hierarchy and direct privilege changes. Use ADD for additions and REMOVE for requested membership removals. |
| Delete a hierarchy or privilege membership |
Retain a row identifying the parent and member and set the documented membership action to REMOVE. Removing a CSV row is not a deletion operation. |
| Delete an individual role |
Accept and scope the request, then confirm an explicit whole-role deletion operation in current Oracle guidance and the target's FSM import contract. Execute only if that operation is supported by Data Loader's selected FSM route. The existing role-definition template has no deletion-action column; do not invent DELETE, treat membership REMOVE as role deletion, or silently switch to browser, REST, SCIM or HDL. If no supported operation is established, record the operation-support gap and required next action. |
Creation, updates and redesign are intentional changes in the selected target;
they are not automatically same-environment restores. Preserve source metadata
and construct a new candidate before validation. Once validated, leave the
archive unchanged through the Data Loader approval and execution steps.
Do not edit or delete Oracle-seeded roles as if they were custom roles. Role
code changes, user provisioning and data-security-policy changes require an
explicit supported contract; this CSV route does not add or remove direct
data-security policies. Inherited data access can change when memberships change.
For deletion or removal, identify the exact affected role and memberships and
show the intended removal in the operation plan before Data Loader's approval
preview. Do not infer deletion from an omitted row, a blank value or a redesign
request. Keep template-export auto-authorization separate from actual role
mutations; Core Data Loader remains the authoritative import approval gate.
Export Manage Job Roles
- Route the export to
shared.setup-export.task-level-export with task name
Manage Job Roles, task code ASXS_MANAGE_JOB_ROLES, the source environment,
and project ID.
- Let that skill perform the task lookup, support-flag validation, export
process creation, polling, download, and project export persistence. Do not
substitute a template export for a data export.
- Preserve the returned ZIP unchanged. Register its path, SHA-256, process ID,
task identity, source environment, and export timestamp as the export record.
- On an export timeout or failure, preserve the task code, process ID, last
status, process log reference, elapsed wait, and next-check path. Do not
start another export process automatically.
Template-first import preparation
Read FSM input preparation when the user needs help with the
template. Accept plain-language requirements, safely extract the package,
explain the columns and prepare the candidate; do not require the user to
understand or populate the CSV before work can start.
For user-specified custom role data, use the target environment's task-level
CSV template/spec package through shared.setup-export.task-level-export.
Template acquisition is not a migration or a same-environment restore.
Automatically authorize and execute the template/spec export needed to prepare
a user-requested role import; do not ask for a separate template-export approval.
This user-authorized exception applies only to setupTaskCSVTemplateExports
for the selected task and environment. It does not authorize populated data
exports, uploads, role imports, or retries after an uncertain POST outcome.
Retain identity, privilege, catalog, payload and audit checks, and leave actual
import approval to core.data-loader. Verify the template
supports every requested field and hierarchy reference; do not invent values,
columns, category codes or an IP-access encoding.
Oracle documents role code, name, description, category and all-IP-address
access in Functional Security Custom Roles, plus parent/member codes and
ADD/REMOVE operations in the hierarchy file. Direct data-security policies are
not included in this CSV route. Consult
the Oracle CSV role contract
and CSV package editing guidance.
The target's template and import validations remain authoritative for a new
role; catalog flags alone do not prove the complete supplied request is valid.
This workflow uses core.data-loader for execution, never browser creation.
- Unless the user explicitly overrides this sequence, export the task first
and provide that export as the import template before asking for import
content. Explain that the template establishes the supported archive and
file structure; it is not approval to import.
- When the user provides an input file, compare it with the export template
for file names, headers, column order, encoding, required values, and
task-specific references. Help correct structural defects in a separate
candidate file; preserve the supplied original and do not silently alter
business values.
- Give the user a concise change summary and identify any unresolved values
or references. Use the corrected file only after it conforms to the export
structure and has been assembled into a new candidate archive using the
supported archive shape. That candidate is a new artifact and must pass the
validation and approval gates below.
- The user may override the export-first sequence, template choice, or
proposed file corrections at any time. Honor that direction, while retaining
the required task-identity, validation, and immediate import-approval gates.
Validate the archive for import
- Require the supplied archive to be a non-empty ZIP and bind its SHA-256 to
task code
ASXS_MANAGE_JOB_ROLES, source environment, and target environment.
- Route setup-data validation to
shared.validation.setup-data-validator and
preserve the resulting validation evidence. Fail closed on archive-shape,
task-identity, scope, catalog, environment, or privilege mismatch.
- Do not alter, unpack-and-repack, merge, or otherwise transform the archive
after validation. Any change invalidates the evidence and approval preview.
Optional Risk and Security Checkup
After archive validation and before the Data Loader handoff, resolve the user's
choice for this candidate and target. This is part of MJR.DESIGN_GATE. The
checkup dependency and its BOSS privileges are conditional on opting in; they
must not block the declined path. Export-only and template-only requests do
not enter this import checkpoint.
Unless the user has already explicitly chosen for this candidate and target, ask:
Would you like to run Risk and Security Checkup on the proposed role access before importing? It checks for sensitive access and toxic privilege combinations.
Wait for an explicit yes or no. Silence, an import request, or import approval
is not consent to this assessment. Reuse an existing explicit choice for the
unchanged candidate and target without asking again.
- Yes: Route to
Risk and Security Checkup
(
shared.common.security.risk-and-security-checkup) under the active project
workflow, using the selected target environment. That skill owns input
normalization, Core-delegated fresh BOSS metadata reads, assessment delivery,
artifacts, diagnostics and token accounting. Complete its preflight before
external reads; do not start direct HTTP, OAuth or hierarchy lookups here.
- No: Record
declined and present Security checkup: Not performed.
Continue to the normal Data Loader validation and approval workflow without
executing the checkup, authenticating for it, or implying the roles are safe.
Assess the proposed resulting role access rather than treating change rows as
a complete final role. Apply the checkup's
input contract:
its job-role ZIP normalizer excludes hierarchy expansion and cannot establish
final membership from REMOVE rows without a baseline. For a delta or redesign,
require baseline and proposed resulting privilege evidence, including resolved
inherited access where relevant, supplied or obtained through an already
supported routed workflow. Do not invent effective access or add a live lookup
route. Preserve the checkup's supplied-input coverage limitations. Evaluate
roles independently unless explicit user/persona grouping is supplied.
Present completed findings and coverage gaps before the import preview. Keep
risk acceptance with the user; findings do not authorize automatic role changes
or create a second import-approval gate. If the selected assessment fails or
required evidence is unavailable, record blocked or failed with its
classified diagnostic and stop this handoff. The user may resolve the blocker
or explicitly decline the optional assessment and proceed with Security
checkup: Not performed; never silently skip it or report a clean result.
Persist an append-only security_checkup_decision in the declared project
decision location and register/update project state through the existing Core
services. Record task, candidate artifact reference, target, explicit choice,
status (declined, completed, blocked, or failed), input coverage, and
assessment/diagnostic artifact references when available. Keep Data Loader
session captures, hashes, previews and approval objects in its live process
according to its contract; do not serialize them into the decision record.
If remediation changes the archive, repeat archive validation and this choice
checkpoint for the new candidate; do not reuse the old assessment. A changed
target or assessment input likewise invalidates prior assessment evidence.
Choosing the checkup never approves an import. Core Data Loader retains its
single authoritative final preview and execution-approval workflow. Present
the checkup outcome separately before that preview without altering the
loader's required preview output.
Import the validated archive
- Complete the optional checkup checkpoint above: require an explicit decline
or a completed assessment presented to the user for the unchanged candidate
and target. Route the immutable validated archive to
core.data-loader as an FSM,
task-routed import. Provide the task context, target environment, archive
SHA-256, and validation evidence.
- Let
core.data-loader complete its required source and API validation and
produce its immutable approval preview. This skill must not bypass or replace
the Data Loader route with a direct FSM API, UCM upload, REST call, CSV
utility, or browser action.
- Present the exact target environment, task code, archive name and SHA-256,
validation result, and expected import impact. Stop before the first POST.
- Proceed only after the user gives a separate, immediate approval for that
immutable preview.
core.data-loader revalidates the archive and owns the
upload, initiation, process monitoring, and diagnostics.
- Do not retry an upload, initiation, import, overwrite, or replacement
process without a fresh approval. Preserve returned request IDs, process-log
references, and redacted diagnostics in the project workspace.
Failure handling
Classify failures as input validation, catalog mismatch, authorization,
transport/environment, Fusion API, process timeout, process failed, artifact
persistence, or approval blocker. Redact credentials, tokens, customer data,
and sensitive role configuration. For any ambiguity or unsafe path, record the
blocker and recommended next action, then stop.
Setup Tasks
No setup tasks were supplied when this skill was generated.
1---2skill_id: "common.security-console.manage-job-roles"3name: manage-job-roles4description: "Prepare individual custom-role creation, updates, redesign and deletion requests, and route supported role changes through validated FSM CSV packages and approval-gated Data Loader execution. Also export, migrate or restore Manage Job Roles setup data."5layer: "pillar"6pillar: "Common"7type: "orchestration"8task_code: "ASXS_MANAGE_JOB_ROLES"9task_name: "Manage Job Roles"10parent_skill_id: "common.security-console"11available_flag: "Y"12export_import_supported_flag: "Y"13csv_export_import_supported_flag: "Y"14dataloader_import_mode: "FSM"15businessObject: ""16source_catalog: "knowledge/setup-task-catalog/effective/setupTasksAll.json"17execution_mode: "hybrid"18owner_team: "FSCR Security team"19version: "0.3.0"20inputs:21 - "project_id"22 - "source_environment"23 - "target_environment"24 - "requested_operation"25 - "job_role_scope"26 - "setup_archive"27 - "user_input_file"28 - "execution_approval"29 - "role_definition_or_change_request"30 - "security_checkup_choice"31 - "proposed_role_and_privilege_evidence"32outputs:33 - "manage-job-roles-export"34 - "import-template-export"35 - "input-file-conformance-result"36 - "corrected-input-file"37 - "archive-validation-result"38 - "import-approval-preview"39 - "data-load-execution-result"40 - "diagnostics"41 - "skill_run_record"42 - "token_usage_record"43 - "role_change_plan"44 - "operation_support_result"45 - "security_checkup_decision"46 - "security_checkup_result_reference"47depends_on:48 - "shared.setup-export.task-level-export"49 - "shared.validation.setup-data-validator"50 - "shared.common.security.risk-and-security-checkup"51 - "core.data-loader"52uses_core:53 - "core.data-loader"54 - "core.project-mgmt.artifact-registry-manager"55 - "core.project-mgmt.project-state-manager"56persists_project_state: true57token_usage_tracking:58 enabled: true59 granularity: "per_skill_run"60 artifact_type: "token_usage_record"61 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"62 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"63 required_fields:64 - "activity_start_time"65 - "skill_id"66 - "task"67 - "trigger"68 - "artifacts_written"69 - "files_read"70 - "estimated_input_tokens"71 - "estimated_output_tokens"72 - "estimated_total_tokens"73 - "estimation_method"74 - "notes"75state_updates:76 - "scope"77 - "exports"78 - "validation_results"79 - "design_decisions"80 - "token_usage_records"81workspace_outputs:82 - artifact_type: "design_decision"83 default_location: "project/{project_id}/decisions/common/security-console/manage-job-roles/"84 versioning_policy: "append-only"85 - artifact_type: "configuration_export"86 default_location: "project/{project_id}/exports/common/security-console/manage-job-roles/"87 versioning_policy: "major-new-version-minor-confirm-update"88 - artifact_type: "validation_result"89 default_location: "project/{project_id}/artifacts/pillars/common/security-console/manage-job-roles/current/"90 versioning_policy: "major-new-version-minor-confirm-update"91 - artifact_type: "skill_run"92 default_location: "project/{project_id}/state/runs/"93 versioning_policy: "append-only"94 - artifact_type: "token_usage_record"95 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"96 versioning_policy: "append-only"97oracle_supplied_guidance_files:98 - purpose: "FSM archive and task identity validation"99 location: "ora-resource/ora_input_validation.md"100 - purpose: "Import dependency and same-environment restore checks"101 location: "ora-resource/ora_dependency_readiness.md"102 - purpose: "Immutable preview and Data Loader route enforcement"103 location: "ora-resource/ora_design_enforcement.md"104 - purpose: "Approval, retry, and diagnostic controls"105 location: "ora-resource/ora_error_handling.md"106oracle_supplied_guidance_status: "Repository-authored task validation guidance; current Oracle documentation and the active Fusion contract remain authoritative."107applicability:108 industries:109 - "All"110 countries:111 - "All"112 fusion_releases:113 - "Current Oracle Fusion Cloud release"114side_effects:115 - "Only when the user opts in, delegates read-only risk metadata retrieval and assessment artifacts to the shared Risk and Security Checkup workflow."116 - "May route an approved task-level export to the shared export skill."117 - "May route an approved immutable FSM archive to core.data-loader for upload and import."118required_privileges:119 - "When the optional checkup is selected, BOSS read privileges required by shared.common.security.risk-and-security-checkup in the selected target environment."120 - "Verified Functional Setup Manager privileges to export the Manage Job Roles setup task."121 - "Verified target-environment privileges to upload and initiate the approved FSM archive through Data Loader."122metadata:123 source: https://skillmd.com/skills/oracle/manage-job-roles124---125126# Manage Job Roles127128## Purpose129130Provide a controlled, cross-pillar method to create, update, redesign and131process deletion requests for individual custom roles, and to export, validate132and approval-gate the import of the **Manage Job Roles** FSM setup task. Delegate133transport and live import execution to the declared shared and core134dependencies. Prepare user-specified role values only against a verified FSM135CSV template, retaining its headers, metadata and supported operations.136137Export and move the FSM setup task **Manage Job Roles** only through the138declared dependency workflows. The catalog identity is task code139`ASXS_MANAGE_JOB_ROLES`; require a current catalog or live-task lookup to140confirm that its export/import flags remain supported before execution.141142## Scope and boundaries143144- Accept creation, update, redesign and deletion requests for individual custom145 roles. Prepare only operations supported by the current FSM CSV contract;146 execute supported changes through `core.data-loader`.147- Support task-level FSM CSV export and import of an exported, supplied or148 template-conformant candidate archive.149- Honor the user's role design and explicit changes in this skill. Preserve150 unrelated fields and memberships; do not substitute another skill's missing151 execution classification for this declared FSM/Data Loader route.152- Do not call Fusion, OAuth, UCM, REST, FSM, or loader commands directly.153 `shared.setup-export.task-level-export` owns export; `core.data-loader`154 owns every import preflight, upload, initiation, and monitoring route.155- Treat a changed archive, source scope, target environment, or validation156 result as a new request that must pass all gates again.157158## Required preflight1591601. Resolve the project workspace, requested operation, source and target161 environments, and the exact job-role scope. Require source and target to be162 distinct for a migration request; require explicit confirmation for a163 same-environment restore.1642. Confirm the exact task name and code with165 `shared.setup-export.task-level-export` and verify its current166 `CSVExportImportSupportedFlag` is `Y`. If the task is ambiguous, unavailable,167 or unsupported, record a catalog-mismatch diagnostic and stop.1683. Confirm the operator has Functional Setup Manager export access in the169 source and Data Loader import privileges in the target. Do not request or170 expose credentials, access tokens, or tenant secrets.1714. Record the source/target identities, task code, scope, and a redacted172 execution plan in the project workspace before any side effect.173174## Individual custom-role operations175176| Requested operation | Preparation and execution boundary |177| --- | --- |178| Create | Prepare a custom-role definition and explicit hierarchy or privilege membership rows using the verified template. |179| Update | Identify the existing custom role by exact code; change only the requested supported definition fields or memberships. |180| Redesign | Prepare an explicit before/after plan for the requested role, hierarchy and direct privilege changes. Use ADD for additions and REMOVE for requested membership removals. |181| Delete a hierarchy or privilege membership | Retain a row identifying the parent and member and set the documented membership action to REMOVE. Removing a CSV row is not a deletion operation. |182| Delete an individual role | Accept and scope the request, then confirm an explicit whole-role deletion operation in current Oracle guidance and the target's FSM import contract. Execute only if that operation is supported by Data Loader's selected FSM route. The existing role-definition template has no deletion-action column; do not invent DELETE, treat membership REMOVE as role deletion, or silently switch to browser, REST, SCIM or HDL. If no supported operation is established, record the operation-support gap and required next action. |183184Creation, updates and redesign are intentional changes in the selected target;185they are not automatically same-environment restores. Preserve source metadata186and construct a new candidate before validation. Once validated, leave the187archive unchanged through the Data Loader approval and execution steps.188189Do not edit or delete Oracle-seeded roles as if they were custom roles. Role190code changes, user provisioning and data-security-policy changes require an191explicit supported contract; this CSV route does not add or remove direct192data-security policies. Inherited data access can change when memberships change.193194For deletion or removal, identify the exact affected role and memberships and195show the intended removal in the operation plan before Data Loader's approval196preview. Do not infer deletion from an omitted row, a blank value or a redesign197request. Keep template-export auto-authorization separate from actual role198mutations; Core Data Loader remains the authoritative import approval gate.199200## Export Manage Job Roles2012021. Route the export to `shared.setup-export.task-level-export` with task name203 `Manage Job Roles`, task code `ASXS_MANAGE_JOB_ROLES`, the source environment,204 and project ID.2052. Let that skill perform the task lookup, support-flag validation, export206 process creation, polling, download, and project export persistence. Do not207 substitute a template export for a data export.2083. Preserve the returned ZIP unchanged. Register its path, SHA-256, process ID,209 task identity, source environment, and export timestamp as the export record.2104. On an export timeout or failure, preserve the task code, process ID, last211 status, process log reference, elapsed wait, and next-check path. Do not212 start another export process automatically.213214## Template-first import preparation215216Read [FSM input preparation](../references/fsm-input-preparation.md) when the user needs help with the217template. Accept plain-language requirements, safely extract the package,218explain the columns and prepare the candidate; do not require the user to219understand or populate the CSV before work can start.220221222For user-specified custom role data, use the target environment's task-level223CSV template/spec package through `shared.setup-export.task-level-export`.224Template acquisition is not a migration or a same-environment restore.225Automatically authorize and execute the template/spec export needed to prepare226a user-requested role import; do not ask for a separate template-export approval.227This user-authorized exception applies only to `setupTaskCSVTemplateExports`228for the selected task and environment. It does not authorize populated data229exports, uploads, role imports, or retries after an uncertain POST outcome.230Retain identity, privilege, catalog, payload and audit checks, and leave actual231import approval to `core.data-loader`. Verify the template232supports every requested field and hierarchy reference; do not invent values,233columns, category codes or an IP-access encoding.234235Oracle documents role code, name, description, category and all-IP-address236access in Functional Security Custom Roles, plus parent/member codes and237ADD/REMOVE operations in the hierarchy file. Direct data-security policies are238not included in this CSV route. Consult239[the Oracle CSV role contract](https://docs.oracle.com/en/cloud/saas/sales/oscus/export-and-import-of-custom-roles-role-hierarchies-and-role-to.html)240and [CSV package editing guidance](https://docs.oracle.com/en/cloud/saas/human-resources/ochus/manage-role-definitions-using-csv-file-packages.html).241The target's template and import validations remain authoritative for a new242role; catalog flags alone do not prove the complete supplied request is valid.243This workflow uses `core.data-loader` for execution, never browser creation.2442451. Unless the user explicitly overrides this sequence, export the task first246 and provide that export as the import template before asking for import247 content. Explain that the template establishes the supported archive and248 file structure; it is not approval to import.2492. When the user provides an input file, compare it with the export template250 for file names, headers, column order, encoding, required values, and251 task-specific references. Help correct structural defects in a separate252 candidate file; preserve the supplied original and do not silently alter253 business values.2543. Give the user a concise change summary and identify any unresolved values255 or references. Use the corrected file only after it conforms to the export256 structure and has been assembled into a new candidate archive using the257 supported archive shape. That candidate is a new artifact and must pass the258 validation and approval gates below.2594. The user may override the export-first sequence, template choice, or260 proposed file corrections at any time. Honor that direction, while retaining261 the required task-identity, validation, and immediate import-approval gates.262263## Validate the archive for import2642651. Require the supplied archive to be a non-empty ZIP and bind its SHA-256 to266 task code `ASXS_MANAGE_JOB_ROLES`, source environment, and target environment.2672. Route setup-data validation to `shared.validation.setup-data-validator` and268 preserve the resulting validation evidence. Fail closed on archive-shape,269 task-identity, scope, catalog, environment, or privilege mismatch.2703. Do not alter, unpack-and-repack, merge, or otherwise transform the archive271 after validation. Any change invalidates the evidence and approval preview.272273## Optional Risk and Security Checkup274275After archive validation and before the Data Loader handoff, resolve the user's276choice for this candidate and target. This is part of `MJR.DESIGN_GATE`. The277checkup dependency and its BOSS privileges are conditional on opting in; they278must not block the declined path. Export-only and template-only requests do279not enter this import checkpoint.280281Unless the user has already explicitly chosen for this candidate and target, ask:282283> Would you like to run Risk and Security Checkup on the proposed role access before importing? It checks for sensitive access and toxic privilege combinations.284285Wait for an explicit yes or no. Silence, an import request, or import approval286is not consent to this assessment. Reuse an existing explicit choice for the287unchanged candidate and target without asking again.288289- **Yes:** Route to290 [Risk and Security Checkup](../../../../shared/common/security/risk-and-security-checkup/SKILL.md)291 (`shared.common.security.risk-and-security-checkup`) under the active project292 workflow, using the selected target environment. That skill owns input293 normalization, Core-delegated fresh BOSS metadata reads, assessment delivery,294 artifacts, diagnostics and token accounting. Complete its preflight before295 external reads; do not start direct HTTP, OAuth or hierarchy lookups here.296- **No:** Record `declined` and present **Security checkup: Not performed**.297 Continue to the normal Data Loader validation and approval workflow without298 executing the checkup, authenticating for it, or implying the roles are safe.299300Assess the proposed resulting role access rather than treating change rows as301a complete final role. Apply the checkup's302[input contract](../../../../shared/common/security/risk-and-security-checkup/references/input-validation.md):303its job-role ZIP normalizer excludes hierarchy expansion and cannot establish304final membership from REMOVE rows without a baseline. For a delta or redesign,305require baseline and proposed resulting privilege evidence, including resolved306inherited access where relevant, supplied or obtained through an already307supported routed workflow. Do not invent effective access or add a live lookup308route. Preserve the checkup's supplied-input coverage limitations. Evaluate309roles independently unless explicit user/persona grouping is supplied.310311Present completed findings and coverage gaps before the import preview. Keep312risk acceptance with the user; findings do not authorize automatic role changes313or create a second import-approval gate. If the selected assessment fails or314required evidence is unavailable, record `blocked` or `failed` with its315classified diagnostic and stop this handoff. The user may resolve the blocker316or explicitly decline the optional assessment and proceed with **Security317checkup: Not performed**; never silently skip it or report a clean result.318319Persist an append-only `security_checkup_decision` in the declared project320decision location and register/update project state through the existing Core321services. Record task, candidate artifact reference, target, explicit choice,322status (`declined`, `completed`, `blocked`, or `failed`), input coverage, and323assessment/diagnostic artifact references when available. Keep Data Loader324session captures, hashes, previews and approval objects in its live process325according to its contract; do not serialize them into the decision record.326327If remediation changes the archive, repeat archive validation and this choice328checkpoint for the new candidate; do not reuse the old assessment. A changed329target or assessment input likewise invalidates prior assessment evidence.330Choosing the checkup never approves an import. Core Data Loader retains its331single authoritative final preview and execution-approval workflow. Present332the checkup outcome separately before that preview without altering the333loader's required preview output.334335## Import the validated archive3363371. Complete the optional checkup checkpoint above: require an explicit decline338 or a completed assessment presented to the user for the unchanged candidate339 and target. Route the immutable validated archive to `core.data-loader` as an FSM,340 task-routed import. Provide the task context, target environment, archive341 SHA-256, and validation evidence.3422. Let `core.data-loader` complete its required source and API validation and343 produce its immutable approval preview. This skill must not bypass or replace344 the Data Loader route with a direct FSM API, UCM upload, REST call, CSV345 utility, or browser action.3463. Present the exact target environment, task code, archive name and SHA-256,347 validation result, and expected import impact. Stop before the first POST.3484. Proceed only after the user gives a separate, immediate approval for that349 immutable preview. `core.data-loader` revalidates the archive and owns the350 upload, initiation, process monitoring, and diagnostics.3515. Do not retry an upload, initiation, import, overwrite, or replacement352 process without a fresh approval. Preserve returned request IDs, process-log353 references, and redacted diagnostics in the project workspace.354355## Failure handling356357Classify failures as input validation, catalog mismatch, authorization,358transport/environment, Fusion API, process timeout, process failed, artifact359persistence, or approval blocker. Redact credentials, tokens, customer data,360and sensitive role configuration. For any ambiguity or unsafe path, record the361blocker and recommended next action, then stop.362363## Setup Tasks364365No setup tasks were supplied when this skill was generated.