lib.osint-runtime
Provider-neutral OSINT lifecycle, ingestion, governance, and knowledge runtime.
@lssm-tech/lib.osint-runtimebun add @lssm-tech/lib.osint-runtimeManifest declarations describe the current workspace; they do not verify registry publication or runtime execution.
Package guide
Provider-neutral OSINT lifecycle and ingestion logic. The runtime separates source discovery, qualification, ingestion, and revalidation, applies scoped fail-closed policy, guarantees idempotent receipts and evidence-backed assertions, filters suppression records, and projects only policy-eligible facts into the existing knowledge system.
Concrete persistence, object storage, embedding, provider web access, queues, and transports are injected through ports. This keeps company, job, and people systems independently deployable while allowing composed, consumer-isolated deployments described by deployment profile data.
Source lifecycle mutations are revision-fenced and return append-only, idempotent receipts containing the exact resulting source manifest. Durable workers can query a receipt by idempotency key, resume an interrupted revalidation, and reject stale work without repeating a committed effect. Canonical request digests and bounded owner leases prevent concurrent evaluators. Each transition receipt binds the claim key, owner, and monotonic attempt so a store can validate the live lease in the canonical mutation transaction; expired claims can be reclaimed while completed claims remain terminal.
Knowledge projections carry exact source versions, evidence locators, ACL grant references, purpose, index generation, and suppression references. Query receipts bind retrieval results back to their evidence and policy decision; knowledge remains a derived retrieval aid and never authorizes a fact or action.
The operation runtime defines the provider-free request, queue, fence, authority, read, and mutation ports used by every transport composition. Canonical request fingerprints bind the complete actor, scope, grants, parameters, and input so a worker can reauthorize the original effect immediately before executing it.
Ingestion accepts an abort signal and propagates it into the source connector, then rechecks cancellation before object persistence and materialization stages. Deployment profiles are data, not package constants: a host loads its profile and program rows (for example from the governance catalog osint.deployment-profiles@1) and injects them with defineOsintDeploymentProfileRegistryV0({ profiles, programs }), which validates every row strictly and refuses duplicate ids, dangling agent or program references and unknown or invalid fields (OSINT_DEPLOYMENT_PROFILE_REGISTRY_INVALID with the issue list) at startup. resolveOsintDeploymentProfileV0(id, registry) throws OSINT_DEPLOYMENT_PROFILE_UNKNOWN; resolveKnownOsintDeploymentProfileV0(id, registry) returns undefined. A profile's optional jobTargetingRef names a neutral job-targeting classifier that the host binds. Registered data-isolated deployment profiles are enforced automatically from the request deployment ID across managed API, MCP, and worker surfaces. A managed worker using a registered profile must attest exact OSINT_QUEUE_NAMESPACE, OSINT_INDEX_NAMESPACE, OSINT_CREDENTIAL_NAMESPACE, OSINT_REGION, OSINT_NETWORK_POLICY_REF, OSINT_DATA_STORE_REF, OSINT_OBJECT_STORE_REF, and OSINT_EXPORT_POLICY_REF bindings before startup. Namespaces must be distinct, and profile entity, jurisdiction, purpose, and concurrency limits are fail-closed.
Worker-derived domain policy
Reusable policy that previously lived in the osint-worker host is owned here and consumed by hosts through explicit subpaths; hosts keep only environment, store, queue, provider, and deployment-targeting bindings.
| Subpath | Owns |
|---|---|
./source-lifecycle-input | Lifecycle mutation shaping, operation-key mapping, policy verifier, qualification predicate, schema shape and the revalidation outcome policy (decideSourceRevalidationV0). |
./embedding-projection | Assertion serialization, evidence ids, authority-bound embedding effect digest, content/batch/record identities, sensitivity and failure codes. |
./scheduled-work | Due-stage work planning with program strategy resolution, interval-bucketed idempotency keys and blocked-stage accounting. |
./operational-recovery | Operator recovery fence admission (scope, attempt, authority, contract, evidence), replay fields and receipts. |
./webhook-delivery | Delivery settlement (2xx/429/5xx, exhaustion, capped backoff) and evidence references. |
./deletion-retry | Rights deletion failure codes and deterministic jittered backoff. |
./research-evidence | Deep-research evidence refs, confidence bounding and untrusted candidate shaping. |
./search-observations | Provider search-result to observation normalization with injected targeting and field-classifier ports; person results are personal, and unclassified fields are restricted; a search URL that is not an unchanged public field is digested (osintWithheldCanonicalKeyHintV0) in the canonical key hint. |
Reference taxonomy (D117-TAXO-01a)
./reference-taxonomy/* holds the store port, digests, validation, refusals, publish, upsert and query logic, an in-memory store and ReferenceTaxonomyServiceV1. Schemes are staged, published and superseded; batch upserts are idempotent and a replay writes nothing.
Relationships
Arrows point from a package to its direct dependency. Counts are derived from captured workspace manifests.
3 declarations
@lssm-tech/lib.contracts-spec-coreworkspace:^
Read the package manual ↗@lssm-tech/lib.crypto-utilsworkspace:^
Read the package manual ↗@lssm-tech/lib.osint-specworkspace:^
Read the package manual ↗
Declared capabilities
Provider-neutral OSINT lifecycle, ingestion, governance, and knowledge runtime.
Scripts
buildcontractspec-bun-build buildbuild:bundlecontractspec-bun-build transpilebuild:typescontractspec-bun-build typescleanrimraf dist .turbolint:checknode ../../../../scripts/biome.cjs check .testbun testprebuildcontractspec-bun-build prebuildtypechecktsgo --noEmit