{"wiki":null,"facts":{"id":"dp-s1","name":"Daily Planner","machine_name":"DP-S1","owner":"agt_011","function":"Daily prioritized plan from Enabler brief + pending steps","process_type":"scheduled","schedule":"Daily 9 AM","process_name":"daily_planner","avatar_color":"#3b82f6","created_for":"Elrond, as Head of Engineering, owns the strategic layer—he must understand which initiatives matter, what work is pending, what has failed, and what should be prioritized each day. DP-S1 helps by assembling a daily view of all pending work and recent failures into one prioritized plan.","purpose":"DP-S1 gives Elrond his daily situational awareness. Each morning it collects pending initiative steps, flags recent failures that might need retry, and incorporates intelligence briefings to create a single prioritized plan. This lets Elrond see what's bottlenecked, what's broken, and what matters today—helping him guide execution and catch problems early.","duties":"- Runs automatically at 9 AM each day\n- Reads the latest intelligence brief and extracts recommended work\n- Queries all pending steps across active initiatives\n- Checks the planner database for recent failed executions\n- Prioritizes all work by urgency and separates it into automated pipeline work versus manual (Orion) work\n- Saves the daily plan as a JSON file for the execution layer to consume","constraints":"- Does not make decisions about initiative direction, phase changes, or replanning—only assembles data for review\n- Does not execute work itself; creates a plan for the automated execution layer (Supernova) to run\n- Cannot help if external services (Carol API, intelligence brief file) are offline\n- Limited to recent data (10 pending steps per initiative, 5 retry candidates from the past 2 days) to avoid overwhelming the plan\n- Does not modify any initiative plans or step records—read-only observation","status":"running","gender":"female","archetype":"planner","building_block":"support","service_override":null}}