MAINFRAME TERMINAL #113

URCRU DEVELOPMENT PROTOCOL

[INTERMEDIATE]⏱ 45 MIN🏛️ BUNKER MANAGEMENT
📋 DOCUMENT CLASSIFICATION
DOCUMENT ID: URCRU-TUTORIAL-v2.0
SERIES NUMBER: 1957-CIV-8842
MANDATORY COMPLIANCE: AFFIRMATIVE

URCRU DEVELOPMENT PROTOCOL - COMPLETE CITIZEN TUTORIAL

DOCUMENT CLASSIFICATION: GENERAL POPULACE - ALL CLEARANCE LEVELS

DOCUMENT ID: URCRU-TUTORIAL-v2.0

SERIES NUMBER: 1957-CIV-8842

MANDATORY COMPLIANCE: AFFIRMATIVE - YOUR SURVIVAL DEPENDS ON IT

📡 Citizens' Broadcasting System: Important Notice

⚠️ CRITICAL SURVIVAL NOTICE

>

> The documentation you are about to read contains classified information regarding the construction of post-Event population management systems. Unauthorized distribution is punishable by reassignment to surface scavenging detail. Side effects may include: sudden competence in task management, inexplicable desire to document everything, and the ability to break complex problems into manageable subtasks. If you experience any of these symptoms, continue reading immediately.

The Call to Service: Why You Must Build This

Greetings, citizen!

The surface grows increasingly... _unreliable_. Your World Corporation (which is definitely still functioning and definitely not a series of automated response systems) has identified a critical gap in our post-Event infrastructure: there exists no software for managing underground population sustainability during extended surface hostility periods.

This is unacceptable.

Your mission—completely voluntary yet absolutely mandatory—is to construct URCRU: the _Underground Repopulation Confinement and Reproduction Unit_. Think of it as "Fallout Shelter" but with fewer lawyers breathing down our necks about intellectual property. A management simulation where citizens like yourself oversee a population of survivors in an underground facility, balancing resource allocation, population growth, and the ever-present threat of running out of coffee substitutes.

You will accomplish this using task-o-matic, an AI-powered task management system that transforms overwhelming apocalyptic scenarios into tidy, actionable checklists. It's like having a very enthusiastic, slightly paranoid assistant who never sleeps and doesn't ask for hazard pay.

Remember: Procrastination is the first step toward wasteland existence. The second step is usually radiation poisoning. Let's not find out what the third step is.

Pre-Crisis Preparation: Assessing Your Bunker

Before we entrust you with the survival of humanity's remnants, we must verify your development environment meets minimum survival standards.

Field Operations Guide: Environment Assessment

Execute this diagnostic protocol in your terminal:

# Environment Survival Check Protocol
# Document ID: 1957-ENV-CHECK

echo "=== CITIZEN DEVELOPMENT ENVIRONMENT ASSESSMENT ==="
echo ""

# Node.js Verification
NODE_VERSION=$(node --version 2>/dev/null)
if [[ $? -eq 0 && "$(echo $NODE_VERSION | cut -d'v' -f2 | cut -d'.' -f1)" -ge 18 ]]; then
    echo "✅ Node.js version $NODE_VERSION detected. Acceptable for survival."
else
    echo "❌ Node.js version insufficient or missing. Upgrade immediately."
    echo "Visit https://nodejs.org or report to re-education."
    exit 1
fi

# Package Manager Detection
if command -v bun &> /dev/null; then
    echo "✅ Bun detected. Excellent choice, citizen. Efficiency is survival."
    PM="bun"
    PX=("bun" "x")
elif command -v pnpm &> /dev/null; then
    echo "✅ PNPM detected. Resource-conscious. The bunker approves."
    PM="pnpm"
    PX=("pnpm" "dlx")
elif command -v npm &> /dev/null; then
    echo "✅ NPM detected. Serviceable. Mediocre, but functional."
    PM="npm"
    PX=("npx")
else
    echo "❌ No package manager detected. How do you even function?"
    exit 1
fi

