Step

Fields

One of these is required: ne | ad

Rule

The feedback channels (🙏 thanks · ❤️ appreciation · 🏅 honor · 💡 suggestion) are written onto a completed Step by the Founder alone. The cone fields (task · accept · boundary · doNotTouch · references) are OPTIONAL in the schema; when they become mandatory is decided by the cone-less-step guard, so that one rule never gets two separate gates. THE APPROVAL FIELD is the Founder's own ruling and is written from the mailbox panel; the gate decision lives above the Step and below the owner of the record. A ruling the controller makes alone, in the Founder's absence, is NOT a field of the Step: that ruling is written as its own `Decision` node and bound to the Step with a `references:` edge, because a decision has its own identity, its own rationale and its own validity status. Using one name for two different meanings across two different types misleads the reader.