Watch
3
0
Fork
You've already forked bootstrap
0
install.sh only: no config, no secrets (ADR-0086 §10)
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Dmitriy Stepanov 511e7f777f
README: narrow three claims the verifier refuted
Your own secrets are planned (not placed yet); the family team reads exactly four repos;
chezmoi init asks only for the tier and tags come from FLEET_TAGS (FLEET_TAGS=gui).
Also: SSO is the design, the --promptChoice form is untested, the config repo exists.
2026-11-11 19:37:59 -08:00
README.md README: narrow three claims the verifier refuted 2026-11-11 19:37:59 -08:00

fleet/bootstrap

This repo is public. It is meant to hold install.sh and this README, with no config and no secrets.

install.sh does not exist yet. This repo has no script in it today, so nothing here runs.

Joining the fleet as a second person

This README is a process for you, or for your Claude, to set up a Mac on the family tier. Read it as an example and inspiration, not a fixed procedure. You can do the steps in your own way.

The design is ADR-0086, Amendment 1, in the repo family/autelier (docs/adr/0086-workstation-fleet-chezmoi-tiers-one-way.md).

Each step carries a status:

  • built: the mechanism exists and has tests.
  • planned: designed, not built yet.
  • untested: it may exist, but nobody has run it for a family Mac yet.

What the family tier gives you

The family tier gets the shared shell, terminal, apps and mise tools, with your own git identity and none of the operator's. The tooling places none of the operator's secrets on your Mac; your own secrets are planned (step 5). Your Mac is meant to carry the gui tag (step 3 says how).

The full list of what renders, and what never renders, is in fleet/dotfiles, README, section "Family tier". That repo is private; you can read it with your Forgejo user once your access is in place (step 1).

The steps

1. Your own Forgejo user and the family team (untested)

  • You sign in to git.stepanovs.dev with your own Forgejo user, which exists; the design has the sign-in go through Authentik SSO.
  • The fleet declares a read-only family team in the fleet org, with you as its member. It reads fleet/dotfiles, fleet/aictl, fleet/wezterm-restore and fleet/bootstrap.
  • The design includes a check that your Forgejo sign-in uses SSO. This README does not know its result.

2. A key for your Mac (planned)

  • Your Mac gets one SSH key titled fleet:<machine> on your own Forgejo user.
  • Your Mac's entry in fleet/inventory comes in through a PR the operator opens. Your team cannot read that repo.
  • The plan is that the wizard (step 6) creates the key and prints the public key with the inventory entry to add. A manual path for this step is not written yet.

3. Clone fleet/dotfiles and run chezmoi init on the family tier (built; untested on your Mac)

  • The tier comes from FLEET_TIER; without it, chezmoi init asks for it (the prompt is named "Tier"). chezmoi does not ask for tags: they come from FLEET_TAGS or the stored config, else none, so set FLEET_TAGS=gui for the terminal and the shared GUI apps.
  • Answering the tier prompt with chezmoi init --promptChoice "Tier=family" is untested; check chezmoi's --help and the dotfiles README (repo address, tiers and tags) before you run it.
  • The family render is built and covered by the fleet/dotfiles tests (ci/render.py, ci/test-git-identity.sh). Nobody has run a real chezmoi init on a family Mac yet, as far as this README knows.

4. Your own git identity (built)

  • On family, chezmoi init asks for your git name and address: "Your git user.name (tier family)" and "Your git user.email (tier family)".
  • It keeps them on the next init. FLEET_GIT_NAME and FLEET_GIT_EMAIL answer the two prompts without asking.
  • The name must be one line, without ", \, # or ;, and without leading or trailing spaces. The address must look like local@domain.tld. Anything else fails the init.
  • The operator's name or address fails the init. A test checks that commits on family carry your address, never the operator's.
  • It also asks for a ledger user id. That one may stay empty for now.

5. Your own secrets from your own Bitwarden account (planned)

  • The design: the family tier renders your secrets from your own Bitwarden account, never from the operator's.
  • This is not built yet. Your secrets are not rendered on family today.
  • The bitwarden app is in the family app list, for your own account.

6. The onboarding wizard (planned)

  • The design is one line from a docs page that downloads install.sh from this repo at a pinned commit, checks its SHA-256 and runs it. The script installs the Xcode command line tools, Homebrew, gum and chezmoi; a terminal wizard then asks for the tier, sets up the key, and runs chezmoi init --apply, brew bundle and aictl sync.
  • The wizard and this repo's script are still to be built.

7. Your config repo for Claude (the repo exists; its content is untested)

  • The repo exists; whether it is seeded yet is not checked here.
  • You get a starter repo of your own, fleet/aictl-config-<name>, seeded with a small set of general skills (research, brainstorm, docs/pdf/xlsx, the guard panel if you review code) and hooks (notifications, wezterm focus).
  • It has no homelab-ops skills and none of the operator's confidential or private ones. You add your own from there.
  • Your Claude Code runs on your own Claude account, not the operator's.
  • Your Claude's first run can go through the onboarding wizard of step 6, once it exists.

8. wezterm-restore (untested)

  • wezterm-restore is part of what the family tier is meant to share, and the family team reads fleet/wezterm-restore. Its setup on a family Mac is not written here yet.

Changing things

  • Changes to your own config land in your own config repo.
  • A change you want in a shared fleet repo, such as fleet/dotfiles, is a PR you open yourself, which the operator reviews. How you open it (from a fork, or another way) is not decided yet.

What others can see

  • The privacy boundary runs one way: it keeps the operator's material off your Mac.
  • The other way, the operator can read what you put on Forgejo.
  • Your repos mirror to private GitHub repos, like every other non-archived, non-fork repo.

Where to ask

  • Issues and pull requests are turned off on this repo, so an issue here is not a channel.
  • Read access on the other fleet repos allows issues and PRs, so a question can go there (untested).
  • Your own Claude can read this README and the dotfiles "Family tier" section and work from them.