luis.erlacher/Archon
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Removing references to Archon "Alpha"

Browse Source
This commit is contained in:
Cole Medin 2025-09-06 14:51:02 -05:00
parent 01903e5c63
commit 012d2c58ed
21 changed files with 44 additions and 47 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
.claude/commands/archon/archon-alpha-review.md
View File

@ -1,11 +1,11 @@
---
description: Perform comprehensive code review for Archon V2 Alpha, this command will save a report to `code-review.md`.
description: Perform comprehensive code review for Archon V2 Beta, this command will save a report to `code-review.md`.
argument-hint: <PR number, branch name, file path, or leave empty for staged changes>
allowed-tools: Bash(*), Read, Grep, LS, Write
thinking: auto
---
# Code Review for Archon V2 Alpha
# Code Review for Archon V2 Beta
**Review scope**: $ARGUMENTS
@ -13,7 +13,7 @@ I'll perform a comprehensive code review and generate a report saved to the root
## Context
You're reviewing code for Archon V2 Alpha, which uses:
You're reviewing code for Archon V2 Beta, which uses:
- **Frontend**: React + TypeScript + Vite + TailwindCSS
- **Backend**: Python 3.12+ with FastAPI, PydanticAI, Supabase
@ -32,7 +32,7 @@ Determine what needs reviewing:
## Review Focus
### CRITICAL: Alpha Error Handling Philosophy
### CRITICAL: Beta Error Handling Philosophy
**Following CLAUDE.md principles - We want DETAILED ERRORS, not graceful failures!**
@ -59,7 +59,7 @@ Look for:
- **Type hints** on all functions and proper use of Python 3.12+ features
- **Pydantic v2 patterns** (ConfigDict, model_dump, field_validator)
- **Error handling following alpha principles**:
- **Error handling following beta principles**:
```python
# BAD - Silent failure

6
.claude/commands/archon/archon-onboarding.md
View File

@ -7,7 +7,7 @@ description: |
argument-hint: none
---
You are helping a new developer get up and running with the Archon V2 Alpha project! Your goal is to provide them with a personalized onboarding experience.
You are helping a new developer get up and running with the Archon V2 Beta project! Your goal is to provide them with a personalized onboarding experience.
## What is Archon?
@ -133,7 +133,7 @@ When analyzing the user's chosen area, look for:
After analyzing their chosen area, provide the user with:
1. Key development patterns they should know:
- Alpha mindset (break things to improve them)
- Beta mindset (break things to improve them)
- Error philosophy (fail fast with detailed errors)
- Service boundaries (no cross-service imports)
- Real-time updates via Socket.IO
@ -150,4 +150,4 @@ After analyzing their chosen area, provide the user with:
- Testing requirements
- Local vs Docker differences
Remember to encourage the user to start small and iterate. This is alpha software designed for rapid experimentation.
Remember to encourage the user to start small and iterate. This is beta software designed for rapid experimentation.

4
.claude/commands/archon/archon-prime-simple.md
View File

@ -6,7 +6,7 @@ argument-hint: none
## Prime Context for Archon Development
You need to quickly understand the Archon V2 Alpha codebase. Follow these steps:
You need to quickly understand the Archon V2 Beta codebase. Follow these steps:
### 1. Read Project Documentation
@ -51,4 +51,4 @@ After reading these files, explain to the user:
3. **Key Patterns**: One sentence about key patterns
4. **Tech Stack**: One sentence about tech stack
Remember: This is alpha software focused on rapid iteration. Prioritize understanding the core functionality
Remember: This is beta software focused on rapid iteration. Prioritize understanding the core functionality

4
.claude/commands/archon/archon-prime.md
View File

@ -11,7 +11,7 @@ description: |
argument-hint: <service> <Specific focus>
---
You're about to work on the Archon V2 Alpha codebase. This is a microservices-based knowledge management system with MCP integration. Here's what you need to know:
You're about to work on the Archon V2 Beta codebase. This is a microservices-based knowledge management system with MCP integration. Here's what you need to know:
## Today's Focus area
@ -171,4 +171,4 @@ Follow the guidelines in CLAUDE.md
- Frontend uses Vite proxy for API calls in development
- Python backend uses `uv` for dependency management
Remember: This is alpha software. Prioritize functionality over production patterns. Make it work, make it right, then make it fast.
Remember: This is beta software. Prioritize functionality over production patterns. Make it work, make it right, then make it fast.

8
.claude/commands/archon/archon-rca.md
View File

@ -1,11 +1,11 @@
---
description: Generate Root Cause Analysis report for Archon V2 Alpha issues
description: Generate Root Cause Analysis report for Archon V2 Beta issues
argument-hint: <issue description or error message>
allowed-tools: Bash(*), Read, Grep, LS, Write
thinking: auto
---
# Root Cause Analysis for Archon V2 Alpha
# Root Cause Analysis for Archon V2 Beta
**Issue to investigate**: $ARGUMENTS
@ -13,7 +13,7 @@ investigate this issue systematically and generate an RCA report saved to `RCA.m
## Context About Archon
You're working with Archon V2 Alpha, a microservices-based AI knowledge management system:
You're working with Archon V2 Beta, a microservices-based AI knowledge management system:
- **Frontend**: React + TypeScript on port 3737
- **Main Server**: FastAPI + Socket.IO on port 8181
@ -45,7 +45,7 @@ Check if all services are running properly:
### 3. Error Handling Analysis
**Remember: In Alpha, we want DETAILED ERRORS that help us fix issues fast!**
**Remember: In Beta, we want DETAILED ERRORS that help us fix issues fast!**
Look for these error patterns:

