Skip to main content

Context and Planning

I explain the problem I am solving, who it is for, where this work fits within the wider documents, and what decisions and assumptions guide the plan.

Purpose​

Provide a clear foundation for the application so later design and build choices make sense. I try and keep it practical, local-first, and aligned with how I already run things on-premises.

Audience​

People building, operating, or reviewing the Fit application. That includes me as the builder, future contributors, and anyone interested in how decisions were made.

Scope and boundaries​

  • Focus on the application context, constraints, and high-level plan.
  • Leave detailed product decisions and implementation notes to the product and active pages.
  • Keep Kubernetes specifics brief unless they materially affect the plan.

Assumptions​

  • The platform is local-first and runs on-premises.
  • I prefer simple, observable components over complex stacks.
  • I use GitOps for repeatable builds and quick rollbacks.
  • Privacy, data locality, and low running cost matter.

How this page fits in​

tip

Did you spot the dad joke?

Terms used​

  • container network interface (CNI): The plugin system that connects pods to the network.
  • API: Application programming interface.
  • DNS: Domain name system.
  • TLS: Transport layer security.
  • TCP/UDP: Transport protocols used by services.

Success criteria​

  • Clear problem statement and audience.
  • Defined constraints and assumptions.
  • A plan that links cleanly between Active and Product contexts without duplication.