cesnimda
3.6 KiB
Owner decision brief — NOT a protected request or signature
Current recommendation: NO-GO for starting the autonomous orchestrator. App/PDF preparation is conditionally closed; resolve the three control-plane items in FINAL_DEVELOPMENT_ENTRY.md. Do not run start/resume against the old5032ccb policy or enable a placeholder adapter.
Proposed decision text for the owner's later review (not a decision made by this file):
Adopt the exact clean published candidate named by ENTRY_PROPOSAL.json and independently resolved final evidence-envelope HEAD, together with its source/evidence/manifest/prompt hashes. Permit PHASE-10/P10-00 baseline and deletion-eligibility assessment only, with no product edits or removals. Preserve all57 contracts/34 routes, canonical Career Profile, historical CV/letter revisions, import review/legacy readers and RD21/provider protections. Stop after P10-00; require protected candidate-specific-cleanup-scope approval before P10-01. Keep optional CV AI disabled, production NO-GO, and the five source-scoped debt requests separately identified. Do not silently enable conditional advancement, later initiative implementation, main merge or deployment.
No exact unused deletion candidate is asserted. P10-00 must produce the proof or report none. Actual scope approval must name the subsequent candidate, affected callers/routes/old data, rollback and tests; this brief cannot supply that missing proof.
The platform/controller maintainer first supplies a qualified composite test adapter and owner-prepared manifest for this exact scope. It must retain the seven stage IDs/order, add the protected stop after P10-00, and use qualified report membership/runtime permissions. Only then use the existing operator terminal flow from the installed SINGLE_USER.md:
. "$HOME\.jobjakt-backlog\single-user-local\Use-JobjaktBacklog.ps1"
Jobjakt auth-status
Jobjakt status
Jobjakt dry-run
If authentication is unavailable, use Jobjakt auth yourself. If qualification expired or binding changed, use Jobjakt qualify; the observation on30October was already real-key PASS and matching until17:33UTC/18:33Paris, so do not recreate the key or repeat valid qualification just to increase evidence.
After reviewing the qualified adapter and runtime evidence, the operator may deliberately select Jobjakt enable-unattended; this requires typed confirmation and does not itself approve Phase10 or enable the roadmap. For the actual reviewed, schema-valid manifest file, use:
# Replace with the actual maintainer-qualified manifest path; none is supplied as executable policy here.
Jobjakt configure -Manifest '<actual-reviewed-qualified-manifest.json>'
Jobjakt approve
Jobjakt configure -Manifest '<same-exact-reviewed-qualified-manifest.json>'
The first configure creates a protected manifest-policy-update request and stops. approve shows its exact payload, requires a random typed challenge, Approve/Revise/Reject and concrete decision text, then uses the real owner key. The second configure adopts only the signed exact manifest. Changed policy/evidence requires a new request; do not replay an old signature.
Stop at this gate. Environment-qualified, roadmap-execution and phase10-development-entry remain independent protected requests. Only after the controller's actual eligibility checks pass and the owner signs each requested exact scope should the owner deliberately invoke start/resume. There is no safe generic “approve everything” command or activation granted by this brief. No controller command in this guide was executed by this task.