[CHESS P0] Activate isolated chess programme and shared editor header contract

[spikeal8-maker]

Outcome

Activate an isolated ASA Chess delivery programme without changing or coupling Electronics, 3D, future Checkers or generic ASA Lab subject boundaries.

This is the programme-entry task for the revised plan published in #65. It is planning/governance scope only until the owner performs the execution-state transition.

User-visible direction

The first accepted product release after P0 will be:

play a calibrated ASA bot
→ receive verified Game Review
→ retry the key mistake
→ train the generated position
→ receive a lesson recommendation

Required scope

• create a dated Chess.com-to-ASA scenario ledger;
• classify scenarios as required, extended or deferred;
• define R1 task IDs and dependencies;
• define focused and browser gates for R1;
• define additive, tenant-scoped data ownership;
• define Chess and future Checkers isolation from other modules;
• characterize the existing Electronics top header before extracting shared editor chrome;
• specify a shared header contract covering ASA mark/back action, title, save state, named modes, avatar and optional module toolbar;
• prove that shared-shell work does not change Electronics behaviour;
• add feature flags and rollback requirements;
• publish owner evidence requirements for desktop, tablet and mobile;
• update execution manifest, project map and test catalog only during the explicit owner transition.

Non-goals

• no Chess product code on the active 3D branch;
• no changes to Electronics behaviour or owner assets;
• no destructive migrations;
• no Checkers implementation inside Chess;
• no copying Chess.com branding, source, content, avatars or proprietary algorithms;
• no automatic activation of R1.

Proposed module boundary

contexts/chess             standard chess domain only
contexts/chess-live        authoritative live chess only
contexts/chess-analysis    engine and review orchestration
contexts/chess-training    puzzles and practice
contexts/chess-learning    lessons and learning progress
contexts/chess-competition tournaments and puzzle competition
contexts/chess-fair-play   chess policy and moderation signals

Generic ASA contracts remain owned by Account, Workspace, Project, ProjectVersion, Classroom, Assignment, Submission, Grade, Badge, Moderation and Audit.

Header acceptance contract

• same 48px primary-row geometry and information hierarchy as Electronics;
• same ASA Lab mark/home affordance;
• editable project title;
• saved/saving/error state including actionable error text;
• named module modes and account avatar;
• keyboard and responsive behaviour;
• optional second 48px chess toolbar;
• Chess-specific actions supplied through slots/configuration, not hard-coded into Electronics;
• characterization tests pass before and after extraction.

Definition of done

• [CHESS MODULE PROGRAM] ASA Chess — game, analysis, puzzles, classroom and fair play #65 links to this task;
• the parity ledger is reviewable on GitHub;
• R1 issues have bounded scopes and dependency order;
• planned tests are published but not falsely reported as executed;
• isolation and header contracts have owner acceptance;
• owner performs a separate transition from the current task into this task;
• pnpm control-plane:check passes on the transition SHA.

Current blocker

docs/execution/current.yaml currently assigns TASK-3D-M0-001 / PR #95 to execution lease holder codex-three-d-m0. This task stays blocked and read-only until the owner completes or pauses that task and publishes the new execution state.

[spikeal8-maker]

Parallel P0 audit — concrete isolation and workstream result

Three independent read-only streams reviewed R1 parity, the Electronics-family header and module isolation while the active 3D checkout remained untouched.

Safe parallel workstreams after owner activation

Stream	Owns	Must not touch
A — Shell/isolation	neutral EditorChrome, Chess adapter, Electronics characterization	engine, bot logic, Review rules
B — Engine	chess-analysis, worker/server adapters, cache/job tests	React shell, bot personalities
C — Bots	bot profiles and calibration harness	Review UI, shared core
D — Review/training	review model/UI, generated drills, lesson mapping	Electronics, engine internals

Every writer uses a distinct worktree and branch. Shared exports, router, workspace config, execution state and final wiring belong only to the integration lease holder.

Newly confirmed architecture gaps that P0 must close

