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

docs: plan stage c iterative receive loop

Browse Source
This commit is contained in:
zhaoyilun
2026-07-09 22:46:16 +08:00
parent 1eed0f62f2
commit de3bb922da
3 changed files with 499 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files

44
docs/source-discovery/README.md
View File

@@ -1,39 +1,43 @@
# Source Discovery Ledger
Date: 2026-07-09
Current loop: Stage B1 - N12-pre zyl evidence source discovery
Current loop: Stage C / Loop C1 - log decryptor and PacketReader parser
## Objective
Find the best real capability source for the MCP core read tools before implementing Stage C.
Build the first business read capability path for `isphere_receive_messages` from decrypted `PacketReader.ProcessPacket` XMPP message logs.
## Inputs
- `runs/offline-evidence-intake/zyl-qqfile-20260709/archives/zyl.rar`
- `runs/offline-evidence-intake/zyl-qqfile-20260709/metadata/archive-list.txt`
- `runs/offline-evidence-intake/zyl-qqfile-20260709/metadata/sha256.txt`
- `docs/source-discovery/2026-07-09-n12-pre-zyl-index.md`
- `docs/source-discovery/2026-07-09-n12-pre-zyl-schema-notes.md`
- `docs/source-discovery/capability-source-matrix.md`
- `docs/mcp-core-tools-contract.md`
- `docs/mcp-core-business-plan.md`
## Loop cadence
## Loop protocol
1. Inventory evidence.
2. Identify source candidates.
3. Map candidates to MCP tools.
4. Select primary/fallback source per tool.
5. Open one Stage C implementation slice.
6. Verify with `go test ./...`, `go build ./cmd/isphere-mcp`, and MCP verification script.
7. Commit exact paths.
1. Write or update the plan before coding.
2. Implement one loop only.
3. Run loop-specific tests.
4. Run full verification with `go test ./...` and `go build ./cmd/isphere-mcp`.
5. Commit exact paths.
6. Update the next loop based on actual results.
7. Continue automatically while the next step is clear; ask the user only when blocked or when the business direction changes.
## Current target order
## Current loop output
1. `isphere_receive_messages`
2. `isphere_search_contacts`
3. `isphere_search_groups`
4. `isphere_receive_files`
Loop C1 must produce:
Reason: message source discovery is the current blocker; contacts/groups can be derived or selected after the message source shape is known.
1. `internal/isphere/logcodec.DecryptLine` for DES/CBC/PKCS7 Base64 log lines.
2. `internal/isphere/packetlog.ParseMessageLog` for redacted `PacketReader.ProcessPacket` XMPP `<message>` stanzas.
3. Passing unit tests with synthetic/redacted fixtures only.
4. A plan update for Loop C2 before any source abstraction code starts.
## Current plan
See `docs/superpowers/plans/2026-07-09-mcp-core-source-discovery-loop.md`.
See `docs/superpowers/plans/2026-07-09-stage-c-log-backed-receive-messages-loop.md`.
## Last completed discovery result
Stage B2 showed that selected `MsgLib.db` files are not direct SQLite. Decrypted `PacketReader.ProcessPacket` XML is now the first implementable source for `isphere_receive_messages`.