Audit cohort transitions
Test stocking, transfers, grading, splits, merges, mortality, escape, harvest, sale, disposal, relabeling, and historical corrections.
SITE · STOCK · WATER · FEED · LIFECYCLE
Aquaculture data becomes accountable when each observation remains connected to the correct site, production system, stock or cohort, method and device, time and place, water and operating context, feed or intervention, model version, staff finding, authorized decision, outcome, access, correction, and retention state.
Visual explanationA diagram or operating scene makes the relationship visible.
Structured modelA flow, comparison, capability set, or boundary map organizes the idea.
Guided explanationOriginal prose connects the concept to its operating context.
FAO provides digital-aquaculture and planning context, USDA APHIS connects water quality, aquatic livestock health expertise, surveillance, and biosecurity, and NIST provides broader connected-system context. These sources support a governance framework, not one universal aquaculture database.
Identity may include farm, lease, pond, cage, tank, raceway, loop, water source, species, strain, cohort, lot, life stage, supplier, movement, feed, device, sample, treatment, harvest, mortality, waste, staff, and service records.
Test stocking, transfers, grading, splits, merges, mortality, escape, harvest, sale, disposal, relabeling, and historical corrections.
Keep raw, calibrated, normalized, aggregated, modeled, manually entered, corrected, deleted, and exported states traceable.
Control farm, health, laboratory, feed, equipment, service, regulator, certifier, processor, research, customer, API, support, and administrator access.
Review export, identifiers, units, files, history, integrations, vendor change, credential revocation, retention, deletion, backups, and emergency offline records.
No aquatic-health, biosecurity, food-safety, environmental, traceability, privacy, ownership, or legal advice is provided.Use current farm programs, qualified experts, agreements, laboratories, security professionals, and applicable authorities.
Data models differ across species and systems.Production method, country, identifiers, regulation, market, certification, devices, laboratories, and integrations require explicit mapping.
Access does not prove quality or authority.Users still need provenance, validation, context, least privilege, qualified interpretation, and accountable decisions.
Follow incoming and outgoing relationship records to understand what supplies, informs, enables, coordinates with, or extends this technology in the published knowledge graph.
04connections visible
Water, stock, feed, equipment, environmental, alert, staff, intervention, and outcome records need governed identity and provenance.
A data-management layer can preserve current RAS configuration, stock context, observations, alarms, controls, maintenance, failures, interventions, recovery, and changes.
Cohort, biomass evidence, feed identity, authorized plan, commands, delivery observations, inventory, water context, exceptions, and outcomes need a connected lifecycle.
Site, stock, feed, water, health, biosecurity, equipment, environment, access, provenance, correction, retention, and accountability intersect with wider farm-data governance.
Follow stock and production-system identity through water sensing, sensor quality, RAS resilience, feeding reconciliation, remote environmental context, and governed aquaculture records.
Preserve site, system, stock, water, feed, observation, alert, biosecurity, action, outcome, access, correction, export, and retention context.
This original briefing uses FAO, USDA APHIS, and NIST digital, health, biosecurity, and connected-system context. It provides no health, food-safety, environmental, traceability, privacy, ownership, security, or legal conclusion.