Architecture

Open this section when the question is structural: where ingest logic lives, how preparation flows through modules, and where the package stops before retrieval semantics take over.

Structural Shape

Ingest architecture is a preparation pipeline with explicit adapters at the edges. Source material enters through interface code, application workflows assemble the run, processing modules normalize and chunk content, and retrieval modules shape handoff records without becoming the long-term owner of search semantics.

flowchart LR
    interfaces["interfaces"]
    application["application services"]
    config["config"]
    processing["processing stages"]
    retrieval["retrieval handoff"]
    observability["pipeline records"]
    infra["storage and adapters"]
    downstream["index package"]

    interfaces --> application
    config --> application
    application --> processing --> retrieval --> downstream
    processing --> observability
    retrieval --> infra

The architectural story here should let a reader follow one preparation run without reading code first. Interfaces admit the input, application code assembles the run, processing makes the content stable, and retrieval surfaces shape the handoff into index. Observability and storage matter because they let that pipeline stay inspectable without moving retrieval ownership upward into ingest.

Read These First

• open Module Map first when you need the fastest route from a behavior question to the owning code area
• open Execution Model when you need the real path from source input to prepared output
• open Integration Seams when a change could blur the handoff into downstream packages

Structural Risk

The main architectural risk here is letting preparation behavior leak into retrieval behavior because the handoff seam is weak or poorly named.

First Proof Check

• packages/bijux-canon-ingest/src/bijux_canon_ingest/application for pipeline assembly and services
• packages/bijux-canon-ingest/src/bijux_canon_ingest/processing for core preparation flow
• packages/bijux-canon-ingest/src/bijux_canon_ingest/retrieval for handoff-ready assembly
• packages/bijux-canon-ingest/tests for proof that the structure still defends deterministic preparation

Pages In This Section

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

Leave This Section When

• leave for Interfaces when the structural question is already a public contract question
• leave for Operations when the issue is running, diagnosing, or releasing the package rather than explaining its shape
• leave for Quality when the structure is clear and the real question is whether the package has proved it strongly enough

Design Pressure

If an architectural explanation here starts to sound like retrieval semantics, the package boundary is already drifting. Ingest stays strong by making the handoff to index cleaner, not by quietly absorbing search ownership.