Interfaces

agentic-proteins interfaces should tell a reader exactly which public surfaces are real, which are only compatibility bridges, and which nearby package actually owns the next step.

The canonical runtime API root is apis/bijux-proteomics-runtime/v1; the compatibility mirror root is apis/agentic-proteins/v1.

flowchart LR
    imports["legacy imports"]
    cli["legacy CLI paths"]
    api["legacy API entrypoints"]
    bridge["agentic-proteins interfaces"]
    runtime["runtime interfaces"]

    imports --> bridge
    cli --> bridge
    api --> bridge
    bridge --> runtime

What Makes This Section Useful

• it distinguishes preserved access paths from canonical runtime ownership
• it helps readers avoid treating a shim as the true long-term interface
• it makes compatibility promises visible enough to review and retire

Start With

• open Public Imports when the question starts from code
• open Data Contracts when the question is really about payload meaning or compatibility
• open Compatibility Commitments before changing any documented public promise

Section Pages

• Public Imports
• Data Contracts
• Artifact Contracts
• API Surface
• CLI Surface
• Configuration Surface
• Entrypoints and Examples
• Operator Workflows
• Compatibility Commitments

What This Package Publishes

• legacy imports, CLI paths, API entrypoints, and runtime-facing compatibility artifacts

What This Section Settles

• which public surfaces are still intentionally preserved
• which compatibility promises are strong enough to document
• where a reader should go once the question stops being about legacy access

First Proof Check

• src/agentic_proteins/interfaces/cli.py
• src/agentic_proteins/api/app.py
• packages/agentic-proteins/tests