// SYSTEM ONLINE — P9SOURCE.COM BUILD 2026.Q2

SYSTEMS
FAIL.
LEGACIES
DON'T.

The source code for building
what lasts. In the AI economy.
In the life you rebuild from zero.

// Enter The Source // View The Architect
9 Core Systems
19+ Years Built
∞ Iterations
SYSTEMS ONLINE AI Economy Infrastructure Digital Legacy Architecture P9SOURCE v3.0 Resilience Engineering Source Code for Builders ARCHITECT MODE: ACTIVE No Plastic Casings. Dark Mode Only. SYSTEMS ONLINE AI Economy Infrastructure Digital Legacy Architecture P9SOURCE v3.0 Resilience Engineering Source Code for Builders ARCHITECT MODE: ACTIVE No Plastic Casings. Dark Mode Only.
// 01

CORE MODULES

[SYSTEMS]

AI Economy
Architecture

Technical "Source Code" for your business

The tools, frameworks, and mental models required to build durable infrastructure in a world being rewritten by artificial intelligence. No hype. No noise. Pure signal.

Access Module
[RESILIENCE]

Human
Reconstruction

Mental "Source Code" for your mindset

What happens when the system that sustains you catastrophically fails? This module documents the rebuild protocol — from breakdown to breakthrough, in exacting detail.

Access Module
[LEGACY]

Permanent
Infrastructure

Strategic "Source Code" for your future

Legacies are not accidents. They are engineered. This is the long-game playbook for building something that outlasts the builder — the Paragon standard.

Access Module
// DIAGNOSTICS

SYSTEM STATUS

p9source — bash — 80×24
p9@source:~$ ./system-check --all-modules
✔ [SYSTEMS] AI Economy Module ........... ONLINE
✔ [RESILIENCE] Reconstruction Engine ..... ACTIVE
✔ [LEGACY] Infrastructure Protocol ........ BUILDING
⚡ [PARAGON9] Next cohort deploying ........ Q3 2026
p9@source:~$ cat /etc/founder.conf
NAME="Greg Scott Kirk"
ROLE="Founder. Architect. Survivor."
STATUS="Operational"
MISSION="Build what lasts."
p9@source:~$
Greg Scott Kirk — Founder, Architect, Survivor — P9SOURCE
ID: GSK-001 // AUTHENTICATED
// THE ARCHITECT — 02

GREG SCOTT
KIRK ◆

Founder | Architect | Survivor

Not a thought leader. Not a content creator. An operator.

Greg Scott Kirk has built, broken, rebuilt, and engineered systems—both human and digital—for over two decades. When the infrastructure of life failed at its most critical juncture, he didn't pivot.

He reconstructed. From the frame up. This is the documented source code of that process, and the permanent infrastructure it produced.

20+ Yrs in Field
3 Near-Zero Points
∞ Iterations Left

Access unlocks the gated LOGs and the P9 checklists. Magic link — no password, no noise.

// 03. PARAGON — THE STANDARD

BUILD TO
PARAGON
SPEC.

Paragon is not a course. Not a community. Not a mastermind group with a monthly fee and a Discord server.

It is a standard. A precision benchmark for what it means to build durable human and digital infrastructure in the modern era. If you're here, you already know the difference.

Software is easy. Resilience is hard. Get the source code to both to build what lasts.

Access unlocks the gated LOGs and the P9 checklists — the Grief-Proof Infrastructure Audit and the Constraint Checklist. Magic link, no password.

// 04

THE LOGS

2026.07.20 [SYSTEMS]

LOG 010.6: Connecting Nine to Azure DevOps — and Getting Credential Custody Right

This is Part 6 of the Nine / 9OS series. Part 5 closed the original arc: Nine online, operating inside the Paragon9 M365 environment with a locked identity, a SharePoint Command Deck, and four Teams channels enforcing the direction of work. That was supposed to be the final entry.

2026.06.15 [SYSTEMS]

LOG 010.5: Connecting OpenClaw to Microsoft Graph and Bringing Nine Online

This is Part 5 of the Nine / 9OS series — the final entry. Parts 1–4 built the infrastructure foundation, the M365 identity layer, and the 9OS workspace. This entry wires everything together: Graph API access, Nine's identity file, confirmation that the inbound webhook delivery via Cloudflare Tunnel (built back in LOG 010.2) is still live, and the live end-to-end test that confirms Nine is operational inside the Paragon9 M365 environment.

2026.06.05 [SYSTEMS]

LOG 010.4: Building the SharePoint 9OS Command Deck and Teams Channels

This is Part 4 of the Nine / 9OS series. Part 3 built the identity layer — the M365 account, NordVPN dedicated IP, and Conditional Access policy. This entry builds the workspace: the SharePoint site Nine operates from, the Teams command channels, and the naming architecture that makes the whole system coherent and scalable.

2026.05.22 [SYSTEMS]

LOG 010.3: Setting Up a Dedicated M365 Identity for Nine

This is Part 3 of the Nine / 9OS series. Part 1 covered standardizing OpenClaw as a headless systemd service on a minimized Ubuntu Server. Part 2 covered connecting it to Microsoft Teams. This entry builds the identity layer — the M365 account, the dedicated static IP, and the access controls that lock Nine to exactly one machine.

2026.05.15 [SYSTEMS]

LOG 010.2: Connecting OpenClaw to Microsoft Teams on a Headless Linux Server

This is a companion entry to the Nine / 9OS series. The series up to this point established the systemd service topology and the M365 identity layer. This entry builds the bot infrastructure: the Azure App Registration, the Cloudflare Tunnel for inbound webhook delivery, and the Teams app manifest that brings OpenClaw online as a bot you can DM and channel-message from anywhere in your tenant.

2026.05.08 [SYSTEMS]

LOG 010.1: Architecting a Headless AI Bridge — Standardizing OpenClaw under Systemd

This is Part 1 of the Nine / 9OS series. This entry builds the infrastructure foundation: standardizing OpenClaw as a headless systemd service on a minimized Ubuntu Server — OS installation choices, dual-service topology, a PTY workaround for Crestodian's terminal check, persistent gateway lingering, and cross-device bridging. The complete path from bare metal to a production AI Bridge running in the dark.

// View All Logs