Running an Execution¶

Once you have a procedure template, you can execute it in Procnote.

Starting an Execution¶

1. Launch Procnote with a workspace directory:

procnote /path/to/my-workspace

If omitted, Procnote uses the current working directory.

1. The home screen lists all procedure templates found in the workspace. Click on a template to view its details.
2. Click Start Execution to begin.

Procnote creates an execution directory under .executions/ with:

• events.jsonl -- The append-only event log
• template.md -- A snapshot of the template at the time of execution

Working Through Steps¶

Each step in the procedure is displayed as a card. To work through a step:

1. Start the step -- Click to mark it as active.
2. Complete checklist items -- Toggle checkboxes as you verify each condition.
3. Record inputs -- Enter measurements, select options, or attach files.
4. Add notes -- Attach freeform notes to any step or to the execution as a whole.
5. Complete the step -- Mark it as done, or skip it with a reason.

Adding Steps During Execution¶

You can add new steps dynamically during an execution using the + Add Step button in the toolbar. The new step is inserted after the currently selected step (or at the end).

Completing or Aborting¶

When all steps are done:

• Click Complete and choose Pass or Fail to finish the execution.
• Click Abort to stop early with a reason.

Reverting Actions¶

Procnote supports reverting previous actions. In the event history panel:

1. Find the event you want to undo.
2. Click the Revert button.
3. Provide a reason for the revert.

The original event is not deleted. Instead, an EventReverted marker is appended to the log, preserving the full audit trail. The execution state is rebuilt by replaying only non-reverted events.

Structural events like ExecutionStarted and StepAdded cannot be reverted. Data capture events (checkboxes, inputs, notes) and completion events can be reverted.

Reviewing Past Executions¶

The home screen shows recent executions with their status (active, pass, fail, aborted). Click on any execution to view its full event history and recorded data.

Storage Layout¶

Each execution is stored in its own directory:

my-workspace/
└── my-procedure/
    ├── template.md
    └── .executions/
        └── 20260402T033055-edb182e8/
            ├── events.jsonl
            ├── template.md
            └── attachments/
                └── a1b2c3d-report.pdf

The events.jsonl file is the single source of truth. It is append-only and never modified after creation.