@hyperscale0/adl 1.0.258 → 1.0.284

package/CHANGELOG.md

@@ -1,5 +1,22 @@
 # Changelog
 
+## Since 1.0.123
+
+Releases after 1.0.123 shipped without per-release entries. This entry
+summarises what changed in the package surface since then.
+
+Added:
+
+- `ProviderAdapter.onboarding` declares whether a provider onboards a `person`,
+  an `organization` or both. The registry refuses an empty, unknown or repeated
+  kind.
+- `conformance/insurance-policy-adapter.ts`, a quote and issuance example with a
+  custom vocabulary.
+
+Changed:
+
+- `BoundaryInstruction.currency` accepts SAR only.
+
 ## 1.0.123
 
 First unified release. Every public Hyperscale package now ships under one

package/README.md

@@ -44,7 +44,7 @@ bun run conformance -- ./src/boundary-fixture.ts
 
 ## Versioning
 
-Semantic versioning. Removing a value from a vocabulary in `src/vocabulary.ts` is a breaking change documented in [CHANGELOG.md](CHANGELOG.md).
+Every public Hyperscale package ships under one version that follows the platform release number, so release N is 1.0.N. Removing a value from a vocabulary in `src/vocabulary.ts` breaks existing declarations and is called out in [CHANGELOG.md](CHANGELOG.md).
 
 ## License and security
 

package/SECURITY.md

@@ -14,8 +14,8 @@ you have. A declaration that triggers the bug is ideal, with every locator
 value removed.
 
 We acknowledge reports within three working days and tell you what we intend
-to do. Fixes ship on the current alpha line; there are no backports before
-1.0.0.
+to do. Fixes ship in the newest published `1.0.N` release; older releases get
+no backports.
 
 ## Scope
 

package/docs/authoring-guide.md

@@ -16,35 +16,44 @@ the bound quote. An accepted request without issuance evidence remains pending.
 The fixture does not rate a policy, collect premium or register a live engine
 adapter.
 
-Use `createProviderAdapterRegistry` to validate declarations. Each operation map
-key must equal its binding's `operation`. Its `resourceKind` must appear in
-`bindings`. Subject requirements describe required authored fields or attachments;
-they never supply an account or choose a party.
+`createProviderAdapterRegistry` validates declarations when they load and throws
+on the first error. It checks the provider key, a unique provider and capability
+pair, `onboarding` as `person`, `organization` or both, each operation map key
+against its binding's `operation`, a nonblank `resourceIdPath`, and subject
+requirements against the UDL object field schema. Subject requirements describe
+required authored fields or attachments; they never supply an account or choose
+a party.
 
 The [boundary adapter](https://github.com/hyperscale0/hyperscale-adl/blob/main/src/boundary-fixture.ts) declares one boundary
 observation operation with no subject requirements. The
 [subject fixture](../conformance/subject-adapter.ts) shows required subject fields.
 
 `adapterConformanceFindings` checks the declaration without contacting a
-provider.
+provider and returns findings instead of throwing. Only it checks that every
+operation's `resourceKind` appears in `bindings`, and that the operation map is
+not empty. It reports a registry refusal as `declaration_invalid`.
 
 ## Dispatch an instruction
 
 `BoundaryInstruction` binds an immutable ID to the environment, tenant, Product,
-retained Build, target, source and destination accounts, positive minor-unit
-amount, currency and adapter. The runtime reserves the amount before dispatch.
-An adapter receives that instruction unchanged.
+retained `productBuildId` and `buildDigest`, target (`kind`, `attachment`,
+`instanceId`), `sourceAccountId`, `destinationAccountId`, positive minor-unit
+`amount`, `currency` and selected `adapter`. The runtime reserves before dispatch.
+An adapter receives the instruction unchanged and cannot choose parties,
+accounts or a replacement binding.
 
 `BoundaryAdapter.dispatch` and `BoundaryAdapter.observe` return a
 `BoundaryObservation` or `undefined`. The observation names the adapter,
-instruction ID, stable external reference, explicit outcome and observation time.
+`instructionId`, stable `externalReference`, explicit `outcome` and ISO `observedAt`.
+`BoundaryAdapter.id` identifies the adapter. Observation identity is the pair of
+adapter and external reference; reuse with different contents refuses.
 Its outcome is `acknowledged`, `unknown`, `confirmed` or `rejected`.
 
 An acknowledgement or missing result leaves the reservation held. HTTP status
 never supplies a terminal outcome. Only a matching `confirmed` observation can
 authorize posting; an explicit `rejected` observation can authorize voiding.
-The runtime records immutable observations and consumes settlement evidence once.
-Recovery completes the same ledger intent without resending uncertain work.
+Observations remain immutable. Storage is separate from consumption; the runtime
+claims settlement evidence once. There is no distributed provider/ledger transaction.
 
 ## Check the declaration
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hyperscale0/adl",
-  "version": "1.0.258",
+  "version": "1.0.284",
   "description": "The Adapter Declaration Language: generic evidence, provider declarations and conformance.",
   "keywords": [
     "adl",
@@ -63,7 +63,7 @@
     "typecheck": "tsc -p tsconfig.json"
   },
   "dependencies": {
-    "@hyperscale0/udl": "1.0.258",
+    "@hyperscale0/udl": "1.0.284",
     "zod": "4.6.5"
   },
   "devDependencies": {
@@ -76,5 +76,5 @@
     "Amir Ayub",
     "Sara AlBakaawi"
   ],
-  "gitHead": "20d3d1eddd70d7629f5ae6a5b14e0e89c4ce536a"
+  "gitHead": "f4101f194e0e7c24997b0625ab1d48bec1255508"
 }