What it is now
Lab-stage concept. It does not advance until more than one Lattice surface exposes stable, repeated actions.
Future command layer, not a current product surface.
Development lane
Keystone
The command layer for recurring research actions.
Keystone is a gated command layer for research workflows once there are enough stable actions worth orchestrating.
Status
Gated lab-stage lane
Dependency
Requires repeated stable actions across products
Current rule
No UI-first planning before the workflows exist
Surface type
Command layer
Who it is for
Analysts and operators moving repeatedly across linked research surfaces.
Understand the future command role rather than expect a live product.
What exists today
Concrete surface area.
Research action orchestration
Keyboard-first command surface
Evidence and note actions
Workflow shortcuts tied to real tasks
What makes it credible
Proof before expansion.
Dependency-gated. Keystone should not ship before upstream product actions become concrete and repeatable.
Stack relationships
How Keystone connects to the portfolio.
Mosaic
Mosaic
Mosaic would provide evidence actions Keystone could eventually orchestrate.
Dictum
Dictum
Dictum drafting actions could become part of a future command layer.
Courier
Courier
Courier delivery actions could later join the same command surface.
Adjacent lanes