Skip to content

Repository Fit

bijux-canon-agent is a separate package because orchestration creates its own readability and contract pressure. Keeping it visible stops workflow logic from hiding inside reasoning code or runtime policy.

Fit Model

flowchart LR
    seam["orchestration seam"]
    package["bijux-canon-agent package boundary"]
    proof["metadata, apis, tests, and handbook"]

    seam --> package --> proof

This page should justify agent as a distinct package instead of a convenient bucket for late-stage workflow code. The fit is strong only when orchestration itself is easier to inspect because the seam exists.

Why This Is A Package

  • packages/bijux-canon-agent/src/bijux_canon_agent makes orchestration ownership visible in code
  • packages/bijux-canon-agent/tests proves determinism and trace quality at the package seam
  • packages/bijux-canon-agent/apis shows where orchestration behavior becomes a tracked public surface

First Proof Check

  • packages/bijux-canon-agent/pyproject.toml for publishable package identity
  • packages/bijux-canon-agent/README.md for package-level reader framing
  • packages/bijux-canon-agent/tests for executable proof that the seam still matters

Fit Warning

If the package can only be defended as “where the workflow code lives,” the orchestration seam has not been explained well enough.

Design Pressure

If agent can only be defended as “where the workflow code lives,” the package boundary has lost its explanatory value. The repository split has to make orchestration more legible, not merely more separate.