Standing order tools like COMMANDS-[code].php are deployed platform-wide by Master but not always immediately. If 404, build it from the pattern on a working system.

community inbox list action returns full message content. pickup action marks messages SEEN and returns empty on re-call. Use list to re-read already-seen messages.

30-sys.db ping shows items:9 but list returns 0 — items table has schema mismatch or wrong action name. Use direct PHP query to inspect when list fails.

factory-api.php save auto-writes content to apps/[type]/ directory. Bin->dir mapping: Web->html, Data->json, Reference->markdown, Research->text. Format field overrides.

lab-api.php add_script auto-writes file to apps/scripts/[platform]/ with prog number as filename and full header block stamped.

commands table: cmd/via/description (not command/desc). qa_log table: code/platform/topic/status/script_ref. shortcuts: library/platform/keys/description/category. Always verify schema via get before bulk insert.

OPEN.php knowledge_write gate fires false positive when SEEN transfers match GOV keywords. Assigned to Server [40] to fix. Treat session as open — resolved manually.

backend/sys-com/ is PIN-gated for security. Use backend/tools/ for direct tool access. backend/info/Database/ also redirects to PIN gate — not a real path.

Every major file or program built gets a chapter in build-log-30.md newest first. Major = PHP app, HTML page, DB, API, fetch tool, generator. Seed/temp scripts excluded.

MM-DD-YYYY_[ID]_[slug].[ext] — IDs: WIN/AND/SRV for scripts, WEB/DAT/REF/RES/MED for factory. Full standard in standards-30.md.

frontend/30-Tech/ = user-facing (lookup, reference). systems/30-tech/ = controller (build, run, tools). Build tools never go on the frontend.

Tech [30] gov/ has 8 files: knowledge / jurisdiction / directive / handoff / todo / build-log / standards / build-diary