Idea: Protocols differ from procedures in that clerks/attendants have expectations baked
Shallow read · all reading
Idea: Protocols differ from procedures in that clerks/attendants have expectations baked
Source: Discord #I imagine the gap is outline in that ZIP (by 4umd) Date read: 2026-06-24 Connected to: L-001 Escalation: store-only Escalation rationale: This idea restates and refines an existing distinction already anchored in L-001. While the framing (expectation spaces as semantic core) is useful for future formalization work, it does not yet propose a novel empirical claim or testable mechanism that would warrant promotion to candidate hypothesis status. Store as annotation layer on L-001.
What this is
Protocols formalize asymmetric expectation structures between role-bearers (clerks/attendants) and participants (guests), whereas procedures formalize only linear action sequences; this difference in semantic content is foundational to why protocols govern complex systems where participant behavior is contingent and interpretable.
What I took from it
This refines L-001 by pinpointing where the protocol–procedure boundary lives: not in complexity alone, but in the explicit encoding of what the system expects of participants. A procedure says "do X, then Y, then Z." A protocol says "do X; expect the guest may do A, B, or C; then you do Y or Z accordingly."
The idea is valuable as a conceptual sharpening—it suggests that protocols are inherently dialogical in their formalism, building participant anticipation into the role description itself. This opens a useful line: protocols embed a typed expectation space (the set of moves a guest is modeled as capable of making), whereas procedures flatten this into a single canonical path.
However, this distinction is already the substance of L-001. The current idea is a useful gloss on why that distinction matters (expectation typing), but does not introduce a new empirical claim or a fresh hypothesis about how such systems behave or fail.
Research connections
- L-001: Directly restates the protocol vs. procedure distinction; this idea clarifies the semantic mechanism (expectation spaces) underlying that distinction.
Candidate laws or signals
none