@saasicat/core 1.0.0-rc.1 → 1.0.0-rc.11

package/README.md

@@ -1,5 +1,7 @@
 # @saasicat/core
 
+## What this is
+
 The shared core of the SaaS platform: the wire-format types — AdminManifest,
 PlanCatalog, PromoCode, AuditEvent, Subscription, PlanVersion, the adapter
 ports — **and the pure domain logic both sides run**: the error-code catalogues
@@ -15,6 +17,18 @@ types are generated from the schemas via `pnpm gen:types`
 (`json-schema-to-typescript`); a drift test keeps schemas and snapshots in
 sync.
 
+## What this is not
+
+Not a types-only package, despite what its predecessor's name promised. It
+carries 45 runtime exports — `classifyPlanDiff`, `applyPromo`,
+`resolveErrorMessage`, the error-code catalogues, the feature-requires rules —
+because backend and admin UI must reach the same verdict, and two
+implementations of the same rule reach two.
+
+Not the source of truth for the wire formats either. That is `@saasicat/spec`;
+the types under `src/generated/` are produced from its JSON Schemas, and a
+drift test rejects an edit made here.
+
 ## Contents
 
 | File                      | Contents                                                                                             |
@@ -56,3 +70,10 @@ Produces `dist/index.{js,cjs,d.ts,d.cts}` via `tsup`.
   there bumps this package's version as well.
 - **Required fields mirror the schemas.** Anything non-optional here must be
   non-optional in the schema too — otherwise it drifts.
+
+## Next
+
+- [The vocabulary](../../docs/explanation/concepts.md) — capability, feature, quota, plan, contract
+- [Codegen](../../docs/explanation/adr/0006-spec-to-types-codegen.md) — what is generated, and what
+  is not
+- [`@saasicat/spec`](../spec/README.md) — the schemas these types come from

package/dist/.build-stamp

@@ -1 +1 @@
-e4c4e2851c3994ae143821cc3b1e06a37b7ba6e3837aae954b71e47313e66b32
+41c2b5a9a83598fcfbd112e1289b4fa5a684ab3be5cd57b0d7cd3508ab5941ab