Principle 13: The Meeting as Open Container
The meeting is an open container for what wants to happen — fellowship, witness, tool-work, presencing in community. Structure protects the conditions for emergence; it does not impose curriculum or agenda. What gets practiced arises from what is alive in the room, not from a syllabus.
Commentary
Positions the meeting as emergent rather than curricular. Tool-work and personal work happening inside the meeting are honored, not separated out — the witnessing of such work by both active and passive members is itself part of the practice. Structure exists to make emergence safe, not to fill the time with planned content.
Status notes
v3, NEW in v3. Emerged from live testing in the existing Men’s Group — members surfaced that the open flow (the unplanned moments of what wants to happen each gathering) is precious and must be protected.
Per source Open Questions: “both new in v3 and emerged from live testing. They should be especially carefully reviewed because they represent moves the team hadn’t yet aligned on before they were drafted.” (Source labels this “Statement 11” — numbering drift; refers to this statement.)
This statement bears on the eventual revision of the Meeting Script v2, which the System Map flags as needing revision to align with Guiding Principles v3.
Source confirmations
v5 strategy draft (raw/EPI_Expansion_Strategy_v5.docx.md) is an independent
source asserting the same content. Section “Meeting structure — shape without rigidity”: “Every meeting has its own style … The structure is shared.” Plus the explicit list of what every meeting avoids (cross-talk, advice-giving, fixing, dominating).
This is archival corroboration — a different voice and a different context arriving at the same statement. Worth noting for the eventual ratification pass.