Activate Algorithms Implementation Guidance
Purpose
Provides ERP Risk and Security implementation guidance for the Activate Algorithms functional area.
When to Use
Use this functional-area skill after Risk and Security scope is confirmed and the project needs activate algorithms setup planning, baseline export, import sequencing, or validation checkpoints.
Catalog Metadata
- Pillar:
ERP - Offering:
Risk and Security(ORA_RISK_AND_CONTROLS) - Functional area / Setup Object:
Activate Algorithms(ORA_GTG_ACTIVATE_ALGORITHMS)
Setup Tasks
- Activate Audit Policies (
ORA_GTG_ACTIVATE_AUDIT_POLICIES) - Activate Algorithms (
ORA_GTG_ACTIVATE_ALGORITHMS)
Strongly recommend completing and verifying Activate Audit Policies in the same environment before beginning Activate Algorithms. A planned backend validation is expected to reject an algorithm activation when its audit policies are disabled. This is currently a sequencing recommendation, not a claim that the backend check already exists.
Execution Routing
This parent skill provides functional-area guidance. For an Activate
Algorithms implementation run, first route to Activate Audit Policies,
then invoke its declared child
Activate Algorithms. Its executable planner is
activate-algorithms/scripts/execute.py relative to that child skill, not
scripts/execute.py relative to this parent.
When the consultant explicitly defers Activate Audit Policies and selects Activate Algorithms as the next task, route directly to that child after recording the deferral. This does not make audit coverage ready or bypass the algorithm child's own readiness, approval, or publication gates.
When the durable workflow re-invokes either child, it may provide that child’s Phase Evidence Handoff for valid same-environment read-only evidence. The verified Audit Policies result is reused only for its immediate approval path; it does not authorize publication. Do not begin algorithm publication while Audit Policies is awaiting an approval or verification. An explicit Audit Policies deferral is not an awaiting state; it permits only the requested task switch.
Inputs
implementation_objectiveproject_contextactivate_algorithms_scopeactivate_algorithms_requirements
Outputs
functional_area_setup_planconfiguration_guidancevalidation_checkpointsskill_run_recordtoken_usage_record
Implementation Notes
Use the generated setup-task metadata files for task-level planning and sequencing. Track token usage for any generated project artifact or skill-run record using the manifest policy.