Linne Engine is a shared foundation for intelligent media, realtime production, rendering, spatial systems, and evidence-led creative tools.
114
Tracked capabilities
109
Engine-proven or better
8
Product-integrated
12
Public system groups
Latest progress · July 13–17
From capability to production proof.
This week focused on making the Engine more autonomous, more portable across machines, and more deeply qualified in the native workflows that production depends on.
Operate
Self-maintaining peer execution
Cross-platform Codex peers can now diagnose Receiver launches, repair local workers, hand off revisions, and converge bounded tasks with redacted operational evidence.
Windows and macOS peer-recovery and Receiver workflow proofs
Understand
Native biomechanics workflows
The native OpenSim path now covers model and motion loading, scaling, dynamics, muscle analysis, joint reaction, OpenSense, and reusable geometry dependencies.
Public-data biomechanics scenarios and native SDK verification
Operate
Qualified production transport
SRT, RIST, RTSP, RTMP, and virtual-camera paths gained hosted qualification, recovery, exact cadence, latest-frame buffering, and GPU-resident publication checks.
Hosted protocol, cross-platform Receiver, and output qualification runs
Create
Clock-centered composition
Adaptive Resident Composition now projects shared clock, resource, execution, artifact, and trust authority into product hosts without creating competing local truth.
Architecture inheritance and host-projection integration
Capability map
One engine. Twelve connected systems.
Browse the public capability projection. Internal implementation details, private operational records, and customer-specific systems are intentionally excluded.
Showing 12 of 12 system groups
Capability dependency map
12 systems · 49 system links · 171 cross-system feature dependencies · snapshot 2026-07-17
100%
Trace a capability path
Drag / arrow keys to move · scroll to zoom
Protect
Understand
Create
Operate
System typeCreateUnderstandOperateProtectSelectionUpstreamDownstream
Explore the engine
Select a system or trace a path.
Arrows run from a capability dependency to the system that uses it. Line weight reflects the number of public feature relationships—not runtime traffic or implementation coupling.
A capability can be real in the engine without being generally available in a product. Maturity labels describe the strongest repeatable proof we have—not a release date, service guarantee, or claim of universal quality.