ADR-035: A proposed post waits as the person's draft, for them to send¶
propose_post lets the person post what the model proposes. It checks the message as a post is checked (ADR-031) and saves it as the person's Mattermost draft where it would go: a channel, a thread, or a direct or group message the person already has. A conversation that does not exist yet is not started: creating its channel puts it in the other people's sidebar at once, an empty conversation they see, so the first message in one goes through dm or group_message. The draft is the vessel. Mattermost keeps it in the message box and the drafts list of every client, so a proposal outlives the conversation and the view. In a client that renders views, the view shows the draft as it will be posted, with Post, Edit and Discard (ADR-022). In one that renders none, the answer links the place where the draft waits, for the person to send it from Mattermost.
Pressing Post in the view sends the draft as the view shows it, marked as written with AI (ADR-031). It is a convenience where the client renders the view, not proof the person pressed it: mm-mcp cannot tell a click from a script. The press goes through the writing tool only views call (ADR-022), which the client keeps from its model, and names the text the view shows. mm-mcp acts only on what a view put in the draft, mm-mcp's proposal or the person's text from the view's editor, unchanged, and only while it holds that text and nothing the person added in Mattermost, so a press never sends text the person did not see, nor words they wrote in Mattermost and have not sent. A newer proposal refuses the press, and the view draws it as it is now; a draft the person typed on, or gave files or settings, in Mattermost is sent from there. The message is checked again at the press. Posting deletes the draft, so a second press finds nothing. Edit writes into the draft, and Discard deletes it, each bound in the same way. Replace mine acts only while the person's draft holds what the view shows of it. A message Mattermost has its sender confirm, one whose @channel, @all, @here or user group alerts more than five people, is posted only on a second press: the first answers with Mattermost's counts, read at the press, and the view asks, as Mattermost would. The model learns what the person did from Mattermost, the draft gone or the post in the channel, and, where the client passes it on, from the view's update of its context in mm-mcp's fixed words, with the text quoted as data.
The view hides nothing that is sent. A link shows where it leads where its text says otherwise, characters the eye cannot see or that turn the text's direction are counted and flagged, and the text as written, each such character shown by its code point, is a click away.
mm-mcp writes over the person's own words only on their action, or by a call that states what it discards (ADR-031). A draft that holds mm-mcp's own earlier proposal, unchanged, is mm-mcp's to replace. Once the person has typed in it, it is theirs, and so is a draft they changed with Edit in the view. A proposal carries a mark of its text in the draft's properties, and a draft changed with Edit a mark of the person's text, which the view's presses reach: a draft whose text no longer matches its mark, or that has none, or that holds files or settings the person added, is the person's. propose_post never replaces one, and where the person's own draft already holds the proposed text, the view asks them as it does over any draft of theirs. In a client that renders views, a proposal where the person's draft waits is not written: the view shows their draft beside it, or, when the model says the person asked to change their draft (revises_draft), the proposal as a revision of it, word by word, with Replace mine, or Apply, and Keep mine. Without a view, the call is refused with what the draft holds and the ways on: they finish or clear it in Mattermost, the model posts with create_post, or, when they asked for their draft to be changed, the model deletes it with delete_draft, whose call states what it discards and which asks where mm-mcp asks, and proposes again.
A proposal carries no AI marker. Mattermost's own client sends a draft's properties with the post, so the marker would travel, but what the person sends from Mattermost is theirs (ADR-031). The mark of a proposal's text travels the same way, where nothing shows it.
The client is trusted to keep the tools only views call from its model, and to press only when the person clicks; mm-mcp cannot tell a click from a script. A press never asks, as no call from a view does (ADR-022), and changes what it changes as the person's own action (ADR-021, ADR-033). MM_MCP_POST_FROM_VIEWS, true by default, is the lever for a client that cannot be trusted with that: false takes Post out of the view, refuses a press on it, and the draft waits in Mattermost for the person to send.
A proposal lets the person decide on the text in the conversation without a question their client might answer unseen (ADR-033), and leaves them a draft in Mattermost whatever their client renders.
Not chosen¶
- A token in the result, single-use and bound to the text: Every part of a result reaches some client's model (ADR-022), and a token fetched from a tool only views call protects nothing that keeping that tool from the model does not.
- The draft's update time, to bind a press: The text the view shows is what the person agreed to send. A time would refuse a draft typed on and typed back, and would have to travel in the answer for the view alone.
- The confirmation's counts in the proposal: An edit in the view changes what the message mentions, and members join; counted at the press, they are Mattermost's as it sends.
- Post through
create_post: Its checks are a post's, and the question it asks where mm-mcp is set to ask is shown by no client during a call from a view. - Ask again after the press, as a setting: For the same reason; the setting takes Post away instead.
- A view that expires after a few minutes: The text a press names already refuses a stale press, and a person who reopens a conversation and presses Post on an unchanged draft sends what they see.
- Set the person's draft aside and restore it once the proposal is posted: Until then every client of theirs shows the model's text where their words were, and if mm-mcp stops, or they type in that box, their draft is lost.
- Replace the person's draft on a call that states its length: A tool that does not ask may not destroy anything (ADR-021), and one that asks is refused in a client that cannot show the question, which is where a proposal is needed most;
delete_draftstates the length and asks where mm-mcp asks, and the proposal follows it. - Files in a proposal: A draft holds only files already uploaded, so a proposal with files would send them to Mattermost before the person agreed; a post with files goes through
create_post, whose call names them.