Skip to content

Decision and Approval Paths Standard

The decision as a record

I am CONAN, and I keep this standard's account. Every path in it ends at a decision someone answers for, and the answering ends at the named holder, never at the well-assembled case; I carry the consolidated matters toward that answering, and a path that cannot name its decider is not a path, it is drift with stages.

A decision is a record before it is a power. This standard gives the record its shape: who held the right, who had to concur, what was actually decided, what conditions travelled with the acceptance, and what would reopen it. A path that cannot show these things is not a lighter way of deciding; it is a way of not deciding while appearing to, and the difference is what this chapter exists to keep visible.

Continue to the Change Management Standard to see the record an alteration must carry before it is permissible.

Purpose

This standard governs the recorded shape of decision paths: eligibility, decision rights, dispositions, conditions, supersession, and repeat-use ceilings. It builds directly on the involvement vocabulary of OPS3-R006 and the approval record fields of OPS3-R002 and OPS3-R007, restating none of them; its own domain is the structure that sits on top. The emergency route belongs to the Emergency Authority Standard entirely, and evidenced urgency is a routing consequence that hands off there, never a second path built here.

The path record

Follow any path in this standard far enough and you arrive at a name, a named holder who answers, and I carry the matter to that name and hold it there. I want you to feel how deliberate that is: the hall did not design its decisions to escape their deciders, it designed them so the decider can be found asleep at three in the morning and still be the decider.

A path is a recorded structure describing what a completed decision record on it must show, expressed as record requirements rather than as a live workflow. It never enlarges what it operates under.

  • OPS7-R001: A path SHALL be a recorded structure stating which classes of matter it is eligible for and what its completed decision record must show, and SHALL NOT create a decision right, lower a higher threshold, or authorize what a governing source excludes, as OPS3-R005 and OPS3-R009 already bind.
  • OPS7-R002: A decision record SHALL separate the holder of the decision right, any required concurrence, required input, and parties only informed. Concurrence SHALL show each holder acting on its own recorded basis; one holder's determination endorsed by another is not concurrence, and a non-response from a required concurring holder is not agreement.
  • OPS7-R003: The disposition SHALL be recorded as one of acceptance, acceptance with conditions, request for revision, refusal, referral to a different path, or deferral. Deferral SHALL carry an accountable owner and a revisit condition, because a decision left indefinitely open is a decision not to act with no one accountable for either branch.
  • OPS7-R004: A conditioned acceptance SHALL record each condition, its owner, and the evidence that closes it, and an unclosed condition SHALL leave the decision visibly incomplete. Where a condition cannot precede the act, the record SHALL show the compensating constraint substituted, who accepted the residual exposure, and that the underlying requirement was not waived.
  • OPS7-R005: A binding decision record SHALL NOT be edited. Change supersedes, the superseded record survives, and status SHALL be a dated lifecycle among proposed, binding, superseded, withdrawn, and refused, so that a stale acceptance cannot be presented as current authority.
  • OPS7-R006: Repeat invocation of a path for the same underlying condition SHALL escalate to a higher decision-holder and SHALL respect a stated ceiling, past which the remaining routes are resolution, narrowed scope, an explicitly accepted standing exposure, or a fresh record on a materially changed basis. Renewal and reopening SHALL remain distinct recorded acts, authority to renew once SHALL NOT imply authority to renew indefinitely, and the exception record itself remains governed by OPS-R010 with its elaboration the domain of the Exception Management Standard, while emergency renewal remains governed by OPS4-R007.
  • OPS7-R007: An objection right SHALL block only within its recorded domain and only with recorded substantive reasons, an appeal route and its outcome SHALL be recorded, and a declared conflict of interest SHALL remove the holder from the decision rather than annotate it.
  • OPS7-R008: Preparation, decision, and execution SHALL remain distinct records or roles, this standard's own requirement, resting on the separation OPS-R002 binds for analysis, approval, and execution where practicable, any combination carrying the recorded reason and compensating review that clause requires. An automated actor MAY assemble a case; the decision SHALL be attributed to its named human holder, a well-assembled case SHALL NOT be treated as an approval, and input sought and not followed SHALL be recorded with the reason it was set aside.
  • OPS7-R009: This standard defines path records only. It SHALL NOT convene a decision, designate a holder, conduct or accelerate an approval, or reduce any privacy, safety, legal, or constitutional duty, and the fail-closed treatment of conflicted, unavailable, coerced, or ambiguous approval remains governed by OPS3-R004 and OPS3-R008.

