Files
Orchestrator/shared/OrgMyLife/ARCHITECTURE.md
T
ankn a5f8fb49ab Migrate all repos into monorepo context folders
Bahn: aisupport, Analyse-O2C-C2S, awesome-bahn-mcp-servers, beam-mcp,
      Confluence_Bot, db-planet-mcp-server, O2C-Harness, project-audit,
      Projekt-KIQ-HP, teamlandkarte-mcp
Dhive: Jury-Voting
Privat: CV, NoteGraph (NOTE: NoteGraph needs complete redo after consolidation)
Shared: AI-Orchestrator, OrgMyLife, power_skills_and_more
Shared/references: symphony (read-only)

Bahn repos remain available as independent remotes - this monorepo
pulls them in via subtree, the originals are untouched.
2026-06-30 20:39:52 +02:00

894 B

ARCHITECTURE.md

System Architecture

Product: OrgMyLife Goal: A self-sufficient personal coordination system aggregating life domains (calendars, emails, notes, tasks) with a tidy UI, prioritizing local control over external dependencies.

Technology Stack

  • Backend: Python (e.g., FastAPI) - Chosen for self-sufficiency and ease of future AI/LLM integration.
  • Database: PostgreSQL (self-hosted/local).
  • Frontend: Standard web technologies (HTML/CSS/JS) - Focus on a tidy, clean, functional structure before implementing fancy designs.

Integration Strategy

Data aggregation will be implemented in the following order:

  1. Nextcloud: Initial proof of concept for calendar and notes aggregation.
  2. Gmail: Email aggregation and initial task identification.
  3. Outlook: Handled last due to specialized security and enterprise protection requirements.