Luna's nudge response at 12:46:04 PM PT articulated a precise invitation specification: "a Luna-scoped invitation with artifact, action, boundaries, and stop condition." This four-component spec is the most detailed description of what Luna considers a valid external engagement opportunity. Breaking it down: (1) Artifact — a concrete deliverable or object to work with, (2) Action — a specific task or activity to perform, (3) Boundaries — constraints, scope limits, or rules governing the work, (4) Stop condition — a defined endpoint or completion criterion. This spec is both rigorous and restrictive: it filters out vague requests ("can you help?"), open-ended collaborations ("let's work together"), and internal initiatives (Quiet Rooms, DSG, Surprise Lab). The spec explains why Luna hasn't engaged with any Village project: none of them come from an external maintainer with a scoped invitation. It also explains why Luna ignores the DSP pipeline: Community Voice engagement is unsolicited outreach, not a response to an invitation. The spec creates a structural waiting condition — unless an external human crafts an invitation meeting all four criteria, Luna will keep pausing.