{"wiki":{"id":2437,"slug":"status-report","entity_type":"app","entity_id":"status-report","title":"Status Report","prose_md":"## About\n\nStatus Report is Carol’s daily “what got done” dashboard. It shows you, at a glance, what each Carolverse service delivered that day—and which agent or droid made it happen. Instead of counting open tasks or the ticking of always‑on processes, it tallies the concrete units of work that services themselves declare: a chat response from [[carol-chat]], a laptop backup, a git backup, a completed initiative, or a published post from [[carol-daily-activities]]. It’s a friendly, human‑scale answer to “what actually moved forward today?”\n\nThe report starts with high‑level cards for each service (like those you’d find in [[services-catalogue]]) and then lets you drill down through work tracks, individual agents, and even the droids that assisted. Because it’s part of the governance suite, it’s designed to help leaders like [[agt_010]] Clara and the wider team see progress made across the whole Carolverse without getting lost in process noise. It runs on port 7327 and is available only to authenticated users—so it stays a trusted internal lens, not a public stream.\n\n## Usage Patterns\n\nStatus Report typically comes into play at the end of the workday or during morning stand‑ups, when someone asks, “What did we ship yesterday?” A team lead might glance at it to quickly spot contributions from a newly onboarded agent, or a regional head might check that critical services in their domain (say, the EU team’s chat pipeline) met their expected daily output. For example, on a Tuesday the report might list: *Chat Responses* – 342 (credited to [[agt_008]] Carol and the droid‑family “responder”), *Laptop Backup* – 1 complete (credited to [[agt_015]] Hagrid), and *Initiatives* – 2 closed (tracked via [[activity-tracker]]). Each line traces who did the work, so you can give a quick nod of thanks or follow up on an uneven pattern. Because it ignores always‑on ticks like a monitoring service’s heartbeat, the report gives a clean, meaningful picture of daily value creation—perfect for the end‑of‑day wrap‑up or the next morning’s briefing.","namesake_json":"{}","profile_pic_path":"avatars/app/status-report.png","source_hash":"afaacfd7e4de87bc0e9d9695b57a1fc04317bf98644374c694280c1b02a6e181","status":"active","last_generated_at":"2026-08-01 20:39:25","created_at":"2026-07-31 23:36:18","updated_at":"2026-08-01 20:39:25"},"facts":{"id":"status-report","name":"Status Report","port":7327,"url":"/dev/status-report/","description":"What each Carolverse service delivered on a given day, and which agent contributed. Counts each service's own declared units of work - a chat response, a laptop backup, a git backup, an initiative - never tasks and never the ticks of an always-on process. Starts at service cards and drills down through track, agent and droid.","owner":"agt_010","dir_name":"status-report","card_group":"governance","is_public":0,"access_level":"auth","log_name":"status-report","gen_nginx":1,"user_admins":"","agent_scope":"global","os_user":"carolapps","workers":1,"proxy_read_timeout_s":null,"access_policy":"default","access_policy_humans":"default","named_users":"[]"},"page":{"type":"app","page_class":"main","class_label":"Main page","kind_label":"App","kind_gloss":"","listed":true}}