Work Item Progress Summary
Adapts aha-links' fact collection and output contract; first read Item Operations and CLI reference. The CLI collects facts, while the current model synthesizes them; do not invoke a standalone reporting backend.
When the current run involves bound items, first follow Execution Snapshot and Live Context to read the execution snapshot for this run, then collect the latest review or period facts using the following process; present the two sources separately. When there are no bound items, use only the scope explicitly specified by the user.
Scope and Time
bash
ae-cli things +digest --agent-space-id <space-id> --from 2026-09-07T00:00:00+08:00 --to 2026-09-14T00:00:00+08:00 --time-zone Asia/Shanghai --format json
ae-cli things +digest --agent-space-id <space-id> --assignee-id <member-id> --format json
ae-cli things +digest --agent-space-id <space-id> --thing-ids <id-a>,<id-b> --format json
Do not guess IDs or select a personal default space; watchlists, groups, and cross-space summaries are not supported. Daily reports are based on calendar days, while weekly reports run from Monday 00:00 to the following Monday 00:00, with Asia/Shanghai as the default. For today/this week, use the current time as the cutoff; for yesterday/last week, use the complete period. Custom intervals must be explicit; both
and
in the command must include a time zone, and intervals are left-closed and right-open.
When producing output, convert record ISO times to the report time zone and explicitly label the time zone next to the time window, collection time, and evidence dates. For example,
in Asia/Shanghai should be displayed as
2026-09-10 12:50 (Asia/Shanghai)
; do not simply remove the Z and write “04:50 Shanghai time.” If reliable conversion is not possible, retain the original ISO time and label it as UTC, disclose that it has not been converted, and do not fabricate a local time.
Evidence and Completeness
Check
,
,
, and
; for explicit sets, also check
and
. If any field is missing, stop before drawing a comprehensive conclusion. CLI automatic pagination supports up to 100 pages/10,000 items per chain, and errors or limit hits mark the result as truncated; do not replace this with a single-page list and pass it off as a complete collection.
- is the current state, are records within the time window, and is the pre-window state inferred from complete business change records; do not fabricate a baseline when none exists or when a version change occurred during collection.
lastEffectiveRecordBeforeWindow
- Before producing output, compare with the window's . When (including a user-specified full calendar week that has not yet ended), the report must state “interim summary as of the collection time; the period has not yet ended”; label the tri-state statistics as “state at collection time,” and do not write “state at the end of the period” or “no subsequent updates.” For example, a weekly report collected on September 10 for September 7–14 cannot assert that the September 14 state is the same as the current state. Even if the window has ended, the period-end state may be reconstructed only when complete post-window change evidence supports it.
- Count , , and separately, and list archived items separately; obtain the latest progress from and read historical changes from / records.
- Notes and repeated process descriptions do not count as valid progress; contains candidates awaiting verification, so exclude entries whose body contains no new information.
- If there are no records, state only “no updates recorded.” This constraint also applies to summaries and next-step recommendations; cannot prove that work has not started, so report only the current state and the absence of recorded facts. Unread, unreadable, or truncated attachments, as well as the non-transactional collection boundary across multiple requests, must be disclosed. If
changed_during_collection
Output and Write-back
First state the scope, time window, collection time, and coverage boundaries; then provide the tri-state and archived counts, period changes, blockers, and next steps. Include the source item and date for every important judgment, and distinguish facts, inferences, and recommendations. Do not display internal record IDs by default.
By default, output only to the conversation. When write-back is explicitly requested, use
to read the target items' report records in full, check for a title with the same scope and period, and then write the final body using
ae-cli things entry append --id <target-id> --type note --title "Work Item Weekly Report｜Start–End Dates｜Scope" --stdin --command-id <uuid> --format json
. Use
Work Item Weekly Report｜Start–End Dates｜Scope
as the recommended title, and use the equivalent format for daily reports. If a report with the same scope and period already exists, prompt for a revision; do not silently overwrite it or append a duplicate. Write a new record only after the user explicitly requests an appended revision, and preserve the original report. Once write-back permission has been granted, there is no need to ask for the same permission again.
Do not automatically send messages, change statuses, assign owners, or create scheduled tasks.
File evidence:
/
automatically paginate to collect asset links. A file with
or
does not count as a usable deliverable; even
only means the reference is available, not that its body has been read or accepted. Disclose unread files and non-transactional collection boundaries. Private session sources may be read only when the current user has permission. Reports may cite facts from shared items, but private history must not be automatically exposed.