Antshiv Robotics develops auditable CPU AI, control and simulation software, and the infrastructure needed to preserve how those systems were built and tested.
The long-term ambition is autonomous physical systems. The present work is more disciplined: harden the mathematics, kernels, runtimes, simulations, evidence, and hardware paths required to earn that capability.
Trace systems from equations and numerical contracts to executable kernels.
Use parity, profiling, and reproducible tests rather than unsupported claims.
Connect CPU AI, simulation, control, and engineering infrastructure.
Publish the process so others can inspect, reproduce, and contribute.
A model, controller, robot, website, and experiment record are often treated as separate products. In practice they form one engineering loop: observe, compute, decide, act, measure, and retain the evidence.
CKE investigates how far CPUs can carry modern inference, bounded training, and eventually distributed execution without hiding the work behind a remote service.
Dynamics, estimation, control, simulation, timing, embedded execution, and field validation must agree before a system deserves an autonomous label.
Antsand and ShivasNotes preserve data, decisions, failures, diagrams, and explanations so progress is not reduced to a final benchmark or product claim.
The programmes share an engineering method, but not the same evidence level.
An open-source Linux CPU runtime and kernel compiler for transformer language, vision, and audio models, hardened through pinned numerical references and nightly tests.
Rigid-body mathematics, sensor models, state estimation, control, and deterministic simulation developed toward embedded and physical validation.
Structured Databoards, federated websites, content pipelines, and evidence infrastructure used to operate and explain the engineering work.
The company is being built around engineering practices that make ambitious work inspectable instead of merely persuasive.
Write down the equation, physical assumption, data contract, numerical reference, and intended behavior before optimizing implementation.
Missing kernels, unsupported routes, invalid shapes, and broken contracts should stop execution rather than silently substitute an unknown path.
Use profilers, intermediate tensors, hardware counters, controlled experiments, and compiler matrices instead of optimizing from intuition alone.
Measured, demonstrated, in progress, and planned are different states. Product language should preserve those distinctions.
Commits, pull requests, tests, technical articles, diagrams, and experiment lineage retain why a system changed and what the change actually proved.
Anthony founded Antshiv Robotics to connect several bodies of work that had been developing separately: native systems software, CPU AI, mathematical modeling, robotics, data infrastructure, and technical education.
He currently directs the engineering, reviews the generated and contributed work, operates the testing and publishing systems, and documents the questions that remain unresolved. The company is deliberately honest about being early, small, and still building its strongest capabilities.
CPU AI runtime and compiler
Data, publishing, and deployment
Derivations, investigations, and evidence
The best next conversation starts with a model, kernel, controller, simulation, hardware platform, experiment, or teaching problem that can be made reproducible.