aggregate_api 1.0.0__tar.gz

aggregate_api-1.0.0/LICENSE

@@ -0,0 +1,28 @@
+BSD 3-Clause License
+
+Copyright (c) 2026, Stephen J. Mildenhall
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this
+   list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice,
+   this list of conditions and the following disclaimer in the documentation
+   and/or other materials provided with the distribution.
+
+3. Neither the name of the copyright holder nor the names of its
+   contributors may be used to endorse or promote products derived from
+   this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

aggregate_api-1.0.0/PKG-INFO

@@ -0,0 +1,187 @@
+Metadata-Version: 2.4
+Name: aggregate_api
+Version: 1.0.0
+Summary: aggregate Loss Lab (aLL): FastAPI service and single-page web app for the aggregate actuarial library.
+Author-email: "Stephen J. Mildenhall" <steve@convexrisk.com>
+Maintainer-email: "Stephen J. Mildenhall" <steve@convexrisk.com>
+License-Expression: BSD-3-Clause
+Project-URL: Homepage, https://github.com/mynl/aggregate_api
+Project-URL: Source Code, https://github.com/mynl/aggregate_api
+Project-URL: Documentation, https://github.com/mynl/aggregate_api#readme
+Project-URL: Changelog, https://github.com/mynl/aggregate_api/blob/main/CHANGELOG.md
+Project-URL: Issues, https://github.com/mynl/aggregate_api/issues
+Keywords: actuarial,insurance,reinsurance,risk,aggregate loss,compound distribution,FFT,pricing,DecL
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Financial and Insurance Industry
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Office/Business :: Financial
+Classifier: Topic :: Scientific/Engineering :: Mathematics
+Classifier: Framework :: FastAPI
+Requires-Python: >=3.13
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: aggregate<2,>=1.0.1
+Requires-Dist: greater-tables>=6.0.0
+Requires-Dist: fastapi>=0.115
+Requires-Dist: uvicorn[standard]>=0.30
+Requires-Dist: pydantic>=2.7
+Requires-Dist: pydantic-settings>=2.4
+Provides-Extra: dev
+Requires-Dist: pytest>=7; extra == "dev"
+Requires-Dist: httpx>=0.27; extra == "dev"
+Requires-Dist: ruff>=0.6; extra == "dev"
+Provides-Extra: status
+Requires-Dist: psutil>=5.9; extra == "status"
+Dynamic: license-file
+
+# aggregate_api
+
+**aggregate Loss Lab** (aLL): a FastAPI service and a single-page web app for
+the [`aggregate`](https://github.com/mynl/aggregate) actuarial library.
+*Description to distribution.*
+
+`aggregate_api` is the package; **aggregate Loss Lab** is the app it serves.
+It puts `build()` behind an HTTP/JSON api (DecL parsing, FFT-based compound
+distributions, plotting, and risk pricing) and ships a Bootstrap 5 and
+CodeMirror 6 DecL workbench that runs against it. A single `aggregate-api`
+process serves both the web UI (at `/`) and the JSON endpoints (under `/v1`)
+same-origin.
+
+> **Status:** 1.0.0, the first public release. Extracted from the `aggregate`
+> repo so the library can ship without it. The package is installable and
+> supported; the `/v1` surface is not yet a frozen interface, and the caveat at
+> the end of [Running headless](#running-headless) says why. See
+> [CHANGELOG.md](CHANGELOG.md) for what has landed and
+> [dev/TODO.md](dev/TODO.md) for the roadmap.
+
+## What's inside
+
+- **Backend** (`src/aggregate_api/`): FastAPI app. Object lifecycle
+  (`POST /v1/objects` to build and cache, then `info`, `meta`, `summary`,
+  `tail_df`, `validation_df`, `stats_df`, `density_df`, `plot`, `kappa`,
+  `price`, `pricing_at`, plus `frame/{which}` in CSV or table-document form),
+  DecL helpers (`/v1/decl/complete`, `/lex`,
+  `/format`), and the example library read straight from `aggregate`'s recipe
+  base (`/v1/examples`, `/v1/examples/heroes`). In-memory LRU cache, build
+  timeout, SQLite audit log, CORS. Swagger UI at `/docs`.
+- **Frontend** (`web/`): vanilla-JS SPA (Vite, Bootstrap, CodeMirror 6,
+  `csv-grid`). A DecL editor with syntax highlighting, autocomplete and history,
+  a landing gallery of showcase examples, tabbed risk output, interactive and
+  native plots, and a rich parse-error pane.
+
+### Tables: one payload, two renderers
+
+Every table under 500 rows is fetched once, as a **table document**: versioned
+JSON carrying semantics only (dtypes, resolved formats, hierarchy, spans, flags)
+and no widths or CSS. Both views render from that one document, so they cannot
+disagree about a number:
+
+- **Static** is `greater_tables`' own JS walker, which draws a book-quality table
+  (sparsified row index, spanned headers, partial rules). The walker and its
+  stylesheet are served straight out of the installed Python package at
+  `/v1/assets/`, so the renderer and the documents it renders can never version
+  skew.
+- **Interactive** is `csv-grid`, fed by `irToGridInput(doc)`: sort, per-column
+  filter, fzf search, copy and save.
+
+Which one you get is a page-wide preference in the header menu. Large frames (the
+densities) skip the document entirely and go to the grid, which is the honest
+instrument for them.
+
+## Install
+
+Requires Python ≥ 3.13. Nothing else: `aggregate` ≥ 1.0.1 and
+`greater-tables` ≥ 6.0.0 come from PyPI with it.
+
+```
+pip install aggregate_api
+aggregate-api --port 8001
+```
+
+Then open http://127.0.0.1:8001/ for the app, or http://127.0.0.1:8001/docs for
+the api.
+
+> **Install the wheel, not the repository.** The web bundle is 2.5 MB of
+> generated Vite output and is deliberately not in git, so it reaches you in the
+> built distribution and only there. `pip install git+https://github.com/mynl/aggregate_api`
+> installs a working api whose `/` returns 404, which is a reasonable thing to
+> want if you are putting your own front end in front of the engine, and a
+> baffling one otherwise. The wheel and sdist are also attached to each
+> [GitHub release](https://github.com/mynl/aggregate_api/releases).
+
+One footnote, which the pins above handle for you and which bites anyone
+installing the table engine on its own: PyPI's `greater-tables` 5.3 is a
+previous generation sharing the `greater_tables` import name, so a bare
+`pip install greater-tables` can get a package with no `build`, `canonical_json`
+or `IR_VERSION`, which fails at import rather than at install. This package pins
+`>=6.0.0` and `tests/test_meta.py` asserts the right generation is present.
+
+## Develop
+
+Needs [`uv`](https://docs.astral.sh/uv/) and Node for the web build. A fresh
+clone syncs with nothing checked out beside it.
+
+```
+git clone https://github.com/mynl/aggregate_api
+cd aggregate_api
+uv sync --extra dev
+.\scripts\build-web.ps1          # Windows; ./scripts/build-web.sh on Unix
+uv run aggregate-api --port 8001 --reload
+```
+
+`build-web` drops the bundle into `src/aggregate_api/static/`, which the FastAPI
+`StaticFiles` mount serves at `/`. Until it has run once, `/` has nothing to
+serve. For hot reload with a Vite dev server proxying `/v1` to `:8000`, use
+`cd web; npm install; npm run dev` instead.
+
+To develop against a local checkout of `aggregate` or `greater-tables` rather
+than the released build, install it editable over the synced environment:
+
+```
+uv pip install -e ../aggregate               # or wherever the checkout is
+```
+
+The next `uv sync` silently reinstalls the released build, so `uv run --no-sync`
+is the way to work in between.
+
+Run the tests. There are two suites and both are the gate:
+
+```
+uv run pytest           # 490 tests, FastAPI TestClient, no live server needed
+cd web; npm test        # 277 tests, node --test over web/test/
+```
+
+Rehearse a release, which is a stronger check than either suite because it
+builds the distributions and runs everything against the installed wheel in a
+clean environment:
+
+```
+.\scripts\release-check.ps1
+```
+
+### Running headless
+
+One process serves both halves: the routers mount under `/v1`, and the built web
+bundle is mounted at `/`. To run the engine alone, behind somebody else's front
+end, say so:
+
+```
+uv run aggregate-api --headless           # or AGGAPI_SERVE_SPA=0
+```
+
+`/v1`, `/docs` and `/openapi.json` all stay; only `/` stops answering. A front
+end on another origin also wants `AGGAPI_CORS_ORIGINS`, comma separated:
+
+```
+AGGAPI_CORS_ORIGINS=https://your.app uv run aggregate-api --headless
+```
+
+`/openapi.json` is the contract. Note that the `/v1` surface is pre-1.0 and its
+shape follows what the bundled web app needs, so treat it as a moving target
+rather than a stable interface for now.
+
+## License
+
+BSD 3-Clause. See [LICENSE](LICENSE).

aggregate_api-1.0.0/README.md

@@ -0,0 +1,149 @@
+# aggregate_api
+
+**aggregate Loss Lab** (aLL): a FastAPI service and a single-page web app for
+the [`aggregate`](https://github.com/mynl/aggregate) actuarial library.
+*Description to distribution.*
+
+`aggregate_api` is the package; **aggregate Loss Lab** is the app it serves.
+It puts `build()` behind an HTTP/JSON api (DecL parsing, FFT-based compound
+distributions, plotting, and risk pricing) and ships a Bootstrap 5 and
+CodeMirror 6 DecL workbench that runs against it. A single `aggregate-api`
+process serves both the web UI (at `/`) and the JSON endpoints (under `/v1`)
+same-origin.
+
+> **Status:** 1.0.0, the first public release. Extracted from the `aggregate`
+> repo so the library can ship without it. The package is installable and
+> supported; the `/v1` surface is not yet a frozen interface, and the caveat at
+> the end of [Running headless](#running-headless) says why. See
+> [CHANGELOG.md](CHANGELOG.md) for what has landed and
+> [dev/TODO.md](dev/TODO.md) for the roadmap.
+
+## What's inside
+
+- **Backend** (`src/aggregate_api/`): FastAPI app. Object lifecycle
+  (`POST /v1/objects` to build and cache, then `info`, `meta`, `summary`,
+  `tail_df`, `validation_df`, `stats_df`, `density_df`, `plot`, `kappa`,
+  `price`, `pricing_at`, plus `frame/{which}` in CSV or table-document form),
+  DecL helpers (`/v1/decl/complete`, `/lex`,
+  `/format`), and the example library read straight from `aggregate`'s recipe
+  base (`/v1/examples`, `/v1/examples/heroes`). In-memory LRU cache, build
+  timeout, SQLite audit log, CORS. Swagger UI at `/docs`.
+- **Frontend** (`web/`): vanilla-JS SPA (Vite, Bootstrap, CodeMirror 6,
+  `csv-grid`). A DecL editor with syntax highlighting, autocomplete and history,
+  a landing gallery of showcase examples, tabbed risk output, interactive and
+  native plots, and a rich parse-error pane.
+
+### Tables: one payload, two renderers
+
+Every table under 500 rows is fetched once, as a **table document**: versioned
+JSON carrying semantics only (dtypes, resolved formats, hierarchy, spans, flags)
+and no widths or CSS. Both views render from that one document, so they cannot
+disagree about a number:
+
+- **Static** is `greater_tables`' own JS walker, which draws a book-quality table
+  (sparsified row index, spanned headers, partial rules). The walker and its
+  stylesheet are served straight out of the installed Python package at
+  `/v1/assets/`, so the renderer and the documents it renders can never version
+  skew.
+- **Interactive** is `csv-grid`, fed by `irToGridInput(doc)`: sort, per-column
+  filter, fzf search, copy and save.
+
+Which one you get is a page-wide preference in the header menu. Large frames (the
+densities) skip the document entirely and go to the grid, which is the honest
+instrument for them.
+
+## Install
+
+Requires Python ≥ 3.13. Nothing else: `aggregate` ≥ 1.0.1 and
+`greater-tables` ≥ 6.0.0 come from PyPI with it.
+
+```
+pip install aggregate_api
+aggregate-api --port 8001
+```
+
+Then open http://127.0.0.1:8001/ for the app, or http://127.0.0.1:8001/docs for
+the api.
+
+> **Install the wheel, not the repository.** The web bundle is 2.5 MB of
+> generated Vite output and is deliberately not in git, so it reaches you in the
+> built distribution and only there. `pip install git+https://github.com/mynl/aggregate_api`
+> installs a working api whose `/` returns 404, which is a reasonable thing to
+> want if you are putting your own front end in front of the engine, and a
+> baffling one otherwise. The wheel and sdist are also attached to each
+> [GitHub release](https://github.com/mynl/aggregate_api/releases).
+
+One footnote, which the pins above handle for you and which bites anyone
+installing the table engine on its own: PyPI's `greater-tables` 5.3 is a
+previous generation sharing the `greater_tables` import name, so a bare
+`pip install greater-tables` can get a package with no `build`, `canonical_json`
+or `IR_VERSION`, which fails at import rather than at install. This package pins
+`>=6.0.0` and `tests/test_meta.py` asserts the right generation is present.
+
+## Develop
+
+Needs [`uv`](https://docs.astral.sh/uv/) and Node for the web build. A fresh
+clone syncs with nothing checked out beside it.
+
+```
+git clone https://github.com/mynl/aggregate_api
+cd aggregate_api
+uv sync --extra dev
+.\scripts\build-web.ps1          # Windows; ./scripts/build-web.sh on Unix
+uv run aggregate-api --port 8001 --reload
+```
+
+`build-web` drops the bundle into `src/aggregate_api/static/`, which the FastAPI
+`StaticFiles` mount serves at `/`. Until it has run once, `/` has nothing to
+serve. For hot reload with a Vite dev server proxying `/v1` to `:8000`, use
+`cd web; npm install; npm run dev` instead.
+
+To develop against a local checkout of `aggregate` or `greater-tables` rather
+than the released build, install it editable over the synced environment:
+
+```
+uv pip install -e ../aggregate               # or wherever the checkout is
+```
+
+The next `uv sync` silently reinstalls the released build, so `uv run --no-sync`
+is the way to work in between.
+
+Run the tests. There are two suites and both are the gate:
+
+```
+uv run pytest           # 490 tests, FastAPI TestClient, no live server needed
+cd web; npm test        # 277 tests, node --test over web/test/
+```
+
+Rehearse a release, which is a stronger check than either suite because it
+builds the distributions and runs everything against the installed wheel in a
+clean environment:
+
+```
+.\scripts\release-check.ps1
+```
+
+### Running headless
+
+One process serves both halves: the routers mount under `/v1`, and the built web
+bundle is mounted at `/`. To run the engine alone, behind somebody else's front
+end, say so:
+
+```
+uv run aggregate-api --headless           # or AGGAPI_SERVE_SPA=0
+```
+
+`/v1`, `/docs` and `/openapi.json` all stay; only `/` stops answering. A front
+end on another origin also wants `AGGAPI_CORS_ORIGINS`, comma separated:
+
+```
+AGGAPI_CORS_ORIGINS=https://your.app uv run aggregate-api --headless
+```
+
+`/openapi.json` is the contract. Note that the `/v1` surface is pre-1.0 and its
+shape follows what the bundled web app needs, so treat it as a moving target
+rather than a stable interface for now.
+
+## License
+
+BSD 3-Clause. See [LICENSE](LICENSE).

aggregate_api-1.0.0/pyproject.toml

@@ -0,0 +1,178 @@
+[build-system]
+requires = ["setuptools>=70", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "aggregate_api"
+version = "1.0.0"
+description = "aggregate Loss Lab (aLL): FastAPI service and single-page web app for the aggregate actuarial library."
+readme = "README.md"
+authors = [
+    {name = "Stephen J. Mildenhall", email = "steve@convexrisk.com"},
+]
+maintainers = [
+    {name = "Stephen J. Mildenhall", email = "steve@convexrisk.com"},
+]
+keywords = [
+    "actuarial",
+    "insurance",
+    "reinsurance",
+    "risk",
+    "aggregate loss",
+    "compound distribution",
+    "FFT",
+    "pricing",
+    "DecL",
+]
+classifiers = [
+    # Beta rather than Production/Stable at 1.0.0, deliberately. The package is
+    # installable and supported; the `/v1` surface still follows what the
+    # bundled web app needs, so it is not a frozen interface. The library can
+    # claim Production/Stable because its API promise is in force; this cannot
+    # yet.
+    "Development Status :: 4 - Beta",
+    "Intended Audience :: Financial and Insurance Industry",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.13",
+    "Programming Language :: Python :: 3.14",
+    "Topic :: Office/Business :: Financial",
+    "Topic :: Scientific/Engineering :: Mathematics",
+    "Framework :: FastAPI",
+]
+dependencies = [
+    # The library this service wraps. An ordinary registry dependency since
+    # 1.0.0 of this package: `aggregate` 1.0.1 published on 2026-10-07 and the
+    # internals the api imports (`parser_errors`, `parser._PARSER`, `charts`,
+    # `exhibits`, `plugins`, `bounds`, `decl_writer`, `constants`) are all in
+    # it. Before that the whole 1.0.0a line was unpublished and this had to be
+    # an editable path source; see dev/done/plan-1.0.0-release.md.
+    #
+    # The floor is 1.0.1 and not 1.0.0 because 1.0.0 is not on PyPI at all:
+    # the library's own 1.0.1 was a packaging fix, "the wheel ships
+    # aggregate.charts, .plots and .exhibits", and the api imports two of those
+    # three. A bare `aggregate` would also let a resolver reach 0.30.1, the
+    # newest of the old line, which has none of these modules and fails at
+    # import rather than at install.
+    #
+    # The ceiling is caution about two private names, `parser._PARSER` and
+    # `parser_errors._TERMINAL_LABELS`. The library's API promise covers its
+    # public surface, and a major is exactly where a private name moves.
+    # Re-check both at each library minor rather than trusting the range.
+    "aggregate>=1.0.1,<2",
+    # Static tables (the author's own package). The api asks it for a semantic
+    # table document (the IR), never for markup: the browser owns geometry. The
+    # same install also ships the walker that renders that IR, which is what
+    # makes version skew between the two impossible. See dev/plan-gt2-ir.md.
+    #
+    # **An ordinary registry dependency since a53.** 6.0.0 has shipped to PyPI,
+    # so the editable source this used to carry is gone and a fresh clone works
+    # with nothing checked out beside it.
+    #
+    # The floor is load bearing and must not be relaxed. PyPI also holds 5.3,
+    # the previous generation of the same package under the same name, and the
+    # two cannot coexist in one environment: 5.3 has no `build`,
+    # `canonical_json` or `IR_VERSION`, so resolving to it does not fail at
+    # install, it fails at import. Without `>=6` a resolver working around some
+    # other constraint could quietly pick it.
+    "greater-tables>=6.0.0",
+    "fastapi>=0.115",
+    "uvicorn[standard]>=0.30",
+    "pydantic>=2.7",
+    "pydantic-settings>=2.4",
+]
+license = "BSD-3-Clause"
+# Was >=3.11 through a31. `greater-tables` declares >=3.13 and that floor is
+# the binding one. Nothing in its source needs 3.13, so if 3.11 or 3.12 ever
+# matters here again, relax it there rather than pinning an old release here.
+requires-python = ">=3.13"
+
+[project.urls]
+Homepage = "https://github.com/mynl/aggregate_api"
+"Source Code" = "https://github.com/mynl/aggregate_api"
+Documentation = "https://github.com/mynl/aggregate_api#readme"
+Changelog = "https://github.com/mynl/aggregate_api/blob/main/CHANGELOG.md"
+Issues = "https://github.com/mynl/aggregate_api/issues"
+
+[project.optional-dependencies]
+dev = [
+    "pytest>=7",
+    # FastAPI's TestClient is a thin wrapper over httpx.
+    "httpx>=0.27",
+    "ruff>=0.6",
+]
+# The resource block of GET /v1/status. An extra rather than a runtime
+# dependency so the lean install is untouched and a deployment opts in with
+# `uv sync --extra status`; `resources.py` carries a stdlib fallback and says
+# which source it used, so the page works either way.
+#
+# Worth declaring even though psutil is usually already present: it arrives
+# transitively through ipython, which aggregate pulls, so the import succeeds
+# by accident rather than by intent and is one unrelated dependency change away
+# from not. That is what an explicit extra is for.
+status = ["psutil>=5.9"]
+
+[project.scripts]
+aggregate-api = "aggregate_api.__main__:main"
+
+# ---------------------------------------------------------------------------
+# There is deliberately no `[tool.uv.sources]` table.
+#
+# It held an editable path source for `aggregate` through 1.0.0a202, because the
+# whole 1.0.0a line was unpublished, and one for `greater-tables` through a53.
+# Both dependencies are on PyPI now, so a fresh clone syncs with nothing checked
+# out beside it.
+#
+# The table has to go rather than merely being unused, because uv honors it when
+# this project is installed *as a git dependency* and resolves the relative path
+# inside the git repository:
+#
+#     uv pip install git+https://github.com/mynl/aggregate_api
+#     x Failed to download and build `aggregate @ git+...#subdirectory=..\..\worktrees\aggregate_REFACTOR`
+#       The source distribution has no subdirectory `..\..\worktrees\aggregate_REFACTOR`
+#
+# So the table did not just fail to help an outside installer, it was fatal to
+# one. pip never saw it, which is why the failure was uv-only and invisible here.
+#
+# To co-develop either dependency against a local checkout for a session,
+# without editing this file:
+#
+#     uv sync --extra dev                                   # PyPI, the default
+#     uv pip install -e V:/worktrees/aggregate_REFACTOR     # swap in the library
+#     uv pip install -e c:/s/ai/greatest-tables             # swap in the tables
+#
+# The tables checkout folder is still named `greatest-tables` after the working
+# name it carried for a day; that is deliberate and the path above is correct.
+#
+# Either swap lasts until the next `uv sync`, which reinstalls from the lock and
+# silently puts the released build back without saying so. That matters because
+# the release workflow runs `uv sync` on every version bump, so a bump in the
+# middle of co-development drops the editable install. `uv run --no-sync` is the
+# way to work in between, and it is what this repo uses anyway.
+# ---------------------------------------------------------------------------
+
+[tool.setuptools]
+include-package-data = true
+package-dir = {"" = "src"}
+packages = ["aggregate_api", "aggregate_api.routes"]
+
+[tool.setuptools.package-data]
+# The built SPA bundle (index.html + assets/) is dropped here by the web
+# build and is gitignored; the committed icons/webmanifest ship too.
+#
+# **`static/assets/*` is a separate entry and must stay one.** A package_data
+# glob matches files in one directory and does not recurse, so `static/*` alone
+# shipped `index.html` and left every script and stylesheet it loads behind.
+# The installed app then served a 200 for `/` and a 404 for all thirteen
+# assets: the shell painted and nothing ran. `static/**/*` would also work, and
+# is not used here because it would sweep in `static/dev/`, which holds
+# development instruments that have no business in a release.
+#
+# `status_page.html` is the operator's page, served by routes/status.py straight
+# out of the package. Deliberately not under `static/`: the web build wipes that
+# directory on every run, so a copy there would be deleted by the next deploy,
+# and a status page whose delivery depends on the pipeline it reports on cannot
+# report on that pipeline failing.
+aggregate_api = ["static/*", "static/assets/*", "status_page.html"]
+
+[tool.ruff]
+line-length = 100

aggregate_api-1.0.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

aggregate_api-1.0.0/src/aggregate_api/__init__.py

@@ -0,0 +1,41 @@
+"""FastAPI service for the :mod:`aggregate` library.
+
+This package stands up an HTTP/JSON wrapper around ``build()``,
+the live ``Aggregate`` / ``Portfolio`` objects, plotting, pricing,
+and DecL helpers (completions, lexing, grammar).
+
+Quickstart
+----------
+
+::
+
+    pip install aggregate_api
+    aggregate-api --port 8001
+
+Then ``POST http://127.0.0.1:8001/v1/objects`` with body
+``{"decl": "agg Dice dfreq [3] dsev [1:6]"}`` to build and cache an
+object, and follow up with ``GET /v1/objects/{id}/info`` etc.
+
+Public surface
+--------------
+
+``create_app()`` returns a configured :class:`fastapi.FastAPI`
+instance. The ``aggregate-api`` console script launches it under
+uvicorn. Tests build their own ``TestClient`` against
+``create_app()``.
+
+Note for Flask users
+--------------------
+
+FastAPI uses an *application factory* (``create_app``) plus an ASGI
+server (uvicorn) instead of Flask's ``app = Flask(__name__)`` + WSGI.
+Routes are grouped on ``APIRouter`` objects (analogous to Flask
+``Blueprint``) and mounted onto the app in :func:`app.create_app`.
+Request bodies are *validated* by Pydantic models (one model per
+endpoint) rather than read out of ``request.json``; the model is a
+function parameter and FastAPI deserializes for you.
+"""
+
+from .app import create_app
+
+__all__ = ["create_app"]