Inviting your co-founder

Your company is a folder of markdown in a git repository you own. A co-founder joins it the way anyone joins a repository: through a git host you already use, under your account. Structure adds no service in between, and in this tree it does not create the home or send the invitation for you. Your git host does both.

Give the company a home

Make a private repository on the git host you already use, then point this company at it and push:

git remote add origin <your private repository's address>
git push -u origin main

Then invite your co-founder as a collaborator, in your host's own settings for that repository. Their invitation comes from the host, and accepting it takes their own sign-in there. Structure never holds a credential for this.

Put them on the roster

structure generate person sofia --email sofia@example.com --write
structure propose company/people/sofia.md -m "Sofia joins"

--write writes their page under company/people/, and propose puts it up for review like every other change to the company. Approve it and they are on the roster.

Their side

They clone the repository, install the command the way Install and first run describes, and work in the company from their own terminal: structure check, structure tui, structure propose. When they first sign something on a device that doesn't know them yet, Structure asks who they are, at their own terminal.

Keeping in step

Proposals are branches and approvals are merges, so the company travels with an ordinary git push and git pull, to the origin you configured and nowhere else. Each approval lands in the history with the name of whoever gave it, whichever copy it was given in.

Leaving

There is nothing of ours to disconnect. Remove the collaborator in your host's settings, or stop using Structure altogether: the repository, its history and the sync between your copies are plain git, and they keep working without us.