2.5 KiB
2.5 KiB
C15 Send Message Source Evidence Precheck
Date: 2026-07-10
Loop: Stage C / C15
Target tool: isphere_send_message
Question
Can isphere_send_message be implemented now from current committed evidence, without guessing a write connector?
Evidence reviewed
| Candidate source | Evidence | Result |
|---|---|---|
| Existing bridge/API/local service | Repository search over committed docs/code for send_message, bridge/API/local service write paths, and MCP contract references |
No committed callable bridge/API/local service for sending was found. Current Go MCP code exposes read tools only. |
| C# WinHelper | native/ISphereWinHelper/Program.cs switch supports only version, self_check, scan_windows, and dump_uia |
No helper op exists for click, type, draft, send, upload, or invoke. |
| UIA selector catalog | internal/uiaselector/catalog.go defines selectors with AllowedUseReadOnlyLocate; catalog includes main window, left panel, roster, fuzzy search edit |
Catalog is read-only locate only and does not validate message input, conversation open, or send button selectors. |
| N12R internal sandbox evidence | docs/internal-sandbox-live-capture-plan.md and docs/internal-sandbox-operator-runbook.md allow only version, self_check, scan_windows, dump_uia and forbid clicking, typing, sending, uploading, and downloading |
N12R evidence is structural/read-only. It does not authorize or prove a write path. |
| Business contract | docs/mcp-core-tools-contract.md defines isphere_send_message with preview/production modes and write errors such as WRITE_NOT_READY and PREVIEW_ONLY |
Contract is ready, but source connector is not validated. |
Decision
isphere_send_message is blocked for implementation. Current evidence supports only contract planning and possibly a future preview-only design, not a production or UIA write connector.
Required unblock evidence:
- A confirmed existing bridge/API/local service that can send messages, or
- An internal-sandbox UIA action evidence package that validates conversation resolution, draft entry, send-button location, pre-send confirmation, and result verification, or
- A validated network/protocol connector with authentication/session handling and audit boundaries.
Next loop recommendation
Do not implement write-capable behavior in C16. Use C16 for read-path hardening: support directory or multi-log configuration for PacketReader sources so the existing receive/contact/group/file-list tools become more useful with operator-local evidence.