vet-sdk-core-ts 0.4.42 → 0.4.44

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -30,8 +30,20 @@ Development and releases follow the mandatory
30
30
  Browser-safe VetChain domain contracts. This repository is independent from
31
31
  UHC SDK packages and must not import them.
32
32
 
33
- The SDK consumes governed browser-safe values from `vet-data-utils-ts` and
34
- owns gateway request construction. GW VET remains the policy authority.
33
+ The SDK consumes governed browser-safe values from `vet-data-utils-ts`, shared
34
+ deterministic contracts from `sos-data-utils-ts`, and runtime-neutral common
35
+ authorization/orchestration from `sos-sdk-core-ts`. It owns only veterinary
36
+ specialization and gateway request construction. GW VET remains the policy
37
+ authority.
38
+
39
+ ```text
40
+ gdc-* frozen → sos-data-utils-ts → sos-sdk-core-ts → vet-sdk-core-ts
41
+ └────────────────────────→ vet-sdk-core-ts
42
+ ```
43
+
44
+ The direct data-package dependency is intentional whenever Vet imports or
45
+ exposes its types. Vet never imports UHC, and the shared SDK never imports Vet.
46
+ See the [VetChain shared SDK architecture diagram](docs/SHARED_SOS_SDK_LAYERING.md).
35
47
 
36
48
  `vet-sdk-core-ts/health-dcat` provides the neutral manager for tenant-owned
37
49
  HealthDCAT metadata. It publishes and searches claims-first resources, asks an
@@ -0,0 +1,8 @@
1
+ /**
2
+ * Shared runtime-neutral emergency authorization.
3
+ *
4
+ * Veterinary policy may constrain callers before invoking this function, but
5
+ * VetChain does not fork the cross-product evidence evaluator.
6
+ */
7
+ export { authorizeEmergencyAction, } from 'sos-sdk-core-ts/emergency-authorization';
8
+ export type { EmergencyAuthorizationEvidence, EmergencyCapability, EmergencyDeliveryTarget, EvidenceDomain, } from 'sos-sdk-core-ts/emergency-authorization';
@@ -0,0 +1,7 @@
1
+ /**
2
+ * Shared runtime-neutral emergency authorization.
3
+ *
4
+ * Veterinary policy may constrain callers before invoking this function, but
5
+ * VetChain does not fork the cross-product evidence evaluator.
6
+ */
7
+ export { authorizeEmergencyAction, } from 'sos-sdk-core-ts/emergency-authorization';
package/dist/index.d.ts CHANGED
@@ -11,4 +11,5 @@ export * from "./health-dcat.js";
11
11
  export * from "./health-card-issuance.js";
12
12
  export * from "./secure-clinic-channel.js";
13
13
  export * from "./scheduling.js";
14
+ export * from "./emergency-authorization.js";
14
15
  export * from "vet-data-utils-ts";
package/dist/index.js CHANGED
@@ -11,4 +11,5 @@ export * from "./health-dcat.js";
11
11
  export * from "./health-card-issuance.js";
12
12
  export * from "./secure-clinic-channel.js";
13
13
  export * from "./scheduling.js";
14
+ export * from "./emergency-authorization.js";
14
15
  export * from "vet-data-utils-ts";
@@ -0,0 +1,32 @@
1
+ # VetChain position in the shared SOS SDK architecture
2
+
3
+ VetChain extends two shared `sos-*` layers without modifying frozen GW CORE v1
4
+ or `gdc-*` packages.
5
+
6
+ ```mermaid
7
+ flowchart TB
8
+ GDC["gdc-* frozen<br/>compatibility primitives"]
9
+ DATA["sos-data-utils-ts<br/>types · JSON Schema · builders · validators"]
10
+ CORE["sos-sdk-core-ts<br/>runtime-neutral authorization · orchestration"]
11
+ VETDATA["vet-data-utils-ts<br/>animal/veterinary data contracts"]
12
+ VETCORE["vet-sdk-core-ts<br/>animal identity · veterinary specialization"]
13
+ VETNODE["Vet Node/GW/BFF adapters"]
14
+ CHANNELS["PetChain portal · professional portal · voice · chat · WhatsApp"]
15
+
16
+ GDC --> DATA
17
+ DATA --> CORE
18
+ DATA --> VETCORE
19
+ VETDATA --> VETCORE
20
+ CORE --> VETCORE
21
+ VETCORE --> VETNODE
22
+ VETNODE --> CHANNELS
23
+ ```
24
+
25
+ The direct `sos-data-utils-ts → vet-sdk-core-ts` dependency is intentional:
26
+ Vet imports and exposes shared deterministic types. Common authorization is
27
+ not copied; `vet-sdk-core-ts/emergency-authorization` reexports the exact
28
+ function owned by `sos-sdk-core-ts`.
29
+
30
+ Dependency direction is one-way. Neither shared SOS layer imports Vet, and Vet
31
+ never imports `uhc-sdk-core-ts`. SOSChain-specific Node infrastructure belongs
32
+ in `sos-sdk-node-ts`, beside—not inside—the Vet runtime.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "vet-sdk-core-ts",
3
- "version": "0.4.42",
3
+ "version": "0.4.44",
4
4
  "description": "Browser-safe VetChain core contracts and governed animal species identifiers",
5
5
  "license": "Apache-2.0",
6
6
  "author": "Connecting Solution & Applications Ltd",
@@ -63,6 +63,10 @@
63
63
  "./scheduling": {
64
64
  "types": "./dist/scheduling.d.ts",
65
65
  "default": "./dist/scheduling.js"
66
+ },
67
+ "./emergency-authorization": {
68
+ "types": "./dist/emergency-authorization.d.ts",
69
+ "default": "./dist/emergency-authorization.js"
66
70
  }
67
71
  },
68
72
  "files": [
@@ -89,7 +93,8 @@
89
93
  "@noble/hashes": "^2.2.0",
90
94
  "@noble/post-quantum": "0.5.4",
91
95
  "gdc-common-utils-ts": "2.9.10",
92
- "sos-data-utils-ts": "0.2.2",
96
+ "sos-data-utils-ts": "0.3.2",
97
+ "sos-sdk-core-ts": "0.2.0",
93
98
  "vet-data-utils-ts": "0.5.28"
94
99
  }
95
100
  }