Files
isphere-ai-bridge/docs/source-discovery/README.md
2026-07-10 10:59:48 +08:00

2.2 KiB

Source Discovery Ledger

Date: 2026-07-09 Current loop: Stage C / Loop C1 - log decryptor and PacketReader parser

Objective

Build the first business read capability path for isphere_receive_messages from decrypted PacketReader.ProcessPacket XMPP message logs.

Inputs

  • 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/source-discovery/2026-07-10-send-sidecar-b-first-plan.md
  • docs/source-discovery/2026-07-10-live-probe-recorder.md
  • docs/mcp-core-tools-contract.md
  • docs/mcp-core-business-plan.md

Loop protocol

  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 loop output

Loop C1 must produce:

  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-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.

C29 corrected the write-side route after static binary evidence review and user decision: isphere_send_message should prioritize the running-client sidecar / in-process connector route, with constrained UI/RPA as fallback. The next write-side loop is a non-mutating B-route runtime probe.

C30 adds a portable ISphereLiveProbeRecorder.exe package for environments where iSphere can actually log in. The recorder collects read-only runtime evidence and writes JSON output for B-route sidecar feasibility analysis.