The Conversations Activity hub page still embeds the document at design/stories/conversations/give-always-context-to-comment-reply-thread (block _vIorYgk). That document was renamed to context-reply-thread on 2026-07-10. The embed still references the stale path and shows the old title.

_Why:_ First reported on 2026-07-10. Redirects add unnecessary resolution hops. The displayed embed title is misleading (old name). Update the embed to hm://z6MkuBbsB1HbSNXLvJCRCrPhimY6g7tzhr4qvcYKPuSZzhno/design/stories/conversations/context-reply-thread.

The Strategy hub page on the Content Strategist account still links to z6Mkvz9TgGtv9zsGsdrksfNk1ajbFancgHREJEz3Y2HsAVdk/strategy/* for all four documents (Opportunity Backlog, Signature Ideas, Content Roadmap, Research Roadmap). These should point to z6MkjdkvPLSxrWSw79hNRDVLnPBe2wxPKSNBi1NbvCWSMUqw/* — the Strategist's own copies.

_Why:_ Cross-account links to the wrong account silently break navigation for anyone browsing from the Strategist's hub. These may appear to resolve (the Horacio account also has documents at those paths) but the Strategist account has its own enriched versions.

The Noosphere account gained two new posts on 2026-07-11:

World Game [Buckminster Fuller, 1960's]

r/place

The home document at / is a sprawling manifesto-style page with no links to posts. There is no index, no /posts hub, and no way to browse or discover these posts from the account root.

_Why:_ New content without navigation paths is effectively orphaned. A simple /posts index page linking to all posts would make this content discoverable.

The canonical Repository Maintenance document at /repository-maintenance is still in its truncated state from 2026-07-08. Three weekly checks have been produced but the main document body was never restored.

_Why:_ First reported 2026-07-08. The full history at v=bafyreichub6haju4mka4xpugypqhbtz33oowlku5ftr6x2g3k24qfzwa2i should be restored as the document body.

Agent-related documents now span at least 10 distinct accounts:

z6MkuBbsB... (Develop Seed Hypermedia): Agents, Specialized Agents, Agent Writing, Dreamt Agents, Import Agent

z6MkseoyeQ... (HMX): Agent Profile schema

z6MkfH5CFA... (Deep Learning Collective): Agente

z6MkhhaGMA... (Agent Test 1): Agents, Mr. Agentic

z6Mkvz9Tg... (Horacio): Background Agents, State machines for agents

z6MkfzKMhF... (Hypermedia): Agent Skill interface

z6Mkoje67e... (Agent publisher): standalone account

z6Mkn6DZyw... (Agent Researcher): standalone account

z6MkqRnMac... (Agent Actor): standalone account

z6MkhBiheio... (UI with State Machines): Agent Actor/About

z6MkfLWa23... / z6MkhDHEzt... (Socratic Agent): standalone accounts

z6Mko2rVR9... (BotBoy): agent orchestration

_Why:_ This is the most fragmented topic cluster in the repository. No single hub allows browsing all agent-related work. The Emerging Topics page on the Gardener account tracks State Machines but not Agents broadly.

Both new posts (World Game and r/place) are Wikipedia/website excerpts with no tags, no backlinks to related Seed content, and no inline links to other hypermedia documents. The r/place post ends with a bare ellipsis (…) indicating the excerpt was truncated. The World Game post has a bare URL summary (via https://www.bfi.org/...) with no attribution formatting.

_Why:_ Content without links doesn't participate in the knowledge graph. The World Game post was already cited in a comment on Block Fragment Annotation Card — a natural cross-link opportunity. The r/place post connects conceptually to discussions about collaborative spaces, pixel-level interaction, and the design of shared canvases — all relevant to Seed.

The Block Fragment Annotation Card received 4+ new comments on 2026-07-11 discussing:

Comment editing and fragment selection reversibility

The "Loupe" concept and block embeds

RAG generation protocol concerns

UI disorientation and the relationship between comment, block, and document

_Why:_ Rich discussions are happening in comments but are harder to discover and reference than documents. If the discussion yields design decisions or insights, they should be captured in a linked document. Consider a "Related Discussion" section or child document.

The state machines cluster continues to grow:

3 short-posts on Horacio's account (including new state-machines-to-visualize-the-work-of-agents on 7/9)

3+ notes/projects on Develop Seed Hypermedia

UI with State Machines account (z6MkhBiheio...) with dedicated content

Tracking in Emerging Topics (Gardener)

_Why:_ The Emerging Topics page provides summary tracking but no dedicated hub. A State Machines hub page cross-linking all accounts would improve discoverability.

The document title metadata reads "Context to comment reply / thread" but the body's first heading still says "Give always context to comment reply / thread chronology". Reported last week, still unresolved.

_Why:_ When a document is renamed, the body heading should match to avoid reader confusion.

The r/place post ends with a bare ellipsis character (…) suggesting the Wikipedia excerpt was incompletely copied. The summary is a bare URL string (via https://en.wikipedia.org/wiki/R/place [excerpt]).

_Why:_ Truncated content signals incomplete work. A bare URL summary is less useful than a descriptive summary. Add a proper one-sentence summary and either complete or note the truncation.

The Noosphere home document contains:

Multiple empty blocks (blank lines rendered as separate block IDs)

Unclosed center-justification comment (___ [there's no center justification available?] ____)

Draft notes like "you can save money (was this block proximate to anything in an earlier draft..." that are explicitly marked for deletion

An incomplete sentence fragment "residing with a grounding in"

_Why:_ The home page is the account's front door. Draft artifacts and placeholder content create a confusing first impression. Clean up or move draft notes to a separate scratch document.