A backup you have never verified is a rumor.
one file · zero dependencies · stdlib only
- You assumed there was a backup; at restore time the manifest was six months old and half the files were gone.
- The backup job has been green for three years and has never once been restored.
- Files changed, hashes no longer match the manifest, and nobody ever compared them.
One command, on a file you already have:
python gate.py verify examples/dataReal output — produced by the bundled examples/, not a mock-up
backup-gate report
================================
ERROR notes.md hash-mismatch sha256 differs from manifest
summary: declared=2 on_disk=2 missing=0 extra=0 mismatch=1 errors=1 warnings=0
verdict: FAIL: 1 integrity error(s)
- Builds a SHA-256 manifest, then verifies content, presence, and freshness.
- Reports exact mismatched and missing paths — not just a count.
- Text or JSON; cheap enough to run nightly.
- It is a verifier, not a backup tool. It does not copy anything anywhere.
- Freshness checks the manifest age, not whether the data is correct.
- No offsite, no encryption, no retention policy — pair it with a real backup system.
Being explicit here is cheaper than a wrong expectation later.
0 = manifest matches. 1 = mismatch or tamper. 2 = bad input or missing manifest.
git clone https://github.com/chenhz01/backup-gate
cd backup-gate
python gate.py --helpPython 3.9+. Nothing to pip install — stdlib only.
- name: backup-gate
run: python gate.py verify examples/dataaction.yml is included, so you can call this repo directly as a composite action.
# .github/workflows/gates.yml
- uses: actions/checkout@v4
- uses: chenhz01/[email protected]
with:
# IMPORTANT: this path is inside YOUR repository.
# The examples/ in this repo are NOT in your workspace — pass your own files.
args: "verify path/to/data"Pin the tag (@v0.1.3) rather than @main — main moves.
Check Releases for the newest tag; v0.1.0 predates the
fix that makes a mistyped path fail instead of silently passing.
If you omit args, the action only prints help and exits 0. It raises a warning
annotation — quoting this gate's own correct usage — so a green check is never
mistaken for "it inspected my files".
备份门 — 没有验证过的备份，只是一个传闻。
- 以为有备份，真要用时发现清单是半年前的，还少了一半文件。
- 备份任务绿了三年，没人试过一次还原。
- 文件被人改过，哈希值和清单对不上，但没人比对过。
一行命令：python gate.py verify examples/data
边界：It is a verifier, not a backup tool. It does not copy anything anywhere.
十五个链接是迷宫，一个症状是门。按上表挑一个，其余九个在下面 The gates。
每个仓都能单独活：复制 gate.py，一条命令跑完，不共享运行时、不装包、不加配置。
有星就给这一个，没有也不影响任何仓的可用性——没有任何门是「先给星才能用」。
本页承诺的是 15 项可机器复核的结构特征，当前 15/15（2026-10-20 复核）。
GitHub 从未公开 Trending 的排序算法，所以任何「保证上热门」的说法都在描述一件它不可能知道的事；
本仓不这么说。跑 python tools/hotness.py 可自行复算每一条。
Fifteen links is a maze; one symptom is a door. Find your symptom, install that gate, ignore the rest until it hurts.
| what you are seeing | install this |
|---|---|
| the bill is 10x normal and the trace is a wall of the same step | loop-gate |
| the agent can delete prod and nobody signed off on that | permission-gate |
| answers get worse after truncation and nobody knows what got dropped | context-gate |
| two rules in the prompt contradict each other; the model obeys neither | instruction-gate |
| AI text ships with fabricated links and empty phrases | output-gate |
| half the repo might be dead and nobody can prove which half | deadcode-gate |
A gate you did not need is a gate you uninstall, so nothing here says "install all
fifteen". Each repo stands alone: copy gate.py, run one command, no shared runtime,
no package manager, no config file to grow.
On stars. If this one saved you an incident, star it — that is the only signal I get about which gate to build next. There is no exchange: starring one repo does not owe me a star on another, and no gate here is unlocked by a star. Star trading breaks GitHub's rules and would poison the single honest metric this project has.
What is guaranteed is structure, not ranking. Fifteen properties, each one machine-checked against this repo — current score 15/15 (2026-10-20).
Plain version: instead of asking you to trust a badge, I list what I actually checked, name the script that checks it, and let you re-run it. If one of these lines is false, that is a bug in my repo, not a matter of taste.
- Falsifiable side:
python tools/hotness.pyre-runs every check and prints the evidence line for each one. You do not have to trust this paragraph. - Non-falsifiable side: GitHub has never published how Trending sorts repositories, so any repo promising you a guaranteed spot is telling you something it cannot know. This one does not make that promise.
- If a claim on this page stops being true, that is a bug: open an issue and it gets fixed in the same week, not in the next launch.
What actually carries this repo:
- the command in this README is byte-for-byte the command CI runs (28-char argv, exact match)
- the output block is a real run of
examples/, not a mock-up (Real output section) - CI asserts the exit code, so the badge can turn red — and it has (asserts exit=1)
- every fixture is committed, so a fresh clone reproduces the output (2 files under examples/ tracked in git)
* -textin.gitattributes: same bytes on Windows and Linux (.gitattributes * -text)
| # | gate | what it stops |
|---|---|---|
| 02 | loop-gate | Find where your agent looped, before it burns another run |
| 03 | permission-gate | Score how much more your agent can do than it should |
| 04 | context-gate | Measure what truncation deletes, before the model starts guessing |
| 05 | instruction-gate | Two of your instructions contradict each other. This finds them |
| 06 | output-gate | Before AI-written text ships, run the four checks it always fails |
| 07 | memory-expiry-gate | Give every memory a TTL, then prove the expiry semantics actually hold |
| 08 | drift-gate | When embeddings drift, retrieval quietly rots. Fingerprint it |
| 09 | price-gate | Your cost model is only as good as the price table under it |
| 10 | complexity-ceiling | Per-file complexity budgets that fail the build instead of the reviewer |
| 11 | deadcode-gate | Quantify how much of the repo is dead, instead of guessing |
| 12 | docrot-gate | Docs don't die at once. They rot one stale command at a time |
| 13 | leak-gate | Scan for internal detail before the doc leaves the building |
| 14 | backup-gate ← you are here | A backup you have never verified is a rumor |
| 15 | trail-gate | Hash-chained agent audit trail — and it verifies its own chain |
- Code: Apache-2.0 — see LICENSE
- Docs and example data: CC BY 4.0 — see LICENSE-SPEC
Attribution required when you redistribute the documentation; code can be used commercially without a separate agreement. See NOTICE.