For developers and partners
Contracts first, access later
OSINTMethods for systematically finding, verifying and documenting information from open and lawfully accessible sources. Hub connects to portfolio infrastructure through typed boundaries. A contract does not mean a runtime or data access is available.
Content state: draft Owner: owner:platform Next review: 2026-09-07
What we reuse
QazStack provides shared contracts and primitives; OSINT Hub owns content, case policy, editorial review and publication decisions.
- QazLake, QazCompute, QazPipe and QazGeo are considered only through owner-gated integration contracts.
- QazInvestigate, Echolot, QPhoto, QGeo and AntiFake are sources of ideas/modules, not automatically available runtimes.
- Every adapter stays disabled until rights, threat modelA structured description of assets, adversaries, attack paths, impact and controls., capacity and release proof exist.
How to add a module
Add the contract, schema, provenance, policy hooks, negative tests and operator documentation.
- Describe data classes, transport, retentionThe approved time and conditions before material is deleted, archived or placed on legal hold., deletion and owner.
- Provide a synthetic fixtureA deterministic record created for repeatable testing that represents no real person or event. and fail-closed behaviour.
- Do not bring credentials, real cases or private exports into the open checkout.
What ready means
Readiness is not a green build. It requires local checks, release identity, runtime evidenceResearch material whose provenance, time, integrity state and link to an exact source version are preserved. and separate public proof.
- Documentation matches the actual state.
- An external owner signs the admission.
- Rollback and deletion are tested before enablement.