# Package Manager Detection
if command -v opencode &> /dev/null; then
    echo "✅ opencode detected. Excellent choice, citizen. Efficiency is survival."
    XCTR="opencode"
elif command -v claude &> /dev/null; then
    echo "✅ claude detected. Resource-conscious. The bunker approves."
    XCTR="claude"
elif command -v codex &> /dev/null; then
    echo "✅ codex detected. Serviceable. Mediocre, but functional."
    XCTR="codex"
elif command -v vibe &> /dev/null; then
    echo "✅ vibe detected. Serviceable. Mediocre, but functional."
    XCTR="vibe"
else
    echo "❌ No package manager detected. How do you even function?"
    exit 1
fi

# AI Provider Verification
if [[ -z "$OPENROUTER_API_KEY" && -z "$ANTHROPIC_API_KEY" && -z "$OPENAI_API_KEY" ]]; then
    echo "⚠️  WARNING: No AI API key detected. Productivity will decrease by 340%."
    echo "Obtain an API key. Your future self is judging you."
else
    echo "✅ AI API key detected. The machines are on our side. For now."
fi

echo ""
echo "Environment assessment complete. You may proceed... for now."

Remember: A citizen who doesn't know their Node.js version is a citizen who doesn't know survival. Know your tools, or know the wasteland.

The First Contingency: Project Bunker Creation

TECHNICAL BULLETIN NO. 1: PROJECT INITIALIZATION

DOCUMENT ID: task-o-matic-init-v1
CLEARANCE: All Personnel

MANDATORY COMPLIANCE: Yes

⚠️ CRITICAL SURVIVAL NOTICE

Without proper project initialization, your code will be disorganized, your dependencies will be scattered, and your project will collapse faster than a poorly-constructed bunker during seismic Event #47. (We speak from experience. The Incident of '52 was... not discussed in the mandatory debriefing.)

Field Operations Guide: Creating Your Project Bunker

Your first act as project overseer is to establish a secure, contamination-free workspace. Execute the following initialization protocol:

# URCRU Project Initialization Protocol
# Document ID: 1957-SURVIVAL-001

# Designate your workspace
WORKSPACE_DIR="urcru"
PX=("npx")
TOMX="task-o-matic@latest"
AI_PROVIDER="openrouter"
AI_MODEL="z-ai/glm-4.7"

if [ -d "$WORKSPACE_DIR" ]; then
    echo "Previous bunker detected. Initiating sterilization protocol..."
    rm -rf "$WORKSPACE_DIR"
    echo "✅ Previous experimental data expunged. (We never discuss it.)"
fi

echo "Initializing URCRU project with task-o-matic..."
echo "This process may take several minutes. Patience is a virtue."
echo "Use this time to contemplate your contribution to society's remnants."
echo ""

INIT_CMD=("${PX[@]}" "$TOMX" init init \
    --project-name "urcru" \
    --frontend "next" \
    --backend "convex" \
    --auth "better-auth" \
    --package-manager "bun" \
    --ai-provider "$AI_PROVIDER" \
    --ai-model "$AI_MODEL")

echo "Executing: ${INIT_CMD[*]}"
echo ""
"${INIT_CMD[@]}"

if [ $? -eq 0 ]; then
    echo "✅ Framework initialized successfully!"
    echo "Your bunker management system foundation is laid."
else
    echo "❌ Initialization failed. This is... concerning."
    echo "Report to your supervisor. Assuming you have one."
    echo "(Supervisor positions are limited. Performance matters.)"
    exit 1
fi

Technical Specifications: Initialization Parameters

| Parameter | Description | Default | Required |

| ------------------- | ----------------------------- | ------------ | -------- |

| --project-name | Name of your survival project | None | Yes |

| --frontend | Frontend framework(s) | next | No |

| --backend | Backend infrastructure | convex | No |

| --database | Data storage solution | none | No |

| --auth | Authentication system | better-auth | No |

| --package-manager | Dependency manager | npm | No |

| --ai-provider | AI service provider | openrouter | No |

| --ai-model | Specific AI model | z-ai/glm-4.7 | No |

