Rules find a home; source comments go self-contained #9

Closed
opened 2026-10-06 10:13:23 +00:00 by pit · 1 comment
Owner

Part of #7

What to build

Give the standing working rules a home of their own and detach the source comments from the numbered conventions. The rules that are really "read before you work here" move to the agent context file as named rules, and every source comment that cites a convention by number or points at the README is rewritten to stand on its own, so nothing dangles once the numbers are gone.

Acceptance criteria

  • The agent context file carries named rules (no numbers): Secrets — nothing plaintext in the repo, vault-encrypted files only, never commit plaintext staging files; and Privacy — do not publish the DDNS hostname or the external IP, with third-party public hosts and public service domains explicitly allowed.
  • The agent context file points at the docs entry point, alongside its existing pointers to the agent docs and the domain docs.
  • "Version pins live in one place" is not carried over as a rule (it is self-evident from the role defaults).
  • No source comment under the ansible or tofu trees references a numbered convention, and none points at the README or the agent context file.
  • No behavioural change: the tofu stacks and the ansible role behave exactly as before; the only code edits are comment rewrites.
  • Lands as its own PR.

Blocked by

Part of #7 ## What to build Give the standing working rules a home of their own and detach the source comments from the numbered conventions. The rules that are really "read before you work here" move to the agent context file as named rules, and every source comment that cites a convention by number or points at the README is rewritten to stand on its own, so nothing dangles once the numbers are gone. ## Acceptance criteria - [ ] The agent context file carries named rules (no numbers): Secrets — nothing plaintext in the repo, vault-encrypted files only, never commit plaintext staging files; and Privacy — do not publish the DDNS hostname or the external IP, with third-party public hosts and public service domains explicitly allowed. - [ ] The agent context file points at the docs entry point, alongside its existing pointers to the agent docs and the domain docs. - [ ] "Version pins live in one place" is not carried over as a rule (it is self-evident from the role defaults). - [ ] No source comment under the ansible or tofu trees references a numbered convention, and none points at the README or the agent context file. - [ ] No behavioural change: the tofu stacks and the ansible role behave exactly as before; the only code edits are comment rewrites. - [ ] Lands as its own PR. ## Blocked by - #8
Author
Owner

Implemented on hermes/9-rules-find-a-home, PR #15: pit/infra-forge#15

AGENTS.md gains a ## Standing rules section with named rules — Secrets and Privacy — and a ## Docs pointer at docs/index.md, alongside the existing agent-docs and domain-docs pointers. "Version pins live in one place" is not carried over: it is self-evident from the role defaults.

Three comments that leaned on the numbered list are detached so nothing dangles once #10 deletes the list: ansible/roles/forgejo/defaults/main.yml ("convention 4"), ansible/ansible.cfg ("see README"), and docs/adr/0001-…md (which cited both "convention 4" and "README convention 7"; its carve-out bullet is renamed to state the rule itself). The ADR is under docs/, not the ansible/tofu trees the AC names, but leaving it would dangle exactly as the parent's problem statement describes.

Citation check: grep -rniE 'convention ?[0-9]|README|AGENTS\.md' ansible tofu returns nothing. No behavioural change — the only code edits are comment rewrites; tofu validate and tofu fmt -check pass on the Guest stack. Four files, +33/-12.

Implemented on `hermes/9-rules-find-a-home`, PR #15: https://forgejo.thepit.space/pit/infra-forge/pulls/15 `AGENTS.md` gains a `## Standing rules` section with named rules — **Secrets** and **Privacy** — and a `## Docs` pointer at `docs/index.md`, alongside the existing agent-docs and domain-docs pointers. "Version pins live in one place" is not carried over: it is self-evident from the role defaults. Three comments that leaned on the numbered list are detached so nothing dangles once #10 deletes the list: `ansible/roles/forgejo/defaults/main.yml` ("convention 4"), `ansible/ansible.cfg` ("see README"), and `docs/adr/0001-…md` (which cited both "convention 4" and "README convention 7"; its carve-out bullet is renamed to state the rule itself). The ADR is under `docs/`, not the ansible/tofu trees the AC names, but leaving it would dangle exactly as the parent's problem statement describes. Citation check: `grep -rniE 'convention ?[0-9]|README|AGENTS\.md' ansible tofu` returns nothing. No behavioural change — the only code edits are comment rewrites; `tofu validate` and `tofu fmt -check` pass on the Guest stack. Four files, +33/-12.
pit closed this issue 2026-10-06 12:06:18 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
olympus/infra-forge#9
No description provided.