Your work. Where you left it.

Public record · Sector 02 · 2026-07-21
In development

Build record · product

The active target — directing real work on Sidera, from a phone

proposed Recorded 2026-07-21 Ref — docs/CLAIMS_REGISTER.md claim 3, availability is prohibited

Entry

Summary
The current build target is a single end-to-end capability: from a phone, with no terminal and no jargon, the owner directs real development work on real projects — including Sidera's own code — and Sidera does the work, proves it with a receipt from something that actually ran, and lands nothing without an explicit approval. It is stated as one target rather than a feature list because the parts are worthless separately: work without proof is a guess, proof without approval is not owner control, and neither matters if it cannot be reached from the device the work actually happens on.
Why it matters
Everything else in this record is a component. This is the thing the components are for, and it is deliberately the same loop the principles page describes — capture, act, verify, approve — closed once, on a real project, rather than argued about. It is also the honest test of the founding condition: a phone is what remains when a laptop fails, so a system that only works from a desk has not solved the problem it was built for.

Unresolved

Open
Not built. This entry is a target, not a report — the status is proposed and nothing in it should be read as working.
Open
Several parts exist and are recorded separately in this log. Several do not, notably approving from a phone. The gap is real and is not narrated away here.
Open
The bar is deliberately reliability with graceful, honest failure — not correctness on every task. What counts as reliable enough has not been fixed to a number.
Open
Multi-user, teams, and fully autonomous work are explicitly out of scope for this target.

Enables next

Next
A single acceptance test that means something: a genuine change to Sidera's own code, directed from a phone, proven and approved, repeated across ordinary days rather than demonstrated once.
Entry notes

Most of this record is components. This is what they are for.

The target is one sentence: from a phone, with no terminal and no jargon, direct real development work on real projects — including Sidera’s own code — have Sidera do the work on the cheapest model capable of it, prove it honestly, and approve the result before anything lands.

It is written as a single target on purpose. Split into features it becomes six things that could each be called done while the whole remains useless: work without proof is a guess, proof without approval is not owner control, and neither is worth anything if the only way to reach it is a terminal.

This is not built. Some of it exists — the parts that do are recorded separately in this log, with their own bounds. Approving from a phone does not. The honest state is a target with real components under it and a real gap between them.

The acceptance test is deliberately unglamorous: not a demo, but a stretch of ordinary days in which genuine changes are directed from a phone, proven, approved, and landed — including at least one change to Sidera itself. Anything less is a screenshot.

← Back to the build record