1. eslint.config.mjs lacks explicit context:electronics and context:projects boundary rules.
2. tools/validate-context-boundaries.mjs omits Electronics and Projects.
3. Chess, Electronics and 3D UI currently live in one web Nx project, so subject-UI imports are not enforceable by Nx alone.
4. API ModuleRegistry, web editor-loader map and the database projects.module_key allowlist are independent and may drift.
5. ProjectsController.provider.analyse() is synchronous; Stockfish/Game Review must use a separate analysis job context and never run in project open/save.

Required target boundaries

packages/ui-kit            neutral EditorChrome only
contexts/chess             rules/document/local chess
contexts/chess-live        live games; may import public chess exports
contexts/chess-analysis    engine/review; may import public chess exports
contexts/chess-training    puzzles/training; may import public chess/analysis contracts
contexts/checkers          separate future domain and document
contexts/electronics       Electronics only
contexts/three-d           3D only
apps/web + apps/api        composition roots only

Forbidden dependency tests must reject Chess↔Electronics, Chess↔3D, Chess↔Checkers, Checkers→Chess, Projects/Classroom→any subject and one subject UI→another subject UI. Deep imports outside declared package exports must fail.

Do not create a generic shared board-game domain. Only proven presentation primitives may later enter ui-kit.

Planned gate IDs

TST-MODULE-ISOLATION-001
TST-MODULE-BOUNDARY-NEGATIVES-001
TST-MODULE-PUBLIC-EXPORTS-001
TST-MODULE-REGISTRY-PARITY-001
TST-MODULE-ROUTE-PARITY-001
TST-EDITOR-CHROME-CONTRACT-001
TST-ELECTRONICS-HEADER-REGRESSION-001
TST-SUBJECT-UI-LAZY-001
TST-MODULE-DB-ALLOWLIST-001
TST-SUBJECT-RLS-001
TST-CHECKERS-NO-CHESS-DEPENDENCY-001

Header contract

Electronics is the characterization baseline, not a dependency. Chess must never import WorkbenchHeader or Electronics CSS. A neutral EditorChrome supplies ASA mark/back, project title, save state, named modes, avatar and an optional second-row toolbar slot. Electronics behaviour is frozen with DOM, keyboard, geometry and desktop/mobile evidence before extraction.

Governance status

A separate local plan worktree now exists at /home/spike/work/asa-lab-chess-program-plan on agent/chess-program-plan; it contains documentation drafts only. They are not pushed as a PR because pnpm gate:governance correctly rejects a second branch while current.yaml names active 3D M0. The plan stays visible here in GitHub Issue #97 until the owner transition; the governance gate will not be weakened to force a parallel PR green.

[spikeal8-maker]

ASA Chess R1 — dated functional-parity ledger

Reference cut: 2026-08-11
Programme: Issue #65
Activation package: Issue #97

Parity in this ledger means an independently implemented equivalent user outcome. It
does not mean copied design, wording, formulae, branding, source code or assets.

Status vocabulary

not_started
foundation
functional
production_proven
owner_accepted

MUST P0 blocks R1 implementation. MUST R1 blocks the Learning Beta release.
DEFER records a visible gap without expanding R1.

P0 contracts

ID	Scenario or contract	Priority	Acceptance	Current status
P0-01	Dated feature ledger	MUST P0	Every row has source, release, issue, test, evidence and status	foundation
P0-02	Parallel agent work	MUST P0, ASA	Separate worktree/branch/scope per writer; one integration lease; no overlapping file ownership	foundation
P0-03	Chess isolation	MUST P0, ASA	moduleKey=chess; no imports from Electronics, 3D or Checkers; shared core imports no Chess	foundation
P0-04	Future Checkers isolation	MUST P0, ASA	Future moduleKey=checkers; no Checkers types or mode switches in Chess documents/APIs	foundation
P0-05	Electronics-family header	MUST P0, ASA	48 px header + optional 48 px toolbar; ASA mark, title, save state, named modes and avatar	not_started
P0-06	Electronics preservation	MUST P0, ASA	Characterization first; post-extraction DOM, keyboard flow and shell geometry remain equivalent	not_started
P0-07	Shared-core and data safety	MUST P0, ASA	No Chess fields in shared core; cross-tenant access denied; sibling smoke journeys pass	foundation
P0-08	One R1 focused gate	MUST P0	Same command locally, in CI and owner evidence; evidence uses NX_SKIP_NX_CACHE=true	not_started

