@hyperscale0/adl 1.0.0-alpha.2 → 1.0.0-beta.1

package/CHANGELOG.md

@@ -6,6 +6,11 @@ follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html) from 1.0.0.
 
 ## [Unreleased]
 
+## [1.0.0-beta.1] - 2026-08-29
+
+- This is the first beta and has no package behavior changes from
+  1.0.0-alpha.2.
+
 ## [1.0.0-alpha.2] - 2026-08-26
 
 ### Removed
@@ -54,6 +59,7 @@ write an adapter in; an adapter is still what you write.
   the exported types derived from them, so the published schema cannot drift
   from the type checker. No exported type changed shape.
 
-[Unreleased]: https://github.com/hyperscale0/hyperscale-adl/compare/v1.0.0-alpha.2...HEAD
+[Unreleased]: https://github.com/hyperscale0/hyperscale-adl/compare/v1.0.0-beta.1...HEAD
+[1.0.0-beta.1]: https://github.com/hyperscale0/hyperscale-adl/compare/v1.0.0-alpha.2...v1.0.0-beta.1
 [1.0.0-alpha.2]: https://github.com/hyperscale0/hyperscale-adl/compare/v1.0.0-alpha.1...v1.0.0-alpha.2
 [1.0.0-alpha.1]: https://github.com/hyperscale0/hyperscale-adl/releases/tag/v1.0.0-alpha.1

package/README.md

@@ -1,15 +1,16 @@
 # ADL
 
-ADL, the Adapter Declaration Language: the format for describing a bank or
-provider to Hyperscale, the validator that refuses a declaration the runtime
-could not operate, and the conformance suite that says when one is ready to
-serve live money.
+ADL is the Adapter Declaration Language: the public format for declaring how a
+bank or provider behaves at the control-plane boundary. Its validator and
+conformance suite refuse incomplete interface facts before a generic runtime
+can poll, classify, reconcile, or deduplicate provider results.
 
-It is the third of three. UDL describes the product, HSX scripts the money
-movement, ADL declares the provider the money moves through.
+The three language boundaries stay separate. HSX authors settlement behavior.
+UDL defines the canonical product contract. ADL declares how an external
+provider performs or confirms work behind that contract.
 
-**Status: alpha.** `1.0.0-alpha.1`. The surface can still change on a minor
-version until 1.0.0.
+**Status: alpha.** The surface can still change on a minor version until
+1.0.0.
 
 ## Adapter symmetry
 
@@ -33,6 +34,9 @@ what a payment means. It states facts, and the checks in this package prove
 those facts are complete enough for a generic runtime to poll, classify,
 reconcile, and dedupe without guessing.
 
