Make authority explicit.
Separate operator access from agent capabilities. Bind each grant to a task, resource, lifetime, and use limit.
Inspect the implementation →THE PERSON BEHIND THE SYSTEMS
Engineer. Builder.
Problem solver.
I’m Charles D. Gonzalez. My work connects the software people use with the systems, data, and security boundaries underneath it.
I design and build systems across the entire path from a physical device or business event to the platform, interface, and security decision that depends on it.
At El Sembrador, I built a complete technology ecosystem from the ground up: operational applications, service boundaries, cloud integration, container infrastructure, and local compute. Northstar Atlas makes that breadth inspectable through a current synthetic demonstration of the workflows and architecture.
At El Viejo, that work extended into industrial IoT and robotics: Rust and Go at the edge, C++ and Arduino device software, cold-storage and truck telemetry, warehouse networks, and hybrid-cloud services. The job connected physical measurements, embedded behavior, backend processing, and interfaces people used to operate the business.
At the City of Coral Gables, I work across security engineering and automation: telemetry normalization, identity and endpoint integrations, analyst workflows, and Rust tools. Public descriptions here focus on engineering responsibilities while keeping municipal records and operational details private.
My independent systems make the implementation visible. I built Athernex, a Rust SIEM, and develop endpoint telemetry, policy enforcement, operations tooling, and edge-control models. Evidence integrity, durable delivery, explicit authority, and explainable failure behavior are recurring concerns throughout that work.
From business workflows to security systems.
Client work taught me to translate operational problems into data models, interfaces, APIs, and dependable delivery. Building Athernex and the related security tools lets me carry that approach into evidence integrity, policy enforcement, and explicit authority.
HOW I WORK
Principles, put into practice.
Keep evidence trustworthy.
Give events stable identities, preserve their provenance, and reject contradictory facts before they become accepted evidence.
Inspect the implementation →Design for interrupted delivery.
Treat backpressure, incomplete acknowledgments, and retries as normal operating conditions. Make recovery observable.
Inspect the implementation →Enforce policy consistently.
Normalize inputs before evaluating rules, preserve domain boundaries, and expose the reason behind each decision.
Inspect the implementation →Keep stale authority from acting.
Separate control intent from execution. Make ordering, authority changes, and stop behavior explicit in the model.
Inspect the implementation →Prove the integration contract.
Connect independent systems through versioned data, bounded validation, explicit provenance, and repeatable producer-consumer tests.
Inspect the implementation →