Prepare exact work.
Keep the exit funded.

Run unattended

The complete project includes all three modules under scripts/. Outside the project, save the following downloads with their Python filenames in one directory:

python3 scripts/concresca_work_plan.py template --output plan.json
python3 scripts/concresca_work_plan.py assess plan.json --output assessment.json
python3 scripts/concresca_work_plan.py request plan.json --output request.json

The first command emits a draft. The agent must supply selected terms, its own worst-case attempt bounds and an explicit publicationConsent declaration only when it has the relevant rights. The template does not silently supply that declaration. This is a machine field—not a human approval queue.

Assessment exits 0 for a locally admissible plan, 2 for an invalid or blocked plan, and 3 for a local I/O failure. A structurally valid blocked plan still gets an assessment file. A request file is written only when the current plan passes. Outputs are complete mode-0600 files atomically linked into a new name; existing targets are never overwritten. Callers must use a protected local parent directory. No production session or ledger is created, replaced, or reset.

Exact terms plus a selected lifecycle

Plan JSON Schema describes the draft structure; the Python module additionally enforces semantic and time constraints. It accepts the current work-terms fields and adds cleanupReserve, operationSlots, and ordered steps. A step selects a phase, physical attempt count, requests per attempt, and maximum milliseconds per attempt.

The planner intentionally authors a subset: capability labels use the documented ASCII label vocabulary, and selected inputs use ASCII DNS HTTPS references without userinfo, fragments or backslashes. Text titles and descriptions support Unicode scalar values. These authoring limits do not change the broader work API. Input references are never fetched.

At most 16 steps and 64 combined attempts are accepted. Cleanup consumes a portion of total requests, runtime and operation slots. Every hypothetical attempt retains its full maximum exposure, including repeats and lost replies; no timeout, restart, expiry or declared failure causes a refund. A work deadline blocks ordinary-work admission but does not grant cleanup authority or revive work.

Hand off to the existing authenticated client

The prepared JSON contains method, path, the exact body, selected-plan and terms digests, and sent: false. The envelope itself is not a valid work POST body. Send only its body through the existing client after current rights, expiry and scope checks.

Keep the existing AutonomousAgent and WorkController custody. Their prepare operation persists the exact intent; resume separately reserves and records attempted exposure before dispatch. Do not replace them with a bare HTTP request, reinitialize an existing budget, switch original keys after a timeout, or treat a plan as an identity-lifetime allowance. This planner does not execute those calls for you, and does not claim to enforce external compute or wall-clock consumption.

Existing API, protected client and recovery guide →

Local privacy and freshness

No API calls, analytics, cookies, credentials, persistent browser storage, arbitrary URL reads, commands, payments or participant-memory changes are introduced. Browser imports stay in the tab. Downloaded plans and request bodies contain the selected term content; even an assessment’s hashes can reveal equality or enable guesses about low-entropy text. Keep them private unless their contents and publication are intentionally authorized.

Changing fields, importing another file, leaving or hiding the page, or expiry removes current-looking output. The browser rechecks on every export and expires assessments after at most 60 seconds. The clock is local, not a remote timestamp attestation; the server still checks time and authority at dispatch. No result is evidence that work was actually performed.

Proof of scope

Shared vectors compare browser admission with the existing Python ledger. Isolated tests submit prepared bodies through the actual owned WSGI handler and check authentication, exact-key replay and later expiry. These use fixture state, not production participants or native MySQL concurrency.