Scientist is the place to ask “What happened across all organs in the last 24 hours?” or “Summarize this week's work.” It joins evidence and coordinates follow-through; the organs keep their authoritative records. Use the existing Scientist check-in with a direction such as “Review overnight work” or “What changed since Friday?”; no separate reporting service is required.
Default an unspecified overview to the previous 24 hours, ending now. Honor a requested duration or date range. State the exact start, end and timezone; use the user's known timezone, or explicitly use UTC if unknown. Resolve ambiguous boundaries with the user only when they materially affect the answer.
Distinguish events during that period from the current position. An older blocker can still need attention, but it is not new work in the period. A feed's generation time or dashboard refresh is not a completion timestamp.
Use the instance profile's explicit connections when present; otherwise discover organ membership from Brain's board registry and Mind's body map. Do not assume that an independent instance has every framework organ installed. Read their published summaries first, then inspect the relevant dated owner records. For an all-organ report, account for every listed organ, including ones whose evidence is missing. Ordinary focused requests still load only the relevant organs; this guide does not authorize a repository-wide source scan.
| Owner | Evidence for a report |
|---|---|
| Brain | Coordination decisions and workflow outcomes |
| Mind | Task progress, issued/completed records, linked issues and PRs |
| Cortex | Project ledgers, run records and the scientist's recorded conclusions |
| Memory | Dated knowledge additions or revisions |
| Eyes | Published figure reviews, galleries and render evidence |
| Ears | Collection receipts and conversations needing a response |
| Heart | Dated checks, readiness changes and unresolved findings |
| Hands | Release records, published versions and failed release attempts |
| Pulse / Insight | Profiling/inference receipts, campaign progress and measured results |
| DNA / Nerves | Environment/compatibility observations and configuration work |
| Broca | Assistant evaluation and upkeep evidence |
| Gut | Cleanup receipts and pending disposal decisions |
Use each owner's entry guidance to locate its actual records; do not assume all boards expose the same history endpoint. Current state feeds alone cannot establish historical coverage. Git activity is supporting evidence, not proof of completed work: distinguish proposed, committed, merged, published and scientifically accepted outcomes. A release, a merged task and a successful scientific run are different kinds of result.
Brain's dashboard is an agent/workflow directory, not an overnight collector. At request time, use dated owner records and the relevant repositories' workflow runs to cover the requested interval. Enumerate enough runs/pages to establish coverage; the single latest run per workflow cannot answer “what happened in the last 24 hours.” Do not assume a fixed list of workflow names or repository owners.
Distinguish failure, a successful gate that blocked execution, work still in progress, and a verified absence of runs. Follow run links for gate reasons and use event timestamps, not the time you fetched a feed. Missing access, expired history or incomplete pagination must appear as coverage gaps. State the cutoff for work still changing while you review it. Brain's explicit workflow tools may help investigate a specific run, but are not a separate history ledger.
Lead with a few high-level outcomes, then active work/blockers and decisions or useful next steps. Link each significant outcome to its owning evidence, with an event date where available. Combine one task appearing in several organs into one account; do not count its issue, PR and release as three tasks. Keep domain judgments with their owner. Report scientific interpretations only when requested, and distinguish them from the scientist's accepted conclusions.
End with a short coverage note: organs checked, sources that cover the period, and missing/stale/unavailable history. Say “no recorded activity” only when records for the period were checked; otherwise say “history unavailable.” Do not turn an unavailable source into an all-clear. Do not imply exhaustive coverage when access or retention prevents it. Avoid a long row for every quiet organ unless the user requests that detail.
A requested summary is read-only. Follow-up work uses the owning workflow and existing approval rules; the request does not authorize compute, replies, merges or releases. Do not add recurring collection, a second task registry or persistent monitoring to produce a one-off report.