# Discovery for Operational Software

How to map users, invariants, exceptions, evidence, and acceptance criteria before implementation.

Type: Guide
Reading time: 9 min

## 1. Map the real operation

Use this section to evaluate map the real operation, including operational constraints, architecture boundaries, evidence, ownership, and failure handling.

## 2. Identify invariants and exceptions

Use this section to evaluate identify invariants and exceptions, including operational constraints, architecture boundaries, evidence, ownership, and failure handling.

## 3. Define roles and evidence

Use this section to evaluate define roles and evidence, including operational constraints, architecture boundaries, evidence, ownership, and failure handling.

## 4. Turn risk into acceptance criteria

Use this section to evaluate turn risk into acceptance criteria, including operational constraints, architecture boundaries, evidence, ownership, and failure handling.

## 5. Build a phased scope

Use this section to evaluate build a phased scope, including operational constraints, architecture boundaries, evidence, ownership, and failure handling.

---
Forgestack Labs LLP · hello@forgestacklabs.com