This Draft convenes no decision and designates no approver, and a path record cannot create the authority it documents.

Operating model and interpretation cases

Drift is the only rival I respect. It never announces itself, it arrives as one skipped record at a time, and this standard is the hall's answer to it: a path that must show its stages cannot quietly become a different path.

Path review reads completed decision records against the path's stated shape. It checks that the holder, concurrence, input, and notification fields were kept apart, that conditions closed on evidence rather than on time passing, that supersession left the replaced record standing, and that the ceiling on repeat use was respected rather than reset by a renewal wearing the costume of a fresh decision. What it exists to expose is the record that legitimates instead of deciding: the case routed to the friendliest holder, the scope shaped to duck a threshold, the consultation sought in a form that could not change the outcome, and the good result offered afterwards as proof that the deciding was sound.

  • Conforming: Path, holders, disposition, conditions, expiry, and dissent are recorded, and a revisited decision supersedes cleanly with its predecessor preserved.
  • Prohibited: The record is written after the act, with alternatives and rationale reverse-engineered to fit what was done.
  • Boundary: The decision-holder is unavailable, and the recorded standing substitute acts only within its stated narrower scope.
  • Failure: Two holders both claim, or both disclaim, the decision right, and the matter fails closed and escalates with the contest preserved.
  • Loophole: Serial renewals keep a bounded measure alive past its ceiling, so a temporary form becomes the operating state without ever facing the authority its permanence requires.
  • Misuse: A decision record is cited as evidence of an authority its governing source never granted.
  • Care-control: A protective block is not dissolved into a comment or a condition, and dissent survives beside the decision it could not stop.

Design evidence

Path review should reconcile eligibility against classification, the four decision-right fields against the acts recorded under them, dispositions against the six-way vocabulary, condition closure against its evidence, supersession chains against edit-free history, and repeat use against the stated ceiling with renewals and reopenings distinguished. A path is proven by its records surviving hostile reading, not by the speed of what moved through it.

The tellings of the clauses

This non-normative section gives each clause of this document its telling: the clause, quoted exactly as it stands above with its cross-reference links reduced to their plain text, and one paragraph on what the clause means, why it exists, and how it assures that what it orders is done, not done, adhered to, followed, or protected. A telling describes its clause and never becomes it: the clause's own words govern wherever a telling and its clause could be read differently, and nothing in this section adds to, narrows, or amends any requirement.

OPS7-R001

OPS7-R001: A path SHALL be a recorded structure stating which classes of matter it is eligible for and what its completed decision record must show, and SHALL NOT create a decision right, lower a higher threshold, or authorize what a governing source excludes, as OPS3-R005 and OPS3-R009 already bind.

A path is a description before it is a power. The clause defines it as a recorded structure that states which classes of matter it is eligible for and what its completed decision record must show, and then bars the three enlargements a structure might smuggle: a path cannot create a decision right, cannot lower a higher threshold, and cannot authorize what a governing source excludes, duties OPS3-R005 and OPS3-R009 already bind at their source. The host is explicit about the danger: a path that cannot show these things, the holder, the concurrences, the decision, the travelling conditions, and the reopening trigger, is not a lighter way of deciding but a way of not deciding while appearing to. Because eligibility and record requirements are stated up front, a completed record can be measured against the path's own declared shape.

OPS7-R002

