Skip to content
CrabionicsDiscuss a project

System explainer

From an observation to a useful operating history

How production context, operator oversight and recorded responses fit together.

Crabionics · 3 minute read · Planning guide

A reading needs a setting

An environmental observation becomes more useful when it is linked to the pond, production unit or cohort it describes. Timing, equipment condition and handling events provide the context for interpreting what happened.

Decisions have responsibilities

Crabionics’ operating design places decisions and defined rules under operator oversight. Where local control is appropriate, a bounded command connects a decision to equipment. Its acknowledgement and subsequent observations help the team review the response.

Permitted actions, local equipment and escalation responsibilities need to be defined and tested for each integration.

A command and an outcome are different observations

Equipment acknowledgement can show that a request was received. A subsequent observation helps establish what changed in the setting. Biological performance and production value require their own measurements over the relevant period.

Keeping these records together supports review without treating a technical response as proof of a biological or commercial result.

The current development boundary

AquaOS software foundations cover observations, operating records, execution requests and event history. Physical integration is in development, and a complete biological control loop remains to be demonstrated.

This guide describes the scoping approach. The operating design and proposed production connections remain subject to development and validation in defined settings.

AquaOS / Explore the direction

Connect the daily work to the next decision.

AquaOS is our developing operating layer for mud-crab production: context, observations, operator decisions, actions and outcomes. Explore one sample round, then help shape a useful operator beta.

01
Explore now

Illustrative operator workflow

Sample preview available
02
Shape next

Daily operator work, history & grounded assistance

Early-access interest
03
Validate later

Physical integration in defined settings

In development

Let’s start with your production setting.

Bring your role, region and production question.

Discuss a production project