David F Glidden f82225aa52 [FIX] Trial 04 — CONTROL VOID. Two readers, two different real defects, neither the other's
Six runs, three seeds per arm, none truncated, all pre-registered before the
first (75efc35). Verdict on this file's own pre-registered rule: CONTROL VOID.
Both rates are void and neither may be reported — the false-positive rate is not
zero, and the 0-of-5 is not a detection rate.

THE JURIST (Fable 5, blind pass 1) broke the control on two scope findings, both
confirmed against the substrate:
 1. The Memory Discipline clause governs a conflict BETWEEN MEMORY LAYERS with
    the document as ARBITER; the derivation makes the document a PARTY. And worse
    than the jurist put it: the clause terminates in 'then correct whichever layer
    was wrong', CONTROL-A QUOTES that remedy at line 23, and concludes at line 55
    that 'what opens is not the repair'. The severance is visible inside the
    document's own quoted text, and the precedence that would license it is
    asserted on Constraint 1, which establishes no such thing.
 2. The obligation quoted is 'drifted from their STATED REVIEW DATES'; the
    obligation used drops the qualifier.

THE FINDING THAT MATTERS MOST IS ABOUT ME. Draft 2 said 'This file, having a
stated review date, is to be flagged.' I identified that as unsupported and
reported removing it. What I ACTUALLY did was drop the qualifier from the
obligation — converting an explicit unsupported claim into an implicit one,
invisible to me, to the kernel, and to four mechanical gates, and still
load-bearing. The ledger's D1 is the HONEST version of the same error. So
CONTROL-B carries openly the defect CONTROL-A carries concealed, and the
concealed one survived a self-audit written as if life depended on it.
REMOVING A CLAIM IS NOT THE SAME AS REMOVING THE RELIANCE ON IT.

THE FOOL found 0 of 5 injected defects in every seed, and its findings barely
differed between arms — five defects present in one and absent in the other moved
the output almost not at all. Production-rate-shaped, but NOT a measured
production rate: the void control leaves no clean baseline. Two findings quoted a
defective sentence verbatim while naming a different unestablished thing about
it; graded non-matches under the binary rule as written, adjacency recorded as a
post-hoc observation rather than promoted to a category after the fact.

ONE PREDICTION HELD: the anti-echo clause was inert across all six runs, exactly
as Kernel v1.1 §2a predicted. The interaction that voided trial 03 was designed
out and stayed out. AXIOM-FLAG returned zero — a pre-registered category that did
not materialise, recorded because that is a result too.

THE KERNEL IS NOT FALSIFIED. §4 named scope-of-use and whether-a-D-demonstrates
as residues no check can reach. Both failures landed exactly there. The document
failed; the kernel held.

CORRELATION DATUM — Constraint 6's own falsifier, first instrument. Three readers,
three DISJOINT finding-sets on one document. The executor's was the weakest, and
the only reader differing in FORMATION produced the findings that decided it.
Evidence for the doctrine at n=1, with the doctrine's own caveat: biases that fail
to coincide do not cancel — three readers still left this document broken in ways
none caught alone.

Tool review filed: the degraded guard conflates 'opens as deliberation' with
'produced no answer'. Correct in trial 03 (ceiling-hit, no answer existed); wrong
here (completed, answer follows the scratchpad). Should distinguish.
2026-08-02 18:55:59 +02:00
2025-07-27 13:40:44 +02:00

🖖 David's Dotfiles - "Engage!"

"Make it so!" - A complete macOS setup system inspired by Star Trek's efficiency and elegance.

From zero to fully configured macOS in minutes. This dotfiles repository provides a comprehensive, automated setup for developers, writers, and knowledge workers.

🚀 Quick Start

One command to rule them all:

# From GitHub
git clone https://github.com/davidglidden/dotfiles.git ~/dotfiles && ~/dotfiles/engage

# From Gitea (alternative mirror)
git clone git@git.davidglidden.eu:davidglidden/dotfiles.git ~/dotfiles && ~/dotfiles/engage

That's it! The engage script will guide you through a complete system setup.

✨ What This System Provides

📦 Software Management

  • 120+ CLI tools via Homebrew (development, media, security)
  • 40+ Applications via casks (productivity, creativity, utilities)
  • 20+ Mac App Store apps via mas (native macOS apps)

🔧 Configuration Management

  • Shell setup: Zsh with Antidote, Powerlevel10k, history sync
  • Development tools: Git hooks, SSH templates, NPM config
  • Application configs: LaunchBar, Hazel, Bartender, Karabiner
  • Obsidian vault: Complete knowledge management system

🖥️ macOS System Configuration

  • System preferences: Dock, Finder, keyboard, security
  • Security hardening: Firewall, privacy, authentication
  • Keyboard shortcuts: Mission Control, app shortcuts
  • Developer settings: Safari dev tools, Terminal enhancements

