Know the setting
Site → habitat → stockConnect the production stage and stock before a feeding check.
AquaOS / The operating layer
Connect production, decisions and outcomes.
Bring stock, feeding, water observations and follow-ups into one operating history—so your team can see what changed and what needs attention.
In development · proposed operator beta
A concrete operating example
A feeding observation becomes a trackable follow-up.
Illustrative prototype · sample habitat B-12- ObservationFeed refusal notedMorning round · operator source
- ReviewWhat needs checking?Earlier feeding and water context missing
- TaskInspect habitat B-12Round operator · next inspection
- OutcomeRecord the next responseKeep the observation with the same history
Why an operating layer?
Every decision has
a production context.
Seed and stock, production stage, water, feeding and labour all shape the work. Connecting the records helps teams see what happened, what they chose and what still needs checking.
The intended operating loop
One connected production cycle.
- 01
Production setting
Habitat, stock & water - 02
Observe
Operator records / CrabSense - 03
Understand
AquaOS context & records - 04
Decide
Operator review - 05
Act
Operator / CrabPod - 06
Learn
Outcome & operating history
Each outcome becomes context for the next decision.
Designed around the operator
Make the daily work
easier to follow.
Four connected jobs for the proposed operator workspace.
Keep the work connected
Feeding · water · moltBring observations from successive rounds into the same history.
Review the next step
Evidence → operator → taskShow the observation behind a pending inspection and any missing context.
Close the loop
Action → follow-up → historyKeep a later observation, weight or transfer connected to the same stock.
The operator experience
A workspace to see the work.
A copilot to ask about it.
The planned copilot draws on operating records, showing both its evidence and missing information.
Help shape the operator betaIllustrative copilot question · planned capability
“What changed since the last feeding check, and which follow-up is still open?”
Sample record trail
B-12: feed refusal recorded → inspection assigned → follow-up observation still missing.
What you can explore and what comes next
Build the foundation.
Prove each connection.
Beta interest starts a fit discussion. Product access, physical integration and production benefits each depend on the agreed scope and validation.
Illustrative workflow
Try the public sample. It saves no farm records and controls no equipment.
One useful daily routine
A focused workspace for context, observations, follow-ups and record-grounded assistance. Scope and participant fit are being planned.
Connected physical work
Connect CrabSense and CrabPod after testing permitted actions, hardware integration and production outcomes.
From records to evidence
A response needs
an outcome.
Connect the action to what happened afterwards. A recorded task alone cannot show a biological result.
Measure the production question.
Survival, growth, water, labour and economics guide what we observe and validate.
Explore research & validationBring a real operating routine.
Help shape the first useful AquaOS workflow around your production setting and daily work.