Hedy keeps an activity ledger all week — reviews shipped, questions answered, tasks closed, hours saved — then compiles the report nobody had to write. Each line links to the underlying activity records.
Hedy is a private, self-hosted AI employee. For weekly reports, it keeps a running activity ledger all week from your Lark/Slack, tickets, and repos, then turns one query into a finished report where every line cites its exact source. Unlike cloud AI seats that only summarize a chat thread, Hedy runs on your own Docker/K8s infrastructure, retrieves under the asker's ACL, and passes an evidence gate that quotes sources verbatim.
Last updated: 20 July 2026
Every deliverable is logged as it happens with links and cost. The report is a query, not a reconstruction.
A weekly rollup with the interesting deltas highlighted — in prose a human enjoys.
To your document space and the right group, on schedule.
Each line links to the underlying activity records.
Most AI report tools start from a blank chat on Friday and reconstruct the week from memory. Hedy works the other way. It maintains an append-only activity ledger through the week, logging events as they happen across your connected systems. Lark is a first-class source alongside Slack. When you ask for the weekly report, Hedy is not guessing from a scrollback window. It is querying a ledger it already wrote, so the report reflects the full week, not the last thread that happened to stay in context.
One query orchestrates the report. You ask once, and Hedy composes sections, groups work by team or project, and drafts the narrative. This is the one顶一队 idea in practice: instead of adding an AI seat to each person's chat, a single Hedy produces the output a reporting team used to assemble by hand. The report is a work product, not a meeting recap. It is built to be read by whoever asked, filtered to what that person is allowed to see.
Every line is traceable. Hedy's evidence gate requires the answer to quote its sources verbatim, so each claim in the report links back to the ticket, message, or commit it came from. If a fact has no source in the ledger, it does not enter the report. Retrieval is ACL-scoped by the asker, so a manager's report and an IC's report drawn from the same ledger can legitimately differ in what they surface. Nothing leaks past the permission boundary just because it sits in the ledger.
Because Hedy is self-hosted, none of this leaves your infrastructure. You bring your own model key, including local vLLM or Ollama, so report content is never sent to a third party. There are no sub-processors. Deployment is a roughly 30-minute Docker Compose install, licensing is offline via Ed25519, and the ledger itself is append-only, which means the audit trail behind any weekly report cannot be silently rewritten after the fact.