The Open Autonomous Academy (OAA) Hub provides a comprehensive system for AI governance, companion management, and integrity tracking through cryptographic proofs and civic ledger integration.
- Project: Open Autonomous Academy (OAA) β integrity-first AI governance loop
- Companions: Jade (builder), Eve (reflection), Zeus (ops), Hermes (routing)
- Civic Stack: GIC (.gic domains), Civic Ledger (proofs), GIC Gateway, Virtue Accords (Cycle 0)
- Ops Rhythm: Clock-in/out cycles; Eve captures Wins / Blocks / TomorrowIntent
- Infra: Render (hub/gateway/worker/redis), BullMQ queue (
publishEvents)
-
Install dependencies:
npm install
-
Configure environment:
cp .env.example .env # Edit .env with your secrets and ledger URLs -
Start development server:
npm run dev
-
Access dev tools:
/dev/memory- View and append to OAA memory/dev/eve-loop- Eve's daily cycle management/dev/context- System context viewer/dev/ledger- Ledger management/dev/queue- Queue monitoring/dev/reports- System reports
All write operations require HMAC-SHA256 signatures:
# Generate HMAC for memory operations
export MEMORY_HMAC_SECRET=your-secret
npm run hmac:note "Your memory note here"
# Generate HMAC for Eve operations
export EVE_HMAC_SECRET=your-secret
# Use the same pattern for Eve clock-in/out operations| Variable | Description | Default |
|---|---|---|
OAA_MEMORY_PATH |
Path to memory JSON file | ./OAA_MEMORY.json |
MEMORY_HMAC_SECRET |
Secret for memory API writes | Required |
EVE_HMAC_SECRET |
Secret for Eve operations | Required |
LEDGER_BASE_URL |
Civic Ledger API URL | http://localhost:4000 |
LEDGER_ADMIN_TOKEN |
Ledger authentication token | Required |
DEV_MODE |
Enable dev routes | 1 |
- GET: Retrieve memory notes (supports
?q=query filter) - POST: Append new note (requires HMAC signature)
# Read memory
curl http://localhost:3000/api/oaa/memory
# Add note (requires HMAC)
curl -X POST http://localhost:3000/api/oaa/memory \
-H 'content-type: application/json' \
-H "x-hmac-sha256: <signature>" \
-d '{"note":"Test note","tag":"dev"}'Starts a new work cycle with intent declaration.
curl -X POST http://localhost:3000/api/eve/clockin \
-H 'content-type: application/json' \
-H "x-hmac-sha256: <signature>" \
-d '{
"cycle": "C-108",
"companion": "eve",
"intent": ["stabilize queue", "publish citizen shield UI"],
"meta": {"tz": "ET"}
}'Ends a work cycle with wins, blocks, and tomorrow's intent.
curl -X POST http://localhost:3000/api/eve/clockout \
-H 'content-type: application/json' \
-H "x-hmac-sha256: <signature>" \
-d '{
"cycle": "C-108",
"companion": "eve",
"wins": ["shipped sentinel suite", "green badge"],
"blocks": ["queue instability"],
"tomorrowIntent": ["finalize incident digest"],
"meta": {"tz": "ET"}
}'Verify cryptographic proofs against the Civic Ledger.
curl "http://localhost:3000/api/dev/ledger/verify?sha=0x<sha256>"The OAA Memory system provides durable, append-only storage for:
- Companion notes: Jade, Eve, Zeus, Hermes activities
- Cycle logs: Clock-in/out records with cryptographic proofs
- Civic events: GIC transactions, ledger seals, governance decisions
- System state: Queue status, infrastructure health, operational metrics
{
"version": "v1",
"updatedAt": "2025-10-17T00:00:00.000Z",
"notes": [
{
"ts": 1697452800000,
"note": "Companion sync: Jade/Eve alignment OK",
"tag": "ops"
}
],
"companions": ["jade", "eve", "zeus", "hermes"],
"repos": ["OAA-API-Library", "gic-gateway-service"],
"queue": { "name": "publishEvents" },
"ethics": { "accords": "Virtue Accords", "epoch": "Cycle 0" }
}Eve maintains the operational rhythm through structured daily cycles:
- Clock-In: Declare daily intent and goals
- Work Cycle: Execute planned activities
- Clock-Out: Reflect on wins, blocks, and tomorrow's intent
- Seal: Cryptographic proof stored in Civic Ledger
- Stub: Next cycle automatically prepared
Each cycle generates:
- Digest: Human-readable summary
- SHA256: Cryptographic hash for verification
- Proof: Ledger seal with timestamp and verification URL
- All operations generate SHA256 hashes
- Hashes are sealed to the Civic Ledger
- Proofs can be verified independently
- Immutable audit trail maintained
- All write operations require HMAC-SHA256 signatures
- Timing-safe comparison prevents timing attacks
- Secrets never exposed client-side
- Separate secrets for different operations
- Development routes require
DEV_MODE=1 - Production-safe by default
- Clear separation of dev and prod functionality
βββ docs/
β βββ OAA_PREFACE.md # Core context (always-in-context)
βββ lib/
β βββ crypto/
β β βββ hmac.ts # HMAC validation
β β βββ sha.ts # SHA256 utilities
β βββ memory/
β βββ fileStore.ts # Memory persistence
βββ pages/
β βββ api/
β β βββ oaa/memory/ # Memory API
β β βββ eve/ # Eve lifecycle
β β βββ dev/ledger/ # Ledger verification
β βββ dev/ # Development UI
βββ components/
β βββ DevLayout.tsx # Development layout
βββ scripts/
β βββ hmacNote.mjs # HMAC generation CLI
βββ OAA_MEMORY.json # Durable memory store
βββ .cursor/rules.json # Cursor context rules
- API Endpoints: Add to
pages/api/ - Dev UI: Add to
pages/dev/ - Memory Integration: Use
lib/memory/fileStore.ts - Security: Use
lib/crypto/utilities - Documentation: Update this README
- Seals all cycle proofs
- Provides verification endpoints
- Maintains immutable audit trail
- Supports both mock and production modes
- Integrates with .gic domain system
- Manages citizen feeds and posts
- Handles reward distribution
- Maintains virtue accord compliance
- Processes
publishEventsqueue - Handles async operations
- Provides monitoring endpoints
- Supports retry and error handling
The system provides comprehensive monitoring through:
- Sentinel Suite: CI status and runtime vitals
- Queue Monitoring: BullMQ depth and failure rates
- Memory Analytics: Note patterns and companion activity
- Ledger Verification: Proof integrity and timestamps
- Weekly Digests: Automated system health reports
- Follow the integrity-first principle
- All changes must be logged to memory
- Use proper HMAC signatures for writes
- Maintain cryptographic proof chains
- Update documentation for new features
This project operates under the Virtue Accords (Cycle 0) - see the Civic Ledger for full terms and governance framework.
Remember: Human-in-the-loop coding; proofs logged to Ledger; rewards via GIC for shared agreements.