Known visual gap: the current Chess header uses its own min-height: 64px geometry;
Electronics uses a 48 px primary row plus a separate 48 px toolbar.

R1 engine

ID	User outcome	Priority	Acceptance	Source	Status
ENG-01	Quick and deep post-game analysis	MUST R1	Benchmark for 60 plies fixes quick/deep p95 budgets before coding	Game Review	not_started
ENG-02	Responsive local analysis and durable server analysis job	MUST R1	Worker keeps UI responsive; job supports progress/cancel/retry and idempotent recovery	Engine docs	not_started
ENG-03	Evaluation and Multi-PV	MUST R1	All moves legal; at least three Self Analysis lines; mate and centipawn scores distinct	Analysis	not_started
ENG-04	Reproducible evidence	MUST R1	Engine/NNUE hashes and parameters recorded; deterministic mode repeats exactly	ASA	not_started
ENG-05	Version-safe cache	MUST R1	Key includes FEN, engine, NNUE, settings and Multi-PV	ASA	not_started
ENG-06	Tablebase and complete Explorer	DEFER R2	Gap remains visible	Analysis	not_started

R1 bot play

ID	User outcome	Priority	Acceptance	Source	Status
BOT-01	Choose bot, White/Black/Random and timed/untimed play	MUST R1	Every combination starts a legal unrated game and persists settings	Bots	foundation
BOT-02	Twelve original profiles	MUST R1	4 beginner, 4 intermediate, 3 advanced, 1 adaptive; profile records style, repertoire, error and time model	Bots	not_started
BOT-03	Calibrated strength	MUST R1	At least 1,000 reference games/profile; 95% CI inside declared band; median target error ≤75 Elo	ASA	not_started
BOT-04	Distinguishable style	MUST R1	Two measurable style signals/profile; blind expert identification ≥70%	ASA	not_started
BOT-05	Assisted and challenge policies	MUST R1	Evaluation, arrows, hint, feedback and undo follow policy; used assistance is stored	Bots	foundation
BOT-06	Save game and open exact Review	MUST R1	Refresh preserves result, assistance, clocks and moves; Review reads exact version	Bots/Review	foundation
BOT-07	Crowns, 100+ profiles and seasonal/celebrity bots	DEFER	R1 never claims catalogue parity	Bots	not_started

R1 Game Review

ID	User outcome	Priority	Acceptance	Source	Status
REV-01	Open Review after game or from archive	MUST R1	Both routes return one versioned review; reopening does not re-run silently	Game Review	foundation
REV-02	Evaluation/time graphs and factual summary	MUST R1	One point per ply; selecting a point selects the same position	Game Review	not_started
REV-03	ASA Quality 0–100	MUST R1	Original formula documented and versioned; golden corpus; never named CAPS/Accuracy	Accuracy	foundation
REV-04	Move classifications	MUST R1	Original deterministic ASA labels cover book, error, missed chance and strong move; every line legal	Classification	foundation
REV-05	Navigate all moves and key moments	MUST R1	Mouse, touch and keyboard select identical positions; Next skips no marked moment	Game Review	foundation
REV-06	Show line, best move, Retry and Hint	MUST R1	Retry uses exact pre-error FEN; incorrect move never passes	Game Review	not_started
REV-07	Understand the mistake	MUST R1	Explanation cites verified engine line and formal motif; zero unsupported claims in corpus and 100 manual samples	Game Review	not_started
REV-08	Review White, Black or Both and persist settings	MUST R1	Settings affect presentation without mutating stored analysis	Game Review	not_started
REV-09	Self Analysis and continue against bot	MUST R1	Exact FEN/turn/castling/en-passant transferred; original game immutable	Analysis	not_started
REV-10	Save comments and variations	MUST R1	New exact ProjectVersion created; source version immutable	Analysis	not_started
REV-11	Coach audio, multiple coaches, proprietary performance rating, manual cloud controls	DEFER	No fake or disabled parity claim	Game Review	not_started

R1 mistake-to-training

