meta/architecture-docs/2025-04-08-high-level-spec.md

fediversity product specification

stack

user-facing

• fediverse
• ...
• prioritize efforts taking in mind
  • added value to operator autonomy
  • strategic relevance to counter-balance big tech
  • demand
  • nix package/service maturity
    • may involve relation with application devs to:
      • upstream nix package
      • ensure architecture takes immutable build/storage in mind

under the hood

• nixos
• opentofu
  • passes relevant info on to nixos config wrapper
• VM hypervisor: proxmox
• storage: garage
• backups / data portability: borgmatic?
• data interoperability: json-schema

component architecture

• orchestration module
  • application service modules (nixos): templates providing sane defaults and unified interface
  • deployment module (opentofu)
• deployment UIs
  • reference imlementation
  • hosting panel: fediversity integration TODO
    • front
    • back
      • existing
      • rewrite?
  • allow for alternate setups
    • e.g. client doing orchestration
• infra

feature-specific architectural notes

• decouple version
• validate component input
• migrate to different host (+ sub-tickets)
• breaking changes