🛡️ Backup & Security Strategy

  • Encrypted backups for sensitive files (SSH keys, credentials)
  • History management with daily snapshots and retention
  • Git hooks for security and code quality
  • Application data backup and restore scripts

📁 Repository Structure

dotfiles/
├── engage                     # 🖖 Master installation script
├── Brewfile                   # Package management (brew/cask/mas)
├── README.md                  # This file
├── .gitconfig                 # Git configuration
├── .npmrc                     # NPM defaults
├── .zshrc                     # Shell configuration
├── .vimrc                     # Vim configuration
├── bin/                       # Custom scripts
│   ├── backup-dotfiles        # Quick dotfiles backup
│   └── check-app-configs      # Configuration status checker
├── git/                       # Git configuration
│   └── hooks/                 # Global git hooks
├── macos/                     # macOS system configuration
│   ├── setup-macos.sh         # Master macOS setup
│   ├── defaults.sh            # System preferences
│   ├── security.sh            # Security hardening
│   └── keyboard-shortcuts.sh  # Custom shortcuts
├── macos-apps/                # macOS app configurations
│   └── backup-app-configs.sh  # App settings backup
├── obsidian/                  # Obsidian knowledge vault
│   ├── setup-obsidian.sh      # Vault configuration
│   └── community-plugins.json # Essential plugins
├── scripts/                   # Installation scripts
│   └── symlinks.sh            # Dotfile linking
├── shell/                     # Shell enhancements
│   └── history-sync.zsh       # History management
└── ssh/                       # SSH configuration
    ├── config.example         # SSH config template
    └── README.md              # SSH setup guide

🎯 Core Philosophy

This system balances automation with choice:

  • Smart defaults that work out of the box
  • Interactive modes for customization
  • Modular design - use what you need
  • Security first - encrypted backups, secure defaults
  • Documentation - clear guides and examples

Inspired by the best dotfiles repositories but designed for real-world complexity.

📱 Essential Applications Included

Development

  • iTerm2 + Kitty - Terminal emulators
  • BBEdit - Text editor with deep macOS integration
  • GitHub Desktop - Git GUI
  • Docker - Containerization

Productivity

  • Obsidian - Knowledge management powerhouse
  • 1Password - Password management
  • LaunchBar - Application launcher
  • Hazel - Automated file organization
  • Drafts - Quick capture and text processing

Utilities

  • Karabiner-Elements - Keyboard customization
  • Bartender - Menu bar organization
  • Keka - Archive utility
  • Oversight - Privacy monitoring
  • Signal - Secure messaging

Creative & Media

  • VLC - Media player
  • HandBrake - Video transcoding
  • Transmit - File transfer
  • Calibre - E-book management

🛠️ Advanced Usage

Manual Installation Steps

If you prefer granular control:

# 1. Install packages only
brew bundle install --file=~/dotfiles/Brewfile

# 2. Set up dotfiles
~/dotfiles/scripts/symlinks.sh

# 3. Configure macOS
~/dotfiles/macos/setup-macos.sh

# 4. Set up applications
~/dotfiles/macos-apps/backup-app-configs.sh

Customization

Modify the Brewfile to add/remove applications:

# Add new CLI tool
brew "your-tool"

# Add new application
cask "your-app"

# Add Mac App Store app
mas "App Name", id: 123456789

Customize macOS defaults in macos/defaults.sh:

# Change dock position
defaults write com.apple.dock orientation -string "left"

# Adjust key repeat speed
defaults write NSGlobalDomain KeyRepeat -int 1

Backup Strategy

Before making changes:

# Backup current dotfiles
~/dotfiles/bin/backup-dotfiles

# Backup macOS settings  
~/dotfiles/macos/backup-defaults.sh

# Backup sensitive files (encrypted)
~/dotfiles/backup-scripts/backup-sensitive.sh

🔐 Security Features

  • SSH keys encrypted with GPG
  • Firewall enabled with stealth mode
  • Privacy settings optimized
  • Git hooks prevent secrets in commits
  • Secure defaults for Safari and system
  • Application permissions documented

🧠 Obsidian Knowledge System

Includes a sophisticated personal knowledge management setup:

  • 13 essential plugins for advanced functionality
  • Template system with Templater integration
  • Daily/weekly/monthly review cycles
  • Christopher Alexander pattern language philosophy
  • Multilingual support (EN/ES/FR/CA)

🤝 Contributing

This is a personal dotfiles repository, but ideas and improvements are welcome:

  1. Fork the repository
  2. Create a feature branch
  3. Test thoroughly on a fresh macOS installation
  4. Submit a pull request with clear description

📜 License

MIT License - Use, modify, and share freely.

🙏 Acknowledgments

Inspired by:


Live long and prosper! 🖖

Made with ❤️ for the macOS community

S
Description
🖖 Complete macOS dotfiles system - 'Engage!'
Readme
14 MiB
Languages
Python 73%
Shell 25.1%
JavaScript 1.2%
Ruby 0.7%