Put the decision in writing.

Describe the software path and the decision ahead. Prepare a brief for your team, then choose what to share in a future conversation with Atom.

.dw-BzG_editor { display: none; }

Use the blank brief.

The local editor needs JavaScript to prepare your download. You can download the blank brief and complete it in any text editor.

System or product name

A working name is enough.

Decision to make

For example: can this transaction path support the next product launch? Up to 1,000 characters.

What must keep working?

Name the behavior you cannot lose: correct balances, compatible APIs, a recovery window. Up to 1,500 characters.

Current situation

Describe the software path, who depends on it, and what prompted the decision. Up to 1,800 characters.

Constraints and dependencies

Include relevant interfaces, migration limits, access restrictions, and delivery commitments. Up to 1,800 characters.

Evidence available

List the reports, traces, tests, or architecture records you already have. Do not paste their contents. Up to 1,400 characters.

Decision timing

A target date or a dependency that sets the pace.

Engagement path

Choose the path that fits the evidence you have today.