bijux-canon-agent

bijux-canon-agent is the package that turns a declared agent workflow into a deterministic, inspectable execution. It is where role implementations, pipeline coordination, trace production, and package-local operator surfaces come together.

If you need to understand how an agent run is composed, how trace-backed output is produced, or where agent-facing CLI and HTTP behavior lives, start here. If you need replay governance, runtime persistence, or cross-package execution authority, you are probably looking for bijux-canon-runtime instead.

What This Package Takes And Produces

• takes: declared agent workflows, role-specific inputs, local orchestration settings, and package-local boundary requests
• produces: deterministic agent traces, role outputs, operator-facing artifacts, and explicit workflow failures when orchestration contracts are broken
• guarantees: role orchestration stays inspectable and trace-backed instead of collapsing into one opaque tool invocation
• does not do: decide runtime replay acceptance, own ingest or index package behavior, or treat provider integrations as cross-package authority

Dependency Surface

Treat the base package as the canonical orchestration surface. CLI, HTTP, provider, and template integrations are package-owned extensions that must stay subordinate to the trace and workflow contract, not the other way around.

Package continuity

• compatibility package: bijux-agent
• previous import root: bijux_agent
• previous command: bijux-agent
• canonical migration guide: Migration guidance
• retired repository target: https://github.com/bijux/bijux-agent (see Repository consolidation notes)

What this package owns

• agent role implementations and the helpers that are specific to those roles
• deterministic orchestration of the local agent pipeline
• trace-backed result artifacts that explain what happened during a run
• package-local CLI and HTTP boundaries for invoking agent workflows

What this package does not own

• runtime-wide persistence, replay acceptance, or execution governance
• ingest and index engines that belong to other package boundaries
• repository tooling, release automation, or root-level quality workflows

Source map

• src/bijux_canon_agent/agents for role-local behavior
• src/bijux_canon_agent/pipeline for execution flow
• src/bijux_canon_agent/application for orchestration policies
• src/bijux_canon_agent/interfaces for CLI and HTTP edges
• src/bijux_canon_agent/traces for durable trace-facing models
• tests for executable package truth

Read this next

• Package guide
• Ownership boundary
• Architecture overview
• Interface contracts
• Operator workflows
• Compatibility packages
• Changelog

Primary entrypoint

• console script: bijux-canon-agent

Release Readiness

• release line prepared for publish: 0.3.9
• release date: 2026-07-04
• package changelog: CHANGELOG.md