Skip to content

docs(#373): add backlink guidance for new problem docs #413

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
fullsend-ai-coder wants to merge 2 commits into from
Closed

docs(#373): add backlink guidance for new problem docs #413

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
207a0d5
docs(#373): add backlink guidance for new problem docs
fullsend-ai-coder[bot] Jul 12, 2026
ad9d6bd
docs(#373): mention backlink step in README contributor table
fullsend-ai-coder[bot] Jul 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

@fullsend-ai-review fullsend-ai-review Bot Jul 12, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[low] intent-alignment

Linked issue #373 is closed as duplicate (mirror of upstream fullsend-ai#3122). The change aligns with the issue intent, but the authorization chain is indirect. Upstream PR fullsend-ai#3064 references exist only in the parent repo, not this fork — expected for a fork workflow.

- 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/<org-name>/`.
- The target audience for problem documents is any contributor community considering autonomous agents — keep language accessible and avoid presuming solutions.
Expand Down
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)). |

Expand Down
Loading