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

chore: package send sandbox evidence gate

Browse Source
This commit is contained in:
zhaoyilun
2026-07-10 14:19:15 +08:00
parent ac3f10f53c
commit 8cdaa3c0bc
8 changed files with 569 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
docs/source-discovery/2026-07-10-send-sidecar-b-first-plan.md
View File

@@ -344,17 +344,17 @@ connector_stage = "preview" | "sandbox_send" | "production"
## Next implementation loop
R6b B-route preview/dry-run contract is now complete. `isphere_send_message` is registered as preview/dry-run only, validates target/content-hash/idempotency input, appends redacted audit JSONL, and blocks production with all side-effect flags false.
R6c local preparation is now complete. Because the local development machine cannot log in, the online sandbox-send gate was converted into a returnable evidence package rather than a local live-send attempt.
Next node should be **R6c online sandbox-send evidence gate**:
Next node should be **R6d returned sandbox evidence intake** after the package is run in an online/internal sandbox and returned:
1. Prepare or collect one operator-approved sandbox send evidence package.
2. Use one explicit sandbox target, one content hash, and one idempotency key.
3. Observe success/ack or local sent-record evidence.
4. Prove duplicate retry with the same idempotency key is locally rejected before any second send.
5. Capture method names, argument shape, IDs/hashes, status booleans, and refs only.
6. Do not enable production `send_message_after_approval` until the evidence gate passes.
1. Check completed `SANDBOX-SEND-INPUTS.json`.
2. Check before/after read-only recorder outputs.
3. Confirm one explicit sandbox target, one content hash, and one idempotency key.
4. Confirm `success_ack_or_sent_record`.
5. Confirm no second send was made.
6. Do not enable production `send_message_after_approval` until returned evidence passes.
## Current status
B is selected as the primary send/file-send route. Runtime discovery, entrypoint metadata preflight, and preview/dry-run audit are in place. A remains the fallback and now has concrete UIA selector/offline-blocker classifier support. Production send remains blocked until dynamic observation and one approved sandbox send prove success/ack behavior.
B is selected as the primary send/file-send route. Runtime discovery, entrypoint metadata preflight, preview/dry-run audit, and the online sandbox evidence package are in place. A remains the fallback and now has concrete UIA selector/offline-blocker classifier support. Production send remains blocked until the returned sandbox package proves success/ack behavior.