Sessions
AI-interpreted events — drafted from any input.
The system architecture and Developer Experience (DX) are streamlined to categorize all hardware development activity into three fundamental elements:
Data enters the system through Sessions. A Session is the AI’s interpretation of an event that has occurred. The system is multimodal and can generate a Session from various inputs:
The AI analyzes these inputs and drafts a Session detailing how the captured event impacts Inventory, Actions, and Blueprints.
Crucially, the Timeline acts as the strict gatekeeper for all system changes.
A Session must first be approved and committed to the Timeline before any subsequent updates occur. It is exclusively this finalized Timeline data—never raw inputs or pending Sessions—that has the authority to subsequently modify the Inventory, Action, and Blueprint pillars.
AI-interpreted events — drafted from any input.
The strict gatekeeper. Only committed data flows downstream.
Stock, status & location
Tasks & physical changes
CAD, SOPs & BOMs
The process moves from AI data capture to a verified timeline through a distinct three-step flow:
AI Captures the Session
Example: A camera records a standard bolt being replaced with a high-tensile bolt. The AI processes the video and creates a pending Session detailing the swap.
Human Review
The drafted Session is presented to a user for review. The user verifies the AI’s interpretation of the event and approves it.
The Timeline is Updated
Upon approval, the Session is pushed to the Timeline—the single source of truth for the company. The AI then automatically updates the related documents based on the approved Session data:
Through this flow, physical and digital activities are captured, verified by a human, and systematically translated into updated company records.