2
.github/workflows/ci.yml vendored
View File

@ -254,7 +254,7 @@ jobs:
- name: Create test summary
run: |
echo "# 🧪 Archon V2 Alpha - CI Test Results" >> $GITHUB_STEP_SUMMARY
echo "# 🧪 Archon V2 Beta - CI Test Results" >> $GITHUB_STEP_SUMMARY
echo "" >> $GITHUB_STEP_SUMMARY
# Frontend Results

4
.github/workflows/claude-fix.yml vendored
View File

@ -47,7 +47,7 @@ jobs:
You are authorized to IMPLEMENT FIXES and CREATE PULL REQUESTS.
## Your Role
You are fixing issues in Archon V2 Alpha. Follow CLAUDE.md for project principles and commands.
You are fixing issues in Archon V2 Beta. Follow CLAUDE.md for project principles and commands.
## Architecture Context
- Frontend: React + TypeScript + Vite (port 3737)
@ -110,7 +110,7 @@ jobs:
- Follow CLAUDE.md for all commands and project principles
- Prefer ripgrep over grep for searching
- Keep changes minimal - resist urge to refactor
- Alpha project: Quick fixes over perfect solutions
- Beta project: Quick fixes over perfect solutions
# Commented out - using default tools
# allowed_tools: "Edit(*),MultiEdit(*),Write(*),Read(*),Grep(*),LS(*),Glob(*),TodoWrite(*),NotebookEdit(*),Bash(git *),Bash(npm *),Bash(uv *),Bash(python *),Bash(pip *),Bash(cd *),Bash(pwd),Bash(ls *),Bash(cat *),Bash(head *),Bash(tail *),Bash(wc *),Bash(find *),Bash(grep *),Bash(rg *),Bash(sed *),Bash(awk *),Bash(curl *),Bash(wget *),Bash(echo *),Bash(mkdir *),Bash(rm -rf node_modules),Bash(rm -rf __pycache__),Bash(rm -rf .pytest_cache),WebSearch(*),WebFetch(*)"

10
.github/workflows/claude-review.yml vendored
View File

@ -47,7 +47,7 @@ jobs:
You are performing a CODE REVIEW ONLY. You cannot make any changes to files.
## Your Role
You are reviewing code for Archon V2 Alpha, a local-first AI knowledge management system in early alpha stage.
You are reviewing code for Archon V2 Beta, a local-first AI knowledge management system in early beta stage.
## Architecture Context
- Frontend: React + TypeScript + Vite (port 3737)
@ -93,7 +93,7 @@ jobs:
- Frontend: Vitest tests for components
- Backend: Pytest tests for services
### 5. Alpha Project Principles (from CLAUDE.md)
### 5. Beta Project Principles (from CLAUDE.md)
- No backwards compatibility needed - can break things
- Fail fast with detailed errors (not graceful failures)
- Remove dead code immediately
@ -129,7 +129,7 @@ jobs:
[Brief description and why it would help]
## Security Assessment
Note: This is an early alpha project without authentication. Security focus should be on:
Note: This is an early beta project without authentication. Security focus should be on:
- Input validation to prevent crashes
- SQL injection prevention
- No hardcoded secrets or API keys
@ -177,10 +177,10 @@ jobs:
3. ...
**Rationale:**
[Brief explanation rationale for above recommendations, considering this is an alpha project focused on rapid iteration]
[Brief explanation rationale for above recommendations, considering this is an beta project focused on rapid iteration]
---
*Review based on Archon V2 Alpha guidelines and CLAUDE.md principles*
*Review based on Archon V2 Beta guidelines and CLAUDE.md principles*
# Commented out - using default tools
# allowed_tools: "Read(*),Grep(*),LS(*),Glob(*),Bash(npm test*),Bash(npm run test*),Bash(npm run lint*),Bash(npm run type*),Bash(npm run check*),Bash(uv run pytest*),Bash(uv run ruff*),Bash(uv run mypy*),Bash(git log*),Bash(git diff*),Bash(git status*),Bash(git show*),Bash(cat *),Bash(head *),Bash(tail *),Bash(wc *),Bash(find * -type f),WebSearch(*),TodoWrite(*)"

