Today
Field notes and photos exist, but donor source, zone context, and outcomes are often disconnected.
ReefLogic Deep Dive
One scroll from overview to architecture
This page connects the full ReefLogic operating concept in one sequence: why teams move beyond fragmented field memory, how decisions are validated in context, and how a managed local-first stack keeps operations resilient.
Deep Dive Sections
Overview
Why teams shift from fragmented field notes to reusable operational memory.
Operations
How reusable maps, one coral record, and one workflow align daily execution.
Concept
How connected objects and rule evaluation turn raw inputs into clear guidance.
Model
How lineage, movement, events, and identity rules stay consistent at scale.
Flow
How donor-to-reuse lifecycle, tracking, sync, and updates operate as one cycle.
System
How diver edge, tracking, topside sync, backend services, and GIS fit together.
Local-First
How managed backend control and local-first clients balance resilience and governance.
01 Overview
From fragmented field memory to reusable program memory
Reef teams are skilled, but critical context is often split across slates, notebooks, chats, and disconnected files. ReefLogic converts those fragments into shared memory that can be reused from one mission to the next.
With ReefLogic
Site, zone, donor, event, and health history stay attached to one continuous record chain.
Operational result
Less reconstruction, faster handover, and fewer high-impact decisions made from partial memory.
02 Operations
One map. One coral record. One field workflow.
ReefLogic unifies spatial context, coral identity, and mission execution so managers, divers, and scientists work from one model instead of parallel files.
Plan
Choose site, zone, donor source, and operational constraints before the mission starts.
Capture
Record location, health, photos, lineage context, and event details in one field workflow.
Validate
Apply spacing, density, genotype, and relocation checks before final commit.
Reuse
Use the same records for dashboards, scientific review, funding reports, and next dives.
Managers
Plan faster, enforce standards, and maintain cross-season continuity with clear audit trails.
Divers
Get clearer pre-dive tasks and reduce repeated writing after surfacing.
Scientists
Analyze cleaner lineage and monitoring histories with stable spatial context.
03 Concept
Connected operational objects with rule-based guidance
ReefLogic is a connected operations model, not a document archive. This object chain preserves context from planning through monitoring, and each candidate action is checked before commit.
- Site
- Zone
- Donor
- Planting
- Observation
Input layer
Candidate location, site/zone context, genotype, nearby plantings, and current density state.
Rule layer
Allowed genotype, forbidden proximity radius, zone capacity limits, and relocation constraints.
Decision outputs
Valid, warning, or blocked results with explicit reasons so teams can act before errors reach the reef.
04 Model
Separate lineage history from spatial movement history
The model stays stable at scale by separating biological descent from spatial movement and storing each change as an append-only event.
Lineage history
Tracks who came from whom across generations: source colony, units, and child fragments.
Movement history
Tracks where each coral unit moved: donor site, nursery slot, reef zone, and relocation path.
Event + identity semantics
Move keeps ID, split creates child IDs, and current state is derived from latest valid events.
05 Operational Flow
Lifecycle flow as a continuous cycle
- Donor
- Nursery
- Outplant
- Relocate
- Reuse
Biology and geography move together: collect from donor sources, place under rules, correlate with track data, sync safely, then search and update from the same records.
Collect
Create the first managed unit from donor source with clear session and location context.
Split + Place
Create child fragments and place them in nursery or reef zones under rule checks.
Correlate + Sync
Align event timestamps with diver tracks, then merge and validate into shared history.
Search + Update
Query by donor, unit, genotype, site, or zone and append health or relocation updates safely.
06 System Stack
Coordinated field-to-backend architecture
ReefLogic is not one app or one device. It is a field-to-backend chain that turns mission activity into durable program memory.
Diver edge
Underwater/mobile capture of photos, forms, donor context, health status, and local event IDs.
Tracking layer
DiveTrack transponder and command stack add diver awareness, position traces, and mission timing.
Topside sync
Session logging correlates phone events with tracks and prepares coherent merge batches.
Backend services
Sync, validation, rules evaluation, search APIs, tenancy controls, and full audit history.
GIS/data layer
PostGIS stores site and zone geometry, channels, nurseries, coral points, and spatial query context.
Persistent operations
Teams can search, inspect, and update over time so records remain operational, not archival.
07 Managed Local-First
Managed backend with resilient local operation
ReefLogic is not browser-first SaaS. Clients keep working with local storage and map cache when connectivity is weak, while managed services handle provisioning, backups, governance, and tenant controls.
Local continuity
Desktop/mobile clients store event logs, photos, and map context offline, then sync deltas when links return.
Managed control plane
Central services handle provisioning, updates, backups, validation, and tenant administration.
Controlled collaboration
Workspaces stay private by default, with explicit grants for regional maps or shared study datasets.
Next Step
Bring ReefLogic into your restoration program
We can map your current workflow to this model, identify quick wins, and define a rollout path that works in real field conditions.
FAQ
Deep Dive questions at a glance
Is ReefLogic only for large organizations?
No. The platform supports NGOs, community teams, research programs, and multi-site operations.
Can teams work with weak or no connectivity?
Yes. Field clients operate local-first and synchronize safely when internet becomes available.
Can data stay private while selected sharing is enabled?
Yes. Workspaces remain private by default, with explicit controls for project-level or dataset-level sharing.
Where do I get support for deployed instances?
Use the support portal and guidance links on the Support page.