Repository navigation
Description
Parent
#392 — #392; complete S16 target #392.
Model tier
Frontier: this slice requires judgment about protected authority, lifecycle/recovery or a new cross-client/service contract; exact new APIs and migrations are not yet settled.
Context to read
AGENTS.md; CONTEXT.md; docs/agents/workflow.md; docs/specs/S16-rakazo-experience.md; docs/specs/S15-conversational-autonomy.md; ADR 0064 and ADRs 0074–0077; docs/design/S16-rakazo-experience.md; docs/design/S16-mobbin-research.md. Reuse the completed design research; do not repeat broad Mobbin discovery.
Starting implementation/contract surfaces: ops/; install.sh; src/s15/adoption/; docs/contracts/s16-binary-files-v1.md. Read their current definitions and relevant tests before selecting changes. Paths with braces denote existing module families, not settled new signatures.
Deliverable
Install/upgrade/back up/export/restore/uninstall the selected service and clients while preserving policies, withdrawals, usage, unknown effects and compatible rollback. Define final aggregate acceptance after feature formats settle; fixture scaffolding can proceed earlier.
Baseline and readiness
Audited stack head 17b814220371cd1e2126be2ec9bd9753537f69e6; main remains the pre-S16 baseline. #398/#399/#403/#404 are open drafts, not merged/live acceptance. Existing S15 services are reusable baseline, and #400/#401 supply draft text/binary custody. No new behavior is claimed here. Branches/PRs and issue ownership were inspected on 2026-11-05; this new ticket has no implementation claim. Recheck at dispatch. Preserve the primary-owned jit/402-s16-file-memory branch.
Needs triage: contract/engineering choices remain; no ready-for-agent label. Resolve named contract decisions and verify prerequisite revisions before unattended implementation. Independent audit/design work may proceed now; final acceptance needs these deliveries.
Implementation steps
- Recheck ownership, branches/PRs, prerequisites and exact source baseline. Compare existing implementation, pinned Rakazo reuse and a simpler alternative; record the chosen tradeoff and versioned contract before coding.
- Inventory all selected persisted formats/assets/native state and existing S14/legacy/S15 adoption contracts.
- Select migration/write-fence/backup consistency protocol and compatible release fallback; no journal-only rollback across CHAT/file format fences.
- Implement bounded secret-free ordinary export and separately protected recovery backup, verified manifests and reconcile-before-admission.
- Exercise clean install, upgrade, interrupted migration, backup/restore and uninstall preservation using disposable fixtures; publish runbooks.
- Integrate the authored experience using real service facts, English/Thai dictionary keys in their designated files, accessible loading/error/empty/reconnect states and current capabilities. For non-UI evidence work, verify those states instead of inventing new UI. Record migrations, compatibility and exact build evidence.
Acceptance criteria
- Restore retains withdrawal/private scope and unknown-effect dedupe.
- Corrupt/missing ledger or byte hash refuses without reconstructing empty state.
- Interrupted upgrade recovers to compatible release without authority rewind.
- Core works without hosted vendor/telemetry and all notices ship.
- Deliverable works end to end through its actual owning service/client; source presence, transport success and model prose alone are insufficient.
- No S14 default, S15 opt-in, installed policy, historical private scope or owner-host configuration changes without its separate explicit transition.
- New contracts, unresolved limits and exact revision/evidence are recorded; applicable upstream licenses, immutable provenance and modified-file notices ship.
Tests and evidence
- Restore retains withdrawal/private scope and unknown-effect dedupe. Use scripted models, protocol fixtures, fake clocks and barriers for deterministic cases; assert actual resulting state/bytes/effects.
- Corrupt/missing ledger or byte hash refuses without reconstructing empty state. Use scripted models, protocol fixtures, fake clocks and barriers for deterministic cases; assert actual resulting state/bytes/effects.
- Interrupted upgrade recovers to compatible release without authority rewind. Use scripted models, protocol fixtures, fake clocks and barriers for deterministic cases; assert actual resulting state/bytes/effects.
- Core works without hosted vendor/telemetry and all notices ship. Use scripted models, protocol fixtures, fake clocks and barriers for deterministic cases; assert actual resulting state/bytes/effects.
- Run relevant existing module/composed regressions plus the new scenario suite; for rendered behavior, exercise the real bundle in English/Thai, keyboard and mobile widths. Record exact test paths/commands in the PR after implementation selects them.
- Keep real host/account/device checks opt-in and evidence-labelled; no absent credential blocks independent deterministic work. Public evidence contains hashes/outcomes only; installation-specific details belong in ignored .local records.
Requirements
S16-AC21; FR-04, FR-15, FR-18, FR-23, FR-35, FR-38, NFR-02, NFR-04, NFR-05, NFR-08, NFR-09, NFR-12. Retain S15 authority decisions and FR/NFR identifiers.
Blocked by
- [Frontier] [BASE16-01] Verify reusable upstream imports and release notices #405: prerequisite owning contract/delivery; currently open, not merged acceptance.
- [Frontier] [ART16-01] Find and revise delivered artifacts with isolated previews #407: prerequisite owning contract/delivery; currently open, not merged acceptance.
- [Frontier] [TEAM16-01] Run shared and explicitly private computers across Bots #411: prerequisite owning contract/delivery; currently open, not merged acceptance.
- [Frontier] [BOT16-01] Create and preserve a persistent Bot through its lifecycle #412: prerequisite owning contract/delivery; currently open, not merged acceptance.
- [Frontier] [ROUT16-01] Run conversational schedules with durable review waits #414: prerequisite owning contract/delivery; currently open, not merged acceptance.
- [Frontier] [CONN16-01] Connect and revoke a real app through the client #417: prerequisite owning contract/delivery; currently open, not merged acceptance.
- [Frontier] [MCP16-01] Use an HTTPS MCP source under current policy #418: prerequisite owning contract/delivery; currently open, not merged acceptance.
- [Frontier] [OPEN16-01] Execute a reviewed OpenAPI and GraphQL gateway source #419: prerequisite owning contract/delivery; currently open, not merged acceptance.
- [Frontier] [SKILL16-01] Import and use a pinned skill or plugin safely #420: prerequisite owning contract/delivery; currently open, not merged acceptance.
- [Frontier] [MODEL16-01] Switch approved routes with actual usage and continuity #421: prerequisite owning contract/delivery; currently open, not merged acceptance.
- [Frontier] [CALL16-01] Continue and interrupt a voice conversation safely #423: prerequisite owning contract/delivery; currently open, not merged acceptance.
- [Frontier] [NOTIFY16-01] Remove Telegram and deliver needs-you and results through Web Push #441: prerequisite owning contract/delivery (replaces closed [Frontier] [CHANNEL16-01] Deliver messaging attachments, results and needs-you #424).
- [Frontier] [DESKTOP16-01] Package an existing-service desktop client #425: prerequisite owning contract/delivery; currently open, not merged acceptance.
- [Frontier] [MOBILE16-01] Use a packaged mobile client with secure notifications #426: prerequisite owning contract/delivery; currently open, not merged acceptance.
- [Frontier] [COMPUTER16-01] Enroll a second computer backend and recover portable state #427: prerequisite owning contract/delivery; currently open, not merged acceptance.
- [Frontier] [SPACE16-01] Search and organize authorized work across the installation #428: prerequisite owning contract/delivery; currently open, not merged acceptance.
Contracts used/delivered
Use current owning POLICY, DATA15, TEAM, MEM, WORK, CHAT and S16 client/file contracts where relevant, plus Schway's supported public host surface. Specific inputs and proposed delivery: ops/; install.sh; src/s15/adoption/; docs/contracts/s16-binary-files-v1.md. The Deliverable and ordered steps define the missing contract outcome; freeze version, schemas, migration/recovery and conformance fixtures in the implementation ADR/PR. Proposed operations are not already supported APIs. A demonstrated missing engine seam requires a bounded public-only reproduction and a linked Schway contract ticket, never an internal import or duplicate runtime.
Out of scope
Other tickets' outcomes, hosted multi-user SaaS, marketplace operation, upstream branding, silent billing, replacing Schway, general historical data conversion, and unapproved live deployment. Live credentials, real-device acceptance and owner-host cutover are separately owned by LIVE16-01/CUT16-01; deterministic implementation remains in scope.
Do not
Do not use source/model/tool output as authority; expose credentials, sensitive-site sessions or protected state to working execution (trusted-site sessions are the S16-D09 exception); remove guards before proof; auto-retry unknown effects; weaken or bypass the S16-D07 human-required list or let anything but the in-chat owner decision approve it; treat current stack limitations as scope cuts; add model attribution; use implement-parallel; alter #402 ownership; self-merge or deploy. No placeholder controls or fabricated success.
Definition of done
Run bun install --frozen-lockfile, bun run typecheck, bun test --timeout 30000 for affected deterministic suites, and git diff --check; record exact selected suite commands and results. Add real-browser tests for rendered paths and package checks for shipped artifacts. Pure feasibility documentation runs link/coverage checks and git diff --check; a prototype must run its conformance cases. PR body includes Closes #429 and Refs #392, contract versions, tested head and honest pending evidence. No self-merge; parent #392 remains open until full accepted outcomes.
Owner revision 2026-11-06
Grok-style autonomy (S16-D06–D11, ADR 0084) and Telegram removal (ADR 0085) apply. Only the S16-D07 human-required list waits for the owner, approved by a one-press in-chat card; GitHub push/PR/review replies/merge after required checks are the product default; trusted sites may keep sessions in the working VM browser while sensitive sites stay in the protected browser. Jit has no messaging channel; notifications use Web Push (#441). Policy/approval changes belong to #442.
#424 is closed as not planned; its prerequisite edge now points to #441.
Activity