Skip to content

Operations

agentic-proteins operations is about preserving trust while the compatibility surface keeps getting less important. A maintainer working in this package should always be asking two questions: did we preserve old callers, and did we avoid rebuilding new authority here?

flowchart LR
    change["compatibility change"]
    route["trace affected entrypoints<br/>CLI, API, imports"]
    prove["prove forwarding and parity<br/>tests, migration checks"]
    release["publish compatibility surface"]
    observe["watch deprecation pressure<br/>docs, release notes, incidents"]
    retire["remove bridge only when<br/>canonical proof is stronger"]

    change --> route --> prove --> release --> observe --> retire

The Operating Job

  • keep legacy callers working without letting the package become the preferred home for new work
  • treat migration proof as part of operations, not as optional background paperwork
  • make release decisions based on compatibility evidence, not just passing package-local tests

Start With

  • open Common Workflows when you need the expected path from edit to proof
  • open Local Development when you are actively changing forwarding behavior or compatibility tests
  • open Release and Versioning before deciding that a compatibility change is publishable
  • open Failure Recovery when callers are already seeing drift between legacy and canonical behavior

Route From Symptom

What Good Looks Like Here

  • compatibility preservation is measurable
  • migration validation stays close to every release decision
  • retirement pressure remains visible in docs, release notes, and review

First Proof Check

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