Foundation

Open this section when you need to decide whether a behavior belongs to orchestration itself rather than to reasoning semantics below or runtime authority above. These pages should make bijux-canon-agent defensible as a coordination layer instead of a vague place where cross-package work happens.

Boundary Model

flowchart LR
    artifacts["reasoning artifacts"]
    package["agent boundary"]
    workflow["workflow coordination"]
    trace["trace-backed sequence"]
    handoff["runtime handoff"]
    blur["reasoning or authority blur"]

    artifacts --> package --> workflow --> trace --> handoff
    package --> blur

The foundation story for agent has to prove that orchestration is a real owned surface. Inputs arrive as reasoning artifacts, coordination happens here, a trace leaves for runtime, and neither reasoning semantics nor final authority gets silently absorbed into the middle.

Read These First

• open Ownership Boundary first when a feature could belong in reasoning logic or runtime governance instead
• open Package Overview when you need the shortest stable description of the package role
• open Lifecycle Overview when the question is how role-based work becomes a traceable workflow

The Mistake This Section Prevents

The most common mistake here is calling any multi-step behavior an agent concern even when the real ownership sits in reasoning policy or runtime acceptance.

First Proof Check

• packages/bijux-canon-agent/src/bijux_canon_agent for the orchestration boundary in code
• packages/bijux-canon-agent/tests for proof that workflow coordination remains deterministic and inspectable
• packages/bijux-canon-agent/apis for tracked agent-facing contracts

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 you need the module or control-flow map
• leave this section for Interfaces when the live question is a caller-facing contract
• leave this section for Quality when the boundary is clear and the real issue is proof, invariants, or review gates

Design Pressure

If “agent” becomes a label for any cross-package behavior, the package loses all discipline. This section has to keep coordination, traceability, and handoff authority visibly separate.