mtkell
/
signal_transport_planning_and_operations_tool
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
1 Commit 2 Branches 0 Tags 31 KiB
Go to file
Mike Kell 8ed0df3dce feat: initialize documentation structure and CI workflow 2026-07-21 08:00:18 -04:00
.github/workflows feat: initialize documentation structure and CI workflow 2026-07-21 08:00:18 -04:00
docs feat: initialize documentation structure and CI workflow 2026-07-21 08:00:18 -04:00
.gitignore feat: initialize documentation structure and CI workflow 2026-07-21 08:00:18 -04:00
README.md feat: initialize documentation structure and CI workflow 2026-07-21 08:00:18 -04:00
mkdocs.yml feat: initialize documentation structure and CI workflow 2026-07-21 08:00:18 -04:00

README.md

Technical Design Documentation: US Army Signal Transport Planning & Operations Tool

Welcome to the central design repository for the US Army Signal Transport Planning & Operations Tool. These design specifications establish the core system architecture, network transport protocols, security models, and synchronization mechanisms for software development.

Documentation Index

  1. System Architecture & Resource Profile

    • High-level system design and client targets (Tactical Web vs. Android Edge).
    • Resource overhead budgets (CPU, RAM, storage, network).
    • Technology stack selection and compute optimizations.

  2. API & Data Protocols Specification

    • Serialization standards (Protocol Buffers v3).
    • gRPC interface definitions for telemetry, spectrum streaming, and AI recommendations.
    • transport_engine.proto complete schema design.

  3. Security Architecture & Defensive Modeling

    • Full OSI Layer 1 through Layer 7 defensive mechanisms.
    • Role-Based and Attribute-Based Access Control (RBAC/ABAC) permission hierarchy.
    • Zero Trust authentication and transport encryption standards.

  4. Signal Workflows & CRDT Synchronization Engine

    • 6-phase Signal Lifecycle Workflow (Engineering through Governance/AAR).
    • Offline peer-to-peer synchronization architecture.
    • Conflict-Free Replicated Data Type (CRDT) deterministic resolution rules.

Quick Reference

  • Core Runtime: C++20 (NDK / WebAssembly)
  • Serialization: Protocol Buffers v3 / gRPC
  • Sync Strategy: LWW-Element-Set CRDT over UDP/DTN
  • Primary Target Environments: Android Tactical Tablets (Dismounted) & Tactical Web (Command Post)