Reference Architectures
Reference architectures, not customer stories: target scenarios Kernex is built to serve, each reproducible from the public crates.
Secure code review pipeline for a fintech team
For teams whose security policy rejects Python agent frameworks: OS-enforced boundaries a security team can verify instead of trust.
Design target: 3-phase pipeline under 30 seconds per PR, audit log built for SOC 2 evidence.
Documentation bot with persistent memory
For the solo maintainer: decisions stored as facts, so a March breaking-change rationale answers the April issue.
Design target: support answers from one memory lookup, not a re-read of issue threads.
Internal knowledge bot for a remote engineering team
Tribal knowledge spread across Notion and Slack. Skills directory committed alongside the codebase. Version-controlled, reviewable, auditable.
Design target: onboarding measured in days of answered questions, not weeks of asking.
Local AI assistant for air-gapped development
Fully offline with Ollama. OS-level sandboxing as the compliance argument. Designed so no data leaves the machine.
Design target: approvable for classified environments, with an inspectable kernel-level policy.
Data pipeline debugging agent
200+ daily ETL jobs. TOML-defined triage pipeline version-controlled alongside the jobs. A new team member can understand the logic by reading the topology file.
Design target: automated first-pass triage in about 2 minutes, vs 30-45 manual.