@wtfalch/reporting 0.5.0 → 0.5.1

package/README.md

@@ -3,9 +3,12 @@
 The estate's operational event log and the housekeeping tick behind it: a
 writer that never fails a request, a claim protocol that needs no scheduler,
 and the readers an operator opens. Per-app Postgres, a host-supplied logger,
-a framework-neutral core and a Next entry. The design and its decisions are
-`docs/plans/reporting.md` and `docs/plans/reporting/core.md` in
-`wtfalch/app-template`.
+a framework-neutral core and a Next entry. The design and its decisions were
+originally `docs/plans/reporting.md` and `docs/plans/reporting/core.md` in
+`wtfalch/app-template`, which was archived 2026-09-24 and replaced by
+`foundry`; those docs are a historical record only. The design history for
+everything past 0.2.0 lives in this repo's own `docs/plans/errors.md` and
+`CHANGELOG.md`.
 
 Three records make up reporting on the estate. This package holds the
 **events** (what the system did: jobs, drains, alerts, an integration saying
@@ -15,6 +18,10 @@ row is transactional and its actor is unforgeable; an event row is best
 effort. The two share column names so a reader can walk between them, and
 nothing else.
 
+## Status
+
+Published: yes, v0.5.1, 2026-09-28
+
 ## Install
 
 ```sh
@@ -136,6 +143,24 @@ every row regardless.
 
 ## Analytics (0.2.0)
 
+**Topology, today:** this package is a library, not a host. `createReporting({
+db, ... })` binds to whichever Postgres the calling app already has, and
+every table below lives in that one app's own database. `tenantId` scopes a
+read to one organisation *within* that single app's database — it does not
+let a console outside that app read anything. There is no cross-app or
+cross-company read: one company's own Boule sees only the rows its own
+process wrote.
+
+**Topology, target (settled 2026-09-28, planned after launch):** one shared
+reporting collector, org-scoped like `@wtfalch/files` and `@wtfalch/ai` —
+every app's `reporting` calls point at that one shared store instead of a
+database of its own, row-level scoping keeps one company's rows out of
+another's reads, Archon reads totals across every company, and each
+company's own Boule reads only its own organisation's slice. Not built yet:
+today's shape is the per-app library described above, and the shared-host
+change (or a lighter "point every app's `reporting` at one app's database"
+approach) is an open architecture question for whoever picks it up next.
+
 Three tables and two writers. `reporting_analytics` holds raw rows for a
 window (`analytics.retention_days`, default 90); `reporting_analytics_daily`
 and `reporting_analytics_weekly` hold counts with no identifier in any column

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wtfalch/reporting",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "description": "The estate's operational event log and housekeeping tick: a writer that never fails a request, a claim protocol that needs no scheduler, and the readers an operator opens. Per-app Postgres, host-supplied logger, framework-neutral core with a Next entry.",
   "repository": {
     "type": "git",