Customer-workflow principles

  1. 01

    Source before synthesis

    A draft should show which approved knowledge supports it and where the source is silent.

  2. 02

    Review before consequence

    A person reviews work before an external send, booking or other consequential action.

  3. 03

    Permission is bounded

    Access to read, draft or act is granted for a defined workflow; it is not a universal authority.

  4. 04

    Contain the failure

    Separate intake, knowledge, review and action so one broken stage does not silently corrupt the rest.

  5. 05

    Record the decision

    Keep the source, edit, approval and outcome so later work can learn from an inspectable record.

  6. 06

    Simulation is labeled

    A demonstration may model an action, but it must not imply that a real message was sent or a booking was made.

Founder practice

Building

Use branches, review and tests. Prefer small stages with explicit inputs and outputs. Stop and reconsider repeated failure.

Trading and research

Use a framework as a diagnostic, not a guarantee. Bias labels describe analytical direction, not predictions or advice.

A manual-review example

An inquiry draft can cite a service note and recommend a follow-up question. The owner can edit or reject it. Until the owner approves and a sending connection exists, the result remains a reviewed draft.