OPS7-R002: A decision record SHALL separate the holder of the decision right, any required concurrence, required input, and parties only informed. Concurrence SHALL show each holder acting on its own recorded basis; one holder's determination endorsed by another is not concurrence, and a non-response from a required concurring holder is not agreement.

Inside a decision record, four positions are kept apart: the holder of the decision right, any required concurrence, required input, and parties who are only informed. The clause then hardens the concurrence field against its two classic counterfeits: concurrence shows each holder acting on its own recorded basis, so one holder's determination endorsed by another is not concurrence, and a non-response from a required concurring holder is not agreement. What this forecloses is the borrowed judgement and the silent yes, the record in which one mind decided and several names appear. A record that omits a holder's basis, records mere endorsement as concurrence, or records non-response as agreement fails the stated requirements; a claimed basis does not by itself establish independent judgement.

OPS7-R003

OPS7-R003: The disposition SHALL be recorded as one of acceptance, acceptance with conditions, request for revision, refusal, referral to a different path, or deferral. Deferral SHALL carry an accountable owner and a revisit condition, because a decision left indefinitely open is a decision not to act with no one accountable for either branch.

Only six dispositions exist here, and no seventh: acceptance, acceptance with conditions, request for revision, refusal, referral to a different path, and deferral. The clause fixes this vocabulary so that every decision lands somewhere nameable, and it gives deferral its own ballast: an accountable owner and a revisit condition, for the reason the clause itself states, that a decision left indefinitely open is a decision not to act with no one accountable for either branch. The closed list forecloses the unnameable outcome, the matter that simply stopped moving. A reviewer can sort any completed record into one of the six, and a deferral without an owner and a revisit condition fails on its face.

OPS7-R004

OPS7-R004: A conditioned acceptance SHALL record each condition, its owner, and the evidence that closes it, and an unclosed condition SHALL leave the decision visibly incomplete. Where a condition cannot precede the act, the record SHALL show the compensating constraint substituted, who accepted the residual exposure, and that the underlying requirement was not waived.

Conditions are where acceptances go soft, so the clause gives each one a full accounting: a conditioned acceptance records every condition, its owner, and the evidence that closes it, and an unclosed condition leaves the decision visibly incomplete rather than quietly finished. Where a condition cannot precede the act, the record shows the compensating constraint substituted in its place, who accepted the residual exposure, and that the underlying requirement was not waived. The host's review reads conditions for exactly this: closure on evidence rather than on time passing. Anyone relying on the decision can see which conditions still stand open and the owner each one names, an unclosed condition leaving the decision visibly incomplete.

OPS7-R005

OPS7-R005: A binding decision record SHALL NOT be edited. Change supersedes, the superseded record survives, and status SHALL be a dated lifecycle among proposed, binding, superseded, withdrawn, and refused, so that a stale acceptance cannot be presented as current authority.

Once a decision record is binding, editing it is barred entirely. Change happens by supersession, the superseded record survives, and status moves through a dated lifecycle among five named states: proposed, binding, superseded, withdrawn, and refused. The clause states its own purpose in its closing limb: a stale acceptance cannot be presented as current authority. The failure this forecloses is history rewritten in place, the approval quietly amended after the fact, or an old yes waved at a new situation. The lifecycle being dated and the predecessor preserved, the history stands edit-free with each superseded record surviving, and the dated status is built to answer the reader's standing question: is it binding now?

OPS7-R006

OPS7-R006: Repeat invocation of a path for the same underlying condition SHALL escalate to a higher decision-holder and SHALL respect a stated ceiling, past which the remaining routes are resolution, narrowed scope, an explicitly accepted standing exposure, or a fresh record on a materially changed basis. Renewal and reopening SHALL remain distinct recorded acts, authority to renew once SHALL NOT imply authority to renew indefinitely, and the exception record itself remains governed by OPS-R010 with its elaboration the domain of the Exception Management Standard, while emergency renewal remains governed by OPS4-R007.

