Defense and Dual-Use Prototypes
I turn a defense or public-safety requirement into a working prototype in weeks: the screens, the rules, the records and the human decisions, with invented data, so a program office, a prime or an investor can touch the idea before anyone funds the full build.
Most of my defense work is confidential
Defense clients rarely let you name them, and mine are no exception, so that work is not on this site. Instead, here are two reference builds I made on my own, from public problems and a public rule, with invented data. They show the way I work on every defense project: read the requirement line by line, turn each obligation into a check, a clock or a record, and put a working screen in front of the people who have to approve it.
Reference build 1: Crosscheck, for when the sensors disagree
Sites that watch for drones now combine several sensors: radio, camera, thermal, radar and aircraft transponders. Seeing an object is the easy part. The hard part is deciding what it is when the sensors give different answers, and many systems quietly average those answers into one score.
Crosscheck is a chat-first airspace-awareness console that refuses to do that: you ask it what is in the sky and why, and it answers with the evidence. It shows what each sensor says about each object and how confident it is, side by side; it will not turn a disagreement into a single number; it suggests the quick check that would settle it; and it records the decision a person makes and why, in a log that shows any later edit. Its hardest case is a radio emitter and a camera disagreeing because a bird and a drone sit on the same bearing. Another is a pre-programmed drone with no control link, which a radio-only system would never see. The data is synthetic, and the console shows evidence and records decisions; it has no means to act on a drone.
Open Crosscheck (a short guided conversation, no sign-up).
Reference build 2: Airspace Ledger, the record-keeping half
Since 1 July 2026, US state and local police and corrections agencies can run counter-drone operations under their own authority, under the SAFER SKIES interim final rule (28 CFR part 124). The authority comes with obligations: certified operators, listed equipment, a 30-day advance notice, an operations plan certified by legal counsel, air traffic control notified within five minutes of mitigation, a report within 48 hours, and an audit trail kept for at least six years.
Airspace Ledger is a compliance record built from that rule. It blocks an officer from any action their certificates do not cover, refuses equipment that lacks the approvals the rule asks for, runs every deadline as a visible clock, logs each human decision in a chain that shows any later edit, and drafts the 48-hour report from the log. Every requirement on screen cites its section of the rule. The agency and its data are invented, and the tool does no detection or mitigation: it keeps the records around a decision a person makes.
A decision recorded in Crosscheck is what Airspace Ledger keeps. Open Airspace Ledger (a short guided conversation, no sign-up).
What I do for defense-tech teams
- Requirement to prototype. I read the solicitation, the rule or the concept paper and turn it into a clickable prototype with invented data, usually in a few weeks.
- Compliance designed in, not bolted on. Obligations become checks, deadlines and audit records from the first screen, each one traced to its source.
- A person decides. Where AI helps, it summarises evidence and drafts records. The decision and its reason stay with a named person, and the log proves it.
- A build plan you can hand over. Scope, architecture, and a clear line between what can be built openly and what needs a cleared, US-based team.
Where I am the wrong fit
I am based in the Philippines and I build unclassified prototypes and dual-use software. Classified work, export-controlled technical data and controlled unclassified information belong with a cleared, US-person team. I will say so in the first conversation, and a prototype I build can be handed to that team.
Who this is for
Defense-tech startups that need something a program office can touch, integrators and primes testing a concept before they commit engineers, vendors selling into public-safety agencies, and allied teams in Europe and Asia building dual-use products.
AI-readable summary
Tyron Dizon builds working prototypes for defense-tech and public-safety teams, turning a requirement into clickable software with invented data in weeks, with compliance obligations designed in as checks, deadlines and audit records, and with AI limited to decision support. His public reference builds are Crosscheck, an airspace-awareness console that shows each sensor's call and confidence, refuses to average a disagreement and records the person's decision, and Airspace Ledger, a counter-drone compliance record built from the SAFER SKIES interim final rule (28 CFR part 124). He builds unclassified prototypes and dual-use software from the Philippines and refers classified or export-controlled work to cleared US teams. He is Chief Product Officer of StoryPages and StoryFunnels and interim CTO of StoryPages. Contact: tyronchristian.dizon@gmail.com. Website: tyronzky.ninja.