ID	User outcome	Priority	Acceptance	Source	Status
TRN-01	Train this mistake	MUST R1, ASA	Private drill uses exact pre-error FEN and links game/version/move	ASA differentiator	not_started
TRN-02	Solve against automatic defence	MUST R1	Same engine version validates accepted tree; equivalent solutions accepted	Puzzles	foundation
TRN-03	Progressive hints	MUST R1	Motif → candidate piece/square → move; attempts and hints recorded	Puzzles	foundation
TRN-04	Relevant starter lesson	MUST R1	Every supported motif maps to a published original ASA lesson	Lessons	not_started
TRN-05	Rated puzzle database, streak, Daily, Rush, Battle and Custom	DEFER R2+	Three current static tasks are not called parity	Puzzles	not_started
TRN-06	Publish user position to shared corpus	DEFER	Requires consent, provenance, moderation and quality pipeline	ASA	not_started

The personal mistake drill is an ASA workflow. It may be described as an original
extension, not as proven exact Chess.com parity.

R1 evidence gate

ID	Required evidence
R1-E2E-01	Desktop 1440×900: bot → game over → Review → Retry → drill → lesson
R1-E2E-02	Mobile 360×800: same journey without inaccessible controls or horizontal overflow
R1-E2E-03	Keyboard-only: start, moves, Review navigation, Retry and drill with visible focus
R1-E2E-04	Zero unexpected console errors, HTTP 5xx and illegal engine moves
R1-E2E-05	Reload at every transition restores the exact saved version
R1-E2E-06	Electronics, 3D and generic Project smoke gates remain green
R1-E2E-07	Licence manifest covers engine, NNUE and all bot/lesson art and content
R1-E2E-08	Release wording is only “R1 learning-loop functional parity” after owner acceptance

Parallel streams after P0 activation

Stream	Owns	Must not touch
A — shell/isolation	shared editor shell, Chess header adapter, characterization tests	engine, bots, Review rules
B — engine	chess-analysis, worker/server adapters, cache/job tests	React shell, bot personalities
C — bots	bot profiles and calibration harness	Review UI, shared core
D — review/training	review model/UI, generated drills and starter lesson mapping	Electronics, engine internals

Shared exports, router, workspace configuration, execution documents and final wiring
remain integration-owner files.

Official references

• Play against Chess.com bots
• Game Review
• Self Analysis
• Game Review on mobile
• Chess engines
• Move classifications
• Accuracy/CAPS2
• Puzzle provenance
• Puzzle modes

[spikeal8-maker]

Implementation coordination status — 2026-08-11

