Governed ingestion
Repeatable intake patterns for files, scans, spreadsheets, and operational records with traceable identity and reviewable receipts.
Founder · Solutions Architect · Platform Systems Builder
My work combines operations discipline, software architecture, DevOps habits, workflow automation, and local-first infrastructure. The goal is practical: turn scattered artifacts and process steps into traceable evidence before making bigger automation or AI claims.
What I build
Repeatable intake patterns for files, scans, spreadsheets, and operational records with traceable identity and reviewable receipts.
Guarded workflow lanes that separate operators, conductors, execution boundaries, policy checks, and read-only proof surfaces.
Dashboards, summaries, and portfolio-safe proof points that make it clear what happened and which evidence supports each claim.
CLI-first scaffolding, schema-driven templates, validation commands, and Nexus artifact integration for repeatable project creation.
Structured pipelines that normalize operational logs, produce incident artifacts, and expose bounded evidence to AI clients safely.
Linux, Docker, scripting, repository discipline, and lab hardware arranged for controlled rehearsal, cost awareness, and explainability.
Featured project
StarkGrid is a private MVP/demonstration platform for deterministic artifact ingestion, evidence review, and governed automation. Built in Java across seven active modules — Janus, Demeter, Argus, Themis, Hermes, Hephaestus, and Mnemosyne — running on Kafka and Docker Compose.
The system runs distributed across two lab nodes: Jarvis as the primary control-plane and Ultron as a GPU-capable remote worker. Athena (React) and athena-observer (FastAPI) provide read-only evidence review and DLQ visibility.
The case study demonstrates clear module ownership, deterministic processing boundaries, source-backed observability, and guardrailed claims — with explicit caveats for what has not been enabled.
Open the case studyEngineering Proof Projects
StarkGrid is the main platform. Forge, SRE Log Pipeline, Forge MCP, and Operator Evidence MCP are public projects that demonstrate repeatable scaffolding, evidence distillation, validation discipline, and safe AI-facing evidence interfaces.
Forge · v0.2.0
Python CLI for creating standardized project lanes with schema-driven templates, validation, Nexus artifact integration, and release workflows.
python-worker, java-spring-service, node-dashboardforge doctor validates local prerequisitesforge project inspect and Nexus template packagingRole fit: Developer tooling, platform engineering, release discipline
View Forge case studySRE Log Pipeline · v0.2.0
Python JSONL pipeline that turns noisy logs into structured incident evidence for debugging, incident review, and postmortem workflows.
Role fit: DevOps, SRE, observability, incident response
View SRE Log Pipeline case studyForge MCP · v0.1.1
Read-only MCP server that exposes Forge repository knowledge — templates, validation commands, project structure — to AI clients without write access.
Role fit: AI tooling, developer platform, MCP integration
View Forge MCPOperator Evidence MCP · v0.1.1
Read-only MCP server that exposes bounded incident evidence and operational summaries to AI clients without write access or execution authority.
serverInfoRole fit: AI infrastructure, incident tooling, secure evidence retrieval
View Operator Evidence MCPContact
Use the professional domain email or LinkedIn profile for public portfolio follow-up.
Email: contact@quentinmcclellan.com
LinkedIn: linkedin.com/in/quentinmmcclellan