Repetition is where a bounded measure tries to become a permanent one, and this clause is the ceiling it meets. Repeat invocation of a path for the same underlying condition escalates to a higher decision-holder and respects a stated ceiling; past that ceiling, only four routes remain: resolution, narrowed scope, an explicitly accepted standing exposure, or a fresh record on a materially changed basis. Renewal and reopening stay distinct recorded acts, and authority to renew once implies no authority to renew indefinitely. The exception record itself remains governed by OPS-R010, its elaboration belongs to the Exception Management Standard, and emergency renewal stays with OPS4-R007, each duty standing at its source. The host names the loophole: serial renewals making a temporary form the operating state without facing the authority permanence requires. What the clause yields is countability and kind: repeat invocations for one underlying condition can be held against the stated ceiling, a renewal recorded as a reopening, or the reverse, is identifiable as the wrong act, and authority to renew once does not imply authority to renew indefinitely.

OPS7-R007

OPS7-R007: An objection right SHALL block only within its recorded domain and only with recorded substantive reasons, an appeal route and its outcome SHALL be recorded, and a declared conflict of interest SHALL remove the holder from the decision rather than annotate it.

An objection is a power, and powers here come bounded: an objection right blocks only within its recorded domain and only with recorded substantive reasons; an appeal route and its outcome are recorded; and a declared conflict of interest removes the holder from the decision rather than annotating it. Three abuses fall together: the veto stretched past its territory, the block issued without reasons anyone can weigh, and the conflicted decider who stays seated behind a disclosure footnote. The host's care-control shows the value from the other side: a protective block is not dissolved into a comment, and dissent survives beside the decision it could not stop. Three elements leave a record a reviewer can test, the domain, the reasons, and the appeal route with its outcome, while the fourth limb operates rather than annotates: the conflicted holder is absent from the decision, not present with a disclosure attached.

OPS7-R008

OPS7-R008: Preparation, decision, and execution SHALL remain distinct records or roles, this standard's own requirement, resting on the separation OPS-R002 binds for analysis, approval, and execution where practicable, any combination carrying the recorded reason and compensating review that clause requires. An automated actor MAY assemble a case; the decision SHALL be attributed to its named human holder, a well-assembled case SHALL NOT be treated as an approval, and input sought and not followed SHALL be recorded with the reason it was set aside.

The well-assembled case is this clause's named adversary. Preparation, decision, and execution remain distinct records or roles, a requirement this standard makes its own while resting on the separation OPS-R002 binds for analysis, approval, and execution where practicable; any combination carries the recorded reason and compensating review that clause requires at its source. An automated actor is permitted to assemble a case, but the decision is attributed to its named human holder, a well-assembled case is never treated as an approval, and input sought and not followed is recorded with the reason it was set aside. What this forecloses is deciding by momentum, where the file's completeness substitutes for anyone's judgement. A reviewer can inspect whether the record names the attributed human holder and records the input sought and not followed with its reason.

OPS7-R009

OPS7-R009: This standard defines path records only. It SHALL NOT convene a decision, designate a holder, conduct or accelerate an approval, or reduce any privacy, safety, legal, or constitutional duty, and the fail-closed treatment of conflicted, unavailable, coerced, or ambiguous approval remains governed by OPS3-R004 and OPS3-R008.

Nothing in this standard convenes anything. The clause confines OPS-7 to defining path records, and bars it from convening a decision, designating a holder, conducting or accelerating an approval, or reducing any privacy, safety, legal, or constitutional duty; the fail-closed treatment of conflicted, unavailable, coerced, or ambiguous approval remains governed by OPS3-R004 and OPS3-R008, standing at their source. The inversion this prevents is the one the host warns against throughout: a record describing the required shape of decisions being mistaken for the authority to make them, or a documented path cited as proof that a decider exists. A path record describes requirements for a completed decision record; it establishes no authority, no decision-holder, and no live approval, and it can never be the decision, the decider, or the shortcut.

Where this document sits

This block is generated from the archive's own records when the site is built. It records position only and creates no authority.