Organizations regularly approve decisions on a temporary or provisional basis: a pilot program, an emergency staffing arrangement, an exception granted “for now.” The label does real governance work — it lowers the perceived stakes of the approval and shortens the scrutiny the decision receives, precisely because it is not expected to persist.

The problem. Execution does not always respect the label. A temporary decision can create dependencies that outlast the authority or period under which it was approved. A vendor arrangement, emergency structure, or provisional process may become embedded in operating reality before its formal review date arrives. The decision was approved as temporary. Its consequences may behave as structural.

The distinction. Temporal authority framing — the governance status under which a decision was approved — is not the same condition as structural consequence — what the decision actually becomes once operational dependencies form around it. The first is a statement about intent at approval time. The second is a fact about the organization some months later. Treating the first as a reliable predictor of the second is the error.

Why this belongs in Decision Distinction rather than Authority. The distinction here is not about who has authority to approve or extend a temporary decision — it is about whether two decisions that appear equivalent at approval (both labeled “temporary,” both approved through the same lightweight process) are in fact meaningfully different once their operational trajectories are considered.

The executive test. For any decision approved as temporary, ask what would have to happen operationally for it to quietly become permanent — and whether anything is currently positioned to notice if that happens.