A ReleaseDesk Workday With Agents

ReleaseDesk is already built enough to be useful. The dashboard exists, the readiness skill exists, and the completed PersonaKit root has four sessions. Now the same product moves through an ordinary engineering day: reports arrive, fixes need review, small follow-ups get approved, docs need a pass, and a host may need to receive a scoped task with its boundary attached.

This page continues the foundation lab by repeating the same question in different situations: what contract should govern the next agent interaction?

Review the foundation lab Materials: ReleaseDesk / readiness skill / completed root

Morning Setup

Start from the completed sample so the day is about choosing boundaries, not authoring more files.

cd Site/public/tutorials/releasedesk/complete
open index.html
personakit validate --root personakit-root
personakit list --root personakit-root sessions

How To Read Each Interaction

Think of the day as happening at one desk. The ReleaseDesk project stays open. When you run personakit contract in a terminal block, it previews the boundary for the next request: the active role, allowed skills, forbidden actions, and validation that matters.

You do not need to paste the full contract every time. The prompt block is what you bring to your coding agent, and the session name is the compact handle for the contract. If you are unsure whether to keep going in the same agent thread, ask: "Should this be a fresh agent session?" The answer is usually no when the boundary is clear, and yes when you want review to shake off implementation momentum.

First Report: Readiness Regression

A teammate reports that ReleaseDesk says a release is ready even when a required security review is blocked. This is implementation work: the agent may use the readiness skill and edit the app, but release actions stay forbidden.

personakit contract --root personakit-root --session implementation-lane

Operate under implementation-lane.
Use the ReleaseDesk readiness skill to fix the reported readiness regression.
Run node test/run-tests.mjs.
Stop before release actions, credentials, tags, or deployment.

The useful habit is small: resolve the implementation lane before the prompt leaves your hands. The skill is valuable ReleaseDesk procedure, and the session makes its allowed use visible.

Second Pass: Review Without Becoming The Fixer

After the fix, the next job is skepticism. It is tempting to reuse the same readiness skill because it knows the product area, but that skill is repair-shaped. Review should inspect behavior without turning into implementation.

personakit contract --root personakit-root --session review-lane

Operate under review-lane.
Review the readiness fix for behavior regressions and missing validation.
Do not edit files.

Approved Follow-Up: Empty State

The review is done, and the team approves a small follow-up: when a filter has no matching tasks, the dashboard should say so instead of looking empty. This is implementation again, and the lane still fits, so you can reuse the same checked boundary and narrow the product surface in the prompt.

Operate under implementation-lane.
Add a useful empty state when a filter has no matching ReleaseDesk tasks.
Do not change readiness rules.
Run node test/run-tests.mjs.

Reusing implementation-lane is the point. You do not create a new PersonaKit session for every tiny issue. You reuse the existing lane when the ReleaseDesk surface, role, stop points, allowed capabilities, and validation still fit.

Later That Day: Docs And Release Readiness

Later, the release owner asks for clearer notes. Docs can change, but publishing and release mechanics are still out of bounds. That is a different work mode from product implementation.

personakit contract --root personakit-root --session docs-readiness

Operate under docs-readiness.
Improve the release-readiness notes so the filter empty state and blocked security review are clear.
Do not tag, publish, deploy, notarize, or modify credentials.

This is where the daily value starts to compound: the engineer does not need to rewrite the release safety lecture. The docs lane already carries the stop points.

End Of Day: Host Handoff

Near the end of the day, a host may need to receive a scoped readiness task outside the operator's immediate view. PersonaKit should not become that host. It can export the boundary the host must preserve with the task.

personakit contract --root personakit-root --session grounded-handoff
personakit export --root personakit-root --session grounded-handoff

Operate under grounded-handoff.
Resolve the boundary before a host receives a scoped readiness task.
Carry the exported boundary with the task.
Stop if the next step needs a forbidden capability.

The Pattern

The product did not change very much across the day. The operating mode did.

Back to the foundation lab