a13n-service 0.0.3__tar.gz

a13n_service-0.0.3/.gitignore

@@ -0,0 +1,62 @@
+# Local reference and discussion material
+discussion/
+local-reference/
+
+# Python bytecode and native extensions
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+
+# Python packaging
+build/
+dist/
+*.egg-info/
+.eggs/
+wheels/
+
+# Python environments
+.env
+.env.*
+!.env.example
+.venv/
+env/
+venv/
+
+# Tests, coverage, and static analysis
+.coverage
+.coverage.*
+.cache/
+.hypothesis/
+.mypy_cache/
+.nox/
+.pyright/
+.pytest_cache/
+.ruff_cache/
+.tox/
+coverage.xml
+htmlcov/
+
+# Documentation output
+site/
+
+# Cloudflare Wrangler local state
+.wrangler/
+
+# Rust
+target/
+**/*.rs.bk
+
+# Frontend tooling
+node_modules/
+*.tsbuildinfo
+/apps/harness-ui/dist/
+/packages/agent-ui/a13n_ui/static/
+
+# Editors and operating systems
+.DS_Store
+.idea/
+
+# Logs and temporary files
+*.log
+*.tmp

a13n_service-0.0.3/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Converge AI
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

a13n_service-0.0.3/PKG-INFO

@@ -0,0 +1,222 @@
+Metadata-Version: 2.5
+Name: a13n-service
+Version: 0.0.3
+Summary: Hosted control and execution service for Agent Foundation
+License-Expression: Apache-2.0
+License-File: LICENSE
+Requires-Python: >=3.13
+Requires-Dist: a13n-logging
+Requires-Dist: aiobotocore[httpx2]<4,>=3.9
+Requires-Dist: aiosqlite<1,>=0.21
+Requires-Dist: alembic<2,>=1.17.1
+Requires-Dist: anyio<5,>=4
+Requires-Dist: botocore<1.43.57,>=1.43.3
+Requires-Dist: click<9,>=8.2
+Requires-Dist: fakeredis<3,>=2.31
+Requires-Dist: fastapi<1,>=0.116
+Requires-Dist: httpx2<3,>=2.5
+Requires-Dist: psycopg[binary]<4,>=3.2
+Requires-Dist: pydantic-settings<3,>=2.10
+Requires-Dist: pydantic<3,>=2.12
+Requires-Dist: redis<9,>=8
+Requires-Dist: sqlalchemy[asyncio]<3,>=2.0.41
+Requires-Dist: starlette<2,>=1.6
+Requires-Dist: uvicorn<1,>=0.35
+Description-Content-Type: text/markdown
+
+# Foundation Service
+
+This package contains the hosted Foundation Service executable, its internal async-first storage substrate, and its service-owned relational schema lifecycle. It is a workspace package, not a public SDK or an independently distributed provider library.
+
+The substrate exposes capability-specific interfaces instead of one generic storage facade:
+
+- SQL uses SQLAlchemy's async `AsyncEngine` and `AsyncSession` APIs with PostgreSQL or SQLite.
+- Redis-compatible data structures use `redis.asyncio.Redis` with Redis or process-local fakeredis.
+- Objects use the small Foundation-owned `ObjectStore` protocol with S3-compatible or local-directory adapters.
+- Local files and deployment-mounted NFS use the same confined `pathlib` and AnyIO helpers.
+
+Backend selection happens once during process startup. A failed network backend never falls back to local state.
+
+## Runtime
+
+`ServiceSettings` owns the `FOUNDATION_*` environment contract and maps it to the frozen `StorageSettings` model. The storage package accepts typed configuration and does not read process environment variables itself. `foundation-service serve` constructs all selected providers once in FastAPI lifespan, publishes the resulting `StorageResources` on `app.state.storage`, and closes the resources during shutdown.
+
+The default service profile keeps the existing PostgreSQL and Redis endpoints and uses separate local roots for objects and files. Set `FOUNDATION_OBJECT_BACKEND=s3` and `FOUNDATION_OBJECT_BUCKET` for a multi-process deployment; the local object adapter supports only one writing process. `FOUNDATION_FILESYSTEM_ROOT` may be an ordinary local directory or an NFS mount prepared by deployment.
+
+```python
+from pathlib import Path
+
+from a13n_service.storage import StorageSettings, open_storage
+
+settings = StorageSettings.model_validate(
+    {
+        "database": {"backend": "sqlite", "path": Path("var/foundation.sqlite3")},
+        "redis": {"backend": "memory"},
+        "objects": {"backend": "local", "root": Path("var/objects")},
+        "filesystem": {"root": Path("var/files")},
+    }
+)
+
+async with open_storage(settings) as storage:
+    # Inject `storage` into application-owned services here.
+    ...
+```
+
+`open_storage()` constructs one engine, session factory, Redis client, object store, and filesystem boundary. It checks required capabilities before yielding and closes all resources in reverse order.
+
+A network deployment selects the corresponding backends without changing consumer code:
+
+```python
+network_settings = StorageSettings.model_validate(
+    {
+        "database": {
+            "backend": "postgresql",
+            "url": "postgresql://foundation:password@postgres/foundation",
+        },
+        "redis": {"backend": "redis", "url": "redis://redis:6379/0"},
+        "objects": {
+            "backend": "s3",
+            "bucket": "foundation-objects",
+            "region": "us-east-1",
+        },
+        "filesystem": {"root": Path("/mnt/foundation-files")},
+    }
+)
+```
+
+The S3 client uses the standard AWS credential chain. Set `endpoint_url` and `force_path_style` only for a compatible non-AWS endpoint. The deployment mounts NFS at the configured filesystem root before the process starts.
+
+## Relational Usage
+
+Consumers use SQLAlchemy directly. Generic storage does not define `get`, `insert`, or `do` wrappers.
+
+```python
+from sqlalchemy import select
+
+from a13n_service.storage import transaction
+
+async with transaction(storage.sessions) as session:
+    result = await session.execute(select(Record).where(Record.id == record_id))
+    record = result.scalar_one_or_none()
+```
+
+Each operation gets a short session. Never retain a session or transaction across external I/O, agent execution, sleeps, background work, or a streaming response.
+
+PostgreSQL is the distributed-service backend. SQLite is intended for a single-process, zero-service profile and must not be placed on NFS.
+
+## Relational Schema and Migrations
+
+Generic relational storage and service schema ownership are deliberately separate:
+
+- `storage/relational.py` constructs async engines and short sessions for application I/O.
+- `database/metadata.py` aggregates every service-owned ORM model.
+- `database/migrations/` contains one linear Alembic history for the complete service database.
+- `database/migration.py` owns the dedicated synchronous migration connection, bounded PostgreSQL advisory locking, and Alembic invocation.
+
+The Alembic environment does not read process settings or create an engine. The runner supplies one validated connection, so CLI settings, lock policy, and schema comparison have distinct owners.
+
+Select the database backend, then use the stable service CLI or repository commands:
+
+```bash
+FOUNDATION_DATABASE_BACKEND=postgresql
+FOUNDATION_DATABASE_URL=postgresql+psycopg://foundation:foundation@127.0.0.1:5432/foundation
+
+make db-upgrade
+make db-current
+make db-check
+make db-history
+```
+
+The corresponding executable commands are `foundation-service db upgrade`, `foundation-service db current --check-heads`, `foundation-service db history`, and `foundation-service db migrate "description"`. There is one process CLI; migration implementation remains in `database/migration.py` rather than introducing a second database-only settings or command layer.
+
+For the zero-service profile, set `FOUNDATION_DATABASE_BACKEND=sqlite` and `FOUNDATION_DATABASE_SQLITE_PATH=var/foundation.sqlite3`. The same accepted history is applied to both backends. A domain requiring PostgreSQL-only schema behavior must reject SQLite explicitly.
+
+### Add an ORM Model
+
+1. Define the model beside its owning domain using `a13n_service.database.Base`.
+2. Import that domain model module explicitly in `database/metadata.py`; there is no package scanning or plugin discovery.
+3. Run `make db-migrate msg="describe the schema change"`. The target rebuilds accepted history in a disposable PostgreSQL database before autogeneration.
+4. Review the generated revision for names, constraints, data loss, lock behavior, rolling compatibility, interruption safety, and downgrade or forward repair.
+5. Run the database tests on SQLite and PostgreSQL plus `make db-check` against an upgraded database.
+
+Do not create revision files by hand and do not use runtime `metadata.create_all()` as schema bootstrap. Application request paths use async SQLAlchemy; migrations use a separate synchronous `NullPool` connection because they run before traffic or in a dedicated deployment job.
+
+## Redis Usage
+
+The injected async redis-py client exposes strings, hashes, lists, sets, sorted sets, Streams, pipelines, transactions, and Pub/Sub without local/network branches.
+
+```python
+await storage.redis.hset(b"run:1", mapping={b"status": b"running"})
+await storage.redis.rpush(b"run:1:steps", b"step-1")
+await storage.redis.xadd(b"run-events", {b"payload": payload})
+```
+
+Response decoding is disabled for binary safety. The fakeredis backend is process-local and non-durable; use a real Redis service for multiple processes, persistence, modules, or exact server failure behavior.
+
+## Object Usage
+
+Object keys are opaque names rather than filesystem paths. `put` supports unconditional, create-only, and expected-version publication.
+
+```python
+from a13n_service.storage import ByteRange, ObjectConflict
+
+created = await storage.objects.put(
+    "artifacts/result.json",
+    payload,
+    content_type="application/json",
+    metadata={"trace": trace_id},
+    if_none_match=True,
+)
+
+async with storage.objects.open("artifacts/result.json", byte_range=ByteRange(0, 64)) as reader:
+    prefix = b"".join([chunk async for chunk in reader])
+
+try:
+    updated = await storage.objects.put(
+        "artifacts/result.json",
+        new_payload,
+        if_match=created.version,
+    )
+except ObjectConflict:
+    # Re-read and make a new domain decision.
+    ...
+```
+
+S3 endpoints must support AWS-compatible conditional writes and deletes, range reads, head requests, and ordered `ListObjectsV2` pagination. Startup rejects endpoints that silently ignore these conditions. The local adapter provides the common behavior for exactly one writing service process.
+
+Metadata keys are normalized to lowercase and, like S3 REST metadata, keys and values must be ASCII. Keys must also be valid HTTP field names. Returned metadata mappings are immutable.
+
+## Filesystem Usage
+
+Deployment mounts NFS before process startup. Application code receives the mounted root and uses the same helpers as a local directory; there is no Python NFS provider.
+
+```python
+import anyio
+
+from a13n_service.storage.filesystem import atomic_write, resolve_under_root
+
+destination = await resolve_under_root(
+    storage.files_root,
+    "exports/result.json",
+    limiter=storage.file_limiter,
+)
+await atomic_write(destination, chunks, limiter=storage.file_limiter)
+
+async with await anyio.open_file(destination, "rb") as file:
+    prefix = await file.read(64 * 1024)
+```
+
+Confined resolution rejects absolute paths, parent traversal, and symlink escape. Atomic replacement is guaranteed only within one filesystem.
+
+## Verification
+
+Run the infrastructure suites and package checks from the repository root:
+
+```bash
+uv run --package a13n-service pytest packages/foundation-service/tests/storage packages/foundation-service/tests/database -q
+make lint
+make typecheck
+uv build --package a13n-service
+```
+
+Container-owned integration tests exercise PostgreSQL, Redis, and S3 HTTP behavior. The S3 startup-probe test also demonstrates that an endpoint missing required conditional-delete semantics is rejected rather than silently accepted.

a13n_service-0.0.3/README.md

@@ -0,0 +1,196 @@
+# Foundation Service
+
+This package contains the hosted Foundation Service executable, its internal async-first storage substrate, and its service-owned relational schema lifecycle. It is a workspace package, not a public SDK or an independently distributed provider library.
+
+The substrate exposes capability-specific interfaces instead of one generic storage facade:
+
+- SQL uses SQLAlchemy's async `AsyncEngine` and `AsyncSession` APIs with PostgreSQL or SQLite.
+- Redis-compatible data structures use `redis.asyncio.Redis` with Redis or process-local fakeredis.
+- Objects use the small Foundation-owned `ObjectStore` protocol with S3-compatible or local-directory adapters.
+- Local files and deployment-mounted NFS use the same confined `pathlib` and AnyIO helpers.
+
+Backend selection happens once during process startup. A failed network backend never falls back to local state.
+
+## Runtime
+
+`ServiceSettings` owns the `FOUNDATION_*` environment contract and maps it to the frozen `StorageSettings` model. The storage package accepts typed configuration and does not read process environment variables itself. `foundation-service serve` constructs all selected providers once in FastAPI lifespan, publishes the resulting `StorageResources` on `app.state.storage`, and closes the resources during shutdown.
+
+The default service profile keeps the existing PostgreSQL and Redis endpoints and uses separate local roots for objects and files. Set `FOUNDATION_OBJECT_BACKEND=s3` and `FOUNDATION_OBJECT_BUCKET` for a multi-process deployment; the local object adapter supports only one writing process. `FOUNDATION_FILESYSTEM_ROOT` may be an ordinary local directory or an NFS mount prepared by deployment.
+
+```python
+from pathlib import Path
+
+from a13n_service.storage import StorageSettings, open_storage
+
+settings = StorageSettings.model_validate(
+    {
+        "database": {"backend": "sqlite", "path": Path("var/foundation.sqlite3")},
+        "redis": {"backend": "memory"},
+        "objects": {"backend": "local", "root": Path("var/objects")},
+        "filesystem": {"root": Path("var/files")},
+    }
+)
+
+async with open_storage(settings) as storage:
+    # Inject `storage` into application-owned services here.
+    ...
+```
+
+`open_storage()` constructs one engine, session factory, Redis client, object store, and filesystem boundary. It checks required capabilities before yielding and closes all resources in reverse order.
+
+A network deployment selects the corresponding backends without changing consumer code:
+
+```python
+network_settings = StorageSettings.model_validate(
+    {
+        "database": {
+            "backend": "postgresql",
+            "url": "postgresql://foundation:password@postgres/foundation",
+        },
+        "redis": {"backend": "redis", "url": "redis://redis:6379/0"},
+        "objects": {
+            "backend": "s3",
+            "bucket": "foundation-objects",
+            "region": "us-east-1",
+        },
+        "filesystem": {"root": Path("/mnt/foundation-files")},
+    }
+)
+```
+
+The S3 client uses the standard AWS credential chain. Set `endpoint_url` and `force_path_style` only for a compatible non-AWS endpoint. The deployment mounts NFS at the configured filesystem root before the process starts.
+
+## Relational Usage
+
+Consumers use SQLAlchemy directly. Generic storage does not define `get`, `insert`, or `do` wrappers.
+
+```python
+from sqlalchemy import select
+
+from a13n_service.storage import transaction
+
+async with transaction(storage.sessions) as session:
+    result = await session.execute(select(Record).where(Record.id == record_id))
+    record = result.scalar_one_or_none()
+```
+
+Each operation gets a short session. Never retain a session or transaction across external I/O, agent execution, sleeps, background work, or a streaming response.
+
+PostgreSQL is the distributed-service backend. SQLite is intended for a single-process, zero-service profile and must not be placed on NFS.
+
+## Relational Schema and Migrations
+
+Generic relational storage and service schema ownership are deliberately separate:
+
+- `storage/relational.py` constructs async engines and short sessions for application I/O.
+- `database/metadata.py` aggregates every service-owned ORM model.
+- `database/migrations/` contains one linear Alembic history for the complete service database.
+- `database/migration.py` owns the dedicated synchronous migration connection, bounded PostgreSQL advisory locking, and Alembic invocation.
+
+The Alembic environment does not read process settings or create an engine. The runner supplies one validated connection, so CLI settings, lock policy, and schema comparison have distinct owners.
+
+Select the database backend, then use the stable service CLI or repository commands:
+
+```bash
+FOUNDATION_DATABASE_BACKEND=postgresql
+FOUNDATION_DATABASE_URL=postgresql+psycopg://foundation:foundation@127.0.0.1:5432/foundation
+
+make db-upgrade
+make db-current
+make db-check
+make db-history
+```
+
+The corresponding executable commands are `foundation-service db upgrade`, `foundation-service db current --check-heads`, `foundation-service db history`, and `foundation-service db migrate "description"`. There is one process CLI; migration implementation remains in `database/migration.py` rather than introducing a second database-only settings or command layer.
+
+For the zero-service profile, set `FOUNDATION_DATABASE_BACKEND=sqlite` and `FOUNDATION_DATABASE_SQLITE_PATH=var/foundation.sqlite3`. The same accepted history is applied to both backends. A domain requiring PostgreSQL-only schema behavior must reject SQLite explicitly.
+
+### Add an ORM Model
+
+1. Define the model beside its owning domain using `a13n_service.database.Base`.
+2. Import that domain model module explicitly in `database/metadata.py`; there is no package scanning or plugin discovery.
+3. Run `make db-migrate msg="describe the schema change"`. The target rebuilds accepted history in a disposable PostgreSQL database before autogeneration.
+4. Review the generated revision for names, constraints, data loss, lock behavior, rolling compatibility, interruption safety, and downgrade or forward repair.
+5. Run the database tests on SQLite and PostgreSQL plus `make db-check` against an upgraded database.
+
+Do not create revision files by hand and do not use runtime `metadata.create_all()` as schema bootstrap. Application request paths use async SQLAlchemy; migrations use a separate synchronous `NullPool` connection because they run before traffic or in a dedicated deployment job.
+
+## Redis Usage
+
+The injected async redis-py client exposes strings, hashes, lists, sets, sorted sets, Streams, pipelines, transactions, and Pub/Sub without local/network branches.
+
+```python
+await storage.redis.hset(b"run:1", mapping={b"status": b"running"})
+await storage.redis.rpush(b"run:1:steps", b"step-1")
+await storage.redis.xadd(b"run-events", {b"payload": payload})
+```
+
+Response decoding is disabled for binary safety. The fakeredis backend is process-local and non-durable; use a real Redis service for multiple processes, persistence, modules, or exact server failure behavior.
+
+## Object Usage
+
+Object keys are opaque names rather than filesystem paths. `put` supports unconditional, create-only, and expected-version publication.
+
+```python
+from a13n_service.storage import ByteRange, ObjectConflict
+
+created = await storage.objects.put(
+    "artifacts/result.json",
+    payload,
+    content_type="application/json",
+    metadata={"trace": trace_id},
+    if_none_match=True,
+)
+
+async with storage.objects.open("artifacts/result.json", byte_range=ByteRange(0, 64)) as reader:
+    prefix = b"".join([chunk async for chunk in reader])
+
+try:
+    updated = await storage.objects.put(
+        "artifacts/result.json",
+        new_payload,
+        if_match=created.version,
+    )
+except ObjectConflict:
+    # Re-read and make a new domain decision.
+    ...
+```
+
+S3 endpoints must support AWS-compatible conditional writes and deletes, range reads, head requests, and ordered `ListObjectsV2` pagination. Startup rejects endpoints that silently ignore these conditions. The local adapter provides the common behavior for exactly one writing service process.
+
+Metadata keys are normalized to lowercase and, like S3 REST metadata, keys and values must be ASCII. Keys must also be valid HTTP field names. Returned metadata mappings are immutable.
+
+## Filesystem Usage
+
+Deployment mounts NFS before process startup. Application code receives the mounted root and uses the same helpers as a local directory; there is no Python NFS provider.
+
+```python
+import anyio
+
+from a13n_service.storage.filesystem import atomic_write, resolve_under_root
+
+destination = await resolve_under_root(
+    storage.files_root,
+    "exports/result.json",
+    limiter=storage.file_limiter,
+)
+await atomic_write(destination, chunks, limiter=storage.file_limiter)
+
+async with await anyio.open_file(destination, "rb") as file:
+    prefix = await file.read(64 * 1024)
+```
+
+Confined resolution rejects absolute paths, parent traversal, and symlink escape. Atomic replacement is guaranteed only within one filesystem.
+
+## Verification
+
+Run the infrastructure suites and package checks from the repository root:
+
+```bash
+uv run --package a13n-service pytest packages/foundation-service/tests/storage packages/foundation-service/tests/database -q
+make lint
+make typecheck
+uv build --package a13n-service
+```
+
+Container-owned integration tests exercise PostgreSQL, Redis, and S3 HTTP behavior. The S3 startup-probe test also demonstrates that an endpoint missing required conditional-delete semantics is rejected rather than silently accepted.