Alexandria is literally the scaffolding for this. Composed articles out of nostr events for remixing.

Instead of a linear chatlog imagine taking a whole programming script/codebase, knowledgebase, fragmenting into pieces

Both humans and AI replace fragments or composed fragments with edits instead of writing the whole generated script from scratch.

There's a lot of scaffolding to be built though

https://next-alexandria.gitcitadel.eu/publication?d=gitcitadel-project-documentation-by-stella-v-1

Reply to this note

Please Login to reply.

Discussion

What's the best way for me to play with this and/or understand where it's heading??

We're still building the playground nostr:npub1s3ht77dq4zqnya8vjun5jp3p44pr794ru36d0ltxu65chljw8xjqd975wz is doing an amazing job building a visually nice library base, with lots of moving parts underneath. It is the demonstration how isolated ideas combine together like polymer chains floating around in a soup (the early visualization panel). Structured and contextualized knowledge - as books, code libraries and articles are.

The other side is the Obsidian-like aspect. Where you work with everything in isolated contexts. Every sentence and paragraph can be seeds of ideas that spin off their own forests.

For that perspective, you'd use nak to pull in kind 30040 (structural glue) and 30041 (content) events from. wss://thecitadel.nostr1.com. Meander through ideas in isolation shuffled up.

That's the conceptual basis, and we're trying to get Alexandria to show both aspects - with human/AI synthesis, agential navigation.

Zettelkasten, the basis for many personal knowledge base is the inspiration - but that's it 'personal', its difficult to scale it up. This event structure is Open System collaboration. Pull in a math textbook with python documentation, connect to a biology knowledge base and then synthesize computational biology research from the mix of ideas in place.

Good overview of Zettelkasten (Obsidian, Roam, notion inspirations)

https://www.lesswrong.com/posts/NfdHG6oHBJ8Qxc26s/the-zettelkasten-method-1

Code repositories, technical documentation and literature become less isolated objects and more puzzle pieces and points of reference for synthesis at both the micro (fragment) and macro (total work) scales. Updated instantly as nostr events and organized at any level of resolution you care. At the bookshelf level (like a library) or the paragraph/note level (like obsidian). Any extra data just makes things more easy to traverse. Sprawling vines to go from one tree (our event structure is a tree tree) to another.

The glass bead game client 👀