fairpm/fair-protocol
0
0
Fork 0
mirror of https://gh.wpcy.net/https://github.com/fairpm/fair-protocol.git synced 2026-06-20 02:22:26 +08:00
Code Issues Projects Packages Activity Actions
fair-protocol/docs/moderation/service-hierarchy.md
Ipstenu (Mika Epstein) 61ccf9838d
Documentation: Proposal - Moderation in the FAIR Ecosystem (#14) 
Signed-off-by: Mika Ipstenu Epstein <ipstenu@ipstenu.org>
Signed-off-by: Brent Toderash <brent@toderash.net>
Signed-off-by: Ipstenu (Mika Epstein) <Ipstenu@users.noreply.github.com>
Signed-off-by: Claudio Rimann <claudio@haptiq.studio>
Signed-off-by: Joe Murray <joe.murray@jmaconsulting.biz>
Signed-off-by: Ryan McCue <me@ryanmccue.info>
Co-authored-by: Brent Toderash <brent@toderash.net>
Co-authored-by: Claudio Rimann <claudio@haptiq.studio>
Co-authored-by: Joe Murray <joe.murray@jmaconsulting.biz>
Co-authored-by: Ryan McCue <me@ryanmccue.info>
2025-08-20 15:50:50 -07:00

1.1 KiB
Raw Permalink Blame History

Service Hierarchy
Status Proposal
Date 2025-07-22

FAIR's discovery system operates on multiple levels:

Repositories

  • Host and distribute actual package files
  • Primary content storage layer

Aggregators

  • Index and list Repositories and their packages
  • Provide search and discovery interfaces
  • Can list other Aggregators (recursive)

Discovery Services

  • Higher-level directories that aggregate multiple Aggregators
  • Enable ecosystem stakeholders to create unified search experiences
  • Examples: Hosting companies, CMS vendors, large developer communities
  • Can combine multiple Aggregators into single interface/API

Example Hierarchy

Discovery Service (Hosting Company A)
├── Aggregator (Dev Company 1)
│   ├── Repository A
│   └── Repository B
├── Aggregator (Dev Company 2)
│   ├── Repository C
│   └── Repository D
└── Own Repository + Aggregator

This hierarchy enables horizontal scaling while maintaining FAIR's decentralized principles.