Bilal SabugarRobotics & product engineeringLet’s talk

03 / Engineering research · Open source

RoboScout.

How can engineering research stay traceable when AI is part of the workflow?

My contribution
Product direction & engineering workflow design
Current stage
Public software project
Available evidence
Application source · Architecture · Sizing routines
Actual RoboScout static torque calculator showing inputs, calculated torque and engineering assumptions
Actual local application · Static torque calculator with default inputs · Font fallback used in this capture

01 / The project

An engineering research tool that connects component selection to source documents, torque calculations and reviewable reports.

An independently maintained public software project connecting robotics requirements with source material and explicit calculations.

Status
Public software project
Tools & technologies
Next.js · TypeScript · Prisma · SQLite · SerpApi

02 / My contribution

Product direction & engineering workflow design.

I directed the project and its engineering workflow: how requirements lead to component research, calculations and reports. AI coding agents produced the implementation, as disclosed in the repository.

The README explicitly describes implementation through AI coding agents, with human architectural direction. This portfolio preserves that distinction.

03 / Purpose & architecture

The problem behind the implementation.

Component research needs more than a plausible recommendation. An engineer needs to trace a specification to its source, check the calculation and understand the assumptions before selecting hardware.

How the parts connect

The Next.js/TypeScript application connects requirement and research workflows with SerpApi retrieval, Prisma/SQLite records and report generation. Static torque sizing is a deterministic TypeScript calculation, separate from generated research text.

04 / Engineering decisions

Decisions that shape the system.

01

Keep calculations deterministic

Static torque sizing and safety margins are calculated in TypeScript. Generative output is not used as the arithmetic engine for physical requirements.

02

Preserve the source of each claim

Research records distinguish verified, reported, unknown and conflicting parameters. The intent is to keep a component recommendation connected to its underlying documentation.

03

Carry research into execution

The documented workflow includes component datasheet retrieval, technical literature, schedules and report export. These outputs help a research session become a reviewable engineering plan.

05 / Results & current scope

What exists today.

An open-source research application with architecture documentation and deterministic sizing routines.

Engineering principleAI can help gather engineering information, but calculations and source checks need explicit rules that a person can inspect.

Recommendations still require engineering review. Public documentation describes the system's intended checks; it does not establish that every retrieved specification is correct or that a hardware design is safe.

06 / Source material

Inspect the work.

Working on a related problem?

Tell me what you need to build, test or understand. Mention RoboScout if it is a useful starting point.

Discuss your project

Continue exploring

WIRKBack to all work