Foundation¶

The foundation section explains the durable role of agentic-proteins before it explains implementation detail. Use it to resolve why preserved legacy surfaces still belong here instead of in the canonical runtime package.

flowchart TB
    past["legacy callers still exist"]
    bridge["agentic-proteins<br/>compatibility package"]
    runtime["canonical runtime"]
    retire["bridge can shrink"]

    past --> bridge
    bridge --> runtime
    runtime --> retire

Why This Section Exists¶

it helps the reader understand why a package can be valuable even while being temporary
it makes retirement pressure explicit instead of letting compatibility linger without a reason
it distinguishes bridge ownership from canonical runtime ownership

Start With¶

Open Package Overview for the shortest statement of the package role.
Open Ownership Boundary when the question is whether a change belongs here or in a neighbor.
Open Scope and Non-Goals when a proposed change risks broadening the package.
Open Capability Map when you need the concrete work the package is allowed to do.

Section Pages¶

What This Section Settles¶

whether a preserved surface still needs a bridge
whether compatibility logic is still narrow enough to stay here
when a legacy concern should move fully into runtime or disappear

First Proof Check¶

packages/agentic-proteins
packages/agentic-proteins/tests
neighboring handbooks once the change crosses the local boundary

Neighbors¶

Open bijux-proteomics-runtime when the question leaves compatibility forwarding for legacy runtime imports and entrypoints.
Open Repository Handbook when the issue is clearly outside this package's local role.