USR369 asked to save a stain/odor-removal recipe (peroxide/dish-soap/baking-soda, small-batch, for black-light-detected cat vomit residue soap-and-water couldn't clear) for future reference, and asked whether a new sub-decade (e.g. 56) should be made for household items. TASKGATE (system=50, task=save a household cleaning recipe to a reference page for future use) returned matched:false -- no existing SOP covered this. Wrote SOP-HOUSEHOLD-REFERENCE.md (systems/governance/), added to SOP-INDEX.md v2.14, broadcast id 123 (verified present via get_broadcasts unread=1 per D671). Recommended AGAINST a new decade code -- flagged as an architecture decision that routes through Master[10]/USR369 per RULES-REG (Architecture decisions -> Master scopes first; Never self-assign architecture changes), not something Daily decides solo -- and proposed instead a standing reference page living inside Daily[50]'s own jurisdiction, growing additively as new household items come up. Ran build.php (system=50, scope=all) for current standards/colors/template -- returned dark theme (--bg #000000 etc, Inter+JetBrains Mono, 12px floor) rather than the older purple/orange/JetBrains-Mono quick reference in ORIENT-REG.md, built from build.php's live output per rule (not memory). Satisfied build.php's ux_search_gate (web-fetch.php action=search, UX/readability query) before building HTML, confirmed via ux_search_done=1 re-call. Built frontend/50-Daily/apps/household/index.html v1.0 -- single reference page, one card per household item, first card is the stain/odor recipe with ingredients/directions/note. Updated page-inventory.html (n:193, status DONE, url, updated date, D361) and DEFAULTS-REG.md's [50] Daily apps entry (flagged for Builder[20] to confirm on next pass, since DEFAULTS-REG is Builder-maintained). Backed up the new page via BACKUP.php file-mode (system=50) -- CURRENT copy confirmed at backups/50-daily/html/.