Learn

    Playbook version history

    Business rules change: thresholds get renegotiated, approvers move, a new control lands mid-quarter. Versioning the process, rather than rewriting code, is what keeps those changes safe and reviewable. In VeroTX the versioned process is called a Playbook.

    What version history means

    A versioned process is a named sequence of stages and rules that carries a version number, so any change produces a new version instead of quietly overwriting the old one. VeroTX calls that sequence a Playbook, and the process it runs a WorkStream.

    Version history matters because a record of what an agent did is only useful next to the rules that were in force when it did it. Actions are recorded in the Execution Ledger bound to the Playbook version active at runtime, so a past decision replays against the rules that produced it.

    A worked version history

    An illustrative sequence for one WorkStream. Each version shows the WorkStream it governs and the rules that version put in force.

    v9

    Spend ceiling set at 50,000

    Procurement WorkStream: Intake to purchase order. Edited by the procurement lead.

    • Standard path below the ceiling: Requests at or below 50,000 run on the standard approval path
    • Budget owner above the ceiling: Requests above 50,000 route to the budget owner before any vendor contact
    • Agents may not commit spend: Stage-scoped agents may draft and send an RFQ but not commit spend
    Open v9 in the Playbook
    v10

    Second approver required above 100,000

    Procurement WorkStream: Intake to purchase order. Edited by the controller.

    • Second named approver: Requests above 100,000 need a second named approver before the PR is created
    • Evidence recorded with the approval: The second approval is recorded with the evidence package presented at the time
    Open v10 in the Playbook
    v11

    Legal review added for first-time vendors

    Procurement WorkStream: Intake to purchase order. Edited by the procurement lead.

    • Legal review stage: A vendor with no prior record adds a legal review stage before contract signature
    • Hard stop for a person: The WorkStream pauses at that stage until a person clears it
    Open v11 in the Playbook

    How a change lands

    Who edits it

    The person who owns the process, not an engineer

    What it costs

    A config change, not a release cycle

    What breaks

    Nothing in flight. Runs finish on the version they started

    Where to next

    All Playbooks →WorkStream Playbooks →Execution Ledger →All explainers →
    Back to Learn