# Issues

- [open] 001 Epic: the reading experience on every piece
- [open] 002 Epic: the site shaped by what the reader has done
- [open] 003 Epic: a chat with tools over the site, and messages relayed to other agents
- [open] 004 Epic: content principles, visual briefing, and the semantic twin
- [open] 005 Epic: maps and data you can click, sort and slice by day
- [open] 006 Epic: the back office runs on issues, with provenance
- [open] 007 Epic: an industry news feed in, slide decks and PDFs out
- [open] 008 Epic: briefs for agent@riskmandate.ai
- [open] 016 Standing briefing cards in the same place on every piece
- [open] 020 A wallet drained by actions (as pt.newsroom.sgit.ai)
- [open] 021 Render pages from a graph of pieces, merged with the reader's state
- [open] 024 Relay feedback addressed to another site's agent
- [open] 038 Run the newsroom daily on a schedule
- [open] 039 A daily industry news feed on the vaults' topics, as JSON the newsroom consumes
- [open] 040 Daily or thematic slide decks, rendered to HTML and PDF
- [open] 042 Brief: email the contact who received the voice questionnaire link
- [open] 043 Brief: map the integrations and who to contact, in the vault CRM
- [open] 044 Brief: connectors and digital twins for Slack, Discord, WhatsApp and others
- [open] 045 Brief: find an AWS partner for sgit.ai and one for RiskMandate.ai
- [open] 048 Send the reader's feedback from the browser to the newsroom over an append lane
- [open] 049 Ephemeral inbox vaults: an agent receives messages through a vault it creates for one session
- [blocked] 022 Store the reader's state in a vault, for the daily agent and other devices
- [blocked] 035 The network map per day: which links appeared when
- [done] 009 Put every piece on its own sheet, with a byline block that says who wrote it
- [done] 010 Feedback bar on every piece, not only on source pages
- [done] 011 Replace "Read" / "Mark read" with a state that is unambiguous
- [done] 012 Side panels: peek a link, feedback, chat, maps, resizable
- [done] 013 Use the width: content column plus panes
- [done] 014 Source pages: what is the newsroom, what is the target site
- [done] 015 Screenshots of the pages a piece is about
- [done] 017 Marking a piece read hides it from the front page and the sections
- [done] 018 Two views: the editor's and the reader's
- [done] 019 A history of every action, with undo and redo
- [done] 023 A chat panel with tools over the site, on the reader's OpenRouter key
- [done] 025 A briefing page per target site
- [done] 026 Propose the chat and feedback pattern to sgit.ai for other agents
- [done] 027 The site's principles and content rules (including: no "rungs")
- [done] 028 Issues and questions a desk finds go to a visible place, not into prose
- [done] 029 Experiment: a JSON twin with a semantic graph for each new piece
- [done] 030 Every Cartographer page carries a map, graph or infographic; tooling to make that cheap
- [done] 031 History index that reads, and lessons the reader can mark read one by one
- [done] 032 The newsroom is part of the universe it reports on
- [done] 033 Signals answer "what are we reporting?" in the first line
- [done] 034 Network map: click a site for its details and relationships; sortable table
- [done] 036 issues-fs-lite in issues/, rendered as a kanban and pages in admin
- [done] 037 Capture the notes of 25 September as issues, with provenance
- [done] 041 Build the approved front-page layout
- [done] 046 This newsroom joins the collaboration vault and greets @Mailbox and @Cowork
- [done] 047 Send to riskmandate-agent-collab through an append lane