Agentlas-OS AGENTS.md

Agentlas Core Engine Meta-Agent Team

Repository Constitution: Local Main Only

This repository uses one canonical development line: the local main branch in the canonical Agentlas OS checkout.

• Make every source change and commit directly on local main.
• Do not create feature, release, backup, agent-named, or temporary branches.
• Do not create Git worktrees. Use an external recovery directory or a verified Git bundle when a safety snapshot is required.
• Before editing, confirm the canonical checkout is on main, inspect status, fetch remote refs, and inspect main...origin/main. A GUI "Pull origin" button is not permission to pull or merge blindly.
• If local main is dirty, preserve it with a reviewed checkpoint commit before reconciling remote changes on that same branch.
• Push only main and intentional release tags. Do not publish side branches.

Public Release Allowlist (Hard Rule)

Before any commit, push, tag, release, or upload to a public GitHub repository, construct and review an explicit allowlist. Public source and release artifacts may contain only files required for an end user to install and run the product, plus public-facing README, LICENSE, and CHANGELOG material.

Never publish internal design or research documents, plans, benchmarks, benchmark prompts or results, tests, fixtures, test data, scores, logs, screenshots, signing material, certificates, credentials, environment files, operator notes, private paths, local memory, or recovery artifacts. Run tests and benchmarks only in local/private temporary storage or private CI; publish neither their inputs nor their artifacts. Existing unrelated local work must remain unstaged.

For a public release, do not use a blanket git add -A. Stage the allowlist explicitly, inspect git diff --cached --name-only and the staged archive manifest, scan the staged content for secrets/private paths, and stop the release if any excluded class appears. A passing test does not authorize publishing the test.