**Git Commit Tracking** - Automatically capture git commit hash when claims/observations are ingested - Store in assertion metadata for temporal context and audit trails - Graceful degradation in non-git environments - Solves double-commit problem by capturing hash at ingestion time **Implementation** - walker/git.rs: get_current_commit_hash() utility function - bridge.rs: Accept optional git_commit parameter in all conversion functions - episteme/local: Store project_root, capture git hash during ingestion - 5 new tests for git hash tracking + metadata validation - All 1162 aphoria tests passing **Documentation Overhaul** - README: Added Observations vs Claims distinction, git tracking, dashboard - CLI Reference: New sections for git integration and ignore/exclusion system - Comprehensive ignore documentation: .aphoriaignore, inline comments, 4 methods - Enhanced verification engine docs with matching capabilities - DOCUMENTATION_UPDATES.md: Complete audit summary **Dashboard Separation** - Moved Aphoria-specific UI from stemedb-dashboard to aphoria-dashboard - Clean separation of concerns: StemeDB for core, Aphoria for security - Added dashboard documentation and setup guides Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| src | ||
| .gitignore | ||
| components.json | ||
| CORPUS_STATUS.md | ||
| DOCUMENTATION_INDEX.md | ||
| next.config.ts | ||
| package.json | ||
| postcss.config.mjs | ||
| QUICK_REFERENCE.md | ||
| README.md | ||
| tsconfig.json | ||
Aphoria Dashboard
Code quality assurance dashboard for Aphoria - the code-level truth linter powered by Episteme.
Features
- Scans: Run and view Aphoria code scans with conflict detection
- Claims: Manage authored claims (architectural decisions, safety invariants, policy requirements)
- Corpus: Browse and filter the community corpus of authoritative sources (RFCs, OWASP, CWEs)
Quick Start
# Install dependencies
npm install
# Run development server (port 18189)
npm run dev
# Build for production
npm run build
# Start production server (port 18189)
npm start
Architecture
- Framework: Next.js 16 with App Router
- UI: TailwindCSS 4 + shadcn/ui components
- Port: 18189 (Aphoria Dashboard)
- API Integration: Proxies requests to StemeDB API at port 18180
API Integration
The dashboard uses Next.js rewrites to proxy API requests:
// All /v1/* requests are proxied to http://localhost:18180/v1/*
// This is configured in next.config.ts
Leave NEXT_PUBLIC_STEMEDB_API_URL empty in .env.local to use proxy mode.
Project Structure
src/
├── app/ # Next.js app router pages
│ ├── scans/ # Aphoria scans route
│ ├── claims/ # Claims management route
│ ├── corpus/ # Corpus browser route
│ └── layout.tsx # Root layout with Aphoria branding
├── components/
│ ├── corpus/ # Corpus browser components
│ ├── scans/ # Scans panel components
│ ├── claims/ # Claims management components
│ ├── layout/ # Sidebar, header, theme toggle
│ ├── shared/ # Shared components (error, api-status)
│ └── ui/ # shadcn/ui components
└── lib/
├── api/ # API client (includes both StemeDB + Aphoria)
└── utils.ts # Utilities
Related Projects
- Aphoria Backend:
applications/aphoria/- Rust CLI and extractor engine - StemeDB Dashboard: Port 18188 - Database admin dashboard
- StemeDB API: Port 18180 - Backend API
Development
The dashboard shares some infrastructure with StemeDB Dashboard (UI components, API client, utilities). See applications/DASHBOARD_SYNC.md for sync procedures if you update shared code.