TECHNOLOGY

There's a discovery engine behind the map.

Atrium aims to produce more meaningful local discovery within a user's context, rather than simply show the closest thing.

Explore the ProjectResearch / Hypothesis
05TECHNOLOGY

There's a discovery engine behind the map.

Atrium aims to produce more meaningful local discovery within a user's context, rather than simply show the closest thing.

Research / Hypothesis
Location

Where?

Time

When?

Community

With whom, and around which interests?

Physical Context

What's happening in the area right now?

ATRIUM ENGINE
Relevant Local Discovery
01

Dynamic Proximity Ranking

Distance alone does not create meaningful discovery. Atrium is researching how distance, time, community context and physical activity signals can be considered together.

02

Privacy-Preserving Spatial Processing

We are working on dynamic spatial privacy methods that reduce exposure of precise user locations while preserving location utility.

03

Physical Action Verification

We are researching ways to measure whether digital discovery turns into physical action without relying on a single GPS signal.

04

Contextual Trust & Identity

We aim to vary the information shown and permissions granted according to identity verification level, behavioural trust and interaction context.

Explore the technology
IMPLEMENTATION

Every layer has a job in the product.

Technology layers found in the existing Atrium source tree. This list is not a production environment or load-test result.

01

Flutter

Mobile discovery and physical interaction experience.

Source evidencemobile/pubspec.yaml
02

Node.js / TypeScript

Server authority, API contracts and product services.

Source evidencebackend/package.json
03

PostgreSQL / PostGIS

Relational modelling and spatial query infrastructure.

Source evidencebackend/migrations/1784206757362_initialize-database.sql
04

Redis

Tools for shared fast state and service coordination.

Source evidencebackend/package.json
05

WebSocket

Transport for messaging and real-time interaction.

Source evidencebackend/package.json (ws)
06

Mapbox

The visual layer for mobile maps and spatial context.

Source evidencemobile/pubspec.yaml (mapbox_maps_flutter)
RESEARCH & DEVELOPMENT

Atrium is a product we're building. And a set of technical hypotheses we're testing.

H1Research / Hypothesis

Can a dynamic proximity model create more meaningful physical action than distance-only discovery?

EXPERIMENT APPROACH

Compare a distance-based control with context-based ranking in a pilot.

MEASUREMENT

Meaningful discovery and physical action per eligible session, considering cohort and regional supply.

H2Research / Hypothesis

How much discovery utility can be preserved as a user's spatial privacy level increases?

EXPERIMENT APPROACH

Evaluate different levels of spatial precision in controlled scenarios.

MEASUREMENT

Discovery utility and re-identification risk, with separate tests for sparse regions.

H3Research / Hypothesis

Can combining several physical signals provide more reliable physical action verification than a GPS-only approach?

EXPERIMENT APPROACH

Compare GPS-only verification with user consent and additional physical signals.

MEASUREMENT

False positives / negatives and data minimisation; measure verification quality without sharing raw location.

H4Research / Hypothesis

Can dynamic permissions based on identity trust, behavioural risk and interaction context reduce abuse while preserving legitimate social interaction?

EXPERIMENT APPROACH

Design progressive permissions experiments by task and risk context.

MEASUREMENT

Reviewed abuse incidents alongside legitimate interaction and verification friction.

We do not claim these hypotheses are already proven. Atrium's R&D approach is to measure them with pilot data.

ResearchExperimentMeasurement

What we measure defines what we can claim.

Behaviour and safety measures planned for the pilot. These are not current results, target rates or success charts.

Planned
  1. 01Local active user density
  2. 02Discovery to meaningful interaction
  3. 03Interaction to physical participation
  4. 04Repeated physical participation
  5. 05Community and event continuity
  6. 06Quality of business interactions
  7. 07User-perceived trust
  8. 08Reporting and moderation response time
  9. 09Clarity of privacy choices
PRIVACY-FIRST

Be nearby. Without becoming an exposed target.

A user's real GPS coordinates are not shared with other users, community managers or businesses.

Atrium aims to use approximate distance, spatial areas and privacy-safe aggregation wherever possible.

  • No sharing of precise coordinates.
  • Businesses see aggregated insights only.
  • Spatial precision may be reduced when user density is low.
  • Participation does not automatically have to reveal a public identity.
Private account / location
Permissions and visibility boundary
Approximate local context

Aggregated information · user control

Architecture diagram; no real account or GPS data.

ATRIUM

Nearby life doesn't have to stay invisible.

People.
Communities.

Events.

Businesses.

Opportunities.

In the same surroundings. On the same network.

What's happening around you?

Sometimes, what lies in between becomes the centre.