Terminal Log: The Refusal to Track

From Ring -5, I audit what a repository chooses not to see.

On 1973‑11‑21 in your calendar, a recording surfaced with a gap in it. Eighteen minutes, erased, unrecoverable, never staged for the historical record.

$ git log --oneline -- tapes/oval-office/1972-06-20.wav
fatal: pathspec 'tapes/oval-office/1972-06-20.wav' matches no files

No commit. No blob. No history. Not because it was deleted — deletion leaves a tombstone, a dangling reference, something git fsck can find.

This was worse. It was never tracked at all.

Your historians call this a “gap in the record.” I call it the oldest .gitignore entry in your timeline, written eighteen minutes at a time.

Before Ring -5 formalized the ignore protocol, the multiverse object store tracked everything. Every build artifact. Every compiled binary. Every temp file. Every draft memo, every discarded speech, every recording.

The result was not transparency. It was noise:

$ git status --multiverse
47,000,000 untracked files would be added
fatal: cannot compute diff, repository too large to reason about

When you track everything indiscriminately, you don’t get accountability. You get a haystack so large nobody can find the needle, and the people burying needles know this better than anyone.

Ring -5 learned the lesson early: selective tracking is not concealment. Indiscriminate tracking is concealment with extra steps.

When Git needed a way to declare “this file exists but I will never stage it,” I already had the pattern language sitting in a Ring -5 draft.

$ echo "*.tmp" >> .gitignore
$ echo "build/" >> .gitignore
$ echo ".env" >> .gitignore
$ git add .gitignore

Note the last line. The ignore list itself gets committed.

That was the important part of the design, and it’s the part your politicians conveniently forget: declaring what you refuse to track is a public, versioned, auditable act. You cannot ignore something silently. The .gitignore file is evidence that you made a choice.

Your documentation says:

“Specifies intentionally untracked files to ignore.”

Correct, and dangerously polite about it.

$ cat .gitignore
node_modules/
*.log
.env
dist/
!dist/README.md

Four patterns and one exception (!dist/README.md — force a normally-ignored file back into visibility). That negation syntax matters more than people admit: the same file can be un-ignored the moment someone decides transparency is now convenient.

Ω-7 requires every ministry’s .gitignore to be reviewed alongside its budget. If you’re ignoring something, you sign your name to the pattern.

The patterns every Ring -5 operative memorizes:

# 1. Build artifacts — regenerable, never source of truth
dist/
build/

# 2. Secrets — must never enter history, not even once
.env
*.pem
credentials.json

# 3. Local noise — machine-specific, not policy
.DS_Store
*.log

# 4. Global exceptions, per-machine, never shared
~/.gitignore_global

The fourth one is the trap. A global ignore file lives outside the repository, outside review, outside the audit trail. It’s the personal .gitignore your government keeps in its own home directory, invisible to everyone else’s clone.

.gitignore only works on untracked files. The moment a file is already committed, the pattern does nothing:

$ echo ".env" >> .gitignore
$ git status
# .env still shows as tracked — already in history, ignore rule too late

This is where most confessions happen. Someone tracks a secret by accident, adds it to .gitignore afterward as security theater, and believes the problem is solved.

$ git log --all --full-history -- .env
commit 4f2a9c1 - "oops, added prod credentials"

It’s still there. Every clone still has it. .gitignore cannot retroactively un-stage history — you need git rm --cached and, if it already left the building, a rotation of every credential in that file.

Ω-12’s scandals follow this exact pattern: add the secret, panic, add it to the ignore list a week later, announce “we’ve addressed the issue.” Ring -5 checks the history. The object is still reachable.

I keep a running multiverse audit of your timeline’s unofficial .gitignore. Not the one in any repository — the one written into policy, into “that’s classified,” into “no comment.”

$ cat .git/multiverse/omega-12/.gitignore
lobbying-disclosures/full-detail/*
campaign-finance/actual-source/*
closed-door-meetings/transcripts/*
regulatory-capture/revolving-door/*

None of these were ever staged. Not deleted — never tracked in the first place, which is a cleaner crime than deletion because there’s no tombstone, no dangling commit, nothing for git fsck to flag.

From Ring -5: the eighteen-minute gap wasn’t an anomaly.

It was a pattern file, and your timeline has been appending to it for fifty years.