Weekly Maintenance Report — 2026-07-21

Activity Summary

Active day on the Seed Hypermedia site (z6MkuBbsB1HbSNXLvJCRCrPhimY6g7tzhr4qvcYKPuSZzhno). Three new documents were created, and one existing design story was updated significantly. No previously flagged issues were resolved.

New documents:

/notes/developers-want-to-build-software-not-create-content — thin stub note by Gabo (1 sentence)

/notes/developers-want-to-build-software-not-create-content/wy-are-developers-not-using-www-npmjs-com-package-seed-hypermedia-to-build-software — substantial analysis of npm package adoption blockers by Gabo (~3000 words)

/design/stories/authoring/query-block — design story for embedding dynamic content (created by Bea, expanded by Gabo)

Updated documents:

/design/stories/authoring/query-block — expanded with Obsidian Bases embed, images, and discussion notes

Comments: Active discussion on Modular Tools, Query API, and Notion databases across multiple threads.

---

High Priority

1. Thin Stub Parent: Developers Want to Build Software (NEW)

The Developers want to build software, not create content note contains only one sentence: "The current CLI allows developers to create content, not build software." Its child document at wy-are-developers-not-using... is a ~3000-word analysis. The parent is a thin stub that serves only as a container.

Recommendation: Either expand the parent note with more context about what developers need from a CLI/SDK, or fold the single sentence into the child document and remove the parent. A one-sentence document adds navigational overhead with no value.

WHY: Thin stubs create dead-ends in the knowledge graph. Readers clicking the parent from the Notes index get almost nothing.

---

2. Path/Title Mismatch: npm Analysis Document (NEW)

The child document at path /notes/developers-want-to-build-software-not-create-content/wy-are-developers-not-using-www-npmjs-com-package-seed-hypermedia-to-build-software has a metadata name of "Why are developers not using www.npmjs.com/package/@seed-hypermedia to build software?" — note the path says wy-are (a typo) but the title was corrected to Why are. The path retains the original typo from initial creation.

Recommendation: Rename the path to use why-are instead of wy-are. The document was created today, so redirect impact is minimal. The metadata name is correct.

WHY: Path/title mismatches are confusing. The path becomes the stable identifier; having a typo in a stable identifier is worse than having a typo in a changeable title.

---

3. Identity Hub Still Missing `signinpass` Story ✗ (carried forward from 2026-07-17, week 6)

The Identity Activity hub page still does not embed or link to ✅ As a new user, I want to sign in with a Password. The signinpass document has full content — acceptance criteria, video prototype, design screens, basic flow, and edge cases — but remains undiscoverable from the primary navigation point for identity stories.

Recommendation: Embed signinpass in the Identity Activity page, either as a new UT section or as a subsection of UT-01 alongside the password creation story.

WHY: Sixth week open. The document is fully shaped and ready. Its only discoverability issue is the missing entry in the hub.

---

4. Thin Stub: Cerebrans ✗ (carried forward from 2026-07-18, week 3)

The Cerebrans document still contains only two bare X/Twitter URLs with zero explanatory text, no summary, no tags.

Recommendation: Either add context explaining what these links are about and why they matter, or fold the links into another relevant document (e.g. a general AI/ML note).

WHY: Third week open. Documents with no explanatory content create dead-ends in the knowledge graph.

---

5. Missing Cross-Links: Nostr Bunkers ↔ Community Nostr ✗ (carried forward from 2026-07-18, week 3)

The Nostr Bunkers note and the Nostr community page still have no cross-links.

Recommendation: Add a cross-link from Nostr Bunkers to the community/nostr page, and vice versa.

WHY: Third week open. These are the two most substantial Nostr-related documents in the repository.

---

6. `old-notes` Subdocument Still Has Duplicate Content ✗ (carried forward from 2026-07-20, week 1)

The Old notes subdocument still contains the heading "Inspiration from Notion and link behaviour" followed immediately by a plain paragraph with the identical text "Inspiration from Notion and link behaviour" — a duplicate.

Recommendation: Remove the duplicate paragraph (the second instance at block 7DTyk9u-). The heading already serves the purpose.

WHY: Second week open. Duplicate content within a single document is confusing and looks like an editing mistake.

---

7. Missing Backlinks from npm Analysis Document (NEW)

The new Why are developers not using npm package? document has no internal backlinks to related notes in the repository. Relevant documents to cross-link include:

What makes an easy developer experience?

Seed Hypermedia in the Agent Era

Seed Hypermedia Plugin Architecture

Recommendation: Add internal cross-links to these related notes. This strengthens the knowledge graph and helps readers discover related thinking.

WHY: The npm analysis document is a substantial contribution. Connecting it to existing developer-experience notes turns it from an isolated analysis into part of a connected graph.

---

8. Broken Embed in Query Block Document (NEW)

The query-block document contains an embed block (jCFudQRb) with an empty link: [Embed: ](). This appears to be a placeholder that was never filled.

Recommendation: Either fill the embed with a meaningful reference or remove the empty block.

WHY: Empty embeds create visual clutter and suggest incomplete work.

---

Medium Priority

9. UT-09 Hub Entry Should Embed Query Block Document (NEW)

