Tachio should generate a conversation for every new project and post daily project briefings to it

[n0fray]

Project briefing

• The project briefings for each project are written every morning at 5:30am PT and posted in two places: the specified project’s project conversation and the current week’s weekly conversation.
• If there are no updates/progress since the last reflection then do not make any post at all.

When Tachio learns about or decides to start a new project, Tachio should create a new conversation in Missive and write a new row to the projects table in the database.

Every morning, Tachio will review additions to the project conversation in Missive (and follow any newly added links to other Missive conversations) and check the project’s related todos in the todos db for newly added todo items or upcoming deadlines, then write a new project briefing as a post in the project conversation in Missive iff there are any updates since the last briefing was posted. Also, each project briefing will be written to the briefings table in the database.

Each project briefing should be generated by an LLM prompt that is carefully written so that the briefing will include a summary of all the progress that has been made on this project since the last briefing was generated (based on reviewing many sources including all the posts, comments, attachments, linked Missive conversations, and web URLs that were posted in the project’s conversation on Missive since the last briefing and any calendar events related to this project that appeared on the calendar during the time since the last briefing), a plan for concrete next steps that the PDW team can do to push the project forward today, and at least one actionable suggestion or proposal for how Tachio can be helpful in this context today.

Context

• For each week, create a new weekly conversation.

  • This week’s daily briefing will be the first post in each week’s new weekly conversation.
  • All of the daily briefings generated during that week will be posted into that week’s weekly conversation.
  • All of the project briefings generated during that week will be posted into that week’s weekly conversation.
  • Note that every week, when the new weekly conversation is started by Tachio, there will be a new Missive conversation ID generated for that week’s weekly conversation.

• For each project, create a new project conversation.

  • Every day, for each project, if there has been any activity related to this project since the last update then write a summary of the new activity as a post in that conversation on Missive.

    • This includes any new/updated/completed todo items that are related to this project, any comments written by users into the project’s conversation, and any other emails/conversations in Missive that are imported into the project’s conversation.

      • A user can “import” an email thread into a project by pasting a link to that email thread’s Missive conversation URL into the project’s conversation. When Tachio detects a Missive conversation URL, Tachio should go read the conversation and write a summary of it into the project conversation where it was detected. The summary of should include all the messages in that conversation, all the comments in that conversation (from previously received webhooks), and any of Tachio’s other existing memories that are associated with the specific Missive conversation ID.

        • This is how we can easily import our team’s daily report emails into project conversation, which will be crucial to generated the biweekly summary reports.

• For each org, create a new org conversation.

  • Every time when a new project gets created that is associated with this org, post a link to that project conversation into the org conversation.
  • Every time that a new person gets created who is associated with this org, post a link to that project conversation into the org conversation.