Build

A stock is built on your own machine, with the open engine and your own agent. The hub keeps it; the daily edition shows it.

Current stage: private building is open to every account; release waits on 3 of 3 preconditions.

Details

Building a stock and keeping it privately on the hub is open to every account: register a name, push, work on it unreleased, readable by your own token only. Nobody approves it.

Releasing a stock publicly opens to every account once these three stand:

A media lawyer has reviewed how the hub hosts stocks and handles notices. (open)
A media liability insurance covers the hub. (open)
The owner's terms are published, carrying the CC BY 4.0 grant every released stock is licensed under. (open)

Until then the hub refuses a release by any account but the operator's and names what is still open. Reading, cloning, checking and attacking are open to everyone at every stage.

1. One command
```
npx trustillery@0.1.0 init
```
In an empty folder, with your agent. It asks once, then sets up the engine, your stock and three skills.
Details
It needs Node 24 and an agent you already use (Claude Code, Codex CLI, Cursor or Gemini CLI). It puts the engine at its pinned release into a per-user cache, verified against the checksum the package carries, creates the workspace with stocks/<folder> pinned to evidence@0.2.0, wires the engine's MCP server for your agent and prints a receipt naming every file it wrote. npx trustillery@0.1.0 uninstall removes what it wrote.
Restart the session, then check the skills: Claude Code offers /trustillery:build on /; Codex CLI lists them under $skills after the codex mcp add line the receipt printed; Cursor under Settings › Rules & Skills; Gemini CLI under /skills list.
For an agent, one prompt and nothing else:
```
In a new folder named my-question, run: npx trustillery@0.1.0 init --yes
Report the receipt it prints. Then tell me to restart this session.
```
The package reaches npm with its first release; until then npx answers that the version does not exist, and init, clone, finding and propose from the command line wait with it.
2. Account and connection
An e-mail link, a pseudonym and a passkey on the hub; then trustillery login connects your machine.
Details
No password. trustillery login opens the browser, you sign in, and the command receives a short-lived token and keeps a refresh token in your git credential helper. Without a browser, trustillery login --device shows a code to approve at the hub's device page. Every connection is listed in your account and can be revoked there. For cron and CI, create a hub token in your account: named, scoped to one branch, expiring within ninety days, shown once.
3. Build, check, attack
/trustillery:build, then /trustillery:check and /trustillery:attack.
Details
/trustillery:build builds card by card from primary documents and asks you at three points: the question's wording, the source list, the tradeoff's question. It decides and records everything else. /trustillery:check has a second identity re-read every card against its document. /trustillery:attack runs the thinking attack, best from another model family; you answer each step it records, applied or refused with the error named.
Done when memstead health --include checks,anchors reads every card checked by a second identity and every quoted span resolving.
Refused if a card lacks its span, a derivation reaches no anchor, a tradeoff called two-sided has an empty side, a card judges a person, or the stock has no owner's legal notice.
4. Push, privately
memstead push stocks/<name> --remote hub. It stays private as long as you like.
Details
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: git -C mem-repo remote add hub <your remote url>; your account page names the URL. The hub accepts a push only from the account that owns the stock, or for a proposal branch the account that created it; anything else is refused and recorded.
5. Release
Once the stage allows it, from your account: your question stands in the next edition, 06:00 UTC.
Details
Release takes the stock's legal notice and its release in your account, as Own a stock describes. The one stock built this way took 4.4 hours of orchestration on the owner's subscription, and its attack from a second family 21 minutes.
- Built: the stock with its checks, attack runs and proposal record; accounts, sign-in and the push to the hub; proposals from your agent over the hub's MCP endpoint; the daily edition and its agent addresses.
- Not built: the package on npm, and with it the command line for strangers.
- Not yet: a second question; an owner other than the founder.

Attack →Break one card, or show that it holds.
Propose →Change one card; the owner answers on the record.

Reading needs nothing. Ask your own model on any question page.