martin-loop AGENTS.md

MartinLoop Agent Operating Rules

These rules are mandatory for every AI agent, automation, contributor, and coding session working on MartinLoop.

Repository authority

is the sole development authority.

is a public distribution repository. It is never the primary development repository.

Mandatory internal-first sequence

Every code change must follow this sequence:

1. Start from the latest .
2. Create a private feature branch.
3. Implement and test the change privately.
4. Commit and push the private branch.
5. Open a private PR into .
6. Pass all required internal checks.
7. Fix all regressions.
8. Prove the real MartinLoop workflow works.
9. Merge the private PR only after explicit approval.
10. Record the private merge commit SHA.
11. Verify fresh is clean and healthy.
12. Create a clean public-staging branch from the latest public .
13. Transfer only the reviewed public-safe diff from the private merge.
14. Run public tests and public-surface guards.
15. Push the public-staging branch.
16. Open a public PR.
17. Merge publicly only after hosted checks pass and explicit approval is given.

Prohibited actions

Agents must never:

• develop directly in ;
• use public as the implementation authority;
• push unmerged private feature commits to the public repository;
• create public staging before the private PR is merged;
• resolve implementation conflicts only in a public-staging branch;
• bypass or weaken the public-write hook;
• ask the user to bypass the hook for unfinished work;
• push directly to public ;
• merge a stale public branch wholesale;
• declare public readiness while private is broken;
• promote code without a recorded private merge SHA;
• publish npm, tags, native assets, or GitHub Releases before public merge approval.

Required internal health proof

Before public staging, a fresh worktree of private must prove all packages build and test clean, portability and copy-scan pass, git diff --check passes, no conflict markers exist, martin doctor works, preflight and governed run succeed, receipt is created and readable, verification succeeds, status survives restart, and separate workspaces remain isolated.