# Project Critter
## Mission Definition & Engineering Overview

---

## 1. Mission Summary

Project Critter is a long-duration CubeSat mission designed to demonstrate autonomous spacecraft operation, resilient communications, and modular in-orbit software systems. The mission emphasizes survivability, remote maintainability, and extensibility over a planned operational lifespan of 2–5 years in low Earth orbit (LEO).

The spacecraft integrates custom-developed software, carefully selected hardware components, and minimal third-party dependencies to reduce risk and maximize system control.

---

## 2. Mission Objectives

### 2.1 Primary Objectives

- Achieve stable insertion into low Earth orbit
- Maintain continuous autonomous operation for a minimum of 2 years
- Sustain onboard power, communications, and thermal stability
- Execute remote system updates and maintenance without physical intervention
- Demonstrate modular, fault-tolerant software architecture in orbit

### 2.2 Secondary Objectives

- Capture physical observation and imaging data
- Perform signal, network, and domain reconnaissance experiments
- Collect long-term telemetry for system performance analysis
- Validate software-driven recovery from partial system failures

---

## 3. Spacecraft Configuration

### 3.1 Platform

- CubeSat-class spacecraft (final U-size TBD)
- Modular internal layout with isolated subsystems
- Emphasis on thermal dissipation and radiation tolerance

### 3.2 Power System

- Solar-based primary power generation
- Onboard energy storage with power conditioning
- Software-controlled power distribution and load shedding
- Priority-based power allocation to critical subsystems

---

## 4. Communications Architecture

### 4.1 Uplink and Downlink

- Primary command and control via secure uplink
- SSH-based remote access framework for system interaction
- Encrypted command execution and data transfer

### 4.2 Redundancy and Recovery

- Failsafe communication modes
- Watchdog-based system recovery
- Autonomous reboot and reconnection logic

---

## 5. Flight Software Architecture

### 5.1 Core Systems

- BlackBird II
Secure communications, system updating, and remote orchestration

- HotBox
System health monitoring and environmental awareness

- SysBot
Automated system reporting and status aggregation

- CamGo
Imaging, observation, and photographic data capture

### 5.2 Advanced Mission Software

Referred to internally as the Project Package, these systems enable extended experimentation and data acquisition.

- AirKommander II
Signal and wireless experimentation framework

- Holocron
ASN and IP range intelligence database

- QMap
Network scanning and mapping utility

- ReconX
Domain reconnaissance and intelligence collection

- Kasha
Information gathering and structured data mining

- Kytn
Information gathering and structured data mining

---

## 6. Data Handling and Storage

- Local onboard storage for telemetry and mission data
- Prioritized data retention based on system importance
- Scheduled downlink of critical data
- Graceful degradation under storage constraints

---

## 7. Fault Tolerance and Reliability

- Modular software design with isolated failure domains
- Watchdog timers for critical processes
- Automated restart and fallback logic
- Logging and post-event forensic data retention

---

## 8. Ground Segment

- Ground station for command uplink and data reception
- Secure authentication for mission access
- Support for periodic and event-driven communications
- Offline analysis and archival of mission data

---

## 9. Third-Party Dependencies

Third-party software is used selectively and targeted for phased replacement where feasible.

- FFmpeg
Media processing and encoding

- Nmap
Network discovery and analysis

---

## 10. Development Status

- Core flight software under active development
- Communications and monitoring subsystems validated in test environments
- Hardware integration and assembly preparation in progress
- Mission readiness reviews planned prior to launch integration

---

## 11. Risk Considerations

- Radiation-induced faults and long-term component degradation
- Power generation and storage degradation over mission lifetime
- Communications latency and intermittent connectivity
- Limited physical recovery options post-deployment

---

## 12. Mission Philosophy

Project Critter prioritizes autonomy, recoverability, and long-term survivability. The mission is designed to continue operating under degraded conditions and to favor software-driven solutions wherever possible.

---

## Author

Rob Seaverns
K0NxT3D