mcp: standing notices ride meeting tool results; flows: notice-flagged queue items - #1546
Draft
DmitriyG228 wants to merge 2 commits into
Draft
mcp: standing notices ride meeting tool results; flows: notice-flagged queue items#1546DmitriyG228 wants to merge 2 commits into
DmitriyG228 wants to merge 2 commits into
Conversation
A say-file under `behavior/queue/` may open with `notice: true` in front-matter. That marks what stays TRUE BETWEEN CALLS rather than what just happened, and it is an admin's edit in the tree that already decides whether an item is spoken at all — no deploy on either side of it. `GET /queue/waiting` now carries `notice` on every item. `GET /queue/notices` is the new, much smaller answer: only the flagged items' say texts, deduped, behind exactly the same door — small enough to ask on every call. No new tool. A file with no front-matter declares nothing and behaves as it always did; an unparseable fence costs the flag, never the sentence. This repo ships the mechanism and flags nothing with it. Signed-off-by: DmitriyG228 <2280905@gmail.com>
An agent reads a tool result and nothing else unless something makes it. So a fact that stays true between calls is attached to the call the agent just made, rather than left on a tool somebody has to remember to call. The five meeting tools (request_meeting_bot, get_meeting_transcript, list_meetings, get_bot_status, stop_bot) now carry the caller's standing notices out: a `notices` field in the body and one `Notice: …` line per notice in the text, once per result. `whats_waiting` is excluded — it already answers with them. Never an error and never a new tool: bounded at two seconds, and an absent domain, a slow one, a refusal or an answer this cannot read all leave the result exactly as it was. A refusal carries the refusal and nothing else. This module knows no vocabulary — a notice is a string it was handed. Signed-off-by: DmitriyG228 <2280905@gmail.com>
Member
Author
|
Baseline note, not caused by this branch: Suites, both green with no new failures: flows 544 passed (511 on base, +33 new), mcp 279 passed (243 on base, +36 new). The 23 pre-existing flows failures are identical on base and branch. |
This was referenced Sep 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A say-file under
behavior/queue/may now open withnotice: truein front-matter.That marks what stays true between calls rather than what just happened — an
admin's edit in the tree that already decides whether an item is spoken at all, with
no deploy on either side of it.
flows —
GET /queue/waitingcarriesnoticeon each item;GET /queue/noticesis a smaller answer behind the same door: only the flagged say texts, deduped, cheap
enough to ask on every call.
mcp — the five meeting tools carry the caller's notices out on their results: a
noticesfield plus oneNotice: …line, once. Bounded at 2s; an absent or slowdomain, a refusal, or an unreadable answer leaves the result exactly as it was.
No new tool (still 21), no new argument, and nothing flagged in this repo.
Draft: opened for review, not for merge.