# Personas and Archetypes (Derived from /main)

**Status**: First Draft – Derived from existing docs on `main`  
**Source**: README.md + whitepaper.md (branch: main)  
**Date**: 2026-07-08

## Overview

This document extracts the implied users and operating contexts directly from the current documentation on the `main` branch. It serves as the baseline before we expand or refine.

---

## Personas

### Pers-1 (Bob) – Sector Trend Tracker (New to AI)
- Is relatively new to AI and the broader space.
- Wants to stay current with trends in AI (and potentially other sectors) without getting overwhelmed.
- Needs a way to keep up with the high volume of new research, tools, and discussions with minimal ongoing effort.
- Benefits from a system that filters noise and surfaces what actually matters.

### Pers-2 (Alice) – Content Creator
- Runs a YouTube channel and an X account with 25k followers.
- Goal is to grow her audience significantly (targeting 1M followers).
- Needs help doing research across AI and related topics.
- Wants to convert research signals into interesting, timely, and compelling content for her audience.

### Pers-3 (Sam) – Hermes Research Agent
- Is a Hermes agent profile with its own memory and endpoint connection.
- Acts as the dedicated research team member for an AI-first development team.
- Needs to stay current on a defined market segment (AI for the MVP; extensible to other segments later).
- Consumes structured signals from Athena to support ongoing research and decision-making within the team.

---

## Archetypes (Operating Environments)

### Arch-1 (Small Scrappy VPS)
- Small, low-budget, and scrappy VPS environment.
- Used primarily for learning and early prototyping.
- Requires a small-footprint workload that can be memory-constrained so it doesn’t destabilize the host system.

### Arch-2 (Research Consumption Layer)
- Functions as a consumption layer for Athena’s research output.
- Designed to support downstream AI systems (examples: MCP tools, LoRA adapters, or other agent profiles).
- Focuses on making Athena’s signals and summaries easily consumable by other systems rather than direct human use.

---

## Notes & Limitations (from /main)

- The current documentation does **not** describe team or multi-user usage.
- Emphasis is on autonomous operation and signal integrity.
- Polished human-facing interfaces (e.g., daily digest) are not yet built.

---

## Next Steps

This version incorporates the updated personas and archetypes.
