ProgramsCapabilitiesProcessAerospaceResearchContact
Independent research · engineering · technology development

Robotics, assistive engineering, aerospace component research, AI systems, computational analysis, and experimental product development.

OTTORobotics + AI
ExoskeletonAssistive engineering
AerospaceComponents + documentation
ResearchComputational + cognitive systems
Programs

Explore the work.

Select a program to inspect its current focus, development direction, and technical stack.

Active development

OTTO

A mobile helper-robot platform combining onboard computing, voice interaction, computer vision, multi-direction sensing, mobility, and layered safety behavior.

Embedded compute · Vision · Voice · Sensor fusion · Motion control · Safety logic
Prototype design

Exoskeleton System

A modular lower-body engineering prototype exploring adjustable structures, powered joints, sensing, mechanical constraints, and controlled assistance.

Mechanical architecture · CAD · Joint mechanisms · Actuation · Sensor integration
Evaluation / sourcing

Aerospace Components

Component identification, documentation research, traceability review, market evaluation, and responsible sourcing or resale with explicit condition disclosure.

Part ID · Trace research · MRO outreach · Market analysis · Documentation control
Ongoing research

Cognitive Systems Research

Evidence-driven work on cognition, memory, attention, learning, neurobiology, and related questions where structured synthesis or computational analysis adds value.

Literature review · Mechanistic analysis · Modeling · Source evaluation · Technical writing
01 / 04
Capabilities

From concept to testable system.

Carlisle Labs connects mechanical design, embedded hardware, AI, research, visualization, and technical documentation so ideas can be evaluated as working systems.

Mechanical designArchitecture, mechanisms, dimensional planning, structural iteration.
Embedded systemsCompute, sensors, cameras, motor control, interfaces, fail-safe logic.
AI integrationVoice, vision, local/remote models, permission systems, behavior.
CAD & visualization2D-to-3D development, assemblies, layouts, iteration-ready models.
Technical researchSource review, literature synthesis, evidence comparison, modeling.
DocumentationVersion history, test records, project logs, technical briefs, trace notes.
Development process

Concept → evidence → revision.

The technical trail matters. Each iteration should make it possible to explain what changed, why it changed, and what the testing showed.

01 / DEFINE
Specify the problem.

Constraints, intended function, measurable objective, unknowns.

02 / DESIGN
Build the architecture.

Mechanisms, electronics, software, models, research method.

03 / PROTOTYPE
Make it testable.

Build enough of the system to challenge the key assumptions.

04 / TEST
Collect evidence.

Performance, failures, safety concerns, usability, anomalies.

05 / ITERATE
Revise with purpose.

Use evidence to drive the next version and preserve design history.

01 / DEFINE

Define the success criteria, constraints, interfaces, unknowns, and what evidence would count as progress.

Aerospace

Documentation before claims.

Aerospace work is handled conservatively: identify the component, determine what records exist, contact appropriate manufacturers or MRO organizations, and disclose condition accurately.

01Identify

Manufacturer, part number, serial, revision, markings, configuration, and visible condition.

02Verify

Manufacturer records, traceability, service history, and qualified evaluation where appropriate.

03Disclose

Undocumented or untested components are not represented as airworthy, serviceable, or released.

Research

Work that can be inspected.

The research arm is intended to publish structured technical work with sources, methods, assumptions, limitations, and revision history. Select a format below for more detail.

Operating principles

Make the claim match the evidence.

Engineering decisions and public claims are grounded in documented testing, measurable results, and technical evidence.

DesignTurn a concept into a defined system.
TestExpose where assumptions fail.
DocumentKeep the technical record usable.
ImproveUse evidence to drive the next version.
Contact

Start with the technical problem.

For engineering collaboration, aerospace inquiries, research discussion, or future product work, send a concise description of what you need.

Email directly

Compose inquiry opens your email app with the form details filled in. Nothing is sent until you send it.