Architecture decisions
Each record states one choice that constrains future work across pykit packages,
why it was made, and what it costs. Package guides describe the current APIs;
the spec board tracks work.
| Decision |
Scope |
Status |
| ADR-0001: Standards and proven libraries come first; pykit wraps, never reimplements |
Design principles |
accepted |
| ADR-0002: Code is placed by what its API contains, and boundaries are one-way |
Package placement and imports |
accepted |
| ADR-0003: Optional integrations stay behind explicit extras and outside the facade |
Optional dependencies |
accepted |
| ADR-0004: Packages release independently under their own tags and version ranges |
Package distribution |
accepted |
| ADR-0005: One framework-neutral HTTP contract, adapted natively by each framework |
HTTP contract |
accepted |
| ADR-0006: pykit verifies tokens an authorization server issued and never issues its own; browsers hold a session, not a token |
Authentication scope |
accepted |
| ADR-0007: pykit's docs follow the shared rn-forge docs standard |
Documentation structure |
accepted |
| ADR-0008: pykit is accepted by its own specs and tests |
Specs, acceptance and releases |
accepted |
| ADR-0009: Each package publishes its own versioned docs; the root site browses them all |
Package documentation |
accepted |
ADR-0010: Soft delete is a nullable delete_time column, in AIP-164's shape |
Soft delete |
accepted |
| ADR-0011: A part of commons becomes its own package only when it passes three tests, and every package takes adapters the same way |
Package boundaries |
accepted |
| ADR-0012: CI and release logic ships as the rn-forge-devops package, never as workflow logic or copied scripts |
CI and release automation |
accepted |
| ADR-0013: Every caller resolves to an internal account, and authorization is computed on the server per request |
Identity resolution and authorization |
accepted |
| ADR-0014: Django and FastAPI expose the same auth HTTP surface and security defaults, over whichever library fits each framework |
Auth framework parity |
accepted |
| ADR-0015: The security baseline is nine named controls, each either failing the build or only reporting, with evidence per release |
Security baseline |
accepted |
| ADR-0016: AppLogger formats braces on its own records and never replaces the process record factory |
Logging record factories |
accepted |
| ADR-0017: The rn-forge home is a written contract that every installer implements, and the home owns the shell hookup |
Tool install home |
accepted |