6e992cc0c5
- Rename 'three-pronged' folder to 'knowledge-layers' — prong metaphor
was misleading (implied parallel tines), replaced with epistemic layers
(deductive base, empirical middle, probabilistic oracle — vertical stack)
- Collapse 11 overlapping files into 3 coherent documents:
- knowledge-layers/_index.org: core framework (two engines + one store,
World Model formula, 0-14 layer table, provenance store design,
conflict resolution, cold-start, stage mapping)
- knowledge-layers/practical-implications.org: design-world-aware-of-
physics, 10 powers, Schafmeister existence proof, epistemic transparency
- knowledge-layers/neurological-empirical.org: neural networks in
provenance framework (kept intact)
- Relocate wolfram/mathematica and Schafmeister docs to ideas/viability/
- Integrate into main architecture _index.org:
- Gate: expanded from two vectors (ACL2+LLM) to three (deductive,
provenance/empirical, LLM oracle)
- Autodidactic loop: split into Track 1 (deductive hardening, fast)
and Track 2 (empirical validation, slow, experimental-feedback-driven)
- See also: added Knowledge Layers cross-reference
- Add all-lisp geometry engine note (ideas/lisp-geometry-engine.org) as
concrete illustration of the empirical layer's effect on design work
- Rebuild site: 148 files, 0 errors
121 lines
4.1 KiB
Org Mode
121 lines
4.1 KiB
Org Mode
#+title: Social Protocol Requirements - 08
|
|
#+author: Amero Garcia
|
|
#+created: [2026-03-16 Mon 14:28]
|
|
#+DATE: 2026-03-14
|
|
#+ID: agora-requirements-07-library
|
|
#+STARTUP: content
|
|
|
|
:PROPERTIES:
|
|
:CREATED: [2026-05-24 Sun]
|
|
:ID: df02cddc-944a-4bcd-8ef5-f080870d5f49
|
|
:END:
|
|
* Library
|
|
|
|
** Concept
|
|
|
|
The Library is a unified content archiving and media management system. It works like a unified *arr suite (Sonarr, Radarr, Readarr, etc.) that builds your personal libraries across all content types.
|
|
|
|
** Supported Content Types
|
|
|
|
- Video (movies, TV shows, educational content)
|
|
- Audio (podcasts, music, audiobooks)
|
|
- Photos (personal albums, professional portfolios)
|
|
- Text (books, articles, documents)
|
|
- Maps (geographic data, custom itineraries)
|
|
- Physibles (physical object designs, 3D models)
|
|
- Manufacturing Processes (recipes, procedures, blueprints)
|
|
|
|
** Architecture
|
|
|
|
The Library consists of three core components:
|
|
|
|
*** Downloaders
|
|
|
|
- Content acquisition tools that fetch media from various sources
|
|
- Support for torrents, Usenet, direct downloads, and IPFS
|
|
- Integration with content discovery networks
|
|
- Automated quality selection and format conversion
|
|
- Metadata fetching from external databases
|
|
|
|
*** Indexers
|
|
|
|
- Local search and categorization of library content
|
|
- Full-text search across documents, subtitles, metadata
|
|
- Tag-based organization (genre, year, creator, etc.)
|
|
- Content deduplication via CID comparison
|
|
- Integration with [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Social Protocol]]'s discovery layer for shared content
|
|
|
|
*** Library Managers
|
|
|
|
- Content organization and presentation interfaces
|
|
- Unified browsing across all content types
|
|
- Playlist and collection creation
|
|
- Offline sync for mobile clients
|
|
- Sharing controls (personal, collective, public)
|
|
|
|
** Content Addressing
|
|
|
|
All Library content is stored as CIDs:
|
|
- Original files content-addressed for integrity
|
|
- Metadata stored as separate Content Objects
|
|
- Thumbnails and previews generated and addressed separately
|
|
- Version history maintained via CID chains
|
|
|
|
** Archiving
|
|
|
|
*** Concept
|
|
|
|
Archiving preserves Content Objects and open web content for long-term access, creating personal or collective knowledge repositories that outlive the ephemeral nature of streams.
|
|
|
|
*** CID Content Archiving
|
|
|
|
**** Personal Archives
|
|
- Users can archive any CID-based content they have access to (public or decrypted)
|
|
- Archive creates local copy with full CID verification
|
|
- Archived Content Objects retain original metadata and provenance
|
|
- Cross-references to related CIDs preserved
|
|
|
|
**** Collective Archives
|
|
- Library Collectives can curate themed archives (e.g., "Climate Science", "Digital Art History")
|
|
- Distributed storage across multiple PDS nodes for redundancy
|
|
- Version tracking as Content Objects are updated
|
|
|
|
*** Open Web Archiving
|
|
|
|
**** Web Archiver Tools
|
|
- Archive any URL to content-addressed storage
|
|
- WARC (Web ARChive) format support for fidelity
|
|
- Text extraction for full-text indexing
|
|
- Media extraction and separate CID addressing
|
|
|
|
**** Link Rot Prevention
|
|
- Replace dead links with archived CID versions
|
|
- "Archive this" browser extension for one-click saving
|
|
- Automatic archival of links referenced in user's content
|
|
|
|
**** Archival Standards
|
|
- Memento Protocol support for temporal negotiation
|
|
- Archive verification via multiple sources (Wayback Machine, Archive.today, personal PDS)
|
|
- Content authenticity via hash verification against original
|
|
|
|
*** Integration with the Social Protocol
|
|
|
|
- Library content can be referenced in posts, messages, and profiles
|
|
- Content can be shared via Relays with appropriate encryption
|
|
- Micro-payments for premium content access
|
|
- Syndication to protocol-aware browsers and gateways
|
|
|
|
** Requirements
|
|
|
|
- The system MUST support unified content management across all media types.
|
|
- The system MUST content-address all library items via CID.
|
|
- The system MUST support local indexing for fast search.
|
|
- The system MUST allow content sharing via the protocol's social layer.
|
|
- The system MUST support offline access for synced content.
|
|
- The system MUST integrate with the protocol's economic layer for paid content.
|
|
|
|
** Related Documents
|
|
|
|
- Protocol Unified Content Primitive
|
|
- Protocol PDS & Relay Architecture
|