Foundation

Open this section when the hard question is why bijux-canon-ingest owns the work before retrieval begins. These pages should settle whether a proposed change makes prepared source material more predictable or merely pushes another package problem upstream.

Boundary Model

flowchart LR
    source["source material"]
    package["ingest boundary"]
    preparation["preparation rules"]
    handoff["prepared handoff"]
    nextowner["index ownership"]
    drift["retrieval or policy drift"]

    source --> package --> preparation --> handoff --> nextowner
    package --> drift

The foundation story for ingest is only credible if a reader can see where messy source material stops being tolerated and where downstream search ownership begins. This section should make that boundary legible before anyone starts arguing about modules or commands.

Read These First

• open Ownership Boundary first when a change could belong in index, reason, agent, or runtime instead
• open Package Overview when you need the shortest stable description of the package role
• open Lifecycle Overview when the question is how raw source material becomes prepared handoff output

The Mistake This Section Prevents

The most common mistake here is expanding ingest to hide uncertainty that really belongs in retrieval, reasoning, or runtime policy.

First Proof Check

• packages/bijux-canon-ingest/src/bijux_canon_ingest/processing for source preparation ownership
• packages/bijux-canon-ingest/src/bijux_canon_ingest/retrieval for the handoff seam into downstream work
• packages/bijux-canon-ingest/tests for evidence that the boundary still holds under change

Pages In This Section

• Package Overview
• Scope and Non-Goals
• Ownership Boundary
• Repository Fit
• Capability Map
• Domain Language
• Lifecycle Overview
• Dependencies and Adjacencies
• Change Principles

Leave This Section When

• leave this section for Interfaces when the dispute is already about a CLI, schema, artifact, or import surface
• leave this section for Operations when the real problem is setup, diagnostics, release, or recovery
• leave this section for Quality when the boundary is already understood and the open question is proof

Design Pressure

If a page here starts defending retrieval quality or later workflow policy, the package boundary is already slipping. Ingest stays coherent by making input predictable, then handing the work forward.