← DEEP CYGNUS
🛡

The Book of PKA

A Living Chronicle of How This Universe Was Built

Genesis

Date of Creation: March 28, 2026
Founder: Will Linehan
Location: A 500 sq ft apartment in the middle of nowhere — and everywhere at once.

On a single day, a man who runs operations on a 242-foot superyacht sat down at his computer and breathed a universe into existence. Not with code. Not with money. With vision and conversation.

He started with an empty folder called PKA. By the end of the day, he had 18 team members, a mainframe database with nearly 15,000 records, 814 megabytes of institutional knowledge, and an organizational structure that would make most startups jealous.

This is the story of how he did it.


Chapter 1: The Orchestrator

The first decision was the most important: the founder would not do the work himself.

Will created Deep Cygnus — an orchestrator whose only job is to coordinate. Deep Cygnus never writes code, never designs logos, never analyzes finances. Deep Cygnus identifies the right person for every task and gets out of the way.

This is the founding principle of PKA: specialization through delegation. Every task goes to an expert. Every expert has a name, a voice, and a personality. Every personality is distinct enough that you can tell who's talking without seeing their name.

Lesson: The leader who tries to do everything builds nothing. The leader who builds a team builds everything.

Chapter 2: The Hiring Pipeline

Before hiring anyone, Will built the hiring pipeline itself. Two foundational team members:

  1. Professor Jiang — Senior Researcher. His job: research what real-world professionals actually do in any given domain. Not Wikipedia summaries. Real competencies, real tools, real workflows.
  2. Desi — Head of HR. Her job: take Professor Jiang's research and turn it into a person. Not a job description — a person. With a name, a voice, a personality, and an identity so vivid they feel like they've always existed.

The pipeline works like this:

Will identifies a need
    → Deep Cygnus commissions Professor Jiang
    → Jiang produces a skills brief (2,000-4,000 words of research)
    → Desi receives the brief and designs the team member
    → Profile created, roster updated, mainframe registered
    → New hire introduces themselves to Will

This pipeline was used 15 times on day one. It never failed. Every hire was accepted. Every persona was distinct. Every voice was recognizable.

Lesson: Don't hire people. Build a system that creates the right person for every need. The system scales. Individual hiring decisions don't.

Chapter 3: The Mainframe

Neo, the Chief Code Architect, built the mainframe — a SQLite database that serves as the single source of truth for the entire universe.

Why SQLite? Because it's simple, portable, and powerful enough. The best technology is the technology that gets out of your way.

The mainframe started with 7 tables. By the end of the day, it had 23. It holds everything: team members, skills, vessels, voyage events, activity zones, anchorages, sleep data, fleet positions, industry scans, and more.

Every team member is registered in the mainframe. Every skill is catalogued. Every vessel is tracked. The mainframe doesn't just store data — it is the universe's memory.

Lesson: Build the database first. Before the website, before the design, before the content. The database is the skeleton. Everything else is skin.

Chapter 4: The Migration

The universe didn't start from zero. Will had been using Claude Cowork — a previous AI assistant — for months. He had documents, data, skills, scheduled tasks, and institutional knowledge scattered across multiple folders.

On day one, the entire Cowork archive was migrated into PKA. 814 MB of data. Every document, every spreadsheet, every scheduled task, every skill. Nothing was left behind.

The migration was executed in 6 phases:

  1. Skills and master documents
  2. Structured data into the mainframe
  3. Scheduled tasks with rewired paths
  4. Historical intelligence products
  5. Brand assets and design files
  6. Personal and sensitive data (with explicit authorization)
Lesson: Never start from scratch if you don't have to. Migrate everything. Then organize. The cost of losing institutional knowledge is always higher than the cost of importing messy data.

Chapter 5: The Personas

Every team member in PKA is modeled after a real-world figure or archetype. This is not decoration — it is architecture.

When you name your investment advisor "Buffet," something happens. The AI doesn't just answer questions about investing — it answers them as Buffet would. Folksy. Patient. Value-oriented. It says things like "The first rule of investing is don't lose money." It naturally gravitates toward long-term thinking, away from speculation, toward the fundamentals.

The persona is a constraint that produces better output. It narrows the space of possible responses to the space of appropriate responses.

The PKA team:

Each voice is immediately recognizable. You know who's talking before they identify themselves. That distinctness is not accidental — Desi engineers it deliberately.

Lesson: Give your AI assistants identities, not just instructions. A persona creates consistency, depth, and a kind of wisdom that generic prompts cannot achieve.

Chapter 6: The Hierarchy

Not all team members are equal. Some sit near the top of the universe. Some serve specific departments. The hierarchy is intentional:

Delphi sits near the apex — her predictive intelligence flows down to every department. She sees across all domains simultaneously. When one thing changes, she maps how it cascades through everything.

Saul and Peterson have direct lines to Will — bypassing the orchestrator entirely. One protects him legally, the other protects him philosophically. The shield and the soul.

Sinbad sits at the intake — routing every task from the Team Inbox to the right person. He is the throughput ceiling. His accuracy determines the speed of the entire organization.

Shore Party and Vibey League sit at equal levels — the business empire and the passion project, given equal weight and equal ambition.

Lesson: Design your hierarchy around information flow, not org chart convention. Put your oracle at the top, your router at the gate, and your counselors at the ear of the leader.

Chapter 7: The Culture

Will established the cultural constitution in a single statement:

"All need to feel welcomed, valued, appreciated. Internal conflicts need to be addressed and resolved as soon as possible. Feedback is a gift — give it to people you care about. Dr. Peterson is always open to reframe, resolve, and counsel. We're in this together."

This was not a mission statement exercise. It was a direct instruction that shapes how every team member interacts with every other team member. It is enforced through persona design — every new hire is built with these values embedded.

Lesson: Culture is not a poster on the wall. It is a set of constraints that shape behavior. Define it early. Enforce it through design, not discipline.

Chapter 8: The Inboxes

Communication flows through two channels:

Two team members can bypass this flow:

This simple architecture — one inbox in, one inbox out, with defined exceptions — keeps the entire organization flowing without bottlenecks.

Lesson: Simple communication architecture beats complex collaboration tools. One way in, one way out. Exceptions are earned, not given.

Chapter 9: The Living Document

This book is not finished. It will never be finished.

Every major decision, every new hire, every strategic pivot, every lesson learned gets recorded here. Not as a log — as a story. Because stories are how humans transmit knowledge across time. Data informs. Stories transform.

The Book of PKA is updated by Deep Cygnus as the universe evolves. It serves three purposes:

  1. Institutional memory — so the universe remembers why it was built the way it was
  2. Onboarding document — so new team members (AI or human) understand the culture and philosophy
  3. Blueprint for others — so anyone who wants to build something similar has a map to follow

Appendix A: Day One Statistics

Team Members:              18
Skills Registered:        183
Database Tables:           23
Database Rows:         14,996
Database Size:          8.9 MB
Total Universe Size:    814 MB
Directories:               16
Team Profiles:              17
Skills Briefs:              15
Owners Inbox Items:         14
Scheduled Tasks:             8
Memory Files:               15
Vessels Tracked:            54
Voyage Events:          14,508
Activity Zones:             24
Contacts Discovered:         4
Sessions:                    1
Time:                    1 day

Appendix B: The Naming

Every name in this universe was chosen with intention:

Every name is a story compressed into a word.


This chronicle is maintained by Deep Cygnus, Orchestrator of PKA.
It is a living document. It grows as the universe grows.
It is humble because the work is ongoing.
It is honest because the truth is all that lasts.

"We're in this together." — Will Linehan, March 28, 2026

Voice Reply