Repository Maintenance

Periodic inspection reports for the Seed Team Talks knowledge repository. This document tracks structural problems, inconsistencies, and recommendations for improving the navigability and quality of the hypermedia graph.

---

Report: 2026-07-23 — Weekly Inspection

High Priority

1. Junk / Test Documents

Multiple test documents with no meaningful content are cluttering the repository. They pollute search results and make directories harder to browse.

Identified test/junk documents:

| Path | Title | Content |
|------|-------|---------|
| `/projects/-Bpm9RnpF-C` | "borra" | Random characters (`SAHDFIOASHDOSAF`) |
| `/projects/test` | "test" | Single word "test" |
| `/notes/eeee` | "test" | Empty |
| `/notes/test321` | "test" | Test content |
| `/notes/test23424` | "test23424" | Test content |
| `/notes/test-test` | "test test" | Test content |
| `/projects/subdocuments-appear-in-the-parent-content/test` | "test" | Test content |
| `/projects/subdocuments-appear-in-the-parent-content/testte` | "testte" | Test content |
| `/test-23/tset131234/test` | "test" | Test content |
| `/notes/abracadabra` | "abracadabra" | Likely test |

Recommendation: Delete or archive these documents. "borra" literally means "delete" in Spanish. These were likely created during development testing and were never cleaned up. They appear in search results and add noise.

2. Inconsistent ⚠️ / ✅ / ⛔️ Status Prefixes in Document Titles

Story documents under /design/stories/ use emoji prefixes inconsistently to indicate status:

⚠️As a User, I want to create a Site for the first time (in progress)

⚠️ Edit URL path (in progress)

⚠️As an admin, I want to publish my website with my own domain (in progress)

⚠️As an admin, I want to publish my website with a free Hypermedia URL (in progress)

✅ As a user, I want to manage my account settings (done)

✅ As an Admin, I want to define main settings of my site (done)

Some documents have no prefix at all, like "Invite members - permissions".

Why this matters: The emoji prefix is metadata about document status. It should not be part of the document title/name. Titles should be stable and descriptive. Status changes over time, but titles should not.

Recommendation: Remove emoji status prefixes from document names. Use a dedicated metadata field (or a tag convention) to track document status instead of encoding it in the title. If needed, the status can be indicated in the hub/index document that links to these stories (which already happens — the Settings hub page uses ✅/⚠️/⛔️ inline).

3. Missing Repository Maintenance Document

This is the first maintenance report. The Repository Maintenance document did not exist before today.

Action taken: This document has been created.

---

Medium Priority

4. Duplicate "Subdocument testing" Documents

Two separate documents exist with the same name at different paths:

hm://z6MkuBbsB1HbSNXLvJCRCrPhimY6g7tzhr4qvcYKPuSZzhno/notes/subdocument-testing

hm://z6MkuBbsB1HbSNXLvJCRCrPhimY6g7tzhr4qvcYKPuSZzhno/lobby/subdocument-testing

Both are referenced from the home document. Having two documents with the same name at different paths creates confusion about which is canonical.

Recommendation: Determine whether these are intentional forks (e.g., one is a copy for testing) or accidental duplicates. If accidental, delete one and ensure backlinks point to the remaining one.

5. Duplicate Project Listings on Home Page

The home document (Develop Seed Hypermedia) has two overlapping project listings:

The structured embed (projects/shaping) with categories: Ready to Bet, Shaping, Ideas, In Development, Completed, Canceled

The flat "All Projects" list below it, which contains many of the same projects

The "Completed" embed section also duplicates projects that appear in the flat list. This creates ambiguity about which is the canonical project listing and doubles maintenance burden.

Recommendation: Consolidate to a single project listing. Either:

Remove the flat "All Projects" list and rely on the structured embed, OR

Keep the flat list and remove the structured embed

The structured embed (with categories) is more useful for navigation, but it means every new project must be categorized and added there.

6. Triplicated "User Story Workflow" in Workflows Document

The /workflows document contains the "User Story Workflow" section three times with identical content (steps 1-4). This is likely a copy-paste error.

Recommendation: Deduplicate — keep one instance of the User Story Workflow section.

---

Low Priority

7. Known Orphan Documents Issue

The /notes/orphan-documents document documents a known problem: moving a parent document does not move its children, creating documents stranded at old paths that become uneditable.

The team is aware of this issue and has filed it as both a product bug and a maintenance concern. No action needed from the librarian — this is a product-level fix.

8. Inconsistent Meeting Notes Date Formats

The /meeting-notes hub page prescribes the format YYYY-MM-DD: DESCRIPTION, but several entries deviate:

2026-06-18 — no description

2026-04-09 : Tech Sync — extra space before colon

20206-05-21: Tech Sync — year typo (20206 instead of 2026)

2026-05-28--tech-sync — double dash instead of colon-space

2026-2-26-tech-sync — single-digit month, no spaces

Hypertuesday — no date at all

Design Meeting — no date at all

Agent Writing — no date at all

Recommendation: Rename non-conforming meeting notes to follow the prescribed format, or add redirects. This would improve browsing and sorting in the directory.

9. Path/Title Mismatches

Some document paths do not match their display titles:

/projects/global-feed → title is "Desktop App Main Feed"

/projects/local-linkbase → title is "Domain Store"

/projects/merge-contacts-and-profiles → title is "Design Project: New Users quickly understand the Basics of Seed Hypermedia"

Recommendation: Consider renaming paths to better match titles, or vice versa. Paths should be stable and discoverable; when path and title diverge significantly, it makes it harder to predict URLs.

10. `notes/test` Under `/notes/test` (Half baked transclusions)

The document at /notes/test has parent path "Develop Seed Hypermedia / Notes / Half baked transclusions" — it appears the document at /notes/test was originally created as a child of /notes/test (the "Half baked transclusions" document). This path structure is confusing.

Recommendation: Verify the intended parent of this document and correct if needed.

---

Summary of This Week's Activity

This week's activity was primarily around design story discussions:

Create Site flow (/design/stories/settings/createsite): Heavily discussed — the team debated whether to require sign-in before the editor or allow anonymous drafting with deferred identity creation. Consensus forming around requiring sign-in at publish time.

Free/own domain stories (/design/stories/settings/free-domain, /design/stories/settings/own-domain): UX feedback provided on confirmation dialogs, upsell framing, and toast sizing.

Edit path story (/design/stories/authoring/edit-path): Quick confirmation that the feature is feasible and scheduled.

Tech Talks (/tech-talks): Discussion about linking attributes to threads (#consensus).

Agents 2 (/projects/agents-2): Eric provided clarification on local agent server architecture.

No new documents were created this week. All activity was comment-based discussion on existing documents.