[Frontier] [DOC16-01] Record Rakazo adoption scope, source provenance and the complete delivery graph #393

Parent

S16 #392 — #392

Model tier

Frontier: reconciles a broad owner-confirmed product target with existing authority, state, engine and upstream licensing boundaries.

Context to read

AGENTS.md, CONTEXT.md, docs/agents/workflow.md, docs/product/02-prd.md, S15, ADRs 0064–0073, #392, and pinned Rakazo abf3c08145a05cba92a912d6c24fdfb5f569d0e0 LICENSE/VISION/README and relevant source.

Deliverable

Owner-confirmed S16 product scope, ADR 0074, an evidence-aware complete feature/delivery graph, source-reuse inventory, and synchronized current-target pointers. Separate confirmed outcomes from engineering proposals and shipped behavior. No runtime/default/cutover changes.

Implementation steps

1. Pin the Rakazo source and inspect license/NOTICE and module boundaries without running its scripts.
2. Write docs/specs/S16-rakazo-experience.md with observable acceptance, FR/NFR mapping and retained product boundaries.
3. Write ADR 0074 covering selective reuse, Schway public seams, protected resources and license distribution.
4. Map every self-hosted reference feature to vertical slices and actual prerequisites in docs/tickets/S16-rakazo-experience-roadmap.md.
5. Update CONTEXT.md, AGENTS.md and product/index pointers in English; retain S15 implementation/evidence and S14/legacy compatibility.
6. Publish narrow follow-up issues after ownership/PR checks; no broad spec parent receives ready-for-agent.

Acceptance criteria

• Owner direction and chosen Jit + Schway integration are recorded accurately.
• Files, browser/desktop, connections/MCP/plugins/skills, Bots/delegation/routines/memory, voice, native clients, computer backends and operational continuity all have owning slices.
• Each capability has observable acceptance and evidence requirements; code presence is not live proof.
• Apache-2.0 license/notice/modified-file obligations and upstream source pin are explicit; Jit identity and existing MIT code are retained.
• Existing FR-01–FR-42/NFR-01–NFR-14 IDs and protected gates remain intact.
• No S14/legacy store, live installation, policy/budget or runtime default is changed.
• Required owner-designated UI/UX authoring (S16: Astra/high with detailed Mobbin MCP research) is a named dependency.

Tests and evidence

1. Verify current GitHub ownership and open PRs before editing.
2. Check all relative links, acceptance-to-slice coverage and acyclic direct prerequisites.
3. Compare current-target statements against S15 implementation/evidence and [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.
4. Run git diff --check.

Requirements

FR-01–FR-42; NFR-01–NFR-14. S16 product baseline and all acceptance cases.

Blocked by

None for bounded documentation work. Required UI/UX is separately authored; this ticket does not author it.

Contracts used/delivered

Uses implemented S15 contracts and supported Schway public host surface. Delivers the S16 requirement baseline and selective-reuse decision; no executable API is claimed.

Out of scope

Runtime code, UI/UX design, data conversion, live tests, activation, billing, replacing Schway, executing upstream scripts.

Do not

Do not weaken protected gates, import credentials, claim product parity from source presence, use implement-parallel, add model attribution, or merge this PR yourself.

Definition of done

Documentation checks and git diff --check pass. PR body Closes #393. The S16 parent stays open until actual delivery and evidence.

Complete backlog publication — 2026-11-05

The complete graph is now published as #405–#433 and recorded in the roadmap/coverage index. Existing documentation/design remain implemented on draft #398; this planning extension does not merge that PR or claim acceptance.

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.