AI Analysis
What was actually agreed
The core goal crystallised as: a participant reading a paper in Origami Text during a session at Hypertext 2026 makes a comment tied to a specific paragraph, and it appears live for others in the room, and in Seed. Eric steered this toward comment syncing specifically, since Seed’s annotations are baked into the document while comments are a floating discussion layer, which is a much better fit for a two-week experiment.
Architecture decisions:
- Origami Text becomes a client to the conference Seed server, the way the Seed website and mobile app work, with no daemon. Running the Seed daemon inside Origami for true P2P is a later option, and Eric noted the two aren’t mutually exclusive.
- It lives as a settings tab called “Hypermedia”, not “Seed” (protocol name, not brand; deliberately untrademarkable).
- Identity via key import/export rather than the full sign-in-via-vault flow, on Eric’s recommendation.
- Laptops only, no mobile. Links and version-addressed URLs are explicitly deferred.
- Eric shared two TypeScript examples on Discord (read-only, and read+write with sign-in) for Claude to port to Swift. You started that research in Xcode during the call.
The one technical question everything hinges on
Eric was clear that comments only work if the document is identical in both places with a single source of truth, addressed by block IDs. Origami EPUBs already have paragraph IDs and use W3C Web Annotation. What nobody knows yet is whether those IDs survive when Seed imports the paper, or whether Seed should instead treat the EPUB as an attached file and let comments target Origami’s IDs directly. Gabo called schema transformation the biggest topic; you called it conceptually trivial if addressing maps. You’re both right, and this is the thing to test first, with one paper, before anything else.
Left open
- Attribution inside Origami: it’s single-user today, so two people’s comments arriving from Seed need identities attached. Eric flagged this as the reason bidirectional is harder than one-way.
- Which direction first. Gabo’s framing (Origami for thinking, Seed for collaboration, archive Origami comments into Seed) suggests one-way Origami → Seed is the safe minimum, with Seed → Origami as the stretch.
- How Seed attaches editions (EPUB, PDF) to a document, whether as IPFS files or otherwise. Unresolved.
- Proceedings permission: Eric believes Gabo and Mark already have this for putting proceedings on Seed; you’re confident the ACM community will support EPUB distribution. Previous years’ sources are mixed, some HTML.
- Live spreadsheet tables as annotations: acknowledged as a hard edge case, deferred by mutual agreement.
Action items
You: run Eric’s prompt in Xcode and post the result to Discord; build the Hypermedia tab; share the transcript and unlisted video. Eric: write plain-language prompts you can paste straight to Claude; download and test Origami Text for usability; optionally branch the repo. Gabo: finish the customer-journey notes; confirm proceedings permission with Mark; ask attendees to bring laptops. All: another meeting soon, with informal calls anytime, coordination on Discord and the HT London Seed site.
One process observation: Eric asked for the user story four times before it landed, and the conversation went from “middleware” abstraction to a concrete workflow the moment you wrote it down in chat. That written version isn’t in the transcript, so it would be worth pasting it into Gabo’s notes as the reference.