Files
isphere-ai-bridge/README.md
2026-07-05 00:44:28 +08:00

40 lines
1.8 KiB
Markdown

# iSphere AI Bridge
This project is for building a safe message-handoff gateway between iSphere/IMPlatformClient and AI digital employees.
The first goal is not full automation. The first goal is to let AI reliably see authorized messages, normalize them, generate reply drafts, and keep evidence. Sending messages is a later step and must stay behind human approval until explicitly changed.
## Scope
- Authorized company communication software only.
- Read messages first; do not modify the original client state in the first POC.
- Prefer stable entry points in this order:
1. Local data/log/cache discovery.
2. Plugin or existing bridge API.
3. UI automation/RPA wrapper.
4. Network/API discovery.
5. Binary reverse engineering only when needed to explain or validate the above.
## Existing Source Material
- Previous iSphere work: `E:\coding\codex\isphere`
- Installer: `E:\coding\codex\isphere\iSphere_4.1.2.6841.exe`
- Existing bridge artifacts: `OpenClawBridge`, `MockCloud`, `XmppBridgeService`
- Existing MCP spec: `E:\coding\codex\isphere\docs\MCP接口需求规格.md`
## Key Directories
- `docs/` - design notes and installed skill map.
- `prompts/` - ready-to-use Codex prompts for each investigation phase.
- `evidence/` - local evidence output; ignored by Git except `.gitkeep`.
- `runs/` - run logs and temporary investigation outputs; ignored by Git except `.gitkeep`.
- `src/` - future implementation code.
## Safety Baseline
- Do not bypass login, licensing, MFA, access control, TLS protections, or endpoint security.
- Do not read non-authorized account data.
- Do not send real messages without explicit human approval.
- Do not modify production databases, logs, config files, registry keys, or binaries during discovery.
- Redact secrets, tokens, private message content, and personal data in reports.