Portfolio · Research & Incubation
Research & Incubation - Mythos Systems Portfolio
Each generation expanded the scope of automation while retaining the same core principles: secure execution, observable state, human control, validation, evidence, and recoverability.
Network Discovery Engine
Architecture direction; publication detail follows evidence review.
Discovery and source-of-truth population for devices, interfaces, addressing, topology, capabilities, and relationships.
- Python
- NetBox
- pynetbox
- Nornir
- NAPALM
- SSH
- REST APIs
- Inventory normalization
- Confidence scoring
- Topology mapping
Endpoint Reports
Architecture direction; publication detail follows evidence review.
Endpoint assessment and reporting: device inventory, health, configuration, security, and operational findings turned into shareable evidence.
- Rust local collection
- Tauri
- SvelteKit
- System APIs
- Normalized telemetry
- Structured findings
- Export pipelines
LABYRINTH
Pre-Phase-0 architecture and implementation blueprint.
NetBox-centered network automation and assurance for telecommunications, fiber, OSS/BSS, inventory, operational state, configuration, telemetry, and source-of-truth reconciliation. LABYRINTH continuously compares NetBox intent, observed state, and business-system context; it introduces admission control, blast-radius scoring, maintenance-window enforcement, dry runs, digital twins, canary execution, postchecks, rollback, and immutable evidence before permitting infrastructure changes.
- Rust
- Axum
- Tokio
- Tower
- Python
- pynetbox
- Nornir
- Pydantic
- Ansible/AWX
- NAPALM
- pyATS/Genie
- Batfish
- containerlab
- PostgreSQL
- Redis
- NATS JetStream
- ClickHouse
- Prometheus
- Grafana
- Loki
- OpenTelemetry
- Kubernetes
- Argo CD
- Terraform
- Vault
- S3-compatible storage
- Tauri 2
- SvelteKit
- TypeScript
SYN4PS3
Architecture direction; not publicly released.
Natural-language infrastructure operations architecture separating a centralized orchestration and governance plane from a local execution engine operating near the managed environment.
- Rust-first execution engine
- Typed APIs
- Web orchestration
- Windows tray or headless agents
- Local credential boundaries
- Infrastructure connectors
- Policy controls
- Result streaming
- Audit evidence
CALLISTO
Foundation architecture and product incubation.
Privacy-first, Rust-native browser platform: secure workspaces, profile isolation, extensibility, integrated vault, VPN routing, privacy enforcement, AI assistance, and cryptographic agility.
- Rust
- Tokio
- Tauri 2
- SvelteKit
- TypeScript
- wgpu
- Vello
- GPU shaders
- SVG rendering
- Native WebView adapters
- Future Servo integration
- WireGuard
- Secure storage
- Signed modules
- Browser extensions
- Native messaging
SYNODIC
Implementation candidate; static validation completed; native Rust build closure pending.
Standalone Windows-first agent engineering environment turning model reasoning into durable, bounded, inspectable engineering work. No model, IDE, plugin, or provider is authoritative; the Rust daemon synodicd is the sole owner of durable state transitions, with CLI, TUI, IDE, SDK, and PANTHEON integrations as equal protocol clients. SYNODIC owns the deterministic Agent Kernel; Missions and WorkOrders; agent topologies, supervisors, arbiters, and execution cells; multi-provider model routing; context compilation; governed memory and Skill contracts; capability grants, leases, scopes, and budgets; out-of-process execution and extension hosts; verification, evidence, recovery, replay, and emergency Quench; and the CLI, TUI, IDE, SDK, and protocol surfaces. Its mission ledger combines normalized transactional state, an append-only event journal, immutable evidence, and a content-addressed Artifact Vault; replay reconstructs state without repeating external side effects. PANTHEON may create Missions and consume evidence through versioned protocol contracts but cannot bypass SYNODIC authority boundaries.
- Rust 1.97.1
- Edition 2024
- Tokio
- Modular monolith
- SQLite WAL
- Protobuf
- Buf
- JSON Schema
- Windows named pipes
- Optional loopback gRPC
- Windows Job Objects
- Content-addressed artifact storage
- OpenTelemetry-compatible observability
- TypeScript SDK generation