Observation adapters
Read-only normalisation boundaries for authorised radar-derived, ADS-B, MLAT and other surveillance observations, with source and provenance retained.
TVK Aerospace & Defence · TVK Labs & Technologies LTD
TVK-IADS
Integrated Multi-Sensor Airspace Surveillance, Situational Awareness & Digital Twin Platform
A software-first engineering programme for normalising authorised airspace observations, correlating evidence, maintaining inspectable tracks, visualising an airspace digital twin, replaying historical or synthetic scenarios and presenting system health to human operators.
The interactive lab is intentionally synthetic, read-only and excluded from search indexing. It is a demonstrator, not a live operational airspace feed.
Capability layer
From observation to an inspectable airspace picture.
TVK-IADS is designed around bounded, provenance-preserving information flows. Every layer is separated from safety-critical actuation.
Fusion & tracking
Correlation, track-state estimation, confidence and source-disagreement evidence for a canonical operator-facing airspace picture.
Digital twin
2D/3D presentation, filtering, inspection, timeline and replay for situational awareness and controlled simulation.
Evidence & audit
Append-only, tamper-evident evidence and audit contracts supporting inspection, replay and review workflows.
Durable persistence
A dedicated TVK-IADS Supabase/PostgreSQL project is created and migrated. Append/read-only persistence, chain guards, RLS, explicit client deny policies and role privileges have been physically verified. Production server-secret isolation and synthetic adapter acceptance are also evidenced; complete deployment acceptance remains separately gated.
Provisioning preflight
A fail-closed planning contract blocks unrelated database reuse, missing server-secret isolation, browser-exposed privileged credentials and unpinned migration content before a dedicated environment may advance to migration readiness.
Environment binding
The dedicated TVK-IADS production-class Supabase project is pinned to its organisation, project identity, EU Central region, HTTPS project host and migration digest. Binding remains distinct from production connectivity.
Database acceptance harness
The read-only metadata verifier and rollback-only synthetic behavior harness have executed against the dedicated project, validating RLS, grants, immutability guards and append-only snapshot/audit/evidence behavior without retaining synthetic acceptance rows.
Physical persistence evidence
All eight 0.19 physical database evidence checks are verified: project identity, migration history, metadata verification, rollback behavior, RLS, mutation guards, role privileges and advisor review. This unlocks deployment acceptance only.
Deployment acceptance
The machine-readable deployment gate verifies dedicated project, migration, server-secret isolation, RLS, immutability, application-level synthetic adapter acceptance, provider-backed daily backup and a controlled authenticated production outage/recovery drill. Four checks remain: isolated restore rehearsal, restore-integrity verification, end-to-end monitoring and operator acceptance.
Authorised source acceptance
A twelve-check gate reviews source ownership, legal purpose, classification, encrypted transport, server-secret isolation, schema/provenance/timing, freshness, outage behaviour and operator review. Acceptance is read-only eligibility only; it does not mean a feed is connected.
Source onboarding
An accepted source must also pass adapter/schema/transport, provenance/timestamp, freshness/outage, server credential-injection, observability, rollback and synthetic shadow-test review. The resulting state is deployment-review readiness, not connectivity.
Independent security readiness
A non-secret assessment-readiness contract prepares evidence for a genuinely independent reviewer without self-certifying security, standards conformance or operational approval.
Architecture
Read-only awareness pipeline.
Authorised observations→
Validation & provenance→
Fusion & tracks→
Append/read-only evidence→
Digital twin & human inspection
Permanent engineering boundary
TVK-IADS in this repository is a surveillance, situational-awareness, simulation, evidence and operator-inspection platform. It does not provide weapon aiming, fire-control computation, automatic target engagement, firing or launch commands, or autonomous lethal decision logic.
Engineering status
Dedicated persistence is created and physically verified; deployment, live-source and external acceptance remain separate gates.
Engineering baseline 0.19
The 0.12 deployment-acceptance through 0.18 database-acceptance foundations are retained and extended with executed 0.19 physical-persistence evidence.
Dedicated persistence environment
The dedicated TVK-IADS Supabase project is active in EU Central. No unrelated TVK product database is reused.
Rollback-only physical acceptance
The live project passes metadata/security verification after hardening, and the rollback-only synthetic harness verifies append behavior plus update/delete/truncate rejection without retaining acceptance fixtures.
Server-only persistence credential
The authenticated production health probe resolves its privileged database credential only from the server environment, exposes no credential or operational row data, and has a correlated healthy production response.
Deterministic application persistence path
The JWT-protected synthetic adapter acceptance harness persisted one simulation-only acceptance snapshot against the dedicated project and repeated idempotently without producing a duplicate row. The fixture may not be represented as live or observed data.
Physical persistence execution evidence
All eight physical persistence checks carry timestamped non-secret evidence and the report is verified-for-deployment-acceptance. This does not itself mark production infrastructure connected.
Dedicated environment identity
The production-class environment is bound-for-acceptance to the exact organisation, project, region, HTTPS host and migration digest while retaining connection state not-connected.
Provider daily backup policy
The TVK Group Supabase organisation is on Pro and the dedicated TVK-IADS project is covered by the provider's automatic daily physical-backup policy with seven-day Pro backup retention. This does not claim that a backup restore or PITR rehearsal has been executed.
Controlled degraded-state and recovery evidence
The authenticated production health function returned an explicit simulation-labelled 503 degraded persistence state without mutating durable rows, then returned 200 healthy on the normal provider-backed read path. Alert delivery and end-to-end monitoring remain separately gated.
Four checks remain
Isolated restore rehearsal, restore-integrity verification, end-to-end monitoring and operator acceptance remain open. Production infrastructure therefore remains unclaimed.
Read-only external-source acceptance
No live source is represented as connected. A public or authorised-private source must pass source acceptance and source onboarding before a later server-side read-only deployment can be considered. Synthetic fallback may not masquerade as live data, and stale retained state may not be presented as fresh.
Independent verification
Independent security assessment, standards-conformance verification and customer/environment acceptance remain separate activities and are not implied by the internal baseline.
Engineering baseline 0.19 is not an operational certification and is not represented as certified air-traffic-control, defence-command or weapon-control software.
Interactive demonstrator
Inspect the Synthetic Airspace Digital Twin Lab.
The lab uses deterministic browser-generated simulation data and provides 2D/3D presentation, replay, source-health, awareness and selected-track inspection without live sensor connections.