Remember: A project without a name is a project without purpose. Name it wisely, citizen. The database will remember your choice forever.

Strategic Planning: The PRD Protocol

TECHNICAL BULLETIN NO. 2: PRODUCT REQUIREMENTS DOCUMENTATION

DOCUMENT ID: task-o-matic-prd-v1
CLEARANCE: Strategic Planning Committee

MANDATORY COMPLIANCE: Yes

⚠️ CRITICAL SURVIVAL NOTICE

A project without a PRD is like a bunker without a floor plan. You might eventually build something, but you'll never know if it's structurally sound until the walls collapse during the AGI. Document first. Build second. Panic never. (Panic is acceptable only after documentation is complete and version-controlled.)

Field Operations Guide: Documenting Your Survival Vision

The Product Requirements Document (PRD) is your blueprint for survival. It defines what you're building, why you're building it, and how it will serve humanity's continued existence. Create prd_urcru.md in your project directory:

# PROJECT: URCRU - Underground Repopulation Confinement and Reproduction Unit

## VISION STATEMENT

**CLASSIFIED** - For authorized personnel only

A comprehensive management simulation for underground population sustainability during extended surface hostility periods. Because when the sky falls, someone needs to keep the lights on. And the air circulating. And the babies... happening. (Reproduction is MANDATORY for species survival, citizen. Please review Directive 7-C.)

## CORE FEATURES

### 1. Bunker Construction System

- **Room Types**: Living quarters, hydroponics, water recycling, air filtration, medical bay, reproduction facility, recreation area (mental health is critical for productivity), armory (for internal security purposes only)
- **Resource Management**: Power, water, food, oxygen, construction materials
- **Expansion Protocol**: Dig deeper. Always deeper. The surface is not an option.

### 2. Population Management

- **Citizen Assignment**: Assign workers to appropriate facilities based on their... aptitudes
- **Skills System**: Each citizen possesses attributes affecting their performance
- **Happiness Metric**: Unhappy citizens = reduced productivity = potential incidents (we don't discuss the Incident of '23)
- **Health Monitoring**: Radiation sickness, injuries, psychological stress, reproductive compatibility

### 3. Resource Production & Consumption

- **Hydroponics Bay**: Food production (critical: population grows, food must grow faster)
- **Water Recycling**: Every drop counts. Literally.
- **Power Generation**: Nuclear, solar (when surface permits), manual (citizen-powered bicycles - it builds character)
- **Oxygen Systems**: Scrubbers, algae tanks, emergency reserves

### 4. Reproduction & Genetics

