DETECT: d_min - 1
CORRECT: ⌊(d_min - 1)/2⌋
ARCHITECTURE: FEC_DECODER
SYNDROME: ZERO
ASKiIMAN™ DOOR 07 / THE VOICE / REALM 12
--:-- · -- --- ----
1011010
X
X
1001110
1011

Ontological Layer: The Fortress Around the Message

Channel Coding

The Source Speaks. The Channel Attacks. The Code Remembers.

The Realm of Redundancy

Realm 11 compressed our data, stripping away all wasted space until every bit carried maximum information. But in a noisy universe, a single flipped bit destroys the message. In Realm 12, we fight back by deliberately injecting structured redundancy. By mathematically expanding our data into larger Codewords, we create a rigid geometric structure. When the channel damages the bits, the receiver uses Syndrome calculations to detect the violation and, through Forward Error Correction (FEC), reconstruct the original truth without asking for a retransmission.

DATA → + PARITY → CODEWORD → NOISY CHANNEL (ERRORS) → RECEIVED WORD → SYNDROME DECODER → RECOVERED DATA

The 16 Coding Nodes

Ontological Mapping: From Parity to Forward Error Correction

CHAMBER 01

The Fundamental Problem

  • A transmitted bit may arrive incorrectly
  • Receiver cannot "look harder" to find the error
  • Solution: Add carefully designed redundancy
  • Structure allows errors to become detectable/correctable
CHAMBER 02

Source vs Channel

  • Source Coding: REMOVE redundancy (Compress)
  • Channel Coding: ADD useful redundancy (Protect)
  • Realm 11 makes information smaller
  • Realm 12 makes information safer
CHAMBER 03

Block Code (n, k)

  • k = original information bits
  • n = total coded bits transmitted
  • n - k = added redundancy (parity) bits
  • Code Rate R = k/n (higher rate = less redundancy)
CHAMBER 04

Hamming Weight

  • The number of non-zero bits in a binary word
  • Provides foundation for understanding distance
  • Example: 101101 contains four 1s (w = 4)
  • Used to evaluate the structure of linear codes
CHAMBER 05

Hamming Distance

  • Number of positions where two sequences differ
  • d_min: Smallest distance between ANY two valid codewords
  • Determines the basic error capability of the code
  • The most important concept in the realm
CHAMBER 06

Detection vs Correction

  • Detection: "Something is wrong" (Invalid codeword received)
  • Correction: "The intended codeword was this one"
  • Correction requires significantly more redundancy
  • Do not collapse them into the same operation
CHAMBER 07

Geometric Correction

  • Imagine valid codewords as points in geometric space
  • Noise pushes the received word away from the point
  • Nearest-neighbor intuition: select the closest valid point
  • If noise pushes it past the halfway mark, an error occurs
CHAMBER 08

Error Capability

  • Must memorize exactly based on d_min
  • Can DETECT up to: d_min - 1 errors
  • Can CORRECT up to: ⌊(d_min - 1)/2⌋ errors
  • d_min=5 means Detect 4, Correct 2
CHAMBER 09

Basic Parity

  • Add one bit so total 1s follow a chosen rule (Even/Odd)
  • Even Parity: Total number of 1s must be even
  • Primary use: Detecting single-bit errors
  • Fatal Flaw: 2 bit errors cancel the parity effect out
CHAMBER 10

2D Parity

1
0
1
1
1
0
1
0
1
0
1
1
0
0
0
0
0
1
0
1
  • Arrange data into rows and columns
  • Parity exists along multiple dimensions
  • Intersection of row/col anomalies identifies corrupted bit
  • Transforms detection into basic correction
CHAMBER 11

Linear Block Codes

  • Combinations of valid codewords produce valid codewords
  • c₁ ⊕ c₂ = c₃ (Modulo-2 addition / XOR)
  • Includes classic Hamming codes
  • Allows for elegant matrix-based encoding/decoding
CHAMBER 12

G and H Matrices

  • Generator Matrix G: Defines how bits are transformed
  • Encoding: c = mG
  • Parity-Check Matrix H: Defines valid code condition
  • Validation: Hcᵀ = 0 (Under modulo-2 arithmetic)
CHAMBER 13

Syndrome Decoding

  • Syndrome tells decoder if parity constraints are met
  • s = Hrᵀ (Received word multiplied by H)
  • s = 0 indicates a valid codeword
  • s ≠ 0 identifies the exact location of the error pattern
CHAMBER 14

FEC & Interleaving

  • FEC: Correct errors locally without asking for retransmission
  • Burst Errors: Clusters of corrupted bits that destroy codes
  • Interleaving: Rearranges bits before transmission
  • Deinterleaving spreads the burst out, making it correctable
CHAMBER 15

Convolutional & Viterbi

  • Unlike Block codes, Convolutional codes introduce MEMORY
  • Trellis unfolds encoder state transitions over time
  • Viterbi Decoder: Maximum-likelihood path search
  • Finds the path with the smallest accumulated distance/metric
FINAL PROTOCOL

16 — The Redundancy Laboratory

1. HAMMING (7,4) CODE INITIALIZED. d_min = 3.
2. RX = 1001010. SYNDROME s = Hrᵀ COMPUTED.
3. s ≠ 0. ERROR DETECTED AT INDEX 3.
4. FEC APPLIED. DATA CORRECTED TO 1011.
[1] CALCULATE WEIGHT [2] MEASURE DISTANCE [3] GENERATE SYNDROME [4] INTERLEAVE BURSTS [5] TRACE TRELLIS

The fortress is complete. By understanding Hamming distance and Syndrome decoding, you can now push clean information through a corrupting channel without requesting a retransmission. But all of this relies on abstract 1s and 0s. How do we actually push these logical bits down a physical copper wire or optical fiber? You are now prepared for Realm 13: Baseband & Line Coding.

SYNDROME DECODER RUNNING