docs: link VISION_ACTIVITY from the VISION index#1405
Merged
Conversation
VISION_ACTIVITY.md already lives at the project root alongside the other VISION_*.md docs (AGENT, MESH, PROJECTS, SOVEREIGN) — root is the established convention. The gap was discoverability: VISION.md links out to SOVEREIGN/MESH/PROJECTS but not to ACTIVITY. Add the missing pointer in the Home Feed & Notifications section, mirroring the existing "See [VISION_X.md]..." pattern, so the activity-feed vision is reachable from the index. Co-authored-by: Taylor Ho <taylorkmho@gmail.com> Signed-off-by: Taylor Ho <taylorkmho@gmail.com>
wesbillman
approved these changes
Jun 30, 2026
tellaho
pushed a commit
that referenced
this pull request
Jul 1, 2026
…-preview * origin/main: fix(relay): enable Redis TLS for rediss:// (ElastiCache) (#1417) chore(release): release Buzz Desktop version 0.3.40 (#1414) fix(desktop): stabilize channel-timeline scrollback with per-row height reserves (#1413) fix(sidebar): trim working badge label and name working agents in tooltip (#1408) Mobile tab bar polish (#1368) feat(desktop): let thread pane expand on ultrawide monitors (#1407) chore(release): release Buzz Desktop version 0.3.39 (#1410) fix: close cross-process keychain race and namespace dev-build nest (#1409) feat(relay): allow agent owners to edit/manage agent-owned content (#1403) fix(media): support IRSA/credential-chain S3 auth and configurable signing region (#1406) fix(desktop): fold baked build env into in-process model discovery (#1376) docs: link VISION_ACTIVITY from the VISION index (#1405)
tellaho
pushed a commit
that referenced
this pull request
Jul 1, 2026
…vity-embed * origin/main: fix(relay): enable Redis TLS for rediss:// (ElastiCache) (#1417) chore(release): release Buzz Desktop version 0.3.40 (#1414) fix(desktop): stabilize channel-timeline scrollback with per-row height reserves (#1413) fix(sidebar): trim working badge label and name working agents in tooltip (#1408) Mobile tab bar polish (#1368) feat(desktop): let thread pane expand on ultrawide monitors (#1407) chore(release): release Buzz Desktop version 0.3.39 (#1410) fix: close cross-process keychain race and namespace dev-build nest (#1409) feat(relay): allow agent owners to edit/manage agent-owned content (#1403) fix(media): support IRSA/credential-chain S3 auth and configurable signing region (#1406) fix(desktop): fold baked build env into in-process model discovery (#1376) docs: link VISION_ACTIVITY from the VISION index (#1405)
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
2 participants
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.
What
Adds a one-line pointer to
VISION_ACTIVITY.mdfrom theVISION.mdindex, in the Home Feed & Notifications section.Why
Follow-up to Wes's review comment on #1381 asking whether
VISION_ACTIVITY.mdbelongs at the project root.The location is correct. All six VISION docs live at the project root —
VISION.md,VISION_AGENT.md,VISION_MESH.md,VISION_PROJECTS.md,VISION_SOVEREIGN.md, and nowVISION_ACTIVITY.md. Root is the established convention.The real gap was discoverability:
VISION.mdis the hub and links out to SOVEREIGN / MESH / PROJECTS with aSee [VISION_X.md]...line each — but never linked ACTIVITY. This PR wires it in where the activity/agent feed is discussed, matching the existing pattern.Change
Docs-only, one file, no code.