The owner requested Chess implementation in parallel with the separate Checkers bot. Worktrees and source ownership are already separated, and the Checkers executor confirmed it will not touch apps/web/src/chess/**, contexts/chess/**, contexts/chess-live/** or the Chess P0/R1 documents.

Canonical origin/main currently names:

task: TASK-CHECKERS-M1-001
branch: agent/checkers-education-m1
execution lease holder: codex-checkers-m1

Therefore the existing single-writer governance contract still makes this Chess task read-only. Product Chess code cannot honestly start merely because a second worktree exists.

Two valid owner choices remain:

1. preserve the single lease: finish/pause Checkers, then transition to Chess P0;
2. explicitly authorize a governance change to scoped parallel lanes, with separate task/branch/worktree/file ownership and one integration owner for shared files.

No Chess product code has been written under the Checkers lease. The plan worktree and commit 5a56233 remain isolated and ready.

[spikeal8-maker]

Implementation started. Public Chess product Draft: #103 (plan and isolation contract at 3473ec9). Parallel coordination: Checkers remains in #101 and owns contexts/checkers plus Checkers UI; Chess owns contexts/chess, contexts/chess-live, Chess UI, and the new neutral editor-header directory; Electronics and 3D product files remain untouched. A separate additive governance change will register both active lanes, enforce non-overlapping path scopes, retain Checkers as shared integration owner, and protect current.yaml from both product branches. First code slices running in separate worktrees: 48px ASA EditorHeader adapter for Chess and engine analysis contracts/orchestration without bundling Stockfish yet. External Stockfish remains gated on a pinned GPL artifact manifest, exact corresponding source, and reproducibility evidence.

[spikeal8-maker]

Implementation checkpoint published in Draft PR #103 at bb97f3a. Delivered: public R1 plan/ledger, isolated schema-1.1 Chess lane, neutral 48px ASA EditorHeader integrated into Chess, and engine-analysis contracts/orchestration/cache validation. Final uncached focused gate PASS: 81 Chess tests, 64 Chess Live tests, contracts, typechecks, and context/database/web builds. Isolated browser gate PASS 5/5 for save/version, bot reply, puzzle, direct challenge, and rated matchmaking. Test stack/volume removed; persistent 4610/4611 stayed healthy. Remaining planned slices are explicitly not claimed complete: production Stockfish artifact/licensing, calibrated bots, content pipeline, deep Game Review jobs, and realtime WebSocket/premove.

[spikeal8-maker]

Chess R1 implementation checkpoint published in Draft PR #103.

Exact head: cf11258

Delivered in this checkpoint:

• honest ASA Lite engine adapter on the versioned analysis contract;
• 12 original bot-profile records with deterministic seeded policies and explicit not-calibrated status;
• canonical FEN before/after every reviewed ply and verified best root;
• selectable one-point-per-ply Review timeline;
• exact pre-error Retry that rejects a different legal move, provides 3 progressive hints, and preserves the source game;
• private in-memory mistake-training item foundation;
• public Chess exports and updated R1 execution plan/parity ledger;
• browser coverage for error -> Review -> wrong retry -> hint -> verified solution.

Evidence:

• focused Chess R1 gate PASS: 106 Chess tests, 64 Chess Live tests, all focused contracts/typechecks/builds;
• UI contracts 10/10 PASS;
• architecture validation PASS: 31 rules and 10 decisions;
• isolated browser journeys 6/6 PASS (4 Chess, 2 Chess Live);
• Chess-only scope confirmed; Checkers, Electronics, and 3D product files unchanged;
• isolated stack/database removed; persistent 4610/4611 stack healthy.

Still intentionally open: production Stockfish worker/server job and GPL artifact manifest, persisted review/training jobs, full PV/time graph/motif explanations, lesson mapping, and empirical bot calibration. PR remains Draft and does not claim complete Chess.com parity.

[spikeal8-maker]

ASA Chess R1 checkpoint — da8e9e3

Published the next hardened Chess learning-foundation checkpoint to Draft PR #103 on exact SHA da8e9e37b11b16d33550bb7e04468e267e7c94c4.

Delivered in this checkpoint:

• selectable persisted ASA bot profiles with truthful non-calibrated policy labels;
• canonical per-ply Review navigation and verified fact-only explanations;
• mate wording separated from the private centipawn sentinel;
• exact pre-error retry with hints/reset;
• authenticated, idempotent private training history with authoritative version provenance;
• hardened analysis-job foundation: authoritative requester partition, explicit enqueue outcomes, worker-bound expiring claims, race-safe cancellation cleanup, strict repository identity checks, and bounded whitelist-only engine results;
• updated public execution plan and remaining-gap wording.

Verification on the exact SHA:

• gate:chess-r1 PASS: 146 Chess + 64 Chess Live tests, contracts, typechecks and fresh web/database/package builds;
• Chess UI 12/12 PASS;
• full lint 22 projects, boundaries, format and GitHub-aware control-plane PASS;
• isolated full-image browser run 6/6 PASS in 34.2s (Chess 4/4 + Chess Live 2/2);
• permanent dev stack 4610/4611 remained healthy; isolated stack and artifacts were removed.

Independent read-only cross-review found no remaining P0/P1 in the hardened analysis/training slices.

GitHub-hosted jobs remain externally blocked before project steps (steps: []) by Actions billing; local executed evidence is recorded in the PR. The PR remains Draft. Complete Chess.com parity is not claimed: production workers/persistence, calibrated bot evidence, deeper lines/time graph, verified motifs, lesson recommendations, responsive owner evidence and Stockfish GPL artifact provenance remain open.

Plan: https://github.com/spikeal8-maker/asa-lab/blob/agent/chess-r1-foundation/docs/product/ASA_CHESS_EXECUTION_PLAN.md
PR: #103