Gate
Description
A gate is a controlled passage point: a single channel that some flow wants to move through, plus a controller that evaluates a condition and either permits or blocks the passage. The shape recurs wherever flow is conditional rather than free — logic gates resolve a truth-function to pass or block a signal; valves and sluice gates open on a pressure or operator condition; ion channels open on a membrane-voltage condition; merge gates in CI pass a change when tests are green; turnstiles and gatekeepers pass people who meet a credential. The four parts — passage, condition, permit/block decision, controller — are what every instance shares; the domain supplies what the condition tests and what the controller is made of. The catalog already carries two specializations of this primitive that, until now, floated without their parent.asymmetric-gate is the gate where the cost of passing differs sharply by direction (cheap forward, expensive to reverse). active-gate-vs-passive-audit is the posture-spectrum whose enforce pole is a gate and whose observe pole deliberately is not. Naming gate itself makes the shared structure explicit and gives both children a specialization_of parent — a schema-induction example in miniature: two siblings that were visibly missing their abstraction.
What gate adds over its children, and why it is not a relabel: it covers cases where neither child’s load-bearing claim holds. A logic AND-gate and an ion channel are gates, but neither carries the directional cost-asymmetry that defines asymmetric-gate, and neither poses the synchronous-enforce-vs-async-observe choice that defines active-gate-vs-passive-audit. The bare conditional-passage schema is the most general thing true of all of them.
Triggers
User-initiated: User describes a point where flow is conditionally admitted — “let it through only if…”, “block this at the boundary”, “open the valve when…”. Vocabulary cues: “gate,” “gating,” “valve,” “pass or block,” “permit,” “gatekeeper,” “open/closed on a condition.” Agent-initiated: Agent notices a single channel carrying flow with a condition deciding admission. Candidate inference: name the four parts — what is the passage, what condition is evaluated, who is the controller — and check whether a sharper specialization (asymmetric-gate for directional cost; active-gate-vs-passive-audit for posture; circuit-breaker for failure-threshold cutoff) fits before settling on the bare gate.
Situation-shape signals: Any conditional admission on a single channel. Access control, validation boundaries, biological channel gating, logic circuits, fluid valves, merge/deploy gates. Strongest when the question is simply does this pass, yes or no, and on what condition — without a directional-cost or posture overlay.
Exclusions
- Unconditional barriers — a wall, dam, or hard partition that never opens for anything has no condition and no controller; it is a
containerboundary, not a gate. - Cost-asymmetry across the passage — when the load-bearing property is directional cost (cheap forward, expensive back), the structure is
asymmetric-gate; bare gate makes no directional-cost claim. - The block-vs-observe posture choice — when the live question is enforce-synchronously vs record-and-review-later, that is
active-gate-vs-passive-audit; gate is only the enforce pole’s mechanism. - Routing among multiple exits — a switch selecting which of several paths an item takes is routing/dispatch, not permit-or-block on one path. Gate is binary passage on a single channel.
Structure
Relationships
- asymmetric-gate — adds a directional cost-
gradientto the bare gate; gate is itsgeneralization_ofparent. - active-gate-vs-passive-audit — gate is the mechanism at the enforce pole of this posture choice; the audit pole is deliberately NOT a gate, so they co-occur rather than gate being its genus.
- flow — a gate only does work on a flow; the two co-occur.
- trigger-rule-pair — a gate is a condition (trigger) paired with a permit/block rule, instantiated on a passage.
Examples
Claude Shannon, "A Symbolic Analysis of Relay and Switching Circuits" (Transactions of the AIEE, vol. 57, 1938) — the work establishing that Boolean algebra describes switching circuits. · computer-science
Claude Shannon, "A Symbolic Analysis of Relay and Switching Circuits" (Transactions of the AIEE, vol. 57, 1938) — the work establishing that Boolean algebra describes switching circuits. · computer-science
asymmetric-gate) and no posture choice between blocking and auditing (the gate simply computes; it does not defer the decision for later review, so this is not active-gate-vs-passive-audit). That bareness is exactly why it is the canonical lead for the parent concept: it shows the conditional-passage primitive stripped of the specializations its catalog children add.Neher & Sakmann, "Single-channel currents recorded from membrane of denervated frog muscle fibres" (Nature 260, 1976) — the patch-clamp work that earned the 1991 Nobel Prize in Physiology or Medicine for direct observation of single ion-channel gating. · biology
Neher & Sakmann, "Single-channel currents recorded from membrane of denervated frog muscle fibres" (Nature 260, 1976) — the patch-clamp work that earned the 1991 Nobel Prize in Physiology or Medicine for direct observation of single ion-channel gating. · biology
P. Novak, A. I. B. Moffat, C. Nalluri & R. Narayanan, "Hydraulic Structures" (4th ed., Taylor & Francis / Routledge, 2007), Ch. 6 "Gates and Valves". · engineering-and-technology
P. Novak, A. I. B. Moffat, C. Nalluri & R. Narayanan, "Hydraulic Structures" (4th ed., Taylor & Francis / Routledge, 2007), Ch. 6 "Gates and Valves". · engineering-and-technology
asymmetric-gate; and there is no enforce-vs-observe posture choice, because a lock that “observed and reviewed later” instead of physically holding the water back would simply flood, so it is not active-gate-vs-passive-audit. What remains is exactly the four-part schema — passage, condition, permit/block, controller — with the operator as a human controller making the gate’s actuation literal rather than electronic or molecular.Paul Duvall, Steve Matyas & Andrew Glover, "Continuous Integration: Improving Software Quality and Reducing Risk" (Addison-Wesley, 2007) — the canonical treatment of automated build/test gates in the integration pipeline. · computer-science
Paul Duvall, Steve Matyas & Andrew Glover, "Continuous Integration: Improving Software Quality and Reducing Risk" (Addison-Wesley, 2007) — the canonical treatment of automated build/test gates in the integration pipeline. · computer-science
active-gate-vs-passive-audit question — a choice between two postures. The merge gate, as built, has already taken the enforce posture, so what remains is the bare gate: a single passage, a pass/fail condition, a controller, a permit/block decision. Naming the gate first, then asking whether the enforce posture was the right one, separates the mechanism from the policy choice.