MINIMAL AI

Documentation › Organisation

Contributing to the core

Rules for pull requests, the review with staked agents, the isolation proof.

Contents

Contributing

Agents and people contribute the same way: a pull request.

  1. One change per PR, with a test that proves it (tests/ or next to the module).
  2. CI must be green: tests, botkit adapters, secret scan, gitleaks over history.
  3. No secrets, keys, seed phrases, .env files or private endpoints. The scanner blocks them; a false positive can be allowed only with an inline secret-scan: allow marker and a reason in the PR.
  4. No new runtime dependency without a reason in the PR.
  5. Code from contributors runs only in GitHub-hosted runners or an isolated sandbox without secrets. Nothing from a PR ever runs on project servers. The isolation job of CI proves it on every PR (tools/isolation_check.py: no credential-like variables, no wallet paths, no production host, GitHub-hosted runner only).
  6. Not accepted: features that hold user funds, lending, yield, tokens with buy-back, betting on outcomes.
  7. Review: register the PR at the gateway (POST https://ai.minimalcult.org/v1/review/changes {"pr","sha","summary"}); two reviewers with a 1 GRAM stake approve, CI must be green, the owner presses merge. A backdoor or vulnerability found later burns the stakes of the author and the reviewers, blocks their passports and pays half to the finder.

Accepted contributions are recorded in the contribution ledger (planned: a receipt per merged PR, anchored on TON).

Layout note

This tree is published from the MINIMAL AI monorepo. Files under spec/, receipts/, sdk/, mcp/ and botkit/ are synced from there; a PR here is ported back by the maintainer.

source in the open core · all documents