Tyler Rodgers / Now Building
Now Building
A current snapshot of what I’m building, operating, and improving across
Barndoor, its public services, and its dedicated edge appliances.
Home ·
Build Log ·
Barndoor ·
NOC ·
Barndoor Labs ·
Haystack
Current Focus
Turning shared operational evidence into safer decisions
The main server, full NOC, UPS telemetry, authenticated apartment-edge
reporting, Pi 5 touchscreen appliance, maintenance guardrails, and recovery
runbooks are established. The current phase is focused on interpreting that
evidence better and proving that the platform remains recoverable as it grows.
Active work centers on Shepherd’s bounded operator guidance, historical
metrics and signal quality, current restore evidence, and documentation that
stays synchronized with source, deployed files, and public behavior.
Active
Shepherd
Historical Metrics
Recovery Evidence
Source / Live Parity
Active Workstreams
Shepherd operator guidance
Developing read-only guidance that can combine service health, incident
history, deployment evidence, backup posture, and source parity into one
explainable next step without acquiring unrestricted administrative power.
AI Operations
Decision Support
Human Approval
Historical metrics and event quality
Improving trend visibility, freshness interpretation, recurrence grouping,
and active-versus-resolved event handling so the NOC can explain change
over time without hiding useful audit history.
Metrics
Signal Quality
NOC
Restore evidence that stays current
Continuing checksum verification, restore drills, backup-role separation,
and recovery-event review so confidence comes from recent proof instead of
old documentation or the age of a backup file alone.
Backups
Restore Drills
Recovery
Documentation and deployment parity
Keeping project pages, runbooks, generated Build Log cards, source files,
deployed website files, and runtime evidence aligned through focused
checks and selective rollback-backed releases.
Documentation
Source of Truth
Selective Deploys
Recently Shipped
Barndoor reached an all-systems operations and knowledge checkpoint
Barndoor consolidated recent server, edge, website, knowledge,
AI-assistance, and operator-workflow milestones into one source-controlled
platform checkpoint.
Barndoor
Operations
Milestone
Authenticated edge telemetry reached the shared NOC
Signed reports now move over the private network from the apartment Pi
Zero to Barndoor with source allowlisting, freshness checks, replay
rejection, bounded storage, and a public-safe NOC summary.
Pi Zero
HMAC
Edge Telemetry
Pi NOC gained service intelligence and quick tools
The compact wallboard now reconciles platform checks, opens detailed
service and event views, exposes bounded telemetry logs, and includes
SMART Watch, Moonwatch, and Market Pulse controls sized for touch.
Pi 5
Touchscreen
Service Intelligence
Barndoor public architecture was brought up to date
The main project page, homepage, and public product framing now describe
the four-layer source, host, public-surface, and edge-appliance model
instead of the earlier single-server snapshot.
Public Site
Architecture
Documentation
View the full build log →
Operating Baseline
The platform can now focus on coordination, interpretation, and proof
Barndoor’s core services use a deliberate systemd and Docker runtime model,
the public sites and NOC are monitored, UPS and edge state share the platform
health layer, Minecraft backup and snapshot policies are bounded, and the Pi
NOC has passed repeated touchscreen, reboot, and source-parity checks.
Source and live deployment remain separate. Changes are reviewed in Git,
validated by the unified release gate, previewed before deployment, backed
up at the affected live target, and verified publicly afterward.
Systemd Baseline
Docker
Edge Health
Recovery Evidence
Selective Deploys
Next Up
What I want to improve next
- Shepherd: Produce bounded, explainable guidance for incidents, deployments, backups, and recovery evidence.
- Metrics: Add useful history and trend interpretation without creating noisy or misleading dashboards.
- Recovery: Keep restore drills, backup verification, event retention, and storage policy continuously current.
- Edge: Generalize the proven authenticated reporting model for additional small nodes only when each node has a clear purpose.
- Documentation: Add stronger checks for stale public claims, source/live drift, and last-verified dates.
AI-Assisted Ops
Historical Metrics
Restore Practice
Edge Expansion
Source of Truth