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

docs: add continuous execution plan

Browse Source
This commit is contained in:
zhaoyilun
2026-07-10 19:44:35 +08:00
parent 93112d6d99
commit 9eb7f382cc
2 changed files with 914 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/current-status-card.md
View File

@@ -58,9 +58,11 @@ N13/N14/N15 are pre-business validation results. They can help identify UI eleme
## Current loop
Current loop: `R6e sandbox-only send connector shell and idempotency audit hardening implemented; next R6f fake/sandbox connector contract or corrected full evidence intake`.
Current loop: `Planning gate complete for continuous execution; awaiting business review before starting R6f`.
Plan file: `docs/superpowers/plans/2026-07-10-core-business-capabilities-roadmap.md`.
Active continuous execution plan: `docs/superpowers/plans/2026-07-10-r6f-r14-continuous-execution-plan.md`.
Previous roadmap file: `docs/superpowers/plans/2026-07-10-core-business-capabilities-roadmap.md`.
Loop rule:
@@ -222,4 +224,10 @@ R6e sandbox-only send connector shell and idempotency audit hardening is complet
- Duplicate same-key/same-target/same-content preview calls return structured metadata with `duplicate_detected=true` and no side effects.
- Same idempotency key reused for different target/content returns `send_status="blocked"` with `conflict_detected=true` and no side effects.
- `scripts\verify-go-mcp.ps1` and `cmd\isphere-capability-smoke` use fresh per-run idempotency state to keep repeatable smoke deterministic.
- Next node: R6f fake/sandbox connector contract or corrected full evidence intake.
- Next node after user approval: R6f fake/sandbox connector contract.
Continuous execution plan R6f-R14 is drafted and awaiting user review:
- Plan file: `docs/superpowers/plans/2026-07-10-r6f-r14-continuous-execution-plan.md`.
- Scope: 15 ordered rounds covering send-message connector/gate hardening, send-file preview/idempotency/package, receive-file download preview, receive-message reconciliation, end-to-end business smoke, and release-candidate report.
- Execution rule after approval: one round at a time, status-card update, verification, commit, push, then continue automatically until an evidence-only blocker requires user action.