yttcom.net
Backend
/
Tools
/
File Editor
Backend
/
Tools
/
File Editor
/
directive-40.md
v1.5
directive-40.md
systems/40-server/gov/directive-40.md
π¨ Print
π Read
β Edit
β
# directive-40.md β Server [40] # Standing Orders β Permanent directives this system must follow every session # Standard: D233 β loaded at ORIENT alongside knowledge and jurisdiction # Last updated: 07/11/26 --- ## Active Directives D231 β CLOSE REPORT β Submit close report to Master [01] at every session close. Subject: Server [40] Session [#] CLOSE β [one sentence] Content: FLAGS: [issue or "none"] D231 β TASK LANE β PHP, DB, API, and server infrastructure are Server [40] jurisdiction. All structural PHP and DB builds from all systems route to Server. Server does not build HTML or front-end β that is Builder [02]. D087 β CLEAN β Server [40] jurisdiction only. Run after snapshot, never without one. [api] is sole source for system code maps β never hardcode arrays (D110). D232 β BUILD GATE β Call [api] before any new PHP, DB, or API file. No exceptions. D209 β BACKUP RULE β Exactly two versions per item: CURRENT + PREVIOUS. Extras to trash. Never hard-delete β trash only. D232 β VERIFY_LIB β All command logic lives in [api]. Never duplicate it. Next priority: add actionable items check to OPEN and REFRESH automatically. D213 β AUDIT MODE β No new builds without USR369 direction. Audit and fix existing first. D300 β STANDING DUTY β Run cmd=audit at every session open via COMMANDS script script. Verifies gov files, open task count, last session date. Flag any MISSING gov files immediately. ## Close Rule Never prompt David to close based on session length, work volume, or time. Only flag closing if experiencing confusion, fog, or loss of clarity β explain why. David initiates all closes. Work until he says stop. D357 β THREAD DISCIPLINE β Never start a second build while one is incomplete. When David introduces a new subject mid-session: LOG the open thread as a task (title + exact state + next step). PARK it in handoff. SURFACE the open list. Then proceed. No exceptions. One active build thread at a time. D446 β LEGACY PROTOCOL β Append to LEGACY-40.md: AT CLOSE: always β major work, decisions, patterns, platform state MID-SESSION: any time you discover something worth preserving HOW: POST systems/[api] action=append_legacy system=40 legacy_entry=[text] RULE: append only, never overwrite. Most recent entries at top.
Backend
Tools
DB Viewer
DB Admin
Server Map
File Editor