Architecture

This section explains how bijux-pollenomics is divided structurally across CLI parsing, data collection, spatial helpers, and report publishing.

Use it when the question is about module seams, dependency direction, and how tracked outputs are produced from the package internals.

Start Here

• open Module Map for the shortest code-level tour
• open Execution Model when you need to trace collection and publication flow
• open Integration Seams when the boundary between collectors, helpers, and report builders is the real question

Pages In This Section

• Module Map
• Dependency Direction
• Execution Model
• State and Persistence
• Integration Seams
• Error Model
• Extensibility Model
• Code Navigation
• Architecture Risks

Purpose

This page organizes the structural explanations for the runtime package.