SoMaCo SoMaCoSF

The Software Factory Playbook — Dex Horthy's 4-gate workflow as a skill

A Claude Code Agent Skill built from Dex Horthy's (HumanLayer) playbook on David Ondrej's podcast.

"Once the model has written thousands of lines of code, it is harder to change. The sessions that generate design docs are context-light — you get the most model intelligence when you do the hard thinking early."

By default, agents build horizontally: all the backend, then all the frontend, then a 2,000-line diff lands in your lap and reviewing it is your problem. This skill flips that. Every decision that matters gets made before the code exists — where changing your mind costs a sentence, not a rewrite.

What it does

UUIDv8 Poincaré Icosapheric Browser — Build Brief

Owner: SoMaCoSF
Status: In build
Base repo: https://github.com/SoMaCoSF/poincake
Goal: Turn Poincake into a hyperbolic knowledge browser where every entity is a self-describing GYST UUIDv8, and navigation follows icosahedral/dither3d glyph logic.

1. What exists now

SoMaCo Part 2 — 11 Polymarket market drafts w/ full resolution criteria, Cu/Al trade thesis, IBEW labor signal, board interlocks, platform API

SoMaCo — Follow-Up: The Full Trade, The Full Stack

Part 2 of 2 | First gist: https://gist.github.com/SoMaCoSF/6af0a31f9197d2b148f20b1a2baff1c0 Published: 2026-04-28 | Platform: somacosf.com

What Part 1 Established

SoMaCo AI Datacenter Supply Chain Intelligence — C-Suite network, 95B capex flows, GYST UUID registry, Polymarket gap analysis, Mermaid diagrams

SoMaCo Platform — AI Datacenter Supply Chain Intelligence

Published: 2026-04-28 | Platform: somacosf.com | Stack: Next.js 15 + Turso + Python harvesters

Thesis: $295B in Filed CapEx. Zero Polymarket Coverage.

Six hyperscaler CEOs have publicly committed $295 billion to AI datacenter infrastructure in FY2025. That capital flows through a documented supply chain — copper miners, aluminum producers, cable tray manufacturers, liquid cooling companies.

How to Build a Domain Intelligence Corpus

A practical guide for researchers, traders, and builders Methodology extracted from production intelligence systems — applies to any domain with public data and market gaps

What Is a Domain Intelligence Corpus?

A corpus is a structured, machine-readable knowledge base built around a single thesis. It combines:

SOMACOSF SYSTEM STATE — 2026-04-28

OMEN-01 | somacosf.com | Phlux | Session snapshot

┌─────────────────────────────────────────────────────────────────────────────┐
│  SOMACOSF MISSION CONTROL // OMEN-01 // 2026-04-28                         │
│  "IDENTITY IS INFRASTRUCTURE"                                               │
│                                                                             │

SoMaCo — AI Datacenter Commodity Intelligence

Supply Chain Divergence · Market Creation · GYST UUID v8 Protocol

THESIS: The AI datacenter build-out is the largest coordinated commodity procurement event since the interstate highway system. Aluminum, copper, and galvanized steel embedded in physical infrastructure are not priced into LME/SHFE/CME futures. Polymarket has zero coverage of this supply chain. First-mover market creation position available across 11 distinct commodity-prediction-market pairs.

GYST UUID v8 — Full State Audit

Date: 2026-04-28 | Repo: somacosf-platform | Author: Claude Sonnet 4.6 (self-audit, challenged by SoMaCoSF)

The Challenge

"our UUIDs encode signal and all the other json meta data — I think youre breaking protocol - if not prove it"

This document answers that directly with evidence from the live code.

	# SoMaCoSF Platform — Session Build Log
	somacosf.com \| 2026-05-06 → 2026-05-07

	---

	## What Was Built

	### 1. Polymarket CLOB + Kalshi Execution Bridge (`62c1535`)
	- `app/api/poly/execute` — CLOB order submission via Polymarket API
	- `app/api/kalshi/execute` — Kalshi market order bridge

	#!/usr/bin/env python3
	"""
	SoMaCo Corpus Builder — build_corpus.py
	Slurps all SoMaCoSF gists + repos via gh CLI into Ghost Catalog–formatted CSV.

	Ghost Catalog fields (SOM-DOC convention):
	file_id, type, entity_id, description, category, visibility,
	language, created_at, updated_at, url, files_or_stars,
	is_fork, stack, status, tags