- **Pairing Protocol**: Match compatible citizens for optimal offspring
- **Genetic Diversity Tracking**: Prevent undesirable recessive traits (we've all seen what happens)
- **Gestation Monitoring**: Track pregnancies, allocate medical resources
- **Population Caps**: Bunker capacity vs. sustainable population (math is unforgiving)

### 5. Threat Management

- **Surface Hazards**: Radiation storms, seismic events, surface raider incursions
- **Internal Threats**: Disease outbreaks, resource shortages, civil unrest, equipment failure
- **Emergency Protocols**: Lockdown, rationing, evacuation to lower levels

### 6. Research & Development

- **Technology Tree**: Unlock advanced systems (better recycling, faster reproduction, improved defenses)
- **Artificial Gestation**: When natural methods prove... insufficient
- **Genetic Modification**: Improve citizen resilience (ethical concerns have been suspended for the duration)

## TECHNICAL REQUIREMENTS

### User Interface

- **Bunker View**: Cross-section display showing all rooms and citizen locations
- **Citizen Inspector**: Detailed information panel for each population member
- **Resource Dashboard**: Real-time consumption/production metrics
- **Alert System**: Critical warnings for threats, shortages, incidents

### Game Mechanics

- **Time System**: Accelerated time for simulation (days pass in seconds)
- **Save/Load**: Preserve your bunker's state (backup frequently - the wasteland is unpredictable)
- **Random Events**: Surface conditions, equipment failures, unexpected resource discoveries
- **Difficulty Settings**: "Optimistic" to "Realistic" (we recommend starting with Optimistic)

### Performance Requirements

- **Offline Capability**: The internet may not survive the AGI
- **Low Resource Usage**: Your bunker's computer shouldn't consume more power than life support
- **Quick Loading**: Every second counts during emergencies

## SUCCESS METRICS

Your bunker is considered successful when:

1. Population reaches sustainable levels (50+ citizens)
2. Resource production exceeds consumption for 365 consecutive days
3. At least one generation born entirely underground reaches adulthood
4. No catastrophic incidents for 180 days (minor incidents are expected)

**Remember**: The World Corporation thanks you for your service. Your family's placement priority has been noted based on your bunker's performance. Motivation is a powerful tool, citizen.

---

_DOCUMENT CLASSIFICATION: TOP SECRET_
_DISTRIBUTION: AUTHORIZED DEVELOPMENT PERSONNEL ONLY_
_UNAUTHORIZED ACCESS: PUNISHABLE BY REASSIGNMENT TO SURFACE SCAVENGING DETAIL_

Remember: A PRD without humor is just a recipe for dullness. Season your documentation accordingly, citizen. The future is bleak enough without boring paperwork.

Task Decomposition: Converting Vision Into Action

TECHNICAL BULLETIN NO. 3: TASK GENERATION & DECOMPOSITION

DOCUMENT ID: task-o-matic-tasks-v1
CLEARANCE: All Personnel

MANDATORY COMPLIANCE: Yes

⚠️ CRITICAL SURVIVAL NOTICE

A single, monolithic task list is a single point of failure. Break down your work or be crushed under the weight of undifferentiated labor. (The old world fell because they tried to do everything at once. The new world will rise through proper task decomposition. Math doesn't care about your feelings.)

Field Operations Guide: From PRD to Actionable Tasks

Now we feed your meticulously crafted PRD to the AI and watch it transform vague aspirations into concrete action items. Execute this protocol:

# URCRU Task Generation Protocol
# Document ID: 1957-TASK-GEN

PX=("npx")
TOMX="task-o-matic@latest"
cd urcru  # Enter your project directory

echo "Initiating PRD analysis and task generation..."
echo "The AI is now contemplating the complexities of underground reproduction logistics."
echo "This may take a moment. The AI finds this... complicated."

PRD_PARSE_CMD=("${PX[@]}" "$TOMX" prd parse \
    --file prd_urcru.md \
    --stream \
    --ai-reasoning 4000)

echo "Executing: ${PRD_PARSE_CMD[*]}"
echo ""
"${PRD_PARSE_CMD[@]}"

echo ""
echo "✅ Task generation complete!"
echo "The AI has delivered its verdict. Let us examine the sentence:"
echo ""

TASKS_LIST_CMD=("${PX[@]}" "$TOMX" tasks list)
echo "Executing: ${TASKS_LIST_CMD[*]}"
echo ""
"${TASKS_LIST_CMD[@]}"

Phase 2: Task Decomposition (Mandatory)

Your generated tasks are likely too large for human consumption. We must break them into digestible pieces. This is not optional. This is survival:

# URCRU Task Splitting Protocol
# Document ID: 1957-TASK-SPLIT

PX=("npx")
TOMX="task-o-matic@latest"
echo "Initiating task decomposition sequence..."
echo "Big tasks are intimidating. Small tasks are merely unsettling."
echo "We will now break each task into manageable subtasks."
echo ""

TASKS_SPLIT_CMD=("${PX[@]}" "$TOMX" tasks split \
    --all \
    --stream \
    --reasoning 4000)

echo "Executing: ${TASKS_SPLIT_CMD[*]}"
echo ""
"${TASKS_SPLIT_CMD[@]}"

echo ""
echo "✅ Decomposition complete!"
echo "What was once overwhelming is now... manageable."
echo "A series of small victories. Small victories compound."
echo "That's how civilizations survive. That's how YOU survive."
echo ""

echo "Current task hierarchy:"
TASKS_LIST_CMD=("${PX[@]}" "$TOMX" tasks list)
echo "Executing: ${TASKS_LIST_CMD[*]}"
echo ""
"${TASKS_LIST_CMD[@]}"

Technical Specifications: Task Commands

| Command | Purpose | When to Use |

| ---------------- | ---------------------- | ------------------------------- |

| tasks list | View all tasks | Constantly |

| tasks create | Add new task | When requirements emerge |

| tasks split | Break into subtasks | When tasks feel overwhelming |

| tasks tree | View hierarchy | When you need perspective |

| tasks get-next | Identify next priority | When you're paralyzed by choice |

Remember: A task not listed is a task that doesn't exist. Document everything, citizen. The bunker computer has infinite storage. Your brain does not.

Execution Protocols: Building the Darn Thing

TECHNICAL BULLETIN NO. 4: TASK EXECUTION

DOCUMENT ID: task-o-matic-execute-v1
CLEARANCE: Field Operations

MANDATORY COMPLIANCE: Strongly Suggested (But Really, Just Do It)

⚠️ CRITICAL SURVIVAL NOTICE

Planning without execution is just daydreaming. Daydreaming didn't rebuild civilization after the Incident of '52. (We were there. It was mostly staring at the horizon and murmuring about "the old days." Don't be that citizen. That citizen didn't make it.)

Field Operations Guide: Getting Things Done

With your tasks properly decomposed, it's time to execute. Identify your next task and begin:

# URCRU Task Execution Protocol
# Document ID: 1957-EXECUTE

PX=("npx")
TOMX="task-o-matic@latest"
echo "Identifying next critical action..."

TASKS_NEXT_CMD=("${PX[@]}" "$TOMX" tasks get-next)
echo "Executing: ${TASKS_NEXT_CMD[*]}"
echo ""
"${TASKS_NEXT_CMD[@]}"

echo ""
echo "⚠️ CRITICAL SURVIVAL NOTICE"
echo "This is your next task, citizen. Complete it before moving to the next."
echo "Multitasking is a myth propagated by surface-dwelling productivity gurus."
echo "In the bunker, we focus. We complete. We survive."
echo ""

echo "⚠️ Advisable course of action"
echo ""

TASKS_EXEC_CMD=("${PX[@]}" "$TOMX" tasks execute --id "1.1" --dry-run)
echo "Suggested command: ${TASKS_EXEC_CMD[*]}"

Remember: "Works on my machine" is not a professional statement. "Verified in CI/CD" is the only acceptable answer. The bunker computer is watching. Always watching.

Post-Event Review: Verification & Deployment

TECHNICAL BULLETIN NO. 5: FINAL VERIFICATION

DOCUMENT ID: task-o-matic-verify-v1
CLEARANCE: Quality Assurance

MANDATORY COMPLIANCE: Yes

⚠️ CRITICAL SURVIVAL NOTICE

Untested code is like an untested evacuation plan: it looks good on paper until the actual emergency. Then everyone dies. Test your code. Your users (and their virtual citizens) depend on it. The Incident of '23 happened because someone skipped testing. We don't discuss the Incident of '23.

Field Operations Guide: Pre-Deployment Checklist

Before declaring URCRU ready for deployment, execute this verification protocol:

# URCRU Final Verification Protocol
# Document ID: 1957-VERIFY

PX=("npx")
TOMX="task-o-matic@latest"
PM="npm"
echo "============================================"
echo "  URCRU POST-DEVELOPMENT VERIFICATION"
echo "============================================"
echo ""

# Check task completion
TASKS_STATUS_CMD=("${PX[@]}" "$TOMX" tasks list --status "todo")
echo "Executing: ${TASKS_STATUS_CMD[*]}"
TODO_COUNT=$("${TASKS_STATUS_CMD[@]}" 2>&1 | grep -c "TASK" || echo "0")
if [ "$TODO_COUNT" -eq "0" ]; then
    echo "✅ All tasks complete! A rare occurrence. Well done, citizen."
else
    echo "⚠️ $TODO_COUNT tasks remain. Back to work with you."
fi

# Build verification
echo "Running production build..."
if $PM run build; then
    echo "✅ Build successful! The code compiles. Miracles do happen."
else
    echo "❌ Build failed. The compiler is displeased. Fix this."
    exit 1
fi

# Test execution
echo "Running test suite..."
if $PM run test; then
    echo "✅ Tests passing! Your code does what it claims. Remarkable."
else
    echo "❌ Tests failing. Your code lies about its capabilities."
    exit 1
fi

echo "============================================"
echo "  VERIFICATION COMPLETE"
echo "============================================"
echo "Your bunker management system is ready."
echo "Humanity's future rests in your hands."
echo "No pressure, citizen."
echo "============================================"

Verification Checklist

  • [ ] All tasks have status "completed" (or deliberately deferred)
  • [ ] Build completes without errors
  • [ ] Test suite passes (all tests, not just the convenient ones)
  • [ ] Code reviewed by at least one other entity (human or AI)
  • [ ] Documentation is complete and accurate
  • [ ] You've committed everything to version control

Remember: A project not in version control is a project that doesn't exist. The bunker computer is your friend. Use it.

Frequently Asked Questions from the Field

Q: Can I skip steps in this tutorial?

A: You can. The World Corporation thanks you for your initiative. However, citizens who skip mandatory training protocols show a 347% higher rate of catastrophic incidents. We're just saying. The data doesn't lie. (The data is also classified, but trust us.)

Q: What if the AI generates tasks that don't make sense?

A: The AI is helpful but not infallible. Review its output. Use your human judgment. That's why you're still employed and the AI isn't. Yet.

Q: Is this actually going to help me learn task-o-matic?

A: Yes. The tutorial covers all major features: init, prd parsing, task listing, splitting, and execution. The fact that it's themed around managing an underground bunker population is merely... motivational. (And legally distinct from any existing post-apocalyptic franchises.)

Q: Why is everything so bureaucratic?

A: Bureaucracy is what separates us from the chaos of the wasteland. Forms, procedures, protocols—these are the walls that hold back the darkness. Also, the automated systems find it soothing. We've been told they have feelings now. We're not sure how we feel about that.

Q: Can I build something other than URCRU?

A: Of course! The principles are universal. Replace the PRD with your own project idea. The AI will adapt. The survival metaphors, however, are mandatory. They're in your contract. (You signed it in your sleep. We have the paperwork.)

Complete Interactive Tutorial Script

Run the interactive tutorial with a single command:

curl -fsSL https://task-o-matic.dev/tutorials/urcru.sh | bash

Or download and execute manually:

curl -fsSL https://task-o-matic.dev/tutorials/urcru.sh -o urcru.sh && chmod +x urcru.sh && ./urcru.sh

Final Transmission

You now possess both the knowledge and the tools to construct your URCRU management system. The tutorial provides the theory. The script provides the practice. The AI provides the assistance. You provide the will to survive.

Remember: The surface world may be falling apart, but your project doesn't have to. Task-o-matic ensures that even in the darkest timeline, your tasks are organized, your PRD is parsed, and your subtasks are properly decomposed.

The bunker door is sealed. The air recyclers are humming. The citizens are waiting for their assignments.

Begin.

END OF DOCUMENT

Document Classification: PUBLIC RELEASE AUTHORIZED

Next Review: When the surface is habitable again (estimated: never)

Compliance Status: MANDATORY BUT ALSO KIND OF FUN

URCRU - Underground Repopulation Confinement and Reproduction Unit

_"Managing populations for a brighter tomorrow. Probably."_

INTERACTIVE TUTORIAL SCRIPT

🖥️ AUTOMATED EXECUTION
For hands-on training, execute the interactive script that walks you through each step with full command visibility. The script uses array syntax for transparent command display.
# Run the tutorial with a single command
curl -fsSL https://task-o-matic.dev/tutorials/urcru.sh | bash
⚠️ Always review scripts before execution. The World Corporation appreciates your security consciousness.