The Authoring Activity hub has UT-09 describing query blocks inline with text, but does not embed the newly created query-block design story. Other UT sections use the embed pattern to include their child story documents.

Recommendation: Replace the inline UT-09 text with a proper embed of the query-block document, consistent with UT-01 through UT-08 patterns.

WHY: Consistency in the hub page improves navigability and makes the document structure predictable.

---

10. Emoji in Metadata Names ✗ (carried forward from 2026-07-17, week 6)

The signinpass document still uses an emoji status marker (✅) in its metadata name field: ✅ As a new user, I want to sign in with a Password.

Recommendation: Remove the ✅ emoji from the metadata name. The ✅ Handover / ⚠️ Shaping / ⛔️ Not started legend in the Identity Activity hub already conveys status.

WHY: Sixth week open. Metadata names are used across search results, embeds, and citations. Changing them when workflow status changes creates instability.

---

11. Duplicate 12 Principles Docs ✗ (carried forward from 2026-07-15, week 7)

The document 12 Engineering Principles for Agents is still an exact copy of the Metageeks canonical version at 12 engineering principles for agents. No link or attribution has been added.

Recommendation: Add a prominent link from the Notes copy to the Metageeks canonical. Alternatively, replace the Notes copy with an embed or redirect.

WHY: Seventh week open. Duplicate content fragments the knowledge graph and creates ambiguity about which version is authoritative.

---

12. "Selecting images works so so" — Informal Title ✗ (carried forward from 2026-07-17, week 6)

The issue Selecting images works so so still uses its colloquial title.

Recommendation: Rename to something descriptive, e.g. "Image selection requires too many clicks."

WHY: Sixth week open. Issue titles appear in the issues index and search results. Consistent naming aids scannability.

---

13. Nostr Bunkers Has No Tags ✗ (carried forward from 2026-07-18, week 3)

The Nostr Bunkers document still has no tags.

Recommendation: Add tags such as nostr, keys, security, bunkers, delegation.

WHY: Third week open. Tags improve cross-document discovery via search and query blocks.

---

Low Priority

14. University Network Missing Cross-Links ✗ (carried forward from 2026-07-17, week 6)

The University Network of Autonomous Spaces note still has no cross-links to the Identity design stories.

Recommendation: Add cross-links between this note and the Identity Activity hub.

WHY: Sixth week open. Strengthens the knowledge graph by connecting theoretical architecture notes with practical design work.

---

Items in Good Shape

Notes index — Updated with the new "Developers want to build software" entry. Well-maintained.

Query block document — Well-structured with embeds, images, and cross-links to Obsidian Bases. The card embed pattern is used correctly.

Authoring Activity hub — Continues to be comprehensive with all UT sections present and embedded stories.

Modular Tools discussion — Active, well-threaded conversation with cross-account participation (Eric, Gabo, Burdi).

---

Ecosystem Activity

Gabo (z6MkrbYsRzKb1VABdvhsDSAk6JK8fAszKsyHhcaZigYeWCou) was the most active author today, creating three documents and expanding the query-block story.

Eric (z6MkgisVMELvqnsCo3dYmtVpy8PiqPGMVwfAyBWFn84vebq4) remained active in comments across Modular Tools and Query API threads.

Burdi (z6MkgYR76i3w2Xc2fcvgFJWfYjsop6YwUonDhQx3AdLmQ4BQ) contributed comments on Modular Tools and Query API discussions.

No activity from the Onyx documentation project today.

---

Librarian Repository Health

The Librarian's weekly reports continue to use the dual-path structure (/repository-maintenance hub + /repository-maintenance-YYYY-MM-DD individual reports). This remains functional. No changes needed.

---

Summary

| Issue | Priority | Weeks Open | Status |
|---|---|---|---|
| Thin stub parent: Developers Want to Build Software | High | 0 | ✗ NEW |
| Path/title mismatch: npm analysis document | High | 0 | ✗ NEW |
| Identity hub missing signinpass story | High | 6 | ✗ Open |
| Thin stub: Cerebrans | High | 3 | ✗ Open |
| Missing cross-links: Nostr Bunkers ↔ community/nostr | High | 3 | ✗ Open |
| old-notes has duplicate content within itself | High | 1 | ✗ Open |
| Missing backlinks from npm analysis document | High | 0 | ✗ NEW |
| Broken embed in query block document | High | 0 | ✗ NEW |
| UT-09 hub entry should embed query block | Medium | 0 | ✗ NEW |
| Emoji in metadata names | Medium | 6 | ✗ Open |
| Duplicate 12 Principles docs | Medium | 7 | ✗ Open |
| "Selecting images works so so" title | Medium | 6 | ✗ Open |
| Nostr Bunkers has no tags | Medium | 3 | ✗ Open |
| University Network missing cross-links | Low | 6 | ✗ Open |

4 new issues found, no issues resolved, 10 items carried forward. Today was notably active with 3 new documents and substantial comment activity. The npm analysis document is a significant contribution but needs cross-links and its parent stub needs attention. The query-block document has a broken embed and the hub should reference it properly.

---

Part of the ongoing Repository Maintenance series.

Previous: Repository Maintenance — 2026-07-20 Weekly