Skip to content

Repository files navigation

DTP-Ω1 - Divinitus Transmission Protocol

"In the Machine’s name, let the data flow and the checksum be pure."Magos Trinary Ux-99

Overview

DTP-Ω1 (Divinitus Transmission Protocol) is a layered, stateful, checksum-verified communication standard designed for sanctified data transfer across Mechanicus-aligned systems, cogitator units, and blessed network links. It ensures purity, order, and compliance in all transmissions.

Features

  • Encrypted rite-seal authentication
  • Instruction-code-based command structure
  • Bi-directional cogitator handshake and session binding
  • CRC16 checksum validation to ensure data sanctity
  • Support for burst transmission, syncing, and rite execution
  • Built-in error reporting and link severance protocols
  • Magos-grade trust ring verification

Packet Structure

+--------------------+
| RITE_HEADER        | → 0xAA55
| ORIGIN_ID          | → 2 bytes (hex)
| DESTINATION_ID     | → 2 bytes (hex)
| INSTRUCTION_CODE   | → 1 byte
| FLAGS              | → 1 byte bitmask
| PAYLOAD_LENGTH     | → 2 bytes
| PAYLOAD            | → N bytes
| DIVINE_CHECKSUM    | → CRC16
| RITE_FOOTER        | → 0x55AA
+--------------------+

Instruction Codes

Code Command Description
0x01 INITIATE_HANDSHAKE Begin session binding
0x02 ACK_HANDSHAKE Confirm binding and receive token
0x03 REQUEST_SYNC Request new codex/versional data
0x04 SYNC_CONFIRMED Confirm synchronization completed
0x05 BLESSING_BURST Transmit high-priority memetic payload
0x06 EXECUTE_RITE Command execution at destination node
0x07 COMPLETION_SIGNAL Confirm successful rite execution
0x08 ERROR_REPORT Report checksum or flag failure
0x09 SEVER_LINK End transmission and purge session

Flags

Bit Flag Description
0x01 ACK Acknowledged
0x02 RST Request Reset
0x04 PRIO High-Priority (Magos or above)
0x08 ERR Error Detected in Last Transmission

Handshake Example

> ORIGIN: Adept_Unit_039
> SEND: INITIATE_HANDSHAKE → PRIO FLAG
> EXPECT: ACK_HANDSHAKE within 800ms
> BIND: Session with rite-seed

Security

  • Rite-Seal Header: Authenticates sender rank and purity
  • Checksum: CRC16 ensures data is uncorrupted
  • Trust Ring Enforcement: Only authorized IDs may perform critical rites
  • Triplicate Echo: Confirms payload via redundant verification cycles

Termination Sequence

> TRANSMIT: SEVER_LINK
> LOG: Rite closure in central Divinitus Registry
> PURGE: Temporary memory and session tokens

Integration

  • Supports interfacing with SCP/MECH-42, TSP/Omni, and LTP-SectorNet buses
  • Bindable to custom automation daemons for server-side rite enforcement
  • Compatible with ModOS, CogitOS, and Arch-Firmware nodes (v9 and above)

Compilation & Usage

Requirements:

  • C compiler (MSVC, GCC, or Clang)
  • CMake 3.10+

Build (Linux/macOS):

mkdir build && cd build
cmake ..
make

Build (Windows with CMake/Visual Studio):

cmake -S . -B build
cmake --build build --config Release

Run

Server Mode:

./dtp server [port] [originID]
# Example:
./dtp server 4242 0xAABB

Client Mode:

./dtp client [host] [port] [originID] [destID]
# Example:
./dtp client 127.0.0.1 4242 0xBEEF 0xAABB

Input via stdin (optional):

echo "client 127.0.0.1 4242 0xBEEF 0xAABB" | ./dtp

Warnings

  • Improper checksum or malformed headers will result in automatic purge
  • Unauthorized rites will be logged and flagged for Magos review
  • Repeated violations will initiate Exterminatus Subroutine 17/Null

Licensing

Distributed under the Omnissiah-Standard License v42. Unauthorized duplication will be sanctified via plasma.

Glory to the Omnissiah. May your pings be clean and your litanies checksum-aligned. DTP-Ω1: Because data deserves devotion.

About

DTP-Ω1 (Divinitus Transmission Protocol) is a layered, stateful, checksum-verified communication standard designed for sanctified data transfer across Mechanicus-aligned systems, cogitator units, and blessed network links. It ensures purity, order, and compliance in all transmissions.

Topics

Resources

Stars

Watchers

Forks

Releases

Contributors

Languages