@finsys/core 4.8.0 → 4.9.0
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/dist/index.cjs +30 -0
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.cts +81 -2
- package/dist/index.d.ts +81 -2
- package/dist/index.js +28 -0
- package/dist/index.js.map +1 -1
- package/dist/schema/adapter-manifest.schema.json +10 -1
- package/package.json +1 -1
|
@@ -137,6 +137,15 @@
|
|
|
137
137
|
"type": { "const": "extraction-pipeline" }
|
|
138
138
|
},
|
|
139
139
|
"description": "SYS-2998 — declaration-only: the adapter's implementation IS the host application's own document-extraction pipeline. No code is loaded and neither fetch() nor extract() ever runs; the host's pipeline writes the canonical rows and records the runs. The manifest exists purely as the declaration plane (produces, cardinality, fieldAuthorizations) for data the host was already producing."
|
|
140
|
+
},
|
|
141
|
+
{
|
|
142
|
+
"type": "object",
|
|
143
|
+
"required": ["type"],
|
|
144
|
+
"additionalProperties": false,
|
|
145
|
+
"properties": {
|
|
146
|
+
"type": { "const": "external-assertion" }
|
|
147
|
+
},
|
|
148
|
+
"description": "SYS-3036 — declaration-only: the adapter is executed entirely OUTSIDE the host. An externally-orchestrated process completes its own ceremony/extraction and PUSHES the result to the host's assertion-ingest surface. No code is loaded and neither fetch() nor extract() ever runs — same declaration-only shape as form-intake/manual-override/extraction-pipeline, but data arrives via an external push rather than the host's own pipeline, form submission, or extract() call."
|
|
140
149
|
}
|
|
141
150
|
]
|
|
142
151
|
},
|
|
@@ -223,7 +232,7 @@
|
|
|
223
232
|
"pattern": "^\\S(.*\\S)?$"
|
|
224
233
|
}
|
|
225
234
|
},
|
|
226
|
-
"description": "Vendor-specific value sets for the enum-kind fields this adapter produces. The category declares only THAT a field is enumerated (kind 'enum' — no values, no ordering); this map declares WHICH labels this vendor emits. Host-validated at registration: every key must appear in `produces` and be declared kind 'enum' by the category, and every enum-kind field in `produces` must have an entry. Labels are string-normalized (non-empty, no leading/trailing whitespace) and unique per set; the adapter emits them VERBATIM and the host refuses out-of-set values at ingest. Ordering and scoring interpretation belong to the consumer's per-value mapping, never here."
|
|
235
|
+
"description": "Vendor-specific value sets for the enum-kind fields this adapter produces. The category declares only THAT a field is enumerated (kind 'enum' — no values, no ordering); this map declares WHICH labels this vendor emits. Host-validated at registration: every key must appear in `produces` and be declared kind 'enum' by the category, and every enum-kind field in `produces` must have an entry. Labels are string-normalized (non-empty, no leading/trailing whitespace) and unique per set; the adapter emits them VERBATIM and the host refuses out-of-set values at ingest. Ordering and scoring interpretation belong to the consumer's per-value mapping, never here. Matching is exact-string (case and whitespace variations from a declared label are distinct, hence out-of-set, deliberately) — `uniqueItems` is likewise exact-match, so e.g. [\"High\", \"high\"] is a legal two-label set; vendors own their exact label byte-for-byte, hosts never fold case or reconcile near-miss spelling."
|
|
227
236
|
},
|
|
228
237
|
"notes": {
|
|
229
238
|
"type": "string",
|