Project Control Implementation Guidance
Purpose
Route customer setup requests to mapped Project Control task skills without treating parent task lists as executable setup tasks.
Setup Tasks
- Manage Project Plan Types (
PJO_MANAGE_PROJECT_PLAN_TYPES)
Inbound Cross-Functional Handoff
Route the exact task name Manage Project Plan Types and task code PJO_MANAGE_PROJECT_PLAN_TYPES to erp.project-financial-management.project-control.manage-project-plan-types, including when the preceding runbook task was Manage Project Types under Project Foundation. Do not search only the originating functional-area folder or rewrite the PJO_ code with a PJF_ prefix.
If a caller supplies only the task name, resolve it through the offering task map before deciding availability. A missing guessed path under Project Foundation is not a workflow gap when this indexed Project Control child exists.
Routing Boundary
Use the nested task skill for task-specific validation, target FSM package handling, approval, submission, and readback. This functional-area skill does not create setup data or submit imports.
Parent-Owned Durable Outputs
Persist this parent's functional_area_setup_plan, configuration_guidance and
validation_checkpoints when they are produced or changed, before returning them
as a durable handoff. Project Control outputs describe the approved scope and
recommendations for the mapped Project Plan Types task. They do not establish
that child validation, import or readback has completed.
- Resolve one selected
project_idfromproject_contextand the active workflow, and reuse existing project artifacts. If no project exists, follow the repository project-initialization policy before writing. An ambiguous or conflicting project identity is aninput_validationblocker; do not infer a different project or require the caller to repeat known context. - Preflight the candidate outputs, catalog/task identity, artifact metadata and
destinations. Use the manifest's Project Control artifact directory under
project/{project_id}/artifacts/pillars/erp/project-financial-management/project-control/current/, its decisions directory, run directory and shared token log as applicable. Resolve paths and reject traversal or symlinks escaping the selected project. Check existing versions and write conflicts before side effects. A missing or inconsistent task mapping iscatalog_or_metadata_mismatch; an unconfirmed replacement isapproval_blocker. Stop the affected handoff in either case. - Use
core.project-mgmt.artifact-version-managerto compare existing and candidate artifacts. Create a new version for major changes; update an existing artifact for a minor change only after explicit confirmation. Keep append-only decisions and history intact. A no-change revisit reuses existing artifacts and registrations without replacing them. - Save changed parent outputs at their declared locations and register them
through
core.project-mgmt.artifact-registry-managerusingschemas/project-artifact.schema.json: retain producing skill, location, version, actual review status, timestamps and checksum when available. Never mark an artifact approved merely because it was saved. Link child-owned evidence instead of copying or overwriting child artifacts or executor receipts. - Use
core.project-mgmt.project-state-managerfor deterministic updates supported by the existing state schema and limited to this parent's declared output categories. Record which run and artifact references caused a change. Thesetup_task_sequencecategory represents a saved planning proposal; it does not authorize changing the active workflow's sequence, route, current step or approvals. Return proposed changes to that workflow for adoption under its own gates; do not add state fields or maintain a parallel workflow state. - Record
skill_run_recordunderproject/{project_id}/state/runs/usingschemas/skill-run.schema.json, with this parent's skill ID, input/output and artifact references, timestamps and actual status. Append a completed run for a successful no-change revisit as well. Record token usage at the manifest's shared token-log location through the declared project service's token-usage guidance; include the same estimate and log reference in the run's supportedtoken_usagefields. Return the saved output and run references to the caller.
Persistence Failure and Recovery
If an artifact write, registration, state update, run record or token-log write
fails, stop the affected parent handoff with artifact_persistence; do not claim
a completed durable result or continue child execution from it. Preserve safely
written artifacts and existing state. Record a failed run when writable, using
schema-supported notes and artifact_refs for the failed stage, failure class,
redacted cause, intended paths, completed writes and recommended recovery action.
If that record also cannot be written, report those details to the caller without
claiming that diagnostics were persisted or switching to another project.
Writes across these services are not assumed atomic. Do not retry blindly, delete partial artifacts or replay child operations. On recovery, inspect existing files, versions, checksums, registrations and state references; reconcile completed steps and resume only the missing local persistence work, retaining the existing versioning and confirmation gates. If a required service or supported contract is unavailable, report the workflow gap instead of substituting another writer. Never print or persist credentials, tokens, token-cache contents, private keys or sensitive payloads. This procedure grants no external-operation authority.