From 207a0d51a8195bf99f30a1002726b4c751f258e4 Mon Sep 17 00:00:00 2001 From: fullsend-code <278716306+fullsend-ai-coder[bot]@users.noreply.github.com> Date: Sun, 12 Jul 2026 09:03:45 +0000 Subject: [PATCH 1/2] docs(#373): add backlink guidance for new problem docs Extend the problem-doc section of AGENTS.md to require authors to search existing docs for references to their topic and add reciprocal backlinks in the same PR. This codifies the practice demonstrated in PR #3064, where the maintainer had to manually add backlinks from three existing docs to a new doc. Closes #373 --- AGENTS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/AGENTS.md b/AGENTS.md index 5620b735fd..74b133608f 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -7,6 +7,7 @@ Fullsend is a platform for fully autonomous agentic development for GitHub-hoste - Problem documents (`docs/problems/`) should present multiple options with trade-offs, not prescribe single solutions. - Each problem document has an "Open questions" section — this is where unresolved issues live. - When adding new problem areas, create a new file in `docs/problems/` and link it from `README.md`. +- When a new problem doc covers a topic already mentioned in existing docs, search for references to the concept across `docs/problems/` and add backlinks from those existing docs to the new doc in the same PR. This ensures readers can discover the new doc from its related contexts. - The security threat model (threat priority: external injection > insider > drift > supply chain) should inform all other documents. - Keep core problem documents organization-agnostic. Organization-specific details belong in `docs/problems/applied//`. - The target audience for problem documents is any contributor community considering autonomous agents — keep language accessible and avoid presuming solutions. From ad9d6bdf727bc623d843dbb77f759c8e78f71529 Mon Sep 17 00:00:00 2001 From: fullsend-fix <278716306+fullsend-ai-coder[bot]@users.noreply.github.com> Date: Sun, 12 Jul 2026 13:56:35 +0000 Subject: [PATCH 2/2] docs(#373): mention backlink step in README contributor table Update the "Where does my contribution go?" table to mention adding backlinks from existing docs, matching the guidance added to AGENTS.md. Addresses review feedback on #413 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 45b56b1ffe..f9c8de77ee 100644 --- a/README.md +++ b/README.md @@ -70,7 +70,7 @@ If you're applying fullsend to your own organization, consider adding your speci | If you have... | Then... | |---|---| | A question, bug, or small suggestion | **File an issue** — lowest friction, can graduate later. | -| A new problem area no existing doc covers | **Create a problem doc** in `docs/problems/` and link it here. | +| A new problem area no existing doc covers | **Create a problem doc** in `docs/problems/`, link it here, and add backlinks from existing docs that reference the same topic. | | More to say about an existing problem area | **Expand the existing problem doc.** | | A specific decision that needs a yes-or-no answer | **Propose an ADR** in `docs/ADRs/` via a pull request ([see ADR 0001](docs/ADRs/0001-use-adrs-for-decision-making.md)). |