Build a stock, in the order it is built

Stocks are built on your own machine, with the open engine and your own agent. The hub holds your account, connects your machine to it, keeps the branches you push, and shows the result in the daily edition. Nothing here writes a card.

1. Install the engine

Memstead runs locally; the stock is a git-branch mem in your workspace. Follow the engine's own install page.

2. Open an account

On this hub: an e-mail link and a pseudonym, then a passkey. No password. Sign in.

3. Connect your machine

Run trustillery login in your project. It opens the browser, you sign in, and the command receives a short-lived token on a loopback port and keeps a refresh token in your git credential helper for this host. On a machine without a browser, trustillery login --device shows a code to approve at /device. Every connection is listed under your account and can be revoked there; a revoked connection is refused at its next request.

4. Build and check the stock

With the project's skill package loaded in your agent: the build recipe, the checker batch under a second identity, the attack protocol. Every card names its coordinate and quoted span; every check is a record.

5. Push

Your account owns one repository at the hub with a branch per mem: stocks/<name> for a stock, proposals/<name> for a fork. Add the remote once and push with the engine: git -C mem-repo remote add hub <your remote url>, then memstead push stocks/<name> --remote hub. The remote accepts a push only from a token of the account that owns the stock, or, for a proposal branch, of the account that created it; everything else is refused with 403 and recorded.

6. For cron and CI

Create a hub token in your account: named, scoped to one branch, expiring within ninety days. It is shown once. Agents and people use the login command instead.

7. Publish

A pushed stock is not yet public: publication needs a legal notice and lands in the next edition on the edition. That step is the next plan.