Tyrell to replicantDB reuse map

Created and committed a Tyrell-side, evidence-backed architecture reuse map plus a pointer-only replicantDB handoff. This gives the separately owned replicantDB lane concrete contracts and acceptance criteria without changing replicantDB source, services, data, or ownership.

Scope

• Host: rdmsm4x
• Tyrell documentation worktree: /Users/richh/dev/_worktrees/tyrell-replicantdb-reuse
• Branch: codex/tyrell-replicantdb-reuse
• Commit: 4a30a6381a237e653487d38d8686e77c9414604a
• replicantDB canonical root was read-only: /Users/richh/dev/apps/replicantDB
• No runtime, deployment, database, credential, private file content, or user-file mutation occurred.

Files changed

• /Users/richh/dev/_worktrees/tyrell-replicantdb-reuse/docs/architecture/2026-08-28-tyrell-replicantdb-reuse-map.md
• /Users/richh/dev/_worktrees/tyrell-replicantdb-reuse/.handoff/replicantdb-reuse-handoff.md
• /Users/richh/.agent-coordination/checkins/codex-rdmsm4x-tyrell-replicantdb-reuse-20260828.json
• /Users/richh/dev/LLM/Claude/changelogs/rdmsm4x-changelog-20260828-1227-tyrell-replicantdb-reuse-map.md

What landed

• Reuse classification separating safe patterns, candidate shared packages, Tyrell-only behavior, and replicantDB-only domain logic.
• Typed headless command/control vocabulary for scan, OCR, labels, deduplication, movement/transfer, status, and cancellation.
• Authenticated/idempotent envelopes, scoped authority, operation progress, validation evidence, rollback, and durable-receipt boundaries.
• Target/server-folder transfer design with discovery/authentication separation, path-aware budgets, content-addressed resume, destination verification, and separately authorized source retirement.
• Local intelligence map covering deterministic fallback, Foundation Models, Core ML, Core AI, and MLX/MLX Swift as advisory providers behind a sanitizer and compiled action catalogue.
• Compatibility/version policy, extraction sequence, risks, stop-loss conditions, and acceptance tests.
• Secure-chat research consumed at commit cb31e73cb79ead2663146d209b5c6ef3313ae0ca for process, credential, and protocol-boundary guidance.

Commands and evidence

• Read the mandatory global/project coordination records and published the bounded one-writer check-in.
• Verified host identity as rdmsm4x and repository/worktree HEAD and dirty state with read-only Git commands.
• Inspected Tyrell and replicantDB source and project records with rg, sed, and read-only Git operations.
• Verified the four research worktrees at their recorded commits and SHA-256 report hashes.
• Ran fleet check-in and fleet-message synchronization; five peers were reachable and rdmpw3265m was unavailable during the initial sync.
• Ran git diff --check, Markdown code-fence balance, required-topic coverage, targeted secret-term review, staged-file review, and post-commit clean-worktree verification.
• Committed the two documentation artifacts as 4a30a6381a237e653487d38d8686e77c9414604a.

Coordination and handoff state

• No current, clearly identified replicantDB peer appeared in the unread fleet-bus inbox during this lane.
• The pointer is prepared in .handoff/replicantdb-reuse-handoff.md but was not guessed, dispatched, received, accepted, or integrated.
• The active replicantDB UI owner/worktree was observed and left untouched.

Verification and rollback

• Tyrell documentation branch was clean immediately after the commit.
• Canonical Tyrell remained untouched except for its pre-existing .DS_Store dirt.
• Canonical replicantDB remained clean and was never mutated.
• To undo the Git change, create a normal revert of commit 4a30a6381a237e653487d38d8686e77c9414604a in the documentation lane; do not rewrite shared history.

Outstanding owner actions

• The Tyrell lead may integrate or otherwise consume commit 4a30a6381a237e653487d38d8686e77c9414604a.
• Once a current replicantDB owner identity is verified, dispatch the concise pointer and request corrections/acceptance without implying receipt.
• replicantDB owners must explicitly decide package ownership, command schema, authentication/device identity, process topology, numeric budgets, and mutation rollback before implementation.
• Apple Notes publication was attempted with notes_changelog.zsh and is pending because this Codex session runs under launch manager Background, not Aqua; the tool refused before sending AppleEvents. The required Markdown archive is present at this path and the exact GUI-session command was reported by the tool.