anbot

root / AGENTS.md

1864 bytes

# ANBot development

- Keep ANBot self-replicating through ANBot nodes. Never use GitHub or git-ssb
  for this project. Commit changes locally and publish or push to an ANBot
  node when requested.
- Use `SPEC.md` to keep the MVP focused on publishing, recovering, and serving
  the node's own Git history. Use `README.md` for setup and operation.
- Treat `selected.json` as the publication commit point. Verify and durably
  store signed records and AndFS blocks before changing the selection.
  An interruption before selection must leave the previous commit cloneable.
- Keep the serving cache disposable. Recovery must work with the cache deleted
  and the original checkout unavailable.
- Preserve ordinary `git clone` and `git fetch`. Require an allowlisted ANBot
  identity for Git pushes. Store node identities and data outside the source
  checkout.
- Serving verifies records against the repository's publisher key (the author
  of the `git-repo` record), not the local identity. The local identity is
  only for signing.
- The gossip poll serves git records and social posts in one
  (payload-timestamp, record ID) ordered stream. The pull client stores
  posts through the store's post operations; posts never touch the update
  chain or the selection.
- Stores are dumb byte holders; verification stays in the core and callers.
  Never store unverified bytes under a verified ID.
- For changes to publication, storage, or Git serving, run `sh test/self-host.sh`
  from a clean, committed checkout. Record the commit the test exercised.
- For changes to push or authorization, run `sh test/push.sh`.
- For changes to the web UI, run `sh test/webui.sh`.
- For changes to the sync endpoints or the pull client, run `sh test/sync.sh`.
- For changes to the core modules, run `sh test/core-imports.sh`,
  `sh test/core-compat.sh`, and `sh test/browser.sh`.

Git ยท Social feed