Individual skill

s4h-information-redundancy

Maps where redundancy creates resilience and error correction versus where it creates waste. Use when asked about 'duplication', 'repetition', 'backup systems', 'is this redundant?', 'we're saying the same thing twice', 'single point of failure', or 'is this repetition helping or hurting'.

skills/s4h-information-redundancy/SKILL.md

Read pinned source

Source commit a30df8b67698ccb03ef5e35d68c2eddc5321ad3f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
240
Repository last updated
Jul 15, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Information: Redundancy

Redundancy is the presence of more information than is strictly necessary to transmit a message. In everyday usage, "redundant" is a criticism — meaning wasteful, duplicative, bloated. Shannon's information theory revealed the other side: redundancy is also the mechanism by which messages survive noisy channels. Without redundancy, a single corrupted bit destroys the message. With the right kind of redundancy, errors are detectable and correctable.

English has roughly 75% redundancy — far more than the minimum required to convey meaning. This is not a design flaw. It's what allows us to understand messages even when words are missing, sentences are incomplete, or the channel is imperfect. The same principle appears everywhere: RAID arrays duplicate data across disks so a drive failure doesn't mean data loss; aviation uses triple-redundant systems so a single component failure doesn't mean a crash; well-structured arguments repeat their core claim in multiple forms because readers approach text non-linearly and a single statement may be missed.

The analytical task is to distinguish these two faces of redundancy. Load-bearing redundancy serves a function: fault tolerance, error correction, pattern reinforcement, or verification. Wasteful redundancy serves no function: it is repetition without purpose, bulk without benefit, duplication that increases cost without increasing robustness. The line between them is determined by the system's failure modes and the value of what it's protecting.

Shannon's coding theorems established that redundancy can be added optimally — there is a minimum amount of redundancy needed to achieve a given level of error correction. This is the basis of modern error-correcting codes. The applied insight: before eliminating redundancy, understand whether the redundancy is doing error-correction work you'd otherwise lose.

---

## Your Process
Back to top