Foundation

Open this section when the dispute is about what retrieved evidence means once it becomes a claim, check, or reasoning artifact. These pages should make bijux-canon-reason defensible as the place where evidence becomes inspectable conclusions rather than raw search output or agent choreography.

Boundary Model

flowchart LR
    evidence["retrieved evidence"]
    package["reason boundary"]
    claim["claim and check logic"]
    record["reasoning artifact"]
    handoff["agent or runtime handoff"]
    blur["retrieval or workflow blur"]

    evidence --> package --> claim --> record --> handoff
    package --> blur

The foundation pages for reason have to defend one sharp idea: this is where evidence becomes meaning that another reviewer can inspect. If that move is not clear here, later workflow and runtime docs will end up carrying reasoning policy they should never have inherited.

Read These First

• open Ownership Boundary first when the behavior could belong in retrieval below or orchestration above
• open Package Overview when you need the shortest stable description of the package role
• open Lifecycle Overview when the question is how evidence turns into verified reasoning output

The Mistake This Section Prevents

The most common mistake here is burying reasoning policy inside retrieval artifacts or workflow code until no one can explain which layer actually made the decision.

First Proof Check

• packages/bijux-canon-reason/src/bijux_canon_reason for the owned reasoning boundary in code
• packages/bijux-canon-reason/tests for proof that claims, checks, and provenance stay aligned
• packages/bijux-canon-reason/README.md for the public package contract readers encounter first

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 Architecture when the question is already about modules or execution flow
• leave this section for Interfaces when the issue is a command, schema, artifact, or import surface
• leave this section for Quality when the reasoning boundary is understood and the open question is whether the package has earned trust

Design Pressure

If a page here starts sounding like search tuning or workflow coordination, the reason boundary is already undercut. This section has to keep interpretation separate from both retrieval below and orchestration above.