nexcore

The Vigilance Kernel — unified Rust workspace (~63K LOC) powering NexVigilant's pharmacovigilance platform, skill orchestration, and AI agent infrastructure.

> nexcore is the proprietary computation kernel developed by NexVigilant LLC for drug safety signal detection, regulatory compliance, and intelligent automation.

# Build
cd ~/nexcore
cargo build --release

# Run tests (~1800+)
cargo test --workspace

# Start REST API (preferred for external integrations)
cargo install --path crates/nexcore-api
nexcore-api  # http://localhost:3030

# Use MCP tools (preferred for Claude Code)
# mcp__nexcore__pv_signal_complete(a=15, b=100, c=20, d=10000)

~/nexcore/
├── Cargo.toml                    # Workspace root
└── crates/
    ├── nexcore-vigilance/        # Core: ToV axioms, Guardian-AV, PV signals, 25+ modules
    ├── nexcore-brain/            # Working memory: sessions, artifacts, code tracking
    ├── nexcore-mcp/              # MCP server (90+ tools for Claude Code)
    ├── nexcore-api/              # REST API server (Axum, 33 routes)
    ├── nexcore-friday/           # FRIDAY orchestrator (voice, webhooks, scheduler)
    ├── nexcore-hooks/            # Claude Code hooks (quality, security enforcement)
    ├── nexcore-faers-etl/        # FAERS data pipeline
    ├── nexcore-config/           # Configuration types
    ├── nexcore-skill-verify/     # Skill validation CLI
    └── nexcore-epa1/             # EPA ECHO API integration

Use a one-way dependency flow to keep layering clear and avoid cycles:

1. foundation crates: shared primitives, utilities, types
2. domain crates: business logic, algorithms, PV, vigilance
3. orchestration crates: workflows, pipelines, schedulers
4. service/bin crates: API servers, CLIs, MCP, UI shells

Rules of thumb:

1. service/bin can depend on anything below it, but never the