Dots imports six AI handover records

Ryohei Asada Moriya creates a shared Google document so his Dots assistant, Cham, and Claude Cowork can record work in one place. A handover record distinguishes completed actions, decisions, unresolved checks and the next step, with the responsible environment and artifact links.

The actual first scheduled import processes six records from a Google Drive inbox. Cham appends them to the handover document, checks that the saved content exists, and only then changes their status from unimported to imported. The schedule is three in the morning in Japan. This ordering matters because marking a record too early could hide work lost during an interrupted write.

Moriya also verifies the document updates himself. Claude can read through the Drive connection in his tested environment, but needs the in-app browser to append content. The account proves the initial record collection and document updates, not that later cross-agent work reliably resumes or saves time. The sales-material example in the article is explicitly fictional. The useful implementation detail is to reread before appending, preserve other records, verify after saving and keep missing URLs and unfinished checks explicit instead of inventing completeness.

Prompt
Original prompt

Source: Blog · Ryohei Asada Moriya