Business problem
The kits make job contracts, fixtures, checks, reports, and runtime limitations directly inspectable.
Loading page
Public AutoCAD, Inventor, SolidWorks/PDM, Revit/BIM, and MicroStation/DGN kits expose fixture checks, job contracts, evidence reports, and native-runtime boundaries so evaluators can inspect current capability without confusing a demo with a customer deployment.
Runnable demonstrationCAD Guardian LLCFounder-built evaluation fleet2026
The kits make job contracts, fixtures, checks, reports, and runtime limitations directly inspectable.
Founder-built evaluation fleet
The common evaluation shape makes platform differences and support boundaries easier to compare.
Five public kits · Comparable evidence shape · Native-runtime honesty
Every kit states what runs anywhere and what still requires licensed platform execution and a local receipt.
The kits make job contracts, fixtures, checks, reports, and runtime limitations directly inspectable.
Five public kits Comparable evidence shape Native-runtime honesty
The common evaluation shape makes platform differences and support boundaries easier to compare.
The fleet covers AutoCAD, Inventor, SolidWorks/PDM, Revit/BIM, and MicroStation/DGN without pretending portable checks equal native execution.
Open technical detailFive public kits
A representative operating model for keeping commands, rules, exceptions, review, and release evidence visible.
Start with the current workflow, accepted output, connected systems, operational risk, and the first result worth implementing.
Review authorship, inputs, constraints, rules, outputs, integrations, validation, metrics, and source context in directly linkable technical sections.
The fleet covers AutoCAD, Inventor, SolidWorks/PDM, Revit/BIM, and MicroStation/DGN without pretending portable checks equal native execution.
Shows how a bounded implementation makes operating rules, exceptions, output, and ownership inspectable.
A representative operating model for keeping commands, rules, exceptions, review, and release evidence visible.
CAD workflow command-surface model — Current public runnable proof · 2026. First-party public diagram paired with the public proof-kit fleet.
Lifecycle automation is framed as an owned state-and-evidence system, not a hidden sequence of file operations.
PDM lifecycle and release-evidence model — Current public runnable proof · 2026. First-party public diagram paired with the SolidWorks/PDM proof boundary; it contains no customer files or lifecycle configuration.
The integration boundary follows the engineering decision and its owners across systems, records, and documents.
Engineering systems integration boundary — Current public runnable proof · 2026. First-party public diagram paired with the cross-platform proof fleet; all systems and handoffs are representative.
Current public runnable proof · 2026. Public CAD Guardian proof-kit repositories reviewed in 2026.
Current public runnable proof · 2026. public GitHub repositories
Publication limit: The public kit demonstrates current evaluation capability with public or synthetic fixtures. Native CAD compatibility still requires a supported licensed runtime receipt.
Current public runnable proof · 2026. repeatable verification commands
Publication limit: The public kit demonstrates current evaluation capability with public or synthetic fixtures. Native CAD compatibility still requires a supported licensed runtime receipt.
Current public runnable proof · 2026. public fixtures and JSON evidence reports
Publication limit: The public kit demonstrates current evaluation capability with public or synthetic fixtures. Native CAD compatibility still requires a supported licensed runtime receipt.
Start with the users, current workflow, accepted output, failure mode, connected systems, and the first implementation decision.