From 4574a0db8ee8b28ed85621545240c7e085493021 Mon Sep 17 00:00:00 2001 From: mm Date: Tue, 6 Oct 2026 17:55:26 -0400 Subject: [PATCH] Require peer comparison for CLI operational conventions (IMP-099) --- AGENTS.md | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) create mode 100644 AGENTS.md diff --git a/AGENTS.md b/AGENTS.md new file mode 100644 index 00000000..5230b321 --- /dev/null +++ b/AGENTS.md @@ -0,0 +1,33 @@ +# OpenProse CLI repository guidance + +**For agents.** These instructions apply throughout this repository, including +root packaging, distribution and harness integrations. Follow narrower +instructions where applicable. For changes beneath `cli/`, read +[implementation rules](cli/AGENTS.md) and [contributor guidance](cli/CONTRIBUTING.md). +This file does not change the CLI's runtime defaults or the OpenProse language. + +## Prefer established operational conventions + +Before implementing conventions for packages, installation, distribution, +updates, configuration, credentials, cache/state/log locations or diagnostics, +inspect the current official documentation or source of comparable established +tools. Relevant peers include Codex, Claude Code, OpenCode and Prime Agent. +Record the comparison in the task, design note or PR before implementation: +sources, areas of agreement, meaningful differences and the selected approach. + +Where peers agree, prefer their established convention. Do not introduce a +custom alternative without first documenting the concrete requirement that +existing conventions cannot satisfy, its user impact and any migration cost. +Where peers differ, report that variation and select an established approach +suited to the product; do not manufacture consensus or require unanimity. +Explicit user decisions take precedence over this general selection guidance. + +Keep user preferences independent of whether the executable comes from npm, +npx, Homebrew or a standalone archive. Distinguish installation artifacts, +user configuration, credentials and reconstructible caches. Preserve explicit +user overrides during upgrades. Missing configuration should inherit built-in +defaults; do not write those defaults as user overrides automatically. + +This constraint governs operational plumbing. It does not authorize copying +another tool's language semantics, bypassing local controls, broadening +permissions or claiming capabilities that have not been implemented and tested.