admin/isphere-ai-bridge
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: trim safety constraints from mcp roadmap

Browse Source
This commit is contained in:
zhaoyilun
2026-07-09 22:02:26 +08:00
parent cfc7787cdd
commit e993ce15fb
8 changed files with 172 additions and 262 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/design.md
View File

@@ -6,7 +6,7 @@ Make iSphere messages usable by AI digital employees without rebuilding the full
## First POC
The first POC reads recent authorized messages, converts them into a normalized JSON model, generates draft replies, and records evidence. It does not automatically send messages.
The first POC reads recent messages, converts them into a normalized JSON model, generates draft replies, and records evidence. Send/file capabilities are part of the staged MCP tool roadmap.
## Architecture
@@ -46,12 +46,11 @@ iSphere / MockCloud / existing bridge
}
```
## Approval Policy
## Write Execution Model
- Read access can be automated in test scope.
- Draft generation can be automated.
- Sending messages requires human approval in the first implementation.
- Every send action must log target, content hash, timestamp, approver, and connector.
- Read access and draft generation can be automated in test scope.
- Send/file tools are staged after source discovery and connector selection.
- Every write action records target, content or file hash, timestamp, operator, and connector.
## Verification