Skip to content

Pagan Private Structure Guide

A domain-driven documentation system for confidential business operations at Pagan Interactive LLC—optimized for both human navigation and AI ingestion.

This repo is for owner-eyes-only documentation. The org wiki (knowledge-base) is for employees and operational SOPs. This repo holds strategy, financials, legal, and sensitive business information.

Core Principle

The file path encodes context.

content/{DOMAIN}/{SYSTEM}/{TYPE}/{FILE}

When your Go service (or any AI) reads 40_vendors/distributors/pokemon-center.md, it immediately knows:

  • Domain: Vendors
  • System: Distributors
  • Topic: Pokemon Center relationship

No frontmatter required for basic context. The path does the work.

Domain Overview

Range Purpose Domains
00–01 Meta PKM system, internal tech architecture
10 Strategy Business plans, competitive intel, expansion
20 Finance Accounting, taxes, banking, projections
30 Legal Entity docs, contracts, IP, compliance
40 Vendors Supplier relationships, negotiations
50 People HR, hiring, compensation
60 Operations Private ops (pricing, sourcing strategies)
90 Historical Immutable records

Numbers leave gaps intentionally—you can insert new domains without renumbering.

The Domains

00_meta/

What this knowledge base is and how to use it.

00_meta/
├── templates/      # Document templates
└── workflows/      # How to use this system

Use for: Document templates, tagging conventions, review processes.

01_architecture/

Internal technical systems and infrastructure.

01_architecture/
├── systems/        # Internal tools, POS architecture, integrations
├── infrastructure/ # Hosting, domains, internal services
└── security/       # Access policies, credential management approach

Use for: Technical decisions that don't belong in the public org wiki. Architecture Decision Records (ADRs) for internal systems go here or in 90_records/decisions/.

Examples: - systems/pos-integration-design.md - infrastructure/domain-registrations.md - security/access-control-policy.md

10_strategy/

Business strategy—confidential planning.

10_strategy/
├── planning/       # Business plans, roadmaps, OKRs, annual goals
├── competitive/    # Competitor analysis, market intel, SWOT
└── expansion/      # Growth plans, new locations, market entry

Use for: Anything you wouldn't want a competitor to see.

Examples: - planning/2025-annual-plan.md - planning/okrs-q1-2025.md - competitive/local-lgs-analysis.md - expansion/second-location-criteria.md

20_finance/

Business financials—confidential.

20_finance/
├── accounting/
│   └── records/    # Monthly closes, P&L, balance sheets
├── taxes/
│   └── records/    # Filed returns, correspondence with CPA
├── banking/        # Business accounts, credit lines, contacts
└── projections/    # Financial models, forecasts, scenarios

Use for: Anything your accountant or CFO would handle.

Examples: - accounting/chart-of-accounts.md - accounting/records/2024-12-close.md - taxes/records/2024-federal-1120s.md - banking/business-accounts.md - projections/2025-revenue-forecast.md

Legal structure, contracts, and compliance.

30_legal/
├── entity/         # LLC docs, operating agreement, registered agent, EIN
├── contracts/
│   └── records/    # Signed agreements (immutable)
├── ip/             # Trademarks, brand assets, copyrights
└── compliance/     # Business licenses, permits, regulatory filings

Key rule: Signed contracts go in contracts/records/ and are never edited—they're legal artifacts.

Examples: - entity/operating-agreement-summary.md - entity/registered-agent.md - contracts/lease-template.md - contracts/records/2024-storefront-lease.md - ip/trademark-neon-ogre.md - compliance/florida-business-license.md

40_vendors/

Supplier and vendor relationships.

40_vendors/
├── distributors/   # Product suppliers (Pokemon, MTG, etc.)
├── services/       # Service vendors (POS, payment processing, insurance)
└── negotiations/   # Active deal notes, pricing discussions

Use for: Contact info, account numbers, relationship notes, pricing agreements.

Examples: - distributors/pokemon-center.md - distributors/alliance-game-distributors.md - services/square-pos.md - services/business-insurance.md - negotiations/2025-alliance-terms.md

Note: Move completed negotiations to 90_records/ or update the vendor file. negotiations/ is for active discussions.

50_people/

HR and team documentation—confidential.

50_people/
├── hiring/         # Job descriptions, interview guides, candidate notes
├── compensation/   # Pay structures, benefits, bonus plans
└── records/        # Offer letters, signed agreements, terminations

Use for: Anything HR-sensitive that employees shouldn't see.

Examples: - hiring/retail-associate-jd.md - hiring/interview-questions.md - compensation/pay-bands.md - compensation/benefits-summary.md - records/2024-01-john-doe-offer.md

Privacy note: Be thoughtful about what you document. Candidate notes should be factual and job-relevant.

60_operations/

Private operational information.

60_operations/
├── inventory/      # Sourcing strategies, pricing models, margin analysis
├── events/         # Tournament economics, prize support calculations
└── real-estate/    # Lease analysis, build-out costs, location scouting

