One Repo

Sidekick's code lives in mehtapratik/sidekick and its docs live in mehtapratik/arkive, joined by a docs symlink and an install script that clones Arkive. Every change that touches code and the docs that describe it takes two PRs, two reviews and two merges, and the two can land out of step. The public face is split too: the docs and writings are on arkive.blog under a name the project no longer uses, and the App has no address of its own.

This PRD moves everything into one repo and gives the project one domain. Arkive's docs, writings and site move into mehtapratik/sidekick with their full history, and the site is rebuilt as the Sidekick public site at ossidekick.com. Docs, writings, the AI harness, source code and other artifacts then sit side by side, and a change and the docs it makes false land in the same PR.

It is part of Synergy's Phase 3 because Synergy is the first phase built in the open: the lessons are recorded live, and one repo and one site make that work visible in one place. The build-facing rules are in the spec's One Repo section; the steps are in Lesson 0 and the site lessons of the Synergy plan.

Goals

• Repo. One repo holds every artifact, with every commit Arkive ever had.
• Domain. One domain is the project's public face: the site at the apex, the App on a subdomain.
• No broken links. Every published URL keeps working, through the move and through the cutover.
• Learning. Pratik types every change, in content/ and apps/www/ as much as in the root config, so Pratik knows what Sidekick's configuration gained. The coach explains each step and never edits the implementation.

The repo

• D213 decision #one-repo #git: mehtapratik/sidekick is the one repo. It takes Arkive's full history (rewritten with git filter-repo) through a single merge commit, the only merge commit on main, and mehtapratik/arkive is archived, not deleted, so its PR links keep working.
• D214 decision #one-repo #monorepo: The vault lives in content/docs/, the writings in content/writings/, and the public site in apps/www/. The App's apps/web is renamed apps/app, so each app folder is named for the address it serves, and every app takes the @sidekick/ scope (@sidekick/www, @sidekick/app). apps/ and packages/ stay as the parent folders, and the root AGENTS.md points into content/docs/.
• D215 decision #one-repo #deployment: content/ is a workspace package, @sidekick/content, that the site depends on. Vercel's Skip deployment setting then leaves the App unbuilt for commits that touch only content, and Turbo rebuilds the site when content changes. A content label marks PRs whose files are all under content/.
• D216 rule #one-repo #formatting: content/ stays out of Prettier. Obsidian writes the vault, and half its files fail Sidekick's Prettier config. The site's files follow the root config, except the files the site ships as given.
• D217 decision #one-repo #licence: The root LICENSE stays MIT and covers the code. content/LICENSE holds CC BY-NC 4.0 and covers the writings and docs, and the README's Licence section says which is which. Fonts keep their own licences, next to the font files.

A change that makes a doc false fixes that doc in the same PR. Lessons still end with Pratik's code PRs and then one coach docs PR, now in the same repo.

The domain

• D218 decision #one-repo #domain: ossidekick.com is the project's domain. The public site serves its apex, www.ossidekick.com redirects to the apex, and the App gets app.ossidekick.com, a DNS-only CNAME to Vercel. Both move there on the same day, the cutover, after the redesign ships. Until then the site stays on arkive.blog and the App on sidekick-six-bay.vercel.app.
• D219 decision #one-repo #app: The public site shows no link to the App until Open House. The App serves one person until then, so a public link would only lead to a sign-in nobody else can use. Supabase sign-up is off for the same reason. derived-from D1
• D220 decision #one-repo #deployment: The public site runs on a Cloudflare Worker with static assets, sidekick-www, built by Workers Builds from the repo root, with a public preview for every branch. Its settings live in apps/www/wrangler.jsonc, so they are reviewed in a PR. A later ossidekick.com/app route could be a script on the same Worker.
• D221 rule #one-repo #urls: No published URL changes. Moving the repo, rehosting the site, redesigning it and moving the domain must each leave every path in sitemap.xml resolving, and a diff of the sitemap paths before and after is the test.
• D222 decision #one-repo #domain: The cutover has no downtime. ossidekick.com is added beside arkive.blog on the Worker first; only then does arkive.blog become a 301 to the same path and query on ossidekick.com, tagged from=arkive.blog. Visitors who arrive through the redirect see a one-line notice that the site moved. arkive.blog redirects for one year and then lapses.

The new site

The site is redesigned from the design handover, a throwaway prototype in the project's shared files (one-repo/design/HANDOVER.md, tokens.css, plates.mjs, reference/). It is never committed. It keeps the content pipeline (vault.mjs, entries.ts, tree.ts, the plugins), the publish: true gate, the privacy and datum gates, retired entries, slugs and "As of", and replaces the chrome, the stylesheet, the script and the code colours. The Arkive name is retired.

Where the handover and this PRD disagree, this PRD wins:

• Typefaces: arkive.blog's three faces, already in public/fonts/: General Sans for headings and interface text, Sentient for reading text (weight 400) and the wordmark, IBM Plex Mono for code, dates and versions. No new fonts (Pratik, 2026-11-04). Colours, layout and plates are unchanged.

• One breakpoint for the phone chrome (D223), at 58rem, not the handover's 40rem.

• Theme control: one button that cycles System, Light and Dark, not a three-button group.

• Contents below the breakpoint: the docs tree takes the whole viewport, not a 332px slide-over with a scrim.

• No App link in the header or the Menu (D219).

• Milestone tiles come from the phase plans (D224), not from 04-plans/ file names.

• RSS carries Writings only (D225).

• D223 rule #one-repo #css: The site uses no media queries for layout, with one exception: a single width breakpoint, @media (width < 58rem), which only swaps chrome (the header nav and theme control move into the Menu, the docs tree gives way to a Contents view, the / hint hides). Media queries are otherwise allowed only for prefers-color-scheme, prefers-reduced-motion and hover. Everything else adapts intrinsically, and a component that adapts to its own column uses a container query.

• D224 decision #one-repo #site: The home page's "Where things stand" shows one tile per phase, read from each 04-phases/NN-name/00-plan.md: order and label from NN, title and status from frontmatter. completed is done, deferred is deferred, the first other phase is up next. Sub-plans get no tile and appear under their phase in the "All phases" list.

• D225 decision #one-repo #site: /rss.xml carries Writings only, newest first by created, with the summary as each item's description. There is no docs feed until someone asks for one. derived-from D2

• D226 rule #one-repo #glossary: Project vocabulary lives in content/docs/07-glossary/, one page per term. When a skill asks for CONTEXT.md, the agent writes or updates the glossary page instead, and no CONTEXT.md is created.

• D227 decision #one-repo #content: An entry that needs UI Markdown cannot express uses a static React component, written as a sidekick:<name> fenced block with YAML props in plain .md and rendered to HTML at build time. There is no MDX until an entry needs an interactive island; adding it later costs what it costs now. Components are plain React styled with CSS modules and the variables in tokens.css, which moves into @sidekick/ui as the one token source. derived-from D47 derived-from D2

How it ships

1. Lesson 0: One repo, at the start of 3a, before lesson 1, so lesson 1's git mv work and the recordings happen in the merged repo. Five PRs and a hosting step. It ends with arkive.blog serving the current site from the sidekick-www Worker, built from Sidekick's main.
2. Site lessons S1 to S7, after Checkpoint 3a and before 3b (Pratik, 2026-11-05), which build the new site from the handover and end with the cutover to ossidekick.com. The Synergy plan lists them.

Lessons 1 to 13 keep their numbers.

How it was decided

Charted on the one-repo wayfinder map and settled ticket by ticket between 2026-11-03 and 2026-11-05. The map and its tickets are retired and stay as the record: One Repo: Wayfinder Map. The research behind tickets 01 to 03 is in the project's shared files (one-repo/research/).

Out of scope

• App features, and any change to the App beyond its folder name and its address.
• Changing any published URL (D221).
• A docs feed, MDX, interactive islands in content, and a Mantine theme for the site.
• ossidekick.com/app. The App lives on its subdomain.