Skip to content

feat(ada): weekly update deck before the Tech WG, sent on Discord (decision 79) - #56

Merged
mttrbrts merged 2 commits into
mainfrom
feat/weekly-update
Nov 13, 2026
Merged

mttrbrts merged 2 commits into
mainfrom
feat/weekly-update

Conversation

@mttrbrts

Copy link
Copy Markdown
Member

The owner wants a weekly slide deck on the network, in hand before the Tech WG call. Every Tuesday at 16:00 London time, Ada writes one of at most 10 slides on the week since the last call: key decisions, changes to the network, feedback, the effect on the KPIs and observations. The gateway sends it to the owner's Discord DMs as a Markdown file in Marp's format, ready to present or turn into slides.

Changes

  • Schedule: ada-weekly-update runs Tuesdays at 16:00 as a gateway schedule, task weekly_update (standard tier, medium effort), capped at $2 a run.
  • Instructions and example: reports/weekly-update.md (how to gather and write it) and reports/weekly-update-example.md (the 11 November WG deck cut down to the 10-slide shape). deploy.ts writes both to the shared memory store, like the rubric, so Ada's other sessions don't pay for them. Ada's spec gets a short "Weekly update (Tuesdays)" section that points to them.
  • send_to_matt takes an optional document: a lower-case .md file name and at most 20,000 characters. The gateway DMs it to the owner on Discord as an attachment with no mentions (DiscordBot.dmFile, multipart), and records discord.document_sent in the audit. It's allowed in a conversation, since a reply can't carry a file. Without OWNER_DISCORD_ID it refuses before sending anything.
  • Deploy workflow: a change under reports/ now triggers deploy:agents.
  • Docs: decision 79, and reports/ in CLAUDE.md's layout table and deploy notes.

Safety

Ada gets no new tool. send_to_matt can attach a file, but only to the owner's own Discord DMs, with mentions off. File names are checked (lower-case letters, digits and hyphens, ending .md), so no path or other file type gets through. No action kind, credential or permission changes.

Deploy

npm run deploy:agents (spec, schedule, model task and the new shared-memory files), then npm run gateway:deploy (tool and Discord client). The deploy workflow does both once the run is approved.

Decision

79

Checks

  • npm test passes (439 tests)
  • Tests cover the gateway change: decisions.test.ts (file sent, refusals, no Discord id, sending during a conversation) and channels.test.ts (the multipart request, and the fetch-binding regression for the new path)
  • network.json regenerated
  • No secrets or Discord/Telegram ids added

Not verified against the live API: Discord's multipart upload (payload_json plus files[0]) in dmFile. The first Tuesday run will be its first live test.

🤖 Generated with Claude Code

mttrbrts-agent and others added 2 commits November 13, 2026 20:08
Every Friday at 17:00, after Vera's weekly scorecard and the evaluation, Ada writes a
slide deck of at most 10 slides on the network's week: key decisions, changes,
feedback, the effect on the KPIs and observations. Its instructions and an example
deck live in reports/ and are written to the shared memory store at deploy, so Ada's
other sessions don't pay for them.

send_to_matt takes an optional document (a lower-case .md file name, at most 20,000
characters), which the gateway DMs to Matt on Discord as an attachment with no
mentions, and records in the audit. Without OWNER_DISCORD_ID it refuses before
sending anything.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Matt Roberts (Agent) <code+agent@rbrts.uk>
…cision 79)

The deck now arrives on Tuesday at 16:00 and covers the week since the last Wednesday call, using that morning's daily scorecard and the previous Friday's weekly one. Files are named for the date of the call.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Matt Roberts (Agent) <code+agent@rbrts.uk>
@mttrbrts
mttrbrts merged commit e51b9f6 into main Nov 13, 2026
5 checks passed
@mttrbrts
mttrbrts deleted the feat/weekly-update branch November 13, 2026 20:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants