internal-package-building

What problem does it solve?

Organize internal Go package structures to enforce boundaries and clean import paths.

Core Features & Use Cases

• Guidance on when to create a new internal package under internal/ (new domain) and when to extend an existing package.
• Rules for package boundaries, cmd vs internal boundaries, and import path conventions.
• Real-world example: organizing a monorepo into internal/db, internal/models, internal/candidate_tree, and internal/evaluator to keep boundaries clear and predictable.

Quick Start

Create a new directory under internal/ for the domain, add at least one Go file with a package name matching the directory, and route entry points through cmd/.