+Conformance checks a declaration. It does not contact a provider, verify a
+credential, certify regulatory readiness, or make a Product live.
+
 ## Install
 
 ```bash
@@ -100,14 +104,14 @@ empty finding list is the certification.
 
 ## Where to go next
 
-- **[docs/authoring-guide.md](docs/authoring-guide.md)** -- the whole job, field
+- **[docs/authoring-guide.md](docs/authoring-guide.md)**: the whole job, field
   by field, with the rule that enforces each one.
-- **[examples/meridian-bank](examples/meridian-bank)** -- a complete certified
+- **[examples/meridian-bank](examples/meridian-bank)**: a complete certified
   adapter for a bank that does not exist, with fixtures and its own tests.
   Copy it.
-- **[conformance/cases.json](conformance/cases.json)** -- every rule as data:
+- **[conformance/cases.json](conformance/cases.json)**: every rule as data:
   one broken fact per case, and what each gate says about it.
-- **[spec/manifest.schema.json](spec/manifest.schema.json)** -- JSON Schema
+- **[spec/manifest.schema.json](spec/manifest.schema.json)**: JSON Schema
   2020-12 for one declaration, for authors who are not writing TypeScript.
 
 ## Running conformance

package/docs/authoring-guide.md

@@ -15,9 +15,9 @@ credential, and never decides what a payment means.
 
 That split is why the checks in ADL are declaration-level. Conformance
 does not call your bank. It proves the facts you declared are complete enough
-for a generic runtime to poll, classify, reconcile, and dedupe **without
-guessing**, because every guess a runtime makes about money is a bug you find
-in production.
+for a generic runtime to poll, classify, reconcile, and dedupe without
+guessing. Every guess a runtime makes about money is a provider-boundary
+defect.
 
 Two consequences worth internalizing before you write a line:
 
@@ -30,7 +30,7 @@ Two consequences worth internalizing before you write a line:
   fact to post from. `validatePartnerBankProfile` refuses a profile whose
   `notificationMechanisms` omits `poll`, whatever else it lists.
 
-### Adapter Symmetry
+### Adapter symmetry
 
 Hyperscale's own bank adapters are written against this package and nothing
 more. There is no private adapter API, no internal hook, no second interface
@@ -108,18 +108,18 @@ Each `ProviderOperationBinding` carries:
 | `resourceKind`   | The platform resource the provider's answer commits onto. Must appear in `bindings`.                                                                                                                                       |
 | `resourceIdPath` | Where the resource id is read from. Non-blank, checked at load.                                                                                                                                                            |
 | `meter`          | Optional. The usage meter this operation feeds.                                                                                                                                                                            |
-| `envelope`       | How **this** operation's response carries its outcome. Required on a live command, see below.                                                                                                                              |
+| `envelope`       | How this operation's response carries its outcome. Required when the runtime sends a provider command, see below.                                                                                                          |
 | `statusEnquiry`  | The authoritative read-after-write. Required on a REST command, see below.                                                                                                                                                 |
 
 ### The envelope class, per operation
 
 `ProviderResponseEnvelope` has three inhabitants:
 
-- `http_200_body_status` -- every response is HTTP 200 and the outcome is a
+- `http_200_body_status`: every response is HTTP 200 and the outcome is a
   status token in the body. A rejection arrives inside a success.
-- `http_status_error_body` -- the HTTP status carries the outcome and a failure
+- `http_status_error_body`: the HTTP status carries the outcome and a failure
   body is prose.
-- `unconfirmed_until_live` -- the provider publishes no error sample, so the
+- `unconfirmed_until_live`: the provider publishes no error sample, so the
   class is honestly unknown.
 
 Declare it **per operation**, never per provider. Real providers answer in more
@@ -130,9 +130,10 @@ Conformance requires the class on any binding where the runtime sends a command
 and reads an answer, meaning `direction: "tenant_initiated"` on an `egress` of
 `rest` or `sync_clearance`. Missing it is `response_envelope_unclassified`; a
 declared `unconfirmed_until_live` is `response_envelope_unconfirmed`, because
-certification is the licence to serve live and the class must be established
-first. A `system_settlement` binding carries no response of its own, so it owes
-no envelope, and declaring one there would be a borrowed fact.
+conformance requires the response class to be established first. Passing that
+check does not grant live readiness. A `system_settlement` binding carries no
+response of its own, so it owes no envelope, and declaring one there would be a
+borrowed fact.
 
 ### Status enquiry, the read-after-write
 
@@ -165,10 +166,10 @@ enquiry support from a command URL, so:
 
 `ProviderEgressMode` is how this adapter reaches the provider at all:
 
-- `none` -- the capability is learned entirely by observation;
-- `rest` -- per-command HTTP;
-- `batch_reconcile` -- files, reconciled after the fact;
-- `sync_clearance` -- one synchronous exchange that carries its own truth.
+- `none`: the capability is learned entirely by observation;
+- `rest`: per-command HTTP;
+- `batch_reconcile`: files, reconciled after the fact;
+- `sync_clearance`: one synchronous exchange that carries its own truth.
 
 A `tenant_initiated` binding on `none` or `batch_reconcile` promises an
 outbound call the egress mode cannot make: `egress_direction_incoherent`.
@@ -191,11 +192,11 @@ missing: polling is the fact.
 `bindings` maps each resource kind this adapter settles to a
 `ProviderResourceBinding`:
 
-- `strict` -- the provider's fact must match the platform's row exactly;
-- `claim` -- the provider's fact claims an existing row;
-- `confirmation_only` -- the provider only confirms what the platform already
+- `strict`: the provider's fact must match the platform's row exactly;
+- `claim`: the provider's fact claims an existing row;
+- `confirmation_only`: the provider only confirms what the platform already
   decided;
-- `evidence_only` -- the fact is recorded as evidence, and settles nothing.
+- `evidence_only`: the fact is recorded as evidence, and settles nothing.
 
 Every `resourceKind` named by an operation binding or a webhook plan needs an
 entry, or conformance reports `resource_binding_missing`: a provider fact with
@@ -226,8 +227,8 @@ would otherwise guess.
 
 `wireCodec` (`rest_json`, `iso20022_xml`, `swift_mt`) and `auth`
 (`ProviderAuthEnvelope` plus a signing scheme). Declaring a grant the bank will
-not accept fails on the first live call, so read the bank's token service, do
-not assume client credentials.
+not accept fails on the first provider call. Read the bank's token service and
+do not assume client credentials.
 
 ### The idempotency spine
 
@@ -415,8 +416,8 @@ An adapter is handed over as source, never as a running service:
 
 ## Stability
 
-The package is `1.0.0-alpha.1` and the surface can still change on a minor
-version until it is `1.0.0`. Two promises hold from now:
+The package is pre-1.0 and the surface can still change on a minor version
+until it is `1.0.0`. Two promises hold now:
 
 - conformance codes are append-only;
 - a value removed from a vocabulary in `src/vocabulary.ts` is a breaking change

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hyperscale0/adl",
-  "version": "1.0.0-alpha.2",
+  "version": "1.0.0-beta.1",
   "description": "The Adapter Declaration Language: provider adapter interfaces, registry validation, and the partner-bank conformance suite.",
   "keywords": [
     "adl",