veripath/docs/templates/workflows-template.md

Workflows – [Client Name]

Status: Draft / Human Review / Locked
Last Updated: YYYY-MM-DD
Reviewed by:
Source Requirements: Link to locked Requirements document

Purpose

Define the operational sequences that fulfill each accepted requirement.
Still no agents or tools — only human-and-system steps, decision points, frequency, and data flows.
Every workflow must stay inside the pricing band the client approved.

Workflows

Workflow ID: W-001

• Linked Requirement ID: R-00X
• Pricing Band: A / B / C
• Trigger Condition: (what starts this workflow)
• Step Sequence:
  1. Agent detects signal and drafts alert
  2. Human reviews draft
  3. Human approves / rejects / requests revision
  4. Action follows (or is deferred)
• Data Dependencies: (what source it reads, what artifact it writes)
• Failure Path: (what happens if data is stale or signal is ambiguous)
• Cadence: Continuous / Daily / Weekly / Event-triggered
• Speculative? Yes / No
• Human Decision: Accepted / Modified / Rejected / Deferred

Workflow ID: W-002

• Linked Requirement ID:
• Pricing Band: A / B / C
• Trigger Condition:
• Step Sequence: 1. 2. 3. 4.
• Data Dependencies:
• Failure Path:
• Cadence:
• Speculative? Yes / No
• Human Decision: Accepted / Modified / Rejected / Deferred

(Add additional Workflow ID blocks as needed)

Summary

• Total workflows drafted:
• Accepted:
• Modified:
• Rejected / Deferred:
• Speculative:

Human Review Gate

• Every workflow is linked to an accepted Requirement ID
• Every workflow stays within the client’s approved pricing band
• Draft → human review → lock gate is explicit in the step sequence
• Cadence has been checked against the client’s real operating hours
• Failure paths are defined
• Human has recorded a decision on each workflow

Once this gate is signed off, the Workflows document is Locked and Layer 6 (Agent Build & Test) may begin.

Reviewer sign-off: _________________ Date: _________