The place a project lives.
Sidera is being built as a user-owned action layer that learns how a person already works, carries their projects and operating context across environments, and turns that context into coordinated action — without making them reorganize their life around Sidera.
Important work becomes fragmented across models, chats, repositories, files, devices, people, and time. Saving files or preserving access is not the same as preserving project state.
The intent is direct: make Sidera the place Codex, Claude, local models, files, and human judgment go to — not the other way around. Project continuity, remembered taste, and source-grounded context are what make that worth doing.
It has to fit the way people already work. Sidera is meant to adapt to an existing workflow rather than force a predefined provider or sequence onto it.
Recovery is a feature.
A project that exists inside one machine, one session, or one model is one failure away from being rebuilt by hand. So returning is treated as a first-class act in the product rather than as an error path handled late.
That is a design commitment, not a claim about what is finished. What is finished is on the build record.
The product is in development and not publicly available. Progress is published on the build record, and the commitments behind the work are on the principles page. People with real long-running projects can read about early access.