This is for operational details too sensitive for the org wiki—pricing strategy, margin targets, sourcing secrets.

Examples: - inventory/margin-targets.md - inventory/singles-pricing-model.md - inventory/sourcing-strategy.md - events/tournament-prize-support-calc.md - real-estate/lease-comparison.md

90_records/

Immutable historical records.

90_records/
├── decisions/      # Business ADRs (Architecture/Any Decision Records)
├── meetings/       # Board meetings, partner discussions, investor notes
└── milestones/     # Major business events (opening day, funding, etc.)

Key rule: Documents in 90_records/ are never edited after creation. They're historical artifacts.

Decision records follow the pattern: - decisions/001-llc-vs-scorp.md - decisions/002-pos-selection.md - decisions/003-location-choice.md

Examples: - meetings/2024-12-partner-sync.md - milestones/2025-01-grand-opening.md

_drafts/

Work in progress.

Excluded from: - MkDocs navigation - Site builds - AI indexing

Move files to their proper domain when ready.

What Goes Here vs. Org Wiki

Pagan Private Org Wiki (knowledge-base)
Business strategy —
Competitive analysis —
Financial records —
Pricing models —
Vendor negotiations Vendor contact info (non-sensitive)
HR/compensation —
Signed contracts —
— SOPs for employees
— Training materials
— Public policies
— System documentation (non-sensitive)

Rule of thumb: If an employee needs it to do their job, it goes in the org wiki. If it's owner/partner eyes only, it goes here.

File Naming

Use kebab-case: - ✅ 2025-revenue-forecast.md - ❌ 2025 Revenue Forecast.md - ❌ 2025_revenue_forecast.md

Keep names 10–30 characters when practical.

Dates in filenames for records: - ✅ 90_records/meetings/2024-12-15-partner-sync.md - ✅ 20_finance/accounting/records/2024-12-close.md

Frontmatter

Optional but useful for richer AI context:

---
title: "2025 Revenue Forecast"
type: Projection
status: draft
created: 2024-12-01
updated: 2024-12-15
confidentiality: owner-only
---

The path already encodes domain/system, so frontmatter adds metadata the path can't express: dates, status, confidentiality level.

Index Files

Every folder must have an index.md.

This file: - Serves as the landing page for that section - Describes what belongs in this folder - Links to key documents

Minimal example:

---
title: "Distributors"
---

# Distributors

Product supplier relationships and account information.

## Active Distributors

- [Alliance Game Distributors](alliance-game-distributors.md)
- [Pokemon Center](pokemon-center.md)
- [PSA](psa-grading.md)

Quick Reference

I need to document... Put it in...
Internal system design 01_architecture/systems/
Annual business plan 10_strategy/planning/
Competitor research 10_strategy/competitive/
Monthly P&L 20_finance/accounting/records/
Tax return copy 20_finance/taxes/records/
Operating agreement 30_legal/entity/
Signed lease 30_legal/contracts/records/
Trademark info 30_legal/ip/
Distributor contact 40_vendors/distributors/
Pricing negotiation 40_vendors/negotiations/
Pay structure 50_people/compensation/
Offer letter 50_people/records/
Margin targets 60_operations/inventory/
Tournament economics 60_operations/events/
Why we chose this POS 90_records/decisions/
Partner meeting notes 90_records/meetings/
Half-finished draft _drafts/

For AI Ingestion

When your Go service scans this repo:

  1. Walk the file tree — filepath.Walk("content", ...)
  2. Parse the path — Extract domain, system from directory structure
  3. Parse frontmatter — Get metadata (dates, status, confidentiality)
  4. Index content — Store in your graph DB and vector DB

The structure means your AI can answer: - "What's our margin target for singles?" → Scan 60_operations/inventory/ - "Summarize our Alliance relationship" → Scan 40_vendors/distributors/ - "What were the key decisions in 2024?" → Scan 90_records/decisions/

Security note: This repo contains sensitive business data. Ensure your AI system respects access controls and doesn't leak this information to unauthorized queries.

Subsidiaries and Entities

Pagan Interactive LLC is the umbrella. If you have multiple business entities (e.g., Neon Ogre as a DBA or separate LLC), you can:

Option A: Single repo, tag by entity 

---
entity: neon-ogre
---

Option B: Subdomain folders 

10_strategy/
├── pagan/          # Holding company strategy
└── neon-ogre/      # Retail strategy

Start simple (Option A). Split only if the entities diverge significantly.

Getting Started

# Clone or unzip the scaffold
cd pagan-private

# Set up Python environment
uv venv
source .venv/bin/activate
uv pip install mkdocs-material

# Run locally
mkdocs serve

Visit http://127.0.0.1:8000

Start with the most pressing domain—probably 30_legal/entity/ to document your LLC structure, or 10_strategy/planning/ if you're in planning mode.