[No QA] Split AgentZero upcoming-features roadmap into focused per-feature pages#94400
Draft
MelvinBot wants to merge 2 commits into
Draft
[No QA] Split AgentZero upcoming-features roadmap into focused per-feature pages#94400MelvinBot wants to merge 2 commits into
MelvinBot wants to merge 2 commits into
Conversation
Co-authored-by: Stephanie Elliott <stephanieelliott@users.noreply.github.com>
This comment has been minimized.
This comment has been minimized.
Co-authored-by: Stephanie Elliott <stephanieelliott@users.noreply.github.com>
Contributor
Author
|
Fixed the failing The check failed on a single unknown word — |
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Explanation of Change
Splits the single AgentZero "Upcoming Features" reference page (
docs/articles/Unlisted/AgentZero-Upcoming-Features.md) into 30 focused, per-feature reference pages, and converts the original page into a links-only index.Why: The original page listed ~30 features across 10 categories in one file. AgentZero's help-doc retrieval embeds each
.mdfile as a single vector, so a 30-feature page produced one "averaged" embedding that ranked poorly for specific queries. In the reported example, a "Certinia integration" question retrieved the top-10 most-similar accounting articles but the roadmap page ranked below #10 and was never seen by the model — so AgentZero answered that Certinia wasn't planned, even though it was on the page. (Full root-cause analysis: https://github.com/Expensify/Expensify/issues/651798#issuecomment-4785559358.)Giving each upcoming feature its own tightly-scoped page means a focused query now matches a page whose entire embedding is about that one feature. Each page also front-loads product names and synonyms (e.g.
Certinia/FinancialForce,Rillet,Puzzle.io,Dynamics 365 Business Central) into thetitle,keywords, and body to further strengthen retrieval.What changed:
docs/articles/Unlisted/Upcoming-*.mdpages — one per planned/in-development New Expensify feature — each preserving the originalnoindex: true,sitemap: false, andinternalScopefrontmatter so they remain AgentZero-referenced but excluded from public search.AgentZero-Upcoming-Features.mdwith a categorized, links-only index pointing to the focused pages (so there's still a single human hub, but it no longer competes with the focused pages in semantic search).This is a docs-only change (markdown content under
docs/articles/Unlisted/). These pages are served by direct URL and are not part of the hub routing system, soroutes.ymldoes not change.Fixed Issues
$ https://github.com/Expensify/Expensify/issues/651798
PROPOSAL: https://github.com/Expensify/Expensify/issues/651798#issuecomment-4785559358
Tests
// TODO: The human co-author must fill out the tests performed before marking this PR "ready for review".
docs/articles/Unlisted/Upcoming-*.mdpage renders and is reachable by direct URL.AgentZero-Upcoming-Features.mdrenders as an index and every link resolves to its focused page.Offline tests
N/A — static help-site documentation content.
QA Steps
// TODO: These must be filled out, or the issue title must include "[No QA]."
PR Author Checklist
### Fixed Issuessection aboveScreenshots/Videos
N/A — documentation-only change.