Operator / Alpha-07
5 ACTIVE SoIs
Role · team · mission · clearance · task
SoI™ / Spheres of Influence
Zero trust.Now spatial.
Persistent, context-aware security boundaries for every person, place, thing, system, and autonomous agent.
SoI turns identity into a dynamic virtual force field—continuously deciding what may enter, what may leave, what may be seen, and what may act.
01IDENTITY
02PROXIMITY
03POLICY
04ACTION
01 / The security primitive
Every boundary begins
with an identity.
At the center of every Sphere of Influence is a persistent eVa address.
eVa resolves what an entity is across space, time, system, and operational plane. SoI applies policy around that identity—so trust follows the entity instead of disappearing at the next network, application, facility, vehicle, or simulation boundary.
PUBLIC / MISSION
SOCIAL / TEAM
PRIVATE / ENTITY
eVa CORE
ONE IDENTITY / MULTIPLE BOUNDARIES
Not a fence around data.
A policy field around reality.
eva://mission.logistics-servicing-launch-02/operator-alpha-07Default deny
Continuous verification
Least privilege
Policy inheritance
02 / Dual-use by design
One primitive.
Two operating depths.
Commercial users need simple, legible control. Defense and government missions need many nested, composable boundaries with far more granular policy and authority.
COMMERCIAL / CONSUMER
Control what the world may know.
PRIVATE
Me, my devices, my protected data
SOCIAL
People and services I approve
PUBLIC
What I choose to make visible
One person can carry a simple set of boundaries across the real world, the experience layer, and virtual environments—revealing only what they authorize.
DEFENSE / GOVERNMENT
Control the mission at every layer.
01MISSION
02ORGANIZATION
03TEAM
04PERSON
05PLACE
06RIG
07PAYLOAD
08DATA
09ACTION
POLICY COMPOSITION
Nested boundaries resolve together at the moment of action.
U → SAP
Classification-aware
EDGE → ORBIT
Location-aware
HUMAN → AI
Agent-aware
03 / Defense granularity
Every mission entity
carries its own boundary.
People, locations, Rigs, payloads, sensors, software, and autonomous systems can each hold multiple SoIs—nested, inherited, time-bound, and continuously evaluated.
Launch Position / LP-02
4 ACTIVE SoIs
Range · pad · hazard · access
Launch Rig / BF-01
6 ACTIVE SoIs
Vehicle · bay · subsystem · telemetry
Payload / PL-04
7 ACTIVE SoIs
Owner · handling · mission · data · state
Drone / SD-07
8 ACTIVE SoIs
Operator · corridor · range · action · proximity
WHO
Identity, organization, role, authority
WHAT
Entity, data, capability, requested action
WHERE
Position, zone, proximity, trajectory
WHEN
Instant, interval, mission phase, expiry
CONTEXT
Plane, risk, posture, classification
04 / Dynamic policy fields
Collapse to identity.
Expand to mission scale.
SoIs are not fixed geometry. They contract, expand, inherit, and compose as risk, proximity, authority, and mission phase change.
The station, rover, and Moon each retain an independent eVa-centered boundary. When operations intersect, policy resolves the layers together without merging or replacing identity.
LUNAR SoI / MISSION THEATER
ROVER SoI / SURFACE OPS
eVa
STATION SoI / LIVE
6 NESTED LAYERS
POLICY FIELDS COMPOSING
Station, rover, and lunar theater boundaries remain sovereign. Shared operations are authorized only at their policy intersection.
01
ENTITY
Persistent eVa core
02
SYSTEM
Crew + critical systems
03
VEHICLE
Station-wide authority
04
MISSION
Current task + manifest
05
CORRIDOR
Orbital approach volume
06
THEATER
Coalition lunar operations
05 / The approach decision
Identity meets proximity.
Policy decides.
A servicing vehicle does not become trusted because it reached the satellite. Its eVa identity, authority, mission role, trajectory, time window, and requested action must resolve before entry.
COMPANY A → COMPANY B
Two owners. Two eVa identities. One governed approach.
LIVE POLICY RESOLUTION
01Resolve vehicle eVa
02Verify asserting authority
03Match approved mission
04Evaluate approach corridor
05Check time + action scope
APPROACH ACCEPTED
eva://orbital/company-a/servicing-drone-07
REQUEST: approach / inspect / 12 minUNRESOLVED VEHICLE
The second vehicle cannot resolve required identity and authority claims. Its SoI remains outside the protected boundary.
APPROACH DENIED
DISCOVER
Detect the approaching entity and its boundary.
RESOLVE
Determine persistent identity and asserting authority.
EVALUATE
Compose both parties' policies in current context.
ENFORCE
Permit, constrain, redirect, quarantine, or deny.
06 / Every operating context
The boundary persists.
The context changes.
The same eVa-centered SoI model can govern the physical world, the interfaces people experience, and the virtual systems used to model, automate, and command operations.
REAL WORLD
People, facilities, vehicles, payloads, sensors, and moving assets carry boundaries through physical space.
EXPERIENCE
Interfaces reveal only the controls, content, and actions appropriate to the user's present context.
VIRTUAL
Digital twins, simulations, AI agents, and data objects inherit the same identity-bound policy model.
PHYSICAL
IDENTITY + SoI
LOGICAL
IDENTITY + SoI
PLAN
IDENTITY + SoI
COMMAND
IDENTITY + SoI
SIMULATION
IDENTITY + SoI
07 / Policy in motion
Not access once.
Trust continuously.
Every change in identity, proximity, posture, authority, time, plane, or requested action can trigger a new policy decision—without breaking the entity's continuity.
RESOLVE IDENTITY
What is approaching?
Resolve the persistent eVa identity and all authoritative claims.
→
COMPOSE CONTEXT
What is true now?
Intersect identity, location, time, plane, risk, role, and intent.
→
ENFORCE ACTION
What may happen?
Allow, constrain, redirect, mask, quarantine, revoke, or deny.
The entity keeps one identity. Its boundary adapts to the mission.
Identity at the center. Trust at every boundary.