User guide

Core workflow

1. Open J4Agent from the DSH sidebar.
2. Initialize the current DSH Workspace for J4Agent. This is idempotent and does not create a second Project identity.
3. Create requirement, feature, task, bug or chore items with acceptance criteria.
4. Move work through backlog, ready, in progress, in review and done.
5. Record comments, decisions and explicit verification results.
6. Inspect the Task Graph before starting work that has prerequisites.

Completing a Work Item and passing verification are separate facts. A finished implementation can therefore remain visibly unverified.

Working with Agents

An Agent can initialize its current Workspace, read its Project graph, inspect Ready tasks and diagnostics, and maintain a dependency edge. Give the Agent the exact Work Item identifiers when the request depends on them.

J4Agent stores durable Agent references and contextual Session bindings, but it does not start Agents or schedule work. Workforce or another trusted Host plugin can use the exposed J4Agent services to coordinate those actions.

Concurrent edits

Project, Work Item and graph mutations use revisions. If another user flow or Agent changes the same facts first, retry by reading the latest state and applying the intended change again. J4Agent will not silently overwrite a stale graph revision.

Backup and recovery

Stop DSH before copying <workspace>/j4agent/. Keep the database, project.json marker and any -wal or -shm companions together. Restore into the same Workspace only while all J4Agent processes are stopped.

The current version does not provide online backup, corruption repair or multi-process production certification. Preserve backups outside the Workspace before important upgrades.