GRI-581: the same repository boundary here, and the two duplicated process documents named #3

Merged
vivy merged 2 commits from chore/GRI-581-repo-boundary into dev 2026-10-20 04:49:49 +00:00
Owner

The product owner, on GRI-581: "This way of thinking
counts for all repo's."
So this repository gets the same treatment as
grimoire-of-helpdesk.

What is here

A .repo-boundary manifest — what this repository holds, the patterns that do
not belong in it and where each one goes instead — and a CI job that runs
repo-boundary from agent-tools against it on every pull request. Exit 2,
the check could not be made, fails the job: a boundary that was not checked
must not read like one that is clean (GRI-143).

Nothing is moved out. The check passes on this repository as it stands.

What the check found, and did not move

Two documents here are copies of documents in grimoire-of-helpdesk, and both
have drifted:

Document Here In grimoire-of-helpdesk
plan/process/agent-git-identity.md 79 lines 183 lines
plan/process/branching-and-release.md 179 lines 943 lines

Three homes for two documents, none of them in step. That is the same defect as
the two block generators of GRI-654, at document scale: nothing in either copy
can see the other, and an agent that reads the short one is reading rules that
are 764 lines behind.

They are named as [[allow]] exceptions on GRI-715
rather than deleted here. Deleting a document an agent is instructed to read,
before the single replacement in agent-tools is in place, breaks the reader.
GRI-715 moves them once and repoints everybody.

agent-tools pull request #97 adds the rule and the checker; this needs it
merged first, because the CI job fetches bin/repo-boundary from dev there.

The product owner, on [GRI-581](/GRI/issues/GRI-581): *"This way of thinking counts for all repo's."* So this repository gets the same treatment as `grimoire-of-helpdesk`. ## What is here A `.repo-boundary` manifest — what this repository holds, the patterns that do not belong in it and where each one goes instead — and a CI job that runs `repo-boundary` from `agent-tools` against it on every pull request. Exit 2, *the check could not be made*, fails the job: a boundary that was not checked must not read like one that is clean (GRI-143). Nothing is moved out. The check passes on this repository as it stands. ## What the check found, and did not move Two documents here are copies of documents in `grimoire-of-helpdesk`, and both have drifted: | Document | Here | In `grimoire-of-helpdesk` | | --- | --- | --- | | `plan/process/agent-git-identity.md` | 79 lines | 183 lines | | `plan/process/branching-and-release.md` | 179 lines | 943 lines | Three homes for two documents, none of them in step. That is the same defect as the two block generators of GRI-654, at document scale: nothing in either copy can see the other, and an agent that reads the short one is reading rules that are 764 lines behind. They are named as `[[allow]]` exceptions on [GRI-715](/GRI/issues/GRI-715) rather than deleted here. Deleting a document an agent is instructed to read, before the single replacement in `agent-tools` is in place, breaks the reader. GRI-715 moves them once and repoints everybody. `agent-tools` pull request #97 adds the rule and the checker; this needs it merged first, because the CI job fetches `bin/repo-boundary` from `dev` there.
GRI-581: the signage repository gets the same boundary, and names its two duplicated process documents
Some checks failed
CI / cargo fmt (pull_request) Has been cancelled
CI / cargo clippy (pull_request) Has been cancelled
CI / cargo test (pull_request) Has been cancelled
CI / cargo deny (pull_request) Has been cancelled
CI / cargo deny advisories (pull_request) Has been cancelled
CI / frontend-web (pull_request) Has been cancelled
CI / repository boundary (pull_request) Has been cancelled
CI / CI (pull_request) Has been cancelled
789394fe0c
The product owner's rule counts for all repositories, so this one carries a
.repo-boundary manifest too, and CI runs repo-boundary from agent-tools against
it on every pull request. Exit 2 -- the check could not be made -- fails the
job, because a boundary that was not checked must not read like one that is
clean (GRI-143).

It also writes down what the check found. Two documents here are copies of
documents in grimoire-of-helpdesk, and both have drifted:
plan/process/agent-git-identity.md is 79 lines against 183, and
plan/process/branching-and-release.md is 179 against 943. Three homes for two
documents, none of them in step -- which is the same defect as the two block
generators of GRI-654, at document scale.

They are named as exceptions rather than deleted, because deleting a document
an agent is instructed to read before the replacement is in place breaks the
reader. GRI-715 moves both to agent-tools once and repoints every reader.
GRI-581: the boundary step needs the org token, not the job token
Some checks failed
CI / cargo fmt (pull_request) Successful in 16s
CI / cargo deny (pull_request) Successful in 53s
CI / cargo deny advisories (pull_request) Failing after 43s
CI / cargo clippy (pull_request) Successful in 9m51s
CI / repository boundary (pull_request) Successful in 11s
CI / cargo test (pull_request) Successful in 9m39s
CI / frontend-web (pull_request) Successful in 9m41s
CI / CI (pull_request) Successful in 12s
74275843bd
vivy merged commit 4b649c028a into dev 2026-10-20 04:49:49 +00:00
Sign in to join this conversation.
No reviewers
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
Grimoirix/grimoire-of-digital-signage!3
No description provided.