lumuzhagun: an indexed protocol for structured negotiation dialogue

lumuzhagun provides a descriptive and neutral index of protocol elements used to structure negotiation sessions. The site documents the metadata, sequential controls, and referential anchors that support continuity across distinct discussion events. Content is explanatory and analytic rather than prescriptive; entries describe how sessions may be segmented, how boundaries are recorded, and how references between sessions are maintained for coherence and traceability.

View protocol layout Explore session structure

Protocol index

The following indexed entries describe discrete protocol components used in negotiation sessions. Each entry outlines intent, structure, and example markers for recording transitions and references. Language is neutral; entries do not prescribe outcomes or offer directives for decision-making beyond structural documentation.

Session framing

Session framing documents the contextual parameters established at the outset of a negotiation conversation. A frame records the identified participants, declared scope, temporal bounds, and the communicative protocols that participants agree to follow for that particular session. Framing entries include a timestamped header, participant roles and affiliations where relevant, and a concise statement of scope that delineates which topics fall within the session perimeter and which are deferred. The framing header also notes any preconditions for participation, such as reference documents or prior-session anchors, and records explicit statements that affect how material is logged or referenced. Proper framing improves traceability by capturing the state of the dialogue and the constraints under which subsequent statements are evaluated. Entries are structured to support indexing, so individual frames can be cross-referenced across later session records.

Boundary setting

Boundary setting describes how participants delimit permissible topics, confidentiality constraints, and permitted forms of reference during an exchange. A boundary entry enumerates prohibitions and allowances in precise language, for example indicating whether specific documents may be cited verbatim, whether portions of the record are redacted, and how external references are to be cited. Boundary protocols also define procedural limits on interruptions, the use of off-record commentary, and rules for handover between subgroups within the conversation. Boundary records are encoded for clarity: each rule is assigned a short identifier, a natural-language explanation, and a coded severity or scope descriptor that clarifies applicability across different session contexts. Recording boundaries ensures the reproducibility of moderation and facilitates automated checks for consistency when assembling aggregated records.

Exchange sequence

The exchange sequence entry defines the ordered steps by which contributions are made and recorded within a session. Sequences formalize turn-taking, proposal presentation, reaction intervals, and the structural transitions between agenda items. Typical entries specify state transitions such as: opening statement, clarification phase, proposal articulation, structured response window, and closure. Each step is described with its expected inputs, explicit markers that indicate the transition to the next step, and optional signals for pausing or invoking an off-ramp. Sequences may include parallel lanes for subcommittees or breakout threads, with reference tokens that map lane events back to the parent session. The documentation format captures both the nominal sequence and exceptions, thereby enabling clear assembly of a session transcript that preserves temporal ordering and contextual dependencies.

Clarification markers

Clarification markers are standardized annotations used to capture requests for explanation and the resolution of ambiguity during exchanges. A marker entry specifies the token used to request clarification, the expected response window, and how clarified content is appended to the record. Markers may carry metadata indicating whether a clarification is technical, definitional, or procedural. The entry also outlines how to handle chained clarifications where a response itself requires further delineation, and how to link clarifications to the original utterance to preserve context. By standardizing markers, records retain a searchable mapping between initial statements and the clarifying sequence, enabling later readers to reconstruct the interpretative path taken by participants and the decisions that followed from clarified content.

Record references

Record references define the persistent identifiers and citation conventions used to link items inside and across session records. Each reference entry outlines identifier schema, versioning rules, and the minimal metadata required for unambiguous retrieval. Conventions cover internal citations (pointing to prior session fragments), external sources (documents or datasets), and derived artifacts (summaries or annotated transcripts). Record references also describe permitted transformations such as redaction or excerpting, and specify how transformed artifacts retain provenance metadata. The entry emphasizes reproducible linkage: each referenced item includes origin, authoring context, and a timestamped anchor so that subsequent sessions can locate the cited material and evaluate its applicability with respect to the current session frame. This indexing supports continuity across sequences of conversations while preserving source fidelity.

Navigating the index

Entries in the index are organized for modular access. Each module corresponds to a protocol component and includes fields for intent, structure, markers, and examples of record encodings. Cross-references link related modules so users can follow topic transitions and identify how a local change in one protocol component affects adjacent entries. The site provides a consistent visual language for entries: framed cards, labeled markers, and referential tokens. The design supports clear reading on mobile and desktop, and all entries include persistent links to allow navigation between frames, boundaries, sequences, clarifications, and references. For a structured layout of the entire protocol, select the full layout view linked above.