Python Backend Core

Shared model for the python-backend cluster. The framework, testing, security, and ML spokes all depend on these conventions — keep them consistent here so no spoke contradicts another.

1. The decision this cluster turns on: a thin adapter over a typed core

Every spoke assumes the same layering. The HTTP/task layer is thin; it parses, validates, delegates, and serializes. Business logic lives in plain, typed, testable Python that knows nothing about the request:

Request ──> Boundary (validate + parse) ──> Service / domain (typed, framework-free) ──> Persistence
                  ▲                                   │
              serialize ◄────────── typed result ◄────┘