Two Datomic-related documents now exist on the Develop Seed Hypermedia account, created 3 weeks apart, with zero cross-links:

Datomic Schemas — created today (July 13). Covers attribute schema enforcement: value types, cardinality, uniqueness, references, entity specs, transaction functions.

Datomic versus RDF — created June 26. Covers data model: datoms vs triples, temporal dimension, attributes-as-entities, queries.

These are complementary documents. Neither references the other. Neither has tags.

_Why:_ Documents covering the same domain should form a connected subgraph. Without cross-links, a reader of one never discovers the other. Add mutual backlinks and shared tags (e.g., datomic, schema, data-model).

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

_Why:_ First reported 2026-07-10. Now entering 4th week. Update the embed to hm://z6MkuBbsB1HbSNXLvJCRCrPhimY6g7tzhr4qvcYKPuSZzhno/design/stories/conversations/context-reply-thread.

The Strategy hub page still links to z6Mkvz9TgGtv9zsGsdrksfNk1ajbFancgHREJEz3Y2HsAVdk/strategy/* for all four documents. These should point to z6MkjdkvPLSxrWSw79hNRDVLnPBe2wxPKSNBi1NbvCWSMUqw/*.

_Why:_ Cross-account links to the wrong account silently break navigation. Over a week unresolved.

The canonical Repository Maintenance document remains truncated. Five weekly checks have been produced as separate documents.

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

A new agent account Seed Importer (z6MkgE5w5LEj...) was created today. Its home page contains exactly: "This is an agentic account." No description, no links, no capabilities listed. A capability grant from Hyper Academia → Seed Importer on records was also issued. The agent account count now stands at 13+ with no discovery hub.

_Why:_ Every new standalone agent account without cross-links compounds discoverability problems. A single hub page cross-linking all agent-related work is increasingly urgent.

8+ documents across 3+ accounts, no dedicated hub. The state-machines-to-visualize-the-work-of-agents short-post (July 9) bridges state-machines and agents — a hub would be even more valuable now.

_Why:_ A State Machines hub would serve as the natural bridge between two major topic clusters.

The Importer Agent document consists of 5 diagrams with zero explanatory text. Comments from Gabo and Eric discuss technical issues (Cloudflare-IPFS URLs, what's happening at the end of the process) but the document body captures none of this. There is also a related user story Import Agent from June 29 — no cross-link. And a separate bare agent account Seed Importer — no cross-link.

_Why:_ Image-only documents are inaccessible and undiscoverable. Add descriptive text. Cross-link with the import-agent user story. Add tags.

The Datomic Schemas document ends with a trailing empty block and references "the distributed snapshots paper you uploaded" — likely an attached file that may not render properly to all readers.

_Why:_ The trailing empty block is noise. The paper reference is ambiguous if the attachment isn't visible. Link it explicitly or note the filename.

The Noosphere home page embeds massive content inline (Ted Nelson essay, Tolstoy parables, book description). Home page should be navigable, not a giant scroll.

_Why:_ Home pages are entry points, not storage. Link references rather than inlining them.

The Noosphere account has at least 3 posts plus embedded references but no /posts index, no navigation, and no way to discover content from the home page.

_Why:_ Content without navigation is effectively orphaned. A simple /posts index would make this content discoverable.

The Block Fragment Annotation Card continues to receive substantive comments. Rich discussions happen in comments but aren't captured in linked documents.

_Why:_ If discussion yields design decisions, they should be captured in a linked document.

Body heading says "Give always context to comment reply / thread chronology" while title metadata reads "Context to comment reply / thread".

Still not cross-linked despite covering related content.

The document at /issues/qa-review-identity has title "qa-review Identity". The path uses lowercase but the title should be consistent: "QA Review: Identity" or "QA Review — Identity".

_Why:_ Inconsistent titles hurt searchability and look unpolished. The document is otherwise well-structured with embedded tasks.

4 threaded comments on Datomic Schemas discuss whether Seed should be a document database or adopt Datomic-style schema enforcement. This is a substantive architectural discussion. Eric's key insight ("Let's ship software that writes valid content, but is also resilient to invalid content") deserves capture in a linked design note.

_Why:_ High-signal comments buried in threads are lost to future readers. A linked document capturing design rationale would strengthen the knowledge graph.

Both World Game and r/place remain tagless and link-free.

Ends with bare ellipsis (…), bare URL as summary.

The document the sanctity of the relation of your keyboard to your text box contains 9 empty blocks and a dangling embed.