A repository adopting the agent-file model reads two pages that both say which agent files it must carry. The list is stated twice, so it can disagree with itself — and it has.
Request
Repository Standard states the agent files in its required-files table, which is the surface a repository is audited against — it is what someone lists when asking "what is missing here". Agentic Development states the same set again in its own table, together with the reasoning for it: one router, and a route for every client that cannot reach it under that name.
The two tables have already disagreed. Repository Standard listed CLAUDE.md at the repository root where Agentic Development listed .claude/CLAUDE.md, and it omitted .github/copilot-instructions.md entirely although Agentic Development marks it Required. Bringing Storhaug-ting/Kilden up to the baseline produced exactly that repository — a root CLAUDE.md and no .github/copilot-instructions.md — because the required-files table was the checklist, and both were corrected only after reading Agentic Development, which is not the page a repository-baseline task routes to.
#122 has since corrected the paths, so the two tables agree today. What it did not remove is the reason they disagreed: it had to fix the same rule in two pages. A file required by the framework but absent from the required-files table gets left out, and a file placed where that table says gets placed wrong, for as long as the table keeps its own copy of the list.
Acceptance criteria:
- A reader following the required-files table produces the same set of agent files that Agentic Development requires, at the same paths.
- The tables cannot drift again: one page owns the list and the other links to it.
- The set described matches what this repository actually carries.
Technical Decisions
Agentic Development owns the agent-file set. It holds the reasoning, and it is where the framework spec points for the exact set an MSX repository carries. Repository Standard should route to it rather than restate it, for the same reason a router does not restate a standard: a copy of a rule is a rule that can drift, and this issue is the proof.
The narrower alternative — correcting the rows — is what #122 already did, and it left the duplication that produced the mismatch in place.
Note that the required-files table legitimately describes files Agentic Development does not, such as .gitattributes and SECURITY.md. Only the agent-file rows move.
Related: #67 tracks required-standard files missing from this repository, and needs re-checking against the settled set.
Implementation Plan
A repository adopting the agent-file model reads two pages that both say which agent files it must carry. The list is stated twice, so it can disagree with itself — and it has.
Request
Repository Standard states the agent files in its required-files table, which is the surface a repository is audited against — it is what someone lists when asking "what is missing here". Agentic Development states the same set again in its own table, together with the reasoning for it: one router, and a route for every client that cannot reach it under that name.
The two tables have already disagreed. Repository Standard listed
CLAUDE.mdat the repository root where Agentic Development listed.claude/CLAUDE.md, and it omitted.github/copilot-instructions.mdentirely although Agentic Development marks it Required. Bringing Storhaug-ting/Kilden up to the baseline produced exactly that repository — a rootCLAUDE.mdand no.github/copilot-instructions.md— because the required-files table was the checklist, and both were corrected only after reading Agentic Development, which is not the page a repository-baseline task routes to.#122 has since corrected the paths, so the two tables agree today. What it did not remove is the reason they disagreed: it had to fix the same rule in two pages. A file required by the framework but absent from the required-files table gets left out, and a file placed where that table says gets placed wrong, for as long as the table keeps its own copy of the list.
Acceptance criteria:
Technical Decisions
Agentic Development owns the agent-file set. It holds the reasoning, and it is where the framework spec points for the exact set an MSX repository carries. Repository Standard should route to it rather than restate it, for the same reason a router does not restate a standard: a copy of a rule is a rule that can drift, and this issue is the proof.
The narrower alternative — correcting the rows — is what #122 already did, and it left the duplication that produced the mismatch in place.
Note that the required-files table legitimately describes files Agentic Development does not, such as
.gitattributesandSECURITY.md. Only the agent-file rows move.Related: #67 tracks required-standard files missing from this repository, and needs re-checking against the settled set.
Implementation Plan
.github/copilot-instructions.md, and matches what this repository carries.