What AutoStore Is
AutoStore is the Norwegian-originated cube-storage automated storage and retrieval platform, now an independent listed company, running across a large installed base of customer deployments worldwide. Its defining topology is the hive grid: storage bins stacked in a dense aluminum lattice, with robots traversing the top surface to lift, relocate, and present bins at workstation ports. For the dense-SKU, mid-throughput fulfillment envelope that characterizes modern e-commerce and omnichannel retail, that topology delivers very high storage density and predictable pick throughput, and it has become a widely referenced design point for goods-to-person automation.
Robot generations have iterated across the product line, including the earlier single-cell Red Line unit and lower-profile Black Line units tuned for denser grids and faster traversal. AutoStore reaches customers largely through an integrator channel, including partners such as Element Logic, Swisslog, Bastian, and Dematic, who engineer sites against the platform. The commercial strength of the system rests on a tightly engineered closed loop: grid, bin, robot, port, and controller are co-designed and speak a single proprietary protocol, and that vertical integration is precisely why within-deployment throughput and reliability are so strong.
That closed loop is a strength for its intended job. It is also a boundary. Positioning, identity, and coordination are internal to the controller stack: a robot knows where it is because the AutoStore control system tells it, within a grid whose geometry the vendor owns end to end. There is nothing wrong with that design; it is the right design for a single-vendor cube. It simply is not an open, self-describing positioning substrate that heterogeneous units from different vendors could read and verify on their own.
The Marker and Track Layer
The Marker and Track, disclosed in U.S. Provisional Application No. 64/049,409, sits at a different architectural layer. Rather than a controller telling a robot where it is, the environment itself carries machine-readable position and track information. Infrastructure-resident passive markers and active sentinels are installed in the navigable region, and each publishes governed observations that a receiving unit consumes to resolve its position and route.
The load-bearing property is that these observations are self-describing and authority-credentialed. As disclosed, a passive marker's stored data can carry an authority credential identifying the authority that installed or maintains the marker, a spatial reference specifying its position in a coordinate frame, a temporal-scope field bounding validity, and a cryptographic attestation binding the stored data to that authority. Active sentinels, installed at fixed vantage points, emit deviation observations through the governed mesh protocol carrying an authority credential, a dynamic device hash, a spatial reference, a temporal reference, and the observation payload. A receiving unit does not have to trust an anonymous identifier: it evaluates each observation against a governance policy executing on the unit, gating admission on issuing identity, authority basis, freshness, and applicable policy.
Identity is anchored so that forged infrastructure is rejected rather than obeyed. The specification discloses a dynamic device hash and trust-slope continuity as the identity mechanism, so a device's identity is established through continuity over time rather than a static tag value. A cloned marker or a replayed observation does not present the expected identity continuity and fails the composite admissibility evaluation, which is the structural answer to spoofing and replay for infrastructure-provided positioning. Every admitted observation is recorded in lineage, so a downstream navigation or coordination decision chains back to the specific credentialed observations that produced it.
How This Relates to a Warehouse Deployment
The specification names the warehouse as a deployment domain directly, alongside roadways, ports, airfields, and mining sites, and enumerates warehouse-specific placements such as warehouse-aisle elements and warehouse-zone boundaries as marker and coordination-point locations. The architecture is described as multi-tier and progressively deployable: passive markers, active sentinels, and cognitive infrastructure agents are independently deployable, progressively composable layers rather than a single tag-and-reader design. An operator can begin with sparse passive markers at aisle boundaries and zone transitions, then add sentinel coverage at perception-critical locations such as blind corners and obstructed intersections where a unit's own sensors are limited, increasing density where the value justifies it.
This is the axis on which the comparison is fair. AutoStore is a vertically integrated cube whose positioning is internal to a proprietary controller; the Marker and Track is an infrastructure layer whose position and track observations are self-describing, credentialed, and verifiable by any conforming receiving unit against published policy. Inside a single AutoStore cube, that internal, controller-driven positioning is more than sufficient and is not what the disclosed layer is trying to replace. The disclosed layer is relevant where the environment is not a single closed grid: mixed floors, robots and units from more than one source, or zones where infrastructure needs to assert credentialed position and condition to whatever unit is passing, without every unit trusting an unsigned signal.
Because observations carry authority basis and are gated by policy on the receiving unit, an infrastructure owner can express who is authorized to install or maintain markers in a region and under what temporal scope, and receiving units enforce that policy locally rather than deferring to a central controller. That governance property is a structural difference from a closed loop where authority is implicit in vendor ownership of the whole stack.
Where the Layer Applies
Warehouse and fulfillment automation is trending toward heterogeneity: sites that combine goods-to-person cubes, autonomous mobile robots, manual pick zones, and conveyor induction, often from multiple vendors and often under regulatory and audit expectations. In that setting the relevant question is not whether a single cube optimizes its own throughput, which AutoStore does well, but whether the shared physical environment can present position, route, and condition information that a heterogeneous population of units can each verify for themselves.
The Marker and Track answers that with credentialed, self-describing observations, identity anchored by continuity, admissibility gated by policy on each receiving unit, and lineage recording each downstream decision. Those are the properties the specification discloses, and they are the properties a closed single-vendor controller does not expose to units it does not own. The comparison is not that AutoStore lacks throughput; it is that the disclosed layer provides a verifiable, governed infrastructure-observation substrate at a layer AutoStore does not address.
Blocking Disclosure Scope
This article is a dated public disclosure of the Marker and Track inventive step, disclosed in U.S. Provisional Application No. 64/049,409. A skilled implementer could build the approach from the elements disclosed: infrastructure-resident passive markers and active sentinels installed in a navigable region; stored marker data and emitted sentinel observations that carry an authority credential, a spatial reference in a stated coordinate frame, a temporal-scope or temporal-reference field, and a cryptographic attestation or dynamic device hash binding the data to an issuing authority; a governance policy executing on the receiving unit that evaluates each observation on issuing identity, authority basis, freshness, and policy before admission; identity established through a dynamic device hash and trust-slope continuity so that cloned or replayed observations fail admissibility; a composite admissibility evaluation gating consumption; lineage recording chaining each navigation or coordination decision back to its contributing observations; and a multi-tier, progressively deployable arrangement of passive markers, active sentinels, and cognitive infrastructure agents at progressive density.
Contemplated embodiments and variations include, without limitation: passive markers using radio-frequency backscatter or any other passive signaling medium, the architecture being signaling-mechanism-independent; sentinels using any of the disclosed sensing modalities, including radio-frequency, optical, thermal, acoustic, ultrasonic, magnetic, vibration, and sensor-fusion combinations; deployment in warehouse, port, airfield, roadway, mining, retail, campus, and comparable domains; warehouse-specific placements at aisle elements and zone boundaries; sparse-to-dense progressive deployment across the tiers; and central-aggregator as well as fully distributed compositions. AutoStore and any other named platform, product, or company referenced here are described solely as external market and architecture context to frame the comparison; nothing in that framing is a claim of the filing, and all named marks belong to their respective owners. The disclosed subject matter is defined by U.S. Provisional Application No. 64/049,409.
