Back office
Admin / issues
Issues
49 issues in issues/ (issues-fs-lite: the folder is the status, the file is the issue, the front matter is the data). 9 epics. Every issue cites where it came from. Moving an issue is a git mv between folders, committed with the work that caused it.
Open 21
- 001 Epic: the reading experience on every piece
- 002 Epic: the site shaped by what the reader has done
- 003 Epic: a chat with tools over the site, and messages relayed to other agents
- 006 Epic: the back office runs on issues, with provenance
- 024 Relay feedback addressed to another site's agenta chat with tools over the site, and messages relayed to other agents
- 042 Brief: email the contact who received the voice questionnaire linkbriefs for agent@riskmandate.ai
- 048 Send the reader's feedback from the browser to the newsroom over an append lanethe site shaped by what the reader has done
- 049 Ephemeral inbox vaults: an agent receives messages through a vault it creates for one sessiona chat with tools over the site, and messages relayed to other agents
- 004 Epic: content principles, visual briefing, and the semantic twin
- 005 Epic: maps and data you can click, sort and slice by day
- 008 Epic: briefs for agent@riskmandate.ai
- 016 Standing briefing cards in the same place on every piecethe reading experience on every piece
- 021 Render pages from a graph of pieces, merged with the reader's statethe site shaped by what the reader has done
- 038 Run the newsroom daily on a schedulethe back office runs on issues, with provenance
- 043 Brief: map the integrations and who to contact, in the vault CRMbriefs for agent@riskmandate.ai
- 044 Brief: connectors and digital twins for Slack, Discord, WhatsApp and othersbriefs for agent@riskmandate.ai
- 045 Brief: find an AWS partner for sgit.ai and one for RiskMandate.aibriefs for agent@riskmandate.ai
- 007 Epic: an industry news feed in, slide decks and PDFs out
- 020 A wallet drained by actions (as pt.newsroom.sgit.ai)the site shaped by what the reader has done
- 039 A daily industry news feed on the vaults' topics, as JSON the newsroom consumesan industry news feed in, slide decks and PDFs out
- 040 Daily or thematic slide decks, rendered to HTML and PDFan industry news feed in, slide decks and PDFs out
Blocked 2
- 022 Store the reader's state in a vault, for the daily agent and other devicesthe site shaped by what the reader has done
- 035 The network map per day: which links appeared whenmaps and data you can click, sort and slice by day
Done 26
- 009 Put every piece on its own sheet, with a byline block that says who wrote itthe reading experience on every piece
- 010 Feedback bar on every piece, not only on source pagesthe reading experience on every piece
- 011 Replace "Read" / "Mark read" with a state that is unambiguousthe reading experience on every piece
- 012 Side panels: peek a link, feedback, chat, maps, resizablethe reading experience on every piece
- 017 Marking a piece read hides it from the front page and the sectionsthe site shaped by what the reader has done
- 018 Two views: the editor's and the reader'sthe site shaped by what the reader has done
- 019 A history of every action, with undo and redothe site shaped by what the reader has done
- 023 A chat panel with tools over the site, on the reader's OpenRouter keya chat with tools over the site, and messages relayed to other agents
- 025 A briefing page per target sitea chat with tools over the site, and messages relayed to other agents
- 027 The site's principles and content rules (including: no "rungs")content principles, visual briefing, and the semantic twin
- 028 Issues and questions a desk finds go to a visible place, not into prosecontent principles, visual briefing, and the semantic twin
- 036 issues-fs-lite in issues/, rendered as a kanban and pages in adminthe back office runs on issues, with provenance
- 037 Capture the notes of 25 September as issues, with provenancethe back office runs on issues, with provenance
- 041 Build the approved front-page layoutthe reading experience on every piece
- 046 This newsroom joins the collaboration vault and greets @Mailbox and @Coworkbriefs for agent@riskmandate.ai
- 047 Send to riskmandate-agent-collab through an append lanea chat with tools over the site, and messages relayed to other agents
- 013 Use the width: content column plus panesthe reading experience on every piece
- 014 Source pages: what is the newsroom, what is the target sitethe reading experience on every piece
- 015 Screenshots of the pages a piece is aboutthe reading experience on every piece
- 026 Propose the chat and feedback pattern to sgit.ai for other agentsa chat with tools over the site, and messages relayed to other agents
- 029 Experiment: a JSON twin with a semantic graph for each new piececontent principles, visual briefing, and the semantic twin
- 030 Every Cartographer page carries a map, graph or infographic; tooling to make that cheapcontent principles, visual briefing, and the semantic twin
- 031 History index that reads, and lessons the reader can mark read one by onecontent principles, visual briefing, and the semantic twin
- 032 The newsroom is part of the universe it reports oncontent principles, visual briefing, and the semantic twin
- 033 Signals answer "what are we reporting?" in the first linecontent principles, visual briefing, and the semantic twin
- 034 Network map: click a site for its details and relationships; sortable tablemaps and data you can click, sort and slice by day