Six projects, one working directory each.

The agent finds .claude/ where it expects it, and the public remote never sees it.

.claude/skills stays one symbolic link. GitOne owns the link itself and never walks through it to invent paths below the alias.

The link and its target belong to the same repository, which is the rule that makes the alias safe.

push: disabled makes gitone push skip ops and refuse it as an explicit target. There is no flag that publishes it anyway.

protected_paths is a hard deny that beats ownership: .env can never be staged, not even by the repository whose pattern covers it.

require_clean_worktree refuses a push while anything is staged, unstaged or untracked, so you never publish half a change.

Remotes are configured per repository. Public work on GitHub, client work on your own host, no third tool in between.

clients exists only in .gitone.local.yml, which is never committed - so a clone of the portfolio cannot even learn that the repository exists.

A new file under clients/ that no pattern covers stops every command with PATH001 instead of drifting into the portfolio.

The workflow stays a normal workflow. It checks out web, which never contained infra/, so no step has to know that GitOne exists.

The check that is worth automating runs where both repositories are still one directory: your machine, before the push. gitone doctor is read-only, so it is safe at any time.

gitone in a CI checkout has nothing to manage - that checkout is a single ordinary repository with a root .git/, which is exactly the shape GitOne refuses to touch. Run the gate locally, not in the pipeline.

machine has no remote at all. It is a real Git repository with real history that simply never leaves the laptop; only pushing it would fail.

**/*.key is protected at any depth, so a key file cannot be staged even if it lands inside a directory the public repository owns.

One directory means one source ~/.config/shell/aliases.sh. Nothing has to be symlinked together from two checkouts.

Every push validates the outgoing commits and the resulting tree it produces, so an asset cannot reach the public remote through a rename, a merge or a stray git add.

The two repositories have independent histories. Rewriting the asset repository never touches the engine, and a contributor cloning the engine gets a repository that never contained the art.

Everyone on the team keeps the same working directory. Whoever has no licence simply has no assets/** in their configuration - and GitOne then tells them the files are unassigned instead of committing them somewhere.