SteadSense
Know what comes next.
One record for the whole homestead cycle: property, soil and water, planning, planting, animals, daily care, harvest, preservation, and the pantry. It stays readable with no signal, it shows the source behind a recommendation, and it declines the questions it cannot answer safely.
Closed testing is being prepared and has not opened. There is no opt-in link yet; when there is, it appears here.
Why it exists
A small homestead is not a hobby with a to-do list.
It is a set of deadlines written by weather, biology, and daylight, and most of them are irreversible. The record of it usually lives in a drawer of unrelated notes, three apps that do not know about each other, and someone's memory. The consequence is not untidiness; it is a bed planted a fortnight late, or a preservation run improvised from a half-remembered time and pressure.
A working system for a small homestead, roughly a tenth of an acre up to ten. It connects property, soil and water, planning, planting, animal readiness, daily care, harvest, preservation, and the pantry into one cycle, instead of a drawer full of unrelated notes.
Who it is forSmallholders working somewhere between a tenth of an acre and ten, who want the reasoning as well as the answer, and who work in places where the network is not a given.
What it solves
Today
The day, and the weather that decides it
Today opens on sync state, what is urgent, and a live National Weather Service forecast for where you actually are, with the source and the retrieval time printed next to it. Emergency and Ask are one tap away rather than buried in a menu.
Priority
Ranked by what happens if you wait
Every task carries its class, its deadline, and the consequence of delaying it; an irreversible weather deadline with twenty minutes left reads differently to a chore. The reason codes behind the ranking are shown, so you can disagree with the order on the evidence.
Place
Tied to the ground you actually have
One property record: household, resolved hardiness zone, growing areas, beds and orchards. What has not been measured is marked unknown rather than filled in with a plausible default: dimensions not recorded, sun unknown, irrigation unknown.
Harvest and pantry
From the bed to the shelf, as one record
Harvests, preservation runs, and pantry stock are a single continuous record, with best-by dates that come from your own source. Process parameters come only from approved, revision-pinned recipes; a run with no matching recipe is labelled no-recipe rather than improvised.
Don't invent certainty
It refuses rather than guesses
Ask answers from your own records and approved guidance, never from general model knowledge. Canning parameters, doses, wild-food identification, water safety, and legality are declined on purpose, with the declined category named. The refusal is the feature.
No signal
The packet that works when nothing else does
Eight scenarios (power outage, severe weather, water loss, fire evacuation, animal emergency, injury, equipment failure, security), each holding the plan you wrote, stored on the device and readable with no connection at all. SteadSense supplies the structure and is explicit that it does not supply the procedure.
Designed differently
-
Readable without a signal
The homestead record and the emergency packet live on the device. Connectivity improves the app; it is not a precondition for it.
-
Guidance carries its provenance
You can see the source behind a recommendation before acting on it, including the retrieval time on live data.
-
A person approves before you see it
Nothing reaches the app straight from a research pipeline. Draft, approved, published, with a human gate in the middle.
-
Conflicts are preserved, not merged
Changes made offline are kept and pushed when connected; conflicting edits are held for manual review rather than silently merged.
-
Unknown is a value
Unmeasured properties read as unknown. The app does not fill the gap with a plausible default and let you act on it.
Under the hood The technical surface, without the implementation
- Offline-first store with conflict-preserving synchronisation
- Location- and season-aware task engine with reason codes
- Evidence provenance on every piece of guidance
- National Weather Service integration with retrieval timestamps
- Human-reviewed knowledge pipeline: draft → approved → published
- Refusal policy for safety-critical domains
Availability
- Status
- In development
- Platform
- Mobile · Offline-capable
- Price
- Free when closed testing opens
Closed testing is being prepared and has not opened. There is no opt-in link yet; when there is, it appears here.
Questions or problems? steadsense@deadstarlabs.com