Skip to content

Rewrite AGENTS.md to hard rules, docs URLs, and escalation - #332

Merged
neuromechanist merged 1 commit into
stagingfrom
feat/agents-hard-rules-and-docs-urls
Sep 14, 2026
Merged

neuromechanist merged 1 commit into
stagingfrom
feat/agents-hard-rules-and-docs-urls

Conversation

@neuromechanist

@neuromechanist neuromechanist commented Sep 14, 2026 •

Copy link
Copy Markdown
Contributor

Applies the pattern nemar-cli settled in epic nemarOrg/nemar-cli#1336 (phase 6, nemarOrg/nemar-cli#1378) to this repository. 486 lines to 286.

What stayed

Everything that is about editing this checkout rather than about the platform: the architecture map, the backend dependency map, environment setup, quick commands, the development workflow, how decisions get recorded, the core principles, and [NEVER DO THIS] verbatim.

What moved

The 96-line versioning and releases section is now develop/website-release (nemarOrg/docs#39), written up before anything was deleted here.

The deploy and staging procedures, 133 lines, now point at the gated systems inventory and staging environment pages, which nemar-cli also points at. One copy instead of two, which is the whole point of the epic.

The check that changed the plan

Checked rather than assumed, using the method nemar-cli phase 4 corrected the hard way: grep concepts, not code identifiers.

  • "prepare-release" and "staging branch" returned zero pages, so the release process was a genuine gap and got written up first.
  • The deploy and staging specifics that looked missing — __EDGE_CACHE_NAMESPACE__, applySecurityHeaders, isNoindexHost, getCrossHostRedirect — turned out to be this repository's own code symbols. Those are implementation detail, not platform facts, and pushing them onto a public documentation site would have been the wrong move. They stayed.

That distinction is the refinement phase 6 adds to the pattern: a section can mix operational facts (which move) with code-level detail (which stays), and the two need separating rather than relocating wholesale.

What is new

A retrieval section. Half the linked material is now gated, so "see the docs" without saying how would be exactly the hollow pointer this epic set out to remove. The file states the .md mirrors, llms.txt, and nemar admin docs <path...>.

The escalation instruction, tagging @nemarOrg/admins: a contributor who cannot read a runbook files the issue anyway and says what they could not read. Escalation replaces read access; silence does not.

Test plan

  • Every docs.nemar.org URL in the file verified live: public pages 200, gated pages 302 to the handoff, both the HTML and .md forms of the new release page 200.
  • No stale pointers to moved content remain.
  • Test suite: 2233 pass / 17 fail, identical with and without this change. Those 17 failures are pre-existing on staging (webSigninEnabled, /api/auth/keys, dedupingFetch) and unrelated to documentation; verified by reverting this file and re-running. Flagging them rather than folding a fix into a docs PR.

Applies the pattern nemar-cli settled in epic nemarOrg/nemar-cli#1336 to
this repo. 486 lines to 286.

Kept, because it is about editing THIS checkout rather than about the
platform: the architecture map, the backend dependency map, environment
setup, quick commands, the development workflow, how decisions get
recorded, the core principles, and [NEVER DO THIS] verbatim.

Moved to docs.nemar.org: the 96-line versioning and releases section is
now develop/website-release, and the deploy and staging procedures (133
lines) point at the gated systems-inventory and staging-environment pages
that nemar-cli also points at, so there is one copy rather than two.

Checked rather than assumed, using the method nemar-cli phase 4 corrected:
grep concepts, not code identifiers. "prepare-release" and "staging
branch" returned zero pages on the docs site, so the release process was a
real gap and was written up first (nemarOrg/docs#39). The deploy and
staging specifics that looked missing turned out to be this repo's OWN
code symbols -- __EDGE_CACHE_NAMESPACE__, applySecurityHeaders,
isNoindexHost, getCrossHostRedirect -- which are implementation detail and
belong here, not on a public documentation site. Those stayed.

New: a retrieval section, because half the linked material is now gated
and "see the docs" without saying how would be a hollow pointer; and the
escalation instruction, tagging @nemarOrg/admins, so a contributor who
cannot read a runbook reports the problem instead of going quiet.

Tested: every docs.nemar.org URL verified live. Test suite is 2233 pass /
17 fail both with and without this change; those failures are pre-existing
on staging (webSigninEnabled, /api/auth/keys, dedupingFetch) and unrelated.
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying nemar-website with  Cloudflare Pages  Cloudflare Pages

Latest commit: ef43104
Status: ✅  Deploy successful!
Preview URL: https://6fc30314.nemar-website.pages.dev
Branch Preview URL: https://feat-agents-hard-rules-and-d.nemar-website.pages.dev

View logs

@neuromechanist
neuromechanist merged commit 4ece357 into staging Sep 14, 2026
5 checks passed
@neuromechanist
neuromechanist deleted the feat/agents-hard-rules-and-docs-urls branch September 14, 2026 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant