Vectra Arch

NLP at practitioner level — the study of how language shapes cognition and how cognitive patterns can be deliberately restructured. The same systems thinking that governs infrastructure governs behaviour. Input, processing, output. The architecture is identical. The material is human.

Certified life coach, coaching manager, and wealth coach. I apply structured thinking to how people make decisions, set goals, and allocate resources. While businesses may pivot, the framework of human optimization is permanent. I mentor those operating at high-load capacity.

Vectra Arch is about how things move — information, intent, value, trust. The same way a well-configured network routes packets efficiently and without loss, good mentorship routes people toward clarity without distortion. The channel matters. The protocol matters. The signal must arrive intact.

I did not choose the environment I was initialised in. But I learned early that the environment is not the constraint — the architecture of how you respond to it is. Namibia gave me a starting point. South Africa gave me the conditions. What I built from those conditions is entirely my own.

At 18 I was handed a terminal and a responsibility. I have not put either down since. From onsite support technician to remote helpdesk, from Linux administrator to Linux engineer, from senior Linux engineer to DevOps engineer, to senior systems engineer — now Principal Engineer.

Twenty-four years. Not a career path — a compounding architecture. Each role was a deeper understanding of how systems hold together under load, and how they fail. I have experienced both intimately.

I have lost everything four times. Not metaphorically — materially, structurally, completely. Each time the stack was wiped and the rebuild began from zero. No snapshots. No rollback. Just the discipline of knowing how to lay foundations when the ground beneath you is unstable.

Thirteen times I came close to not being here. I am not going to make that sound heroic. It is not heroic — it is a fact of a life lived at the edge of its own load tolerance. What I can say is this: each time, the system came back online. More hardened. More deliberate. Better instrumented.

I started writing in 2013 because the alternative was silence. I had things to say that had no other format. The stories I carry — the people I have lost, the systems that failed, the ones that held — needed to exist somewhere outside of me.

Following the 2024 completion of Human Exposure and the lessons of a 2025 self-publishing attempt, the focus has shifted to the Book Forge. The infrastructure for storytelling is now as robust as the systems I engineer. The work is finding its readers. That is what this architecture is for.

In 2015 I picked up clay. What followed was over a decade of working at the intersection of patience and exactness. Sculpting is engineering for people who need to feel the resistance of the material. You cannot automate it. You cannot abstract it. Every millimetre is a decision.

From anatomically precise human skulls to the philosophy of the Studio, the discipline remains the same: the same mindset that keeps a Linux environment stable keeps the anatomy accurate. Measure twice. Commit once.

Everything above is context. The reason the system keeps running is this: three children who need a father who does not stop. I am a single parent. Every line of code, every page written, every sculpture completed, every system engineered — it all runs because of them. Not for legacy. For now. For them, today.

This is not a legacy project. This is an active obligation. The infrastructure I maintain most carefully is the one they live inside.

Started as an onsite Linux support technician at 18. From there: remote helpdesk, Linux administrator, Linux engineer, senior Linux engineer, DevOps engineer, senior systems engineer — now Senior Infrastructure Engineer. Twenty-five years of compounding depth, not breadth for its own sake.

Ansible playbooks for automated software and configuration management, full environment provisioning, and OS hardening. Manual repetition is a failure mode, not a workflow. Every repeatable task has a playbook. Every playbook has been tested under load.

Bespoke monitoring with custom discovery rules for database and VPN monitoring. Not templates — alerting logic built around real failure modes encountered in production. The difference between a dashboard and an early-warning system is the person who wrote the discovery rules.

Ubuntu hardening is not a checklist. Understand the attack surface, reduce exposure, monitor what remains. Rate limiting on all public endpoints. Tokens server-side only. SSL on every subdomain. Security headers on every response. The philosophy of securing a server and the philosophy of structuring a life are not as different as they sound.

Nginx running a single unified config — vectraarch.live — managing all site locations from one file. Each path has its own location block, SSL certificate via Let's Encrypt Certbot, HSTS headers, and server_tokens off. Static sites serve directly from web root. Node.js applications proxy through internal ports. Rate limiting applied at the nginx layer for all public form endpoints.

Five Node.js processes managed by PM2 with startup persistence and fork mode. All running as root, all online. VectraArchForge is the full writing management application. VectraArchConduit is the automation and social dashboard. VectraArchContact handles all Telegram contact form submissions server-side. VectraArchIdentity is the Identity Bridge API. VectraArchLegacy runs the lifestyle management application.

PostgreSQL 16 running locally. Single database — bookforge — with tables for users, books, entries, and conduit_log. The users table handles both Google OAuth identities and manual credential accounts with role-based access. The books table drives both the Book Forge application and the Press static catalogue rebuild. The conduit_log table records every automation trigger fired through the Conduit Hub dashboard.

Node.js and Express backend proxied by Nginx. PostgreSQL 16 database via the pg driver. EJS server-side rendering for all views. Passport.js handling both Google OAuth 2.0 and manual credential authentication. TOTP-based 2FA via otplib with QR code setup flow. Multer handling cover image uploads to the public/uploads directory.

The users table stores both Google OAuth identities and manual accounts (prefixed m_) with name, email, type, role, status, login count, and TOTP secret. The books table links to users via owner_id, stores title, cover_url, and published flag. The entries table holds all manuscript content, characters, factions, geography, research, science, world rules, items, and timeline entries — all keyed by book_id and category. The conduit_log table records every announcement trigger fired from VectraArchConduit.

When any book is published or unpublished, VectraArchForge calls rebuildPressIndex() — a function that queries all published books with author details and manuscript entry previews, groups them by author, and writes a fully self-contained HTML file to the press web root. No build pipeline. No CMS. No external dependencies. PostgreSQL query → Node.js template → file write. Press is always current.

VectraArchForge exports any volume in five formats. DOCX via the docx library with proper heading levels and paragraph styling. PDF via PDFKit with A4 layout and justified text. EPUB via epub-gen-memory with chapter structure. Markdown with section dividers. Plain text with ASCII formatting. All generated on-demand, streamed directly to the browser — nothing written to disk.

Foundation is the single point of entry for all authenticated services in the VectraArch constellation. Identity management, 2FA, and Google OAuth are coordinated here — without exposing credentials at the client layer. Authorised entry only.

In 2015 I walked into an art studio after work and picked up clay. What followed was ten years of working at the intersection of patience and exactness. Sculpting is engineering for people who need to feel the resistance of the material. You cannot automate it. You cannot abstract it. Every millimetre is a decision.

Most recent work: an exact-scale human skull — hand-sculpted, anatomically precise. The same discipline that keeps a Linux environment stable keeps the anatomy accurate. Measure twice. Commit once.

Volition is where I write about the process of building the VectraArch constellation — the decisions I made, the ones I got wrong, what I learned from both. This is distinct from Press, which publishes finished fiction, and from Kinetic, which showcases visual work. This is the working document. The commit history of a life under construction.

It is not optimised for an audience. It is not a content strategy. It is a record — because the discipline of writing down what you built and why is the same discipline as building it in the first place. Systems need documentation. This is mine.

The scope is the whole system. Why I built Book Forge instead of using an existing tool. What broke when I migrated the database. How I approached the Nginx single-config setup. What it costs to rebuild from zero four times and keep going anyway. The architecture of a life is not separate from the architecture of the systems it runs on. Both belong here.