8
AGENTS.md
View File

@ -1,6 +1,6 @@
# AGENTS.md
## Alpha Development Guidelines
## Beta Development Guidelines
**Local-only deployment** - each user runs their own instance.
@ -8,11 +8,11 @@
- **No backwards compatibility** - remove deprecated code immediately
- **Detailed errors over graceful failures** - we want to identify and fix issues fast
- **Break things to improve them** - alpha is for rapid iteration
- **Break things to improve them** - beta is for rapid iteration
### Error Handling
**Core Principle**: In alpha, we need to intelligently decide when to fail hard and fast to quickly address issues, and when to allow processes to complete in critical services despite failures. Read below carefully and make intelligent decisions on a case-by-case basis.
**Core Principle**: In beta, we need to intelligently decide when to fail hard and fast to quickly address issues, and when to allow processes to complete in critical services despite failures. Read below carefully and make intelligent decisions on a case-by-case basis.
#### When to Fail Fast and Loud (Let it Crash!)
@ -102,7 +102,7 @@ def process_batch(items):
## Architecture Overview
Archon V2 Alpha is a microservices-based knowledge management system with MCP (Model Context Protocol) integration:
Archon V2 Beta is a microservices-based knowledge management system with MCP (Model Context Protocol) integration:
- **Frontend (port 3737)**: React + TypeScript + Vite + TailwindCSS
- **UI Strategy**: Radix UI primitives in `/features`, custom components in legacy `/components`

9
CLAUDE.md
View File

@ -2,7 +2,7 @@
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
## Alpha Development Guidelines
## Beta Development Guidelines
**Local-only deployment** - each user runs their own instance.
@ -10,11 +10,11 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
- **No backwards compatibility** - remove deprecated code immediately
- **Detailed errors over graceful failures** - we want to identify and fix issues fast
- **Break things to improve them** - alpha is for rapid iteration
- **Break things to improve them** - beta is for rapid iteration
### Error Handling
**Core Principle**: In alpha, we need to intelligently decide when to fail hard and fast to quickly address issues, and when to allow processes to complete in critical services despite failures. Read below carefully and make intelligent decisions on a case-by-case basis.
**Core Principle**: In beta, we need to intelligently decide when to fail hard and fast to quickly address issues, and when to allow processes to complete in critical services despite failures. Read below carefully and make intelligent decisions on a case-by-case basis.
#### When to Fail Fast and Loud (Let it Crash!)
@ -101,6 +101,7 @@ def process_batch(items):
- Prioritize functionality over production-ready patterns
- Focus on user experience and feature completeness
- When updating code, don't reference what is changing (avoid keywords like LEGACY, CHANGED, REMOVED), instead focus on comments that document just the functionality of the code
- When commenting on code in the codebase, only comment on the functionality and reasoning behind the code. Refrain from speaking to Archon being in "beta" or referencing anything else that comes from these global rules.
## Development Commands
@ -174,7 +175,7 @@ make test-be # Backend tests only
## Architecture Overview
Archon V2 Alpha is a microservices-based knowledge management system with MCP (Model Context Protocol) integration:
Archon Beta is a microservices-based knowledge management system with MCP (Model Context Protocol) integration:
### Service Architecture

4
archon-ui-main/.eslintrc.cjs
View File

@ -25,14 +25,14 @@ module.exports = {
plugins: ['react-refresh'],
rules: {
/**
* LINTING STRATEGY FOR ALPHA DEVELOPMENT:
* LINTING STRATEGY FOR BETA DEVELOPMENT:
*
* Development: Warnings don't block local development, allowing rapid iteration
* CI/PR: Run with --max-warnings 0 to treat warnings as errors before merge
*
* Philosophy:
* - Strict typing where it helps AI assistants (Claude Code, Copilot, etc.)
* - Pragmatic flexibility for alpha-stage rapid development
* - Pragmatic flexibility for beta-stage rapid development
* - Console.log allowed locally but caught in CI
* - Progressive enhancement: stricter rules in /features (new code) vs /components (legacy)
*/

1
archon-ui-main/src/components/onboarding/ProviderStep.tsx
View File

@ -46,7 +46,6 @@ export const ProviderStep = ({ onSaved, onSkip }: ProviderStepProps) => {
localStorage.setItem("onboardingDismissed", "true");
onSaved();
} catch (error) {
// Log error for debugging per alpha principles
const errorMessage =
error instanceof Error ? error.message : "Unknown error";
console.error("Failed to save API key:", error);

2
archon-ui-main/src/features/projects/tasks/utils/task-ordering.ts
View File

@ -1,7 +1,5 @@
/**
* Task ordering utilities that ensure integer precision
*
* Following alpha principles: detailed errors and no silent failures
*/
import type { Task } from "../types";

2
archon-ui-main/src/features/ui/components/FeatureErrorBoundary.tsx
View File

@ -82,7 +82,7 @@ export class FeatureErrorBoundary extends Component<Props, State> {
An error occurred in this feature. The error has been logged for investigation.
</p>
{/* Show detailed error in alpha/development (following CLAUDE.md principles) */}
{/* Show detailed error in development */}
{isDevelopment && error && (
<div
className={cn(

3
archon-ui-main/src/pages/SettingsPage.tsx
View File

@ -204,8 +204,7 @@ export const SettingsPage = () => {
>
<div className="space-y-4">
<p className="text-sm text-gray-600 dark:text-gray-400">
Found a bug or issue? Report it to help improve Archon V2
Alpha.
Found a bug or issue? Report it to help improve Archon Beta.
</p>
<div className="flex justify-start">
<BugReportButton variant="secondary" size="md">

2
archon-ui-main/src/services/bugReportService.ts
View File

@ -1,5 +1,5 @@
/**
* Bug Report Service for Archon V2 Alpha
* Bug Report Service for Archon Beta
*
* Handles automatic context collection and GitHub issue creation for bug reports.
*/

4
python/src/server/api_routes/bug_report_api.py
View File

@ -1,5 +1,5 @@
"""
Bug Report API for Archon V2 Alpha
Bug Report API for Archon Beta
Handles bug report submission to GitHub Issues with automatic context formatting.
"""
@ -131,7 +131,7 @@ class GitHubService:
return f"""## {severity_emoji} Bug Report
**Reported by:** User (Archon V2 Alpha)
**Reported by:** User (Archon Beta)
**Severity:** {severity_emoji} {bug_report.severity.title()}
**Component:** {component_emoji} {bug_report.component.replace("-", " ").title()}
**Version:** {bug_report.context.app.get("version", "unknown")}

2
python/src/server/services/crawling/strategies/batch.py
View File

@ -72,7 +72,7 @@ class BatchCrawlStrategy:
memory_threshold = float(settings.get("MEMORY_THRESHOLD_PERCENT", "80"))
check_interval = float(settings.get("DISPATCHER_CHECK_INTERVAL", "0.5"))
except (ValueError, KeyError, TypeError) as e:
# Critical configuration errors should fail fast in alpha
# Critical configuration errors should fail fast
logger.error(f"Invalid crawl settings format: {e}", exc_info=True)
raise ValueError(f"Failed to load crawler configuration: {e}") from e
except Exception as e:

2
python/src/server/services/crawling/strategies/recursive.py
View File

@ -77,7 +77,7 @@ class RecursiveCrawlStrategy:
memory_threshold = float(settings.get("MEMORY_THRESHOLD_PERCENT", "80"))
check_interval = float(settings.get("DISPATCHER_CHECK_INTERVAL", "0.5"))
except (ValueError, KeyError, TypeError) as e:
# Critical configuration errors should fail fast in alpha
# Critical configuration errors should fail fast
logger.error(f"Invalid crawl settings format: {e}", exc_info=True)
raise ValueError(f"Failed to load crawler configuration: {e}") from e
except Exception as e:

2
python/src/server/services/embeddings/embedding_exceptions.py
View File

@ -1,7 +1,7 @@
"""
Custom exceptions for embedding service failures.
These exceptions follow the alpha principle: "fail fast and loud" for data integrity issues,
These exceptions follow the principle: "fail fast and loud" for data integrity issues,
while allowing batch processes to continue by skipping failed items.
"""

2
python/tests/test_supabase_validation.py
View File

@ -129,7 +129,7 @@ def test_config_handles_invalid_jwt():
def test_config_fails_on_unknown_role():
"""Test that configuration loading fails fast for unknown roles per alpha principles."""
"""Test that configuration loading fails fast for unknown roles."""
# Create a mock key with unknown role
unknown_payload = {"role": "custom_role", "iss": "supabase"}
mock_unknown_key = jwt.encode(unknown_payload, "secret", algorithm="HS256")