Skip to content

An AI-native system-of-record for optics and photonics research and development design automation

Oct 2026 · Optical Design Automation II · 0 citations

TL;DR

It is argued that an optical laboratory reduces to two primitives, the components on the bench and the connections between them, and that promoting this decomposition to a first-class, versioned graph, rather than a file hierarchy, is the substrate that makes both human retrieval and AI-assisted design automation tractable.

Abstract

Documentation in optics and photonics research and development is overwhelmingly unstructured (spreadsheets, plots, instrument exports, images, and free-text notes) and is scattered across shared drives and nested folder hierarchies. A folder tree imposes a single rigid access path, yet any one artifact is relevant along many dimensions at once (by wavelength, by component, by project, by person, by team, or by date), so the tree is the wrong index for almost every question and gives an automated agent no relational signal, only blind path-guessing. We argue that an optical laboratory reduces to two primitives, the components on the bench and the connections between them (with the convenience of grouping a reusable assembly into a modular component that can be saved and reused). Promoting this decomposition to a first-class, versioned graph, rather than a file hierarchy, is the substrate that makes both human retrieval and AI-assisted design automation tractable. We present an AI-native system-of-record built on this principle. It treats a hardware configuration much as version control treats source code: a user can branch a setup to explore an option or debug a problem without disturbing the main line, and each configuration is tied to the specific measurement, parameter, or test it was built for. Every change, by a scientist or by the AI, is captured in an append-only audit log, so nothing is ever truly lost: an accidental deletion or edit can be rolled back, and the whole development history of an experiment, setup, or project stays visible, what was tried, which decisions were made, and where problems arose. Unlike software, where an AI has the whole codebase and the internet for context, hardware leaves it blind to everything outside the computer; a components-and-connections graph gives the AI the same structured view of the bench that a human has, and the AI in turn can fold the free-form artifacts scientists already produce into that structure, acting over it through the same interface as human users. We have implemented the full architecture as a working prototype and report its design and our experience building it.

View source

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 727 citations · ⚡54
#computer vision Jun 2008

The impact of agile practices on communication in software development

The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.

M. Pikkarainen, Jukka Haikara, O. Salo et al. · 401 citations · ⚡48
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.

Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al. · 394 citations · ⚡54
#computer vision Review Mar 2008

Agile methods in European embedded software development organisations: a survey on the actual use and usefulness of Extreme Programming and Scrum

The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.

O. Salo, P. Abrahamsson · 238 citations · ⚡9
#computer vision Open access Jul 2017

What happens when software developers are (un)happy

Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al. · 236 citations · ⚡13
#computer vision Open access Oct 2004

Mobile-D: an agile approach for mobile application development

The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.

P. Abrahamsson, Antti Hanhineva, H. Hulkko et al. · 225 citations · ⚡18

Related blog posts

Microsoft Research Blog Oct 12, 2026

Simulating student learning for better AI tutoring

StudentSim is a research system for evaluating and improving AI tutoring tools before they are tested with learners. It models how individuals may engage with tutors, giving feedback to improve tutor performance across subjects like chess, writing, and mathematics. The post Simulating student learning for better AI tutoring appeared first on Microsoft Research.

MIT News · Artificial Intelligence Oct 2, 2026

Documenting the tech worker movement

Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.