Architecture

Operating Structure

Mullusi uses separated repositories and domains so public presentation, documentation, runtime services, developer tools, research engines, and internal operations do not collapse into one unclear system.

System Map

Repository Roles

Each repository has one primary responsibility. Public repositories explain or deliver public surfaces. Private repositories hold operational planning, deployment notes, costs, and sensitive control records.

Deployment Flow

GitHub repository
  -> build or static validation
  -> deployment host
  -> DNS target
  -> public domain
  -> monitoring and rollback

Boundary Rule

Website claims, documentation claims, runtime behavior, and research claims are separate outputs. A claim moves between layers only when its source, validation path, and rollback plan are explicit.