Owner-confirmed direction

On 2026-11-05 the owner requested the full Rakazo-style product experience and authorized adapting its concepts and code. The owner explicitly chose to keep Jit + Schway and integrate selected Rakazo parts, rather than replace Jit with a Rakazo fork.

Reference: https://github.com/elie222/rakazo at abf3c08145a05cba92a912d6c24fdfb5f569d0e0 (Apache-2.0). Preserve upstream licensing, applicable notices and modified-file notices for every imported source. Retain the Jit name and do not imply upstream endorsement.

Product outcome

A persistent team of Bots that the owner talks to naturally: continuous conversations, useful memory, shared/private working computers, browser/desktop work with owner takeover, durable background work, routines, delegation, rich files/artifacts, app connections, governed MCP/OpenAPI/plugins/skills, voice, and Web/desktop/mobile clients of the same protected Jit service.

Rakazo is the primary product reference. Schway remains the engine for execution loops, provider protocols, native sessions, compaction and retries. This parent does not silently replace S14/legacy stores or activate a live installation.

Retained boundaries

• Authenticated owner requests and standing policy are authority; sources, imported code, memory, models and other Bots are not.
• Existing protected communication, financial, production, private-data and major-change gates remain until an explicitly reviewed replacement contract is implemented.
• Credentials, sensitive-site sessions and protected Jit state remain beyond working-agent administration; trusted-site sessions in the working VM browser are the owner-accepted S16-D09 exception.
• One installation remains single-owner. Hosted billing, SaaS tenancy and use of the owner's everyday desktop are not inferred.
• Existing S15 live evidence/adoption work ([Frontier] [EVID15-01] Prove the protected boundaries and the GitHub scenario on the tested build #340/[Frontier] [CUT15-01] Install S15 fresh on jit-vm with owner acceptance and a recoverable install #341) remains open with its own exact-build scope.

Delivery

Publish docs/specs/S16-rakazo-experience.md, ADR 0074 and a complete delivery graph. Preserve FR-01–FR-42 and NFR-01–NFR-14. Distinguish confirmed product outcomes, engineering proposals and implemented evidence. Split narrow vertical implementation tickets with current ownership/PR/blocker checks under docs/agents/workflow.md.

All UI/UX uses the owner's designated author. For S16 the owner selected Astra at high effort on 2026-11-05, replacing the unavailable prior author, and authorized detailed Mobbin MCP research before design. Runtime integration uses only supported Schway public contracts. Test deterministically with scripted models/fake clocks; real providers, website logins and host acceptance have separate opt-in evidence.

Acceptance

• Every requested self-hosted product capability is mapped to an observable acceptance case, owning implementation slice and evidence status.
• Required UI/UX handoff is authored by the designated model.
• The Web experience performs real work with files, mediated browser/computer use and connected tools through the same policy.
• Persistent Bots, delegated work, routines, memory and results survive interruption without duplicate effects or widened authority.
• Voice, desktop and mobile clients use the same product contracts and expose actual availability.
• Applicable third-party license/notice obligations are included in source and release artifacts.
• Deterministic, composed and opt-in live acceptance is attributed to exact builds. Unsupported cases and pending owner inputs are explicit.
• Existing S14/legacy data and private scopes, rollback and installed policies remain preserved.

This is a spec parent, not an implementation ticket. It is not ready-for-agent. Do not close it for documentation delivery or partial feature presence.

Stack flexibility and initial delivery

The owner's follow-up on 2026-11-05 explicitly invites changing existing stacks and incidental constraints when that makes Jit simpler or better. Compare concrete alternatives and propose material changes; keeping Jit + Schway does not require retaining the existing SSR frontend, database internals, API protocol or packaging.

Initial scoped work:

• DOC16-01 #393: baseline, architecture alternatives, source/license inventory and complete graph.
• UX16-01 #394: required product experience and first file workflow handoff.
• API16-01 #395: real tool-backed conversation through reusable client contracts.
• FILE16-01 #396: file input to a real delivered result/artifact.
• BROW16-01 #397: useful modern website interaction with protected effect/disclosure semantics.

The repository graph records the remaining complete feature scope. Unpublished/unadmitted rows are planned work, not ready-for-agent or implemented features.

Complete backlog publication — 2026-11-05

The complete published backlog now has 29 new scoped tickets (#405–#433), in addition to the nine existing S16 issues including this parent. All 28 delivery rows and AC01–AC22 have owning tickets. This is publication, not implementation or parity. The machine-auditable coverage/index is docs/tickets/S16-rakazo-experience-coverage.json, with status/next-work notes in the roadmap. Native parent and blocking edges are used. No issue is closed by planning.

• [Frontier] [BASE16-01] Verify reusable upstream imports and release notices #405 — BASE16-01: Verify reusable upstream imports and release notices.
• [Frontier] [CHAT16-02] Steer active work and run an independent conversation #406 — CHAT16-02: Steer active work and run an independent conversation.
• [Frontier] [ART16-01] Find and revise delivered artifacts with isolated previews #407 — ART16-01: Find and revise delivered artifacts with isolated previews.
• [Frontier] [BROW16-01A] Prove a modern browser mediation contract #408 — BROW16-01A: Prove a modern browser mediation contract.
• [Frontier] [BROW16-01B] Complete a protected modern website workflow #409 — BROW16-01B: Complete a protected modern website workflow.
• [Frontier] [DESK16-01] Watch and take over a working computer safely #410 — DESK16-01: Watch and take over a working computer safely.
• [Frontier] [TEAM16-01] Run shared and explicitly private computers across Bots #411 — TEAM16-01: Run shared and explicitly private computers across Bots.
• [Frontier] [BOT16-01] Create and preserve a persistent Bot through its lifecycle #412 — BOT16-01: Create and preserve a persistent Bot through its lifecycle.
• [Frontier] [DELEG16-01] Finish bounded peer and temporary-worker assignments #413 — DELEG16-01: Finish bounded peer and temporary-worker assignments.
• [Frontier] [ROUT16-01] Run conversational schedules with durable review waits #414 — ROUT16-01: Run conversational schedules with durable review waits.
• [Frontier] [ROUT16-02] React to signed events and file changes without duplicate work #415 — ROUT16-02: React to signed events and file changes without duplicate work.
• [Frontier] [MEM16-01] Search, correct and forget sourced memory in the shared client #416 — MEM16-01: Search, correct and forget sourced memory in the shared client.
• [Frontier] [CONN16-01] Connect and revoke a real app through the client #417 — CONN16-01: Connect and revoke a real app through the client.
• [Frontier] [MCP16-01] Use an HTTPS MCP source under current policy #418 — MCP16-01: Use an HTTPS MCP source under current policy.
• [Frontier] [OPEN16-01] Execute a reviewed OpenAPI and GraphQL gateway source #419 — OPEN16-01: Execute a reviewed OpenAPI and GraphQL gateway source.
• [Frontier] [SKILL16-01] Import and use a pinned skill or plugin safely #420 — SKILL16-01: Import and use a pinned skill or plugin safely.
• [Frontier] [MODEL16-01] Switch approved routes with actual usage and continuity #421 — MODEL16-01: Switch approved routes with actual usage and continuity.
• [Frontier] [VOICE16-01] Dictate messages and speak replies with bounded usage #422 — VOICE16-01: Dictate messages and speak replies with bounded usage.
• [Frontier] [CALL16-01] Continue and interrupt a voice conversation safely #423 — CALL16-01: Continue and interrupt a voice conversation safely.
• [Frontier] [CHANNEL16-01] Deliver messaging attachments, results and needs-you #424 — CHANNEL16-01 closed as not planned 2026-11-06; replaced by [Frontier] [NOTIFY16-01] Remove Telegram and deliver needs-you and results through Web Push #441 — NOTIFY16-01: Remove Telegram and deliver needs-you and results through Web Push.
• [Frontier] [AUTH16-01] Run Grok-style default autonomy with in-chat approval of the human-required list #442 — AUTH16-01: Grok-style default autonomy with in-chat approval of the human-required list.
• [Frontier] [DESKTOP16-01] Package an existing-service desktop client #425 — DESKTOP16-01: Package an existing-service desktop client.
• [Frontier] [MOBILE16-01] Use a packaged mobile client with secure notifications #426 — MOBILE16-01: Use a packaged mobile client with secure notifications.
• [Frontier] [COMPUTER16-01] Enroll a second computer backend and recover portable state #427 — COMPUTER16-01: Enroll a second computer backend and recover portable state.
• [Frontier] [SPACE16-01] Search and organize authorized work across the installation #428 — SPACE16-01: Search and organize authorized work across the installation.
• [Frontier] [OPS16-01] Upgrade and recover the complete selected S16 stack #429 — OPS16-01: Upgrade and recover the complete selected S16 stack.
• [Frontier] [EVID16-01] Run the complete deterministic cross-client acceptance matrix #430 — EVID16-01: Run the complete deterministic cross-client acceptance matrix.
• [Frontier] [LIVE16-01] Collect exact-build Linux, account and native-device evidence #431 — LIVE16-01: Collect exact-build Linux, account and native-device evidence.
• [Frontier] [CUT16-01] Adopt one exact tested release with owner-reviewed rollback #432 — CUT16-01: Adopt one exact tested release with owner-reviewed rollback.
• [Frontier] [FILE16-01C] Use attached files in bounded computer work and collect output #433 — FILE16-01C: Use attached files in bounded computer work and collect output.

Next eligible scoped investigation: #408, after ordinary ownership check. Next primary implementation: #402 after ancestry/commit-contract review against draft #403/#404. All other newly published runtime slices remain needs-triage; #431/#432 need concrete artifacts and human inputs. Existing S15 #340/#341 remain separate. No source/model/import grants authority; product-default GitHub approval and the opt-in personal exception stay distinct.

Parent

None. This is the owner-confirmed S16 spec parent, not an implementation dispatch ticket.

Model tier

Frontier: complete product integration across authority, persistence, clients and protected execution requires reviewed contracts and evidence.

Context to read

AGENTS.md, CONTEXT.md, docs/agents/workflow.md, docs/specs/S16-rakazo-experience.md, retained S15 spec, ADRs 0064/0074/0075/0076/0077, docs/design/S16-rakazo-experience.md and its existing Mobbin research, the roadmap and machine-auditable coverage index.

Deliverable

The full self-hosted persistent teammate outcome in S16-AC01–AC22, preserving Jit + Schway and all retained authority/continuity requirements. The native children own concrete implementation and evidence; publication alone cannot complete this parent.

Implementation steps

1. Verify scoped child prerequisites, contracts, ownership and existing branches/PRs before dispatch.
2. Implement each vertical outcome and its deterministic composed/client evidence under the published graph; review material tradeoffs without treating old stacks as fixed.
3. Collect separately authorized real host/account/device evidence at exact artifacts.
4. Complete the exact owner-reviewed adoption/rollback and reconcile all acceptance gaps before proposing parent closure.

Acceptance criteria

• All S16-AC01–AC22 required outcomes have accepted evidence at exact builds.
• FR-01–FR-42 and NFR-01–NFR-14 retain complete, traced coverage.
• Protected credentials, sessions, source lineage and genuine human-required gates remain effective.
• Required client, computer, connection, voice, lifecycle and operational outcomes are real; no unsupported case is hidden by a feature count.
• State-preserving live adoption and rollback are separately approved and evidenced; S14 default/S15 opt-in remain unchanged unless explicitly decided.

Tests and evidence

1. Each child supplies domain-specific deterministic tests, actual client outcomes and exact contract/build evidence.
2. [Frontier] [EVID16-01] Run the complete deterministic cross-client acceptance matrix #430 supplies the complete composed acceptance matrix, including failure/restart/withdrawal and cross-client continuity.
3. [Frontier] [LIVE16-01] Collect exact-build Linux, account and native-device evidence #431 supplies real Linux/account/device evidence without promoting fixtures to live proof.
4. [Frontier] [CUT16-01] Adopt one exact tested release with owner-reviewed rollback #432 supplies exact host transition and rollback evidence; [Frontier] [EVID15-01] Prove the protected boundaries and the GitHub scenario on the tested build #340/[Frontier] [CUT15-01] Install S15 fresh on jit-vm with owner acceptance and a recoverable install #341 retain separate S15 scope.

Requirements

S16-AC01–AC22; FR-01–FR-42; NFR-01–NFR-14; retained S15 owner decisions.

Blocked by

Parent completion requires all applicable scoped deliveries and accepted evidence, including #430/#431/#432. This is aggregation, not a native blocking edge from the parent to its own descendants and not an implementation-ready label.

Contracts used/delivered

The versioned contracts owned by the scoped issues, with Jit product authority and supported public Schway engine integration. No proposed operation is made supported by editing this parent.

Out of scope

Multi-user hosted SaaS, upstream branding/marketplace operation, replacing Schway without an owner-reviewed contract, unapproved host activation and silent conversion of historical private data.

Do not

Do not grant authority from models/sources/imported tools; expose protected credentials/state/sessions to working execution; weaken the S16-D07 human-required list or let anything but the in-chat owner decision approve it; claim parity from documentation; use implement-parallel; add model attribution; self-merge or deploy.

Definition of done

All child acceptance evidence is reviewed, the coverage index and native graph reconcile, git diff --check and relevant deterministic/packaging/client checks pass, and exact live/adoption gates are accepted. Only a final reviewed completion PR may use Closes #392; planning and partial feature PRs use Refs #392. No self-merge.

Planning documents: draft PR #434, head 1297a7d1205736b3e53d286a5e89ca8ae462ca3b, stacked on #404. Publication validation: 38 S16 issues including parent, 37 native parent edges, 91 blocking edges, no cycles; all 28 rows/22 acceptance cases/56 requirements have owners. No runtime tests or implementation are claimed by this documentation-only PR.

Owner revision 2026-11-06

The owner chose Grok-style autonomy and removed Telegram: S16-D06–D11 in the spec, ADR 0084, ADR 0085. Bots act without per-action approval except the human-required list (payments/billing, Bot-initiated or unnamed-recipient messages, public posts, production deploys, destructive changes to real data outside the VM, credential/account/policy changes, first private-data disclosure to a new recipient, login/2FA handoff), approved by a one-press in-chat card. GitHub publication/merge after required checks is the product default. Trusted sites may keep sessions in the working VM browser; sensitive sites stay in the protected browser. S16-AC18 is now notifications (Web Push). Child issues carry an "Owner revision 2026-11-06" section.