docs(roadmap): August 2026 planning refresh - #5689
Conversation
This comment was marked as spam.
This comment was marked as spam.
|
🤖 Review · |
This comment was marked as spam.
This comment was marked as spam.
Site previewPreview: https://485c1151-site.fullsend-ai.workers.dev Commit: |
This comment was marked as spam.
This comment was marked as spam.
Replace ranked workstream categories with Now/Next/Later delivery horizons from the July 28 planning board, including a July done recap and tracking across fullsend and agents. Update platform-nativeness links that pointed at removed roadmap anchors. Signed-off-by: Adam Scerra <ascerra@redhat.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Signed-off-by: Adam Scerra <ascerra@redhat.com> Co-authored-by: Cursor <cursoragent@cursor.com>
77a2c20 to
afc06e9
Compare
|
🤖 Review · |
|
🤖 Finished Review · ✅ Success · Started 7:17 PM UTC · Completed 7:29 PM UTC |
ReviewFindingsHigh
Next steps:
Previous runReviewFindingsHigh
Next steps:
Previous run (2)Looks good to me Labels: PR modifies only documentation files under docs/ |
![fullsend-ai-review[bot]](https://avatars.githubusercontent.com/in/3478501?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
fullsend-ai-review
Bot
added
ready-for-merge
waynesun09
left a comment
waynesun09
left a comment
There was a problem hiding this comment.
Automated review pass — 3 findings on docs/roadmap.md (see inline comments). No blocking issues beyond what's noted; posting as informational review only.
|
|
||
| - See [#267](https://github.com/fullsend-ai/fullsend/issues/267) | ||
|
|
||
| ## Foundation (April–May 2026) |
There was a problem hiding this comment.
MEDIUM: Foundation (Apr–May 2026) section deleted with no mention, only home for MVP/history facts
This PR deletes main's entire ## Foundation (April–May 2026) section (main:docs/roadmap.md:220-232 — MVP timeline, "20+ Konflux repositories," "fullsend is using fullsend" dogfooding note, core architecture bullets) with no mention in the PR description. Verified via git log -S "Foundation (done)" that this section (created 2026-05-14 in 739bf26) survived two full roadmap rewrites (36ac3a5 June 9 refresh, 57820bb July 1 refresh — which only renamed it from "Foundation (done)" to "Foundation (April–May 2026)") without being cut, unlike the monthly "N (done)" recap which is an established, intentionally-rotating section (and correctly rolls June→July in this same PR). Verified docs/architecture.md:199 retains the "repo is the coordinator" principle, but concrete facts specific to this section (MVP date, Konflux repo count, dogfooding claim) appear nowhere else in the live docs tree.
Suggestion: Restore a trimmed version of this permanent milestone/history anchor, or explicitly call out the removal in the PR description and confirm the underlying facts have a durable home elsewhere before merging.
There was a problem hiding this comment.
Hm maybe we should have a 2nd file where we store the past roadmap and milestone data to preserve it?
I'm going to do this and collect the previously removed roadmap for past months there aswell. Call it archived-roadmap.md
There was a problem hiding this comment.
Done — created docs/archived-roadmap.md with:
- Archive-only banner for humans/AI reviewers
- Quick reference for Foundation + June 2026 (done)
- Full snapshots from May post-MVP, early June, June planning, and July-as-merged (with source commit SHAs)
Also linked from live roadmap.md, added a VitePress sidebar entry, and excluded the archive from lychee so historical links do not fail CI.
| | Review-fix loop | Less human mechanical iteration | [fullsend#5666](https://github.com/fullsend-ai/fullsend/issues/5666) · [fullsend#5550](https://github.com/fullsend-ai/fullsend/issues/5550) · [agents#447](https://github.com/fullsend-ai/agents/issues/447) · [agents#343](https://github.com/fullsend-ai/agents/issues/343) · [agents#478](https://github.com/fullsend-ai/agents/issues/478) | | ||
| | Contributor meeting | Broader contributor call (incl. RH AI) | — | | ||
| | Per-workflow cost visibility | Cost by workflow type | [fullsend#5361](https://github.com/fullsend-ai/fullsend/issues/5361) · [fullsend#5537](https://github.com/fullsend-ai/fullsend/issues/5537) | | ||
| | Jira poller | Jira events → agents | [fullsend#3812](https://github.com/fullsend-ai/fullsend/issues/3812) · [fullsend#4885](https://github.com/fullsend-ai/fullsend/issues/4885) · [fullsend#3428](https://github.com/fullsend-ai/fullsend/issues/3428) · [fullsend#2269](https://github.com/fullsend-ai/fullsend/issues/2269) | |
There was a problem hiding this comment.
MEDIUM: "Now" row cites PRs #3812/#3428 as Jira-poller evidence, but both have live ADR-number collisions with main
The new "Jira poller" row (this line) cites fullsend#3812 and fullsend#3428; "Example custom agent that responds to Jira" (next row) also cites #3812. Verified via gh pr view --json files and the ADR files on main: #3812 adds docs/ADRs/0069-jira-project-enrollment-via-cli.md, but main's 0069 slot is already 0069-ready-made-configuration-presets.md (itself correctly tracked by #4910 "Epic: ADR 0069" and #4914, which this same roadmap cites two rows down). #3428 adds docs/ADRs/0068-privacy-allowlist-for-poll-input-drivers.md, but main's 0068 slot is already 0068-public-community-mint-architecture.md (Accepted). Both PRs are currently OPEN with reviewDecision=CHANGES_REQUESTED and neither can merge without renumbering — a structural blocker the roadmap doesn't surface for work framed as ~30-day "Now" delivery.
Suggestion: Note the blocker inline for the Jira poller row (e.g. "pending ADR renumber"), or confirm with the #3812/#3428 authors that they'll move to free ADR slots before relying on this as near-term roadmap evidence.
There was a problem hiding this comment.
The PR author will fix the ADR numbers as they go I don't want to get into that level of detail here on the roadmap
| | PR risk assessment | Risk signal on PRs | [fullsend#4698](https://github.com/fullsend-ai/fullsend/issues/4698) | | ||
| | Basic auto-merge capability | Smallest safe foothold + config | [fullsend#2791](https://github.com/fullsend-ai/fullsend/issues/2791) · [fullsend#3016](https://github.com/fullsend-ai/fullsend/issues/3016) | | ||
| | Review-fix loop | Less human mechanical iteration | [fullsend#5666](https://github.com/fullsend-ai/fullsend/issues/5666) · [fullsend#5550](https://github.com/fullsend-ai/fullsend/issues/5550) · [agents#447](https://github.com/fullsend-ai/agents/issues/447) · [agents#343](https://github.com/fullsend-ai/agents/issues/343) · [agents#478](https://github.com/fullsend-ai/agents/issues/478) | | ||
| | Contributor meeting | Broader contributor call (incl. RH AI) | — | |
There was a problem hiding this comment.
MEDIUM: Unexplained internal-style "RH AI" abbreviation added to public roadmap
Added on this line: "Contributor meeting | Broader contributor call (incl. RH AI) | —". This docs site targets external contributor communities. "RH AI" appears nowhere else in the repo, and the project's actual convention when referencing the parent org is to spell out "Red Hat" in full (e.g. docs/landscape.md, docs/ADRs/0068, docs/spikes/2026-05-25-*) — never abbreviated. docs/glossary.md asks PRs introducing new terminology to add an entry, which wasn't done here. Other partners in the same table (OpenShell, Ansible, TektonCD) are fully spelled out, making this parenthetical stand out as unexplained internal shorthand in public planning prose.
Suggestion: Spell out what "RH AI" refers to (e.g. "Red Hat AI"), or replace with an unambiguous public-facing term; remove the parenthetical if it isn't meant for public disclosure.
There was a problem hiding this comment.
Contributor meeting outcome is now just Broader contributor call
| | PR risk assessment | Risk signal on PRs | [fullsend#4698](https://github.com/fullsend-ai/fullsend/issues/4698) | | ||
| | Basic auto-merge capability | Smallest safe foothold + config | [fullsend#2791](https://github.com/fullsend-ai/fullsend/issues/2791) · [fullsend#3016](https://github.com/fullsend-ai/fullsend/issues/3016) | | ||
| | Review-fix loop | Less human mechanical iteration | [fullsend#5666](https://github.com/fullsend-ai/fullsend/issues/5666) · [fullsend#5550](https://github.com/fullsend-ai/fullsend/issues/5550) · [agents#447](https://github.com/fullsend-ai/agents/issues/447) · [agents#343](https://github.com/fullsend-ai/agents/issues/343) · [agents#478](https://github.com/fullsend-ai/agents/issues/478) | | ||
| | Contributor meeting | Broader contributor call (incl. RH AI) | — | |
There was a problem hiding this comment.
| | Contributor meeting | Broader contributor call (incl. RH AI) | — | | |
| | Contributor meeting | Broader contributor call (incl. RH AI) | — | | |
| | Agent contribution example | Help users see how to improve fullsend; make it easier to contribute | [fullsend#5720](https://github.com/fullsend-ai/fullsend/issues/5720) | |
There was a problem hiding this comment.
@deboer-tim here, adding that concrete idea for improving the "contributability".
There was a problem hiding this comment.
Captured in the Now table as Agent contribution example → fullsend#5720.
| | ------------------------------------------ | -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ||
| | PR risk assessment | Risk signal on PRs | [fullsend#4698](https://github.com/fullsend-ai/fullsend/issues/4698) | | ||
| | Basic auto-merge capability | Smallest safe foothold + config | [fullsend#2791](https://github.com/fullsend-ai/fullsend/issues/2791) · [fullsend#3016](https://github.com/fullsend-ai/fullsend/issues/3016) | | ||
| | Review-fix loop | Less human mechanical iteration | [fullsend#5666](https://github.com/fullsend-ai/fullsend/issues/5666) · [fullsend#5550](https://github.com/fullsend-ai/fullsend/issues/5550) · [agents#447](https://github.com/fullsend-ai/agents/issues/447) · [agents#343](https://github.com/fullsend-ai/agents/issues/343) · [agents#478](https://github.com/fullsend-ai/agents/issues/478) | |
There was a problem hiding this comment.
| | Review-fix loop | Less human mechanical iteration | [fullsend#5666](https://github.com/fullsend-ai/fullsend/issues/5666) · [fullsend#5550](https://github.com/fullsend-ai/fullsend/issues/5550) · [agents#447](https://github.com/fullsend-ai/agents/issues/447) · [agents#343](https://github.com/fullsend-ai/agents/issues/343) · [agents#478](https://github.com/fullsend-ai/agents/issues/478) | | |
| | Review-fix loop | Less human mechanical iteration | [fullsend#5666](https://github.com/fullsend-ai/fullsend/issues/5666) · [fullsend#5550](https://github.com/fullsend-ai/fullsend/issues/5550) · [agents#447](https://github.com/fullsend-ai/agents/issues/447) · [agents#343](https://github.com/fullsend-ai/agents/issues/343) · [agents#478](https://github.com/fullsend-ai/agents/issues/478) | | |
| | Versioned docs | Better docs experience for users | [fullsend#5717](https://github.com/fullsend-ai/fullsend/issues/5717) · [fullsend #5718](https://github.com/fullsend-ai/fullsend/issues/5718) | |
There was a problem hiding this comment.
Added — Versioned docs with fullsend#5717 and fullsend#5718.
| | Per-workflow cost visibility | Cost by workflow type | [fullsend#5361](https://github.com/fullsend-ai/fullsend/issues/5361) · [fullsend#5537](https://github.com/fullsend-ai/fullsend/issues/5537) | | ||
| | Jira poller | Jira events → agents | [fullsend#3812](https://github.com/fullsend-ai/fullsend/issues/3812) · [fullsend#4885](https://github.com/fullsend-ai/fullsend/issues/4885) · [fullsend#3428](https://github.com/fullsend-ai/fullsend/issues/3428) · [fullsend#2269](https://github.com/fullsend-ai/fullsend/issues/2269) | | ||
| | Example custom agent that responds to Jira | BYOA pattern for Jira | [fullsend#3812](https://github.com/fullsend-ai/fullsend/issues/3812) | | ||
| | Triage agent works in response to Jira | Default triage from Jira | [fullsend#2264](https://github.com/fullsend-ai/fullsend/issues/2264) | |
There was a problem hiding this comment.
| | Triage agent works in response to Jira | Default triage from Jira | [fullsend#2264](https://github.com/fullsend-ai/fullsend/issues/2264) | | |
| | Triage agent works in response to Jira | Default triage from Jira | [fullsend#2264](https://github.com/fullsend-ai/fullsend/issues/2264) | | |
| | Make agent status comments configurable | Reduce agent spam on issues for users who don't want it | [fullsend#3697](https://github.com/fullsend-ai/fullsend/issues/3697) | |
There was a problem hiding this comment.
Added — Make agent status comments configurable with fullsend#3697.
Add Ralph's Now rows, spell out Red Hat AI, and move Foundation plus prior published roadmap snapshots into archived-roadmap.md. Signed-off-by: Adam Scerra <ascerra@redhat.com> Co-authored-by: Cursor <cursoragent@cursor.com>
|
🤖 Finished Review · ✅ Success · Started 2:18 PM UTC · Completed 2:30 PM UTC |
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
fullsend-ai-review
Bot
removed
the
ready-for-merge
Restructure archived-roadmap.md into skim-friendly monthly editions with collapsed full snapshots, and remove the contributor-meeting parenthetical. Signed-off-by: Adam Scerra <ascerra@redhat.com> Co-authored-by: Cursor <cursoragent@cursor.com>
|
🤖 Review · |
Signed-off-by: Adam Scerra <ascerra@redhat.com> Co-authored-by: Cursor <cursoragent@cursor.com>
|
🤖 Finished Review · ✅ Success · Started 2:49 PM UTC · Completed 3:03 PM UTC |
| - id: lint-md-links | ||
| name: lint markdown links | ||
| entry: lychee --offline --no-progress --include-fragments --exclude-path node_modules --exclude-path experiments '**/*.md' | ||
| entry: lychee --offline --no-progress --include-fragments --exclude-path node_modules --exclude-path experiments --exclude-path docs/archived-roadmap.md '**/*.md' |
There was a problem hiding this comment.
[high] protected-path
This PR modifies .pre-commit-config.yaml, a protected governance/infrastructure file. The change adds --exclude-path docs/archived-roadmap.md to the lychee markdown link linter. The PR has no linked issue providing explicit authorization for modifying this protected path. Human approval is required for all protected-path modifications.
Suggested fix: A human reviewer must approve this change. The modification is a 1-line addition to exclude the new archived roadmap file from link checking — reasonable given the file contains intentionally stale historical links, but human sign-off on infrastructure file changes is always required.
4 participants
Summary
docs/roadmap.mdfor the July 28 planning session: Now / Next / Later delivery horizons (flat deliverable tables, not ranked workstream categories)fullsend-ai/fullsendandfullsend-ai/agentsdocs/archived-roadmap.md(Foundation / April–May, June planning, July planning) so monthly history is not lost when the live page rotatesArchive (
docs/archived-roadmap.md)Makefile+.pre-commit-config.yaml)Review follow-ups included
Broader contributor call(no parenthetical)Why
docs/problems/platform-nativeness.mdis in this PRThe August roadmap rewrite removed the old section headings (
#infrastructure,#cross-forge-orchestration, etc.).platform-nativeness.mdstill linked to those fragments, so the repo’s markdown link linter fails on commit/CI until those references are updated. This PR retargets that sentence to the roadmap generally (GitLab MVP, cross-forge orchestration, Kubernetes/OpenShift) without depending on deleted anchors.Test plan
docs/roadmap.mdon the PR (tables render, links open)docs/archived-roadmap.md(monthly summaries visible; expanders show full snapshots)fullsend#/agents#tracking URLsplatform-nativeness.mdno longer references removed roadmap fragmentsdocs/archived-roadmap.md