Second Brain

R-Same GitHub Repo Created + Cross-Session Sync Protocol

3 min read

R-Same GitHub Repo Created + Cross-Session Sync Protocol

Decision

Codename unified R-Dash → R-Same (Law 2 Zero Ambiguity — matches repo name). GitHub repo created at github.com/ARJ-TECH/r-same (private) under ARJ-TECH org (not runwal-ai as prior memory incorrectly noted — corrected). Local path /opt/infra/r-same/. Initial commit seeds: README + STATE + working-principles + frozen-decisions (L1+L2+L3 brief) + 04-backend-plan + 6 ADRs (codename, consumption-only, local-auth, monorepo-modular-monolith, 6-wave-schedule, minimalist-Linear-aesthetic) + runbooks index + proprietary LICENSE + .gitignore. Cross-session continuity protocol: every Claude session (a) git pull, (b) reads STATE.md first, (c) scans recent commit log, (d) updates STATE.md on work completion, (e) commits with structured trailers per working-principles, (f) pushes origin. ADRs are immutable once accepted — changes produce new ADRs superseding old. docs/plan is the authoritative project record; docs/adr captures irreversible decisions; docs/runbooks holds ops procedures; vault-mcp records are cross-project context (not replaced).

Rationale

User directive 2026-04-17: “Create a GitHub repository. Call the name r-same. Ensure we can always continue our good work in various sessions by referring to the GitHub repository. Plan, current status, deliverables should be synced into the repository appropriately.” Cross-session continuity is a first-class concern for a 6-month project where no single session holds full context. GitHub as the SoT for project state is the correct pattern — survives session boundaries, agent rotations, even developer turnover. Codename unification to R-Same was Claude’s Law-2 inference (one name per concept) to prevent drift between repo name and codename; explicitly flagged to user as revertible but proceeded on “no-news-is-go” per feedback_expert_recommendations. ARJ-TECH org chosen (not runwal-ai which doesn’t exist in gh org list) — AJ has admin rights, repo private, transferable to Runwal Corp later per R&D→prod pattern.

Alternatives Rejected

Repo under personal ARJ999 account — rejected: ARJ-TECH org is more professional, transferable, and aligns with future Runwal Corp hand-off pattern.

Public repo — rejected: proprietary, internal, no open-source story v1. Private is correct.

Keep R-Dash as codename + r-same as repo name (dual-name) — rejected: Law 2 violation. Confusion across memory, commit messages, docs, UI. User said “call the name r-same” which most pragmatically means rename.

Skip ADRs, just use commit log — rejected: ADRs capture WHY with alternatives, commit messages capture WHAT. Both needed. ADRs are immutable decisions; commits are changes.

Put everything in README instead of docs/ — rejected: README is orientation; docs/ is depth. Separation improves maintainability.

Use Nx or Turbo for monorepo orchestration — deferred (not rejected): 3 apps + 4 packages don’t warrant Nx/Turbo overhead yet; Makefile + pnpm workspaces + uv workspaces sufficient. Revisit if build graph complexity demands.

Scaffold all Wave 0 files in this commit too — deferred: initial commit is docs-only for rapid cross-session continuity; Wave 0 code scaffolding is next commit, gated on user “go”.

Outcome

Pending

  • r-dash-requirements-freeze-checkpoint-1
  • r-dash-architecture-freeze-checkpoint-2
  • R-Dash Auth Amendment Local Auth v1
  • r-dash-design-direction-freeze-checkpoint-3
  • github-org-arj-tech-not-runwal-ai
  • r-same-cross-session-continuity-protocol
  • r-same-github-org-is-arj-tech-not-runwal-ai
  • r-same-project-location-state-and-wave-status
  • github-org-is-arj-tech-not-runwal-ai
  • state-md-pattern-for-cross-session-continuity
  • uv-over-pip-for-python-2025-projects
  • cross-session-continuity-via-state-md-git-pull-pattern
  • r-same-cross-session-continuity-via-state-md
  • r-same-expert-delegation-principle-tactical-self-approve
  • r-same-state-md-cross-session-continuity-protocol
  • arj-tech-is-the-accessible-github-org
  • r-same-repo-and-infra-location
  • state-md-cross-session-continuity-protocol
  • code-complete-does-not-mean-deployed-running
  • taskflow-pwa-rebuild-single-org-runwal-architecture-decision

Graph View

Backlinks