North of Summer

Story × Technology

Scroll to begin ↓

SCENE 01 · Story

Story is upstream.

Every system begins with a premise. What this work serves. What it protects. What it is for. That premise sets the direction of everything that follows.

Location
Misool Marine Reserve
S 02.24° · E 130.56°
Destination
Piaynemo
0.5642° S · 130.2708° E
Conditions
Partly cloudy
27°C air · 29°C water
0.3 m seas in lee
SE 3–5 kt
20–25 m
Crew arrival
Most on deck
06:32 · UTC+9
Boats at dock
Fuel & batteries ready
04:00 · UTC+9
Gear laoded
05:52 · UTC+9
#sunrise
Run Sheet
Ops Active
Field frame illustration for Misool shoreline
Radios & signals ready Boats fueled Final checks

SCENE 02 · Technology

Field Log · Low Pass Over The Islands

Technology gives it form.

Technology is the material of execution. It turns intent into interfaces, data, and behavior. It makes the work tangible.

Comms offline
Piaynemo · Raja Ampat
Drone Pilot 06:14:05

Dawn layer thinning. Holding steady 👍

Captain 06:14:14

Copy. Maintain orbit.

Drone Pilot 06:14:22

RT captain. Keeping lens on ridge.

Captain 06:14:35

Make this pass then return for battery swap.

DJI Mavic 3 Pro
Live
Field moment hero asset
06:14:32
N 63.99° · W 22.55°
70mm · f/2.8 · 1/250 · ISO 100

SCENE 03 · Architecture

Architecture defines the structure.

Architecture determines how parts relate.

Where boundaries sit.

How components connect.

What can evolve within the frame.

It sets the shape the system grows inside.

  • - GPS + timestamp lock at the moment of capture
  • - Offline logging when the signal drops out
  • - Notes and tags recorded where the story actually happens

Shot Log 03B

Location: Piaynemo · On-site capture

Context: Logged during surface operations.

Device: Mobile app · Local session

Capture Log
Offline
02°24' S · 130°56' E
Linked media · 1 /1
Tags
Note

SCENE 04 · Systems

Data in the field

Systems emerge from architecture.

Systems are the living expression of architectural decisions.

They carry the structure into operation — into teams, workflows, and change.

  • - Multiple operators running Capture Log on their phones, each logging from their own angle.
  • - Video crews dragging SD cards back on deck; clips and stills attach once they’re within reach.
  • - BTS phone video, quick notes, and crew comms landing in the same lane as the “hero” shot instead of disappearing into random chats and folders.
Lagoon pass · edge view First light · Misool
Media
Hero clip + stills
Camera and drone passes tied together as one moment in the lagoon.
Notes
Shot notes · surface ops
Subject, dive number, and operator intent collected across the crew.
Telemetry
GPS + UTC drift
Coords, device time, heading, and link health bound to the same pass.

The timeline can arrive out of order, late, and in pieces—but the moment stays singular. Everything the crew records about this pass stacks up on devices at the edge, and only then crosses as a single POST /moment into the machine.

Ingress diagram
Devices · Capture Logs · /moment
Camera
Housing · 4K log
Drone
Manta pass · top-down
Op · Phone 01
Shot notes · surface ops
Op · Phone 02
Alt angle · timing
Capture Log · A
Deck
Media + notes · boat deck
Capture Log · B
Chase
Notes + telemetry · chase boat
API
POST /moment
Every device’s view of this pass converges here. Next scene: inside.
Media
Notes
Telemetry

SCENE 05 · Coherence

System runtime

Coherence aligns the whole.

Coherence is when the parts reinforce each other.

New work builds on existing shape. Change fits within the structure. Teams move within shared understanding. Coherence is alignment over time.

  • The Spine System runtime Extract, transform, and load move media, field notes, and signals together, in lockstep, without scattering through queues.
  • The Archive Durable store Core storage and cold backup hold the moment intact, so downstream tools read from the same anchored source.
Moments in The Spine
One identity, addressable in time, end to end

Signals move together along a single path and remain bound to the same moment throughout the system.

Because devices change. Formats change. The Spine does not.

Hero asset in system map
Shot 03B from Misool enters once and leaves as a stable object in storage; every downstream tool is just reading along the same spine.
System map
Devices · API · System spine
CAMERA
R5C housing · 4K log
CAPTURE LOG
Shot notes · tags · 03B
DRONE
Manta pass · top-down
API
/moment
Single POST boundary
EXTRACT INTAKE
Validate · accept moment
TRANSFORM PROCESS
Clean · align · derive metadata
LOAD ARCHIVE
Core storage · anchored
BACKUP COLD
Off-path replica
Media
Field notes
Signals

SCENE 06 · Fractional Architecture

Return
Story taking shape
Narrative surface placeholder — moments held together long enough for relationships, sequences, and intent to emerge.
Sequences
Moments seen together
Beats
Patterns becoming legible
Context
Never stripped away

Narrative Return

Stewardship over time.

Architecture benefits from continuity.

Fractional Architecture places upstream architectural thinking inside a team across sustained arcs — guiding boundaries, reviewing structural decisions, and maintaining alignment as the system evolves.

Continuity
Story stays grounded
Story forms from intact moments - the field never goes quiet.

SCENE 07 · North of Summer

Studio

North of Summer works at the intersection of story and technology — inside the decisions that shape everything downstream.

Practice
  • - Expedition and documentary systems
  • - Research and conservation tooling
  • - Editorial and narrative infrastructure
  • - Media pipelines and data transformation
  • - Field → ingest → narrative architectures
North of Summer operates where the wild is still raw, systems bleed, and the story forms anyway. Story × Technology. Upstream by design.