TetraTau Observe
Observation layer for radio sources, space, GNSS, the ionospheric environment, indicator models and the Garmin interface.
TetraTau combines data observation, AI systems, energy technologies, modelling, algorithm development and intellectual property control within one integrated research and technology environment.
Each module can operate independently while sharing one data architecture, security layer, logging framework and AI layer.
Observation layer for radio sources, space, GNSS, the ionospheric environment, indicator models and the Garmin interface.
An algorithmic agent based on related instrument pairs, Pair Score, Recovery Engine and a supervisory Risk Engine.
A registry of development history, hashes, timestamps, backups, integrity, incidents and intellectual property value.
A data platform for energy, pricing, renewables, emissions and energy efficiency, designed to expand into analytics and transaction services.
Audit and report generators, building data models, zones, envelopes, ventilation, heat-loss calculations and energy documentation.
Scope 1–3, emission-factor libraries, product and process modelling, and reporting aligned with GHG methodologies.
A dedicated TetraTau environment for the Garmin watch face, observation data, telemetry, source tracking, replay and historical collection. The module is designed as a bridge between wearable visualization and the wider TetraTau data architecture.
Premium scientific HUD for Garmin with the OBS core, dynamic observation ring, compact data fields and active-source markers.
Collection layer for normalized observation data prepared for the watch, server-side processing and future synchronized datasets.
Compact status and measurement flow for selected ionospheric, GNSS, geomagnetic and supporting environmental indicators.
Visual layer for moving sky objects and radio-source markers used by the watch interface and observation model.
Historical reconstruction of observation states for development, comparison, validation and later playback in TetraTau tools.
A future workspace for retained watch-related datasets, generated observation structures, snapshots and selected historical records.
The interface below presents the public TetraTau system architecture. Private modules will operate through authenticated APIs, PostgreSQL, VPS services and a dedicated security layer.
| System | Module | State | Security | Next action |
|---|---|---|---|---|
| TetraTau Observe | Runtime / Garmin / Space Data | ACTIVE | Protected | Data normalization |
| TetraTau Invest AI | Pair Cycle / Recovery / Risk | R&D | Vault planned | Pair Score v0.1 |
| IP & Evidence Vault | Integrity / History / Legal | READY | Core layer | Backend + PostgreSQL |
| TetraTau Energy AI | Energy / CO₂ / Market Data | MVP | Protected | Expand data model |
| Layer | Role | Status |
|---|---|---|
| Ionosphere pipeline | TEC / normalization / archive | RUNNING |
| Space weather | Kp / Bz / supporting indicators | RUNNING |
| Observation ring | Runtime accumulation / replay | READY |
| Engine | Function | Gate |
|---|---|---|
| Pair Scanner | Correlation / cointegration / spread / Z-score | SPEC |
| Recovery Engine | Controlled reinforcement of winning leg | SPEC |
| Risk Engine | Drawdown, cycle limits, kill switch | MANDATORY |
| Evidence class | Retention | Integrity | State |
|---|---|---|---|
| Source snapshots | Long term | Hash + version | PLANNED |
| Daily evidence package | Long term | Manifest + timestamp | TEMPLATE READY |
| Security logs | Defined policy | Immutable copy | TO DEPLOY |
The security and business continuity layer is being developed in parallel with the individual systems.
VPS, API, PostgreSQL, repositories, logging and access control.
Hashing, timestamps, backups, version registry, chain of custody and evidence packages.
Automated data pipelines, decision models, Pair Engine and Risk Engine.
Unified dashboard, permission control, automation and further TetraTau modules.
The architecture separates the public layer from private systems. Access to source code, algorithms, logs and API keys remains strictly backend-side.
Every significant release can receive a SHA-256 manifest, repository version reference and historical snapshot.
A layer designed to confirm the existence and integrity of selected data at a specific point in time.
Independent backups, immutable/offline copies and the ability to restore the project without relying on a single device.
Secure access is being prepared for internal TetraTau modules. Authentication, MFA, role-based permissions and backend session controls will be enabled before any private system becomes available.