Interactive briefing · desktop recommended
VASTE / Electronic Artefacts
Most systems are isolated. VASTE is built to execute connected reality.
A graph-native runtime for organizations, interfaces, agents, knowledge, and infrastructure.
You are exploring a demo of the VASTE logic layer and its strategic direction, not the full operating system.
⇅ To navigate, use the mouse wheel, keyboard arrows, or the rail on the right.
Electronic Artefacts
The studio behind VASTE, designed to turn experimental systems into a coherent runtime vision.
Joey-Néot Marquet, founder & CTO
Execution
Design · Architecture · Development
One builder stack, kept coherent across product, narrative, and implementation.
Why current systems fail
Fragmented tools. Static architectures. Incompatible systems.
Every new workflow adds another integration, another copy of state, another place to drift. AI agents make the gap more visible because they need dynamic, governed environments, not isolated apps.
Why now
Everything is becoming dynamic.
Agents, real-time data, adaptive interfaces, and connected environments need a runtime, not another app.
Core insight
Everything becomes executable.
Organizations. Interfaces. Agents. Knowledge. Infrastructure. Research. Simulations. Same substrate. Same runtime. Same primitives.
Answer
An execution substrate, not an application.
VASTE is graph-native, modular, and built to unify connected systems on one operational base instead of a stack of disconnected products.
Substrate
Runtime
Orchestration
The grammar
These primitives can map organizations, interfaces, agents, knowledge, and infrastructure into a common substrate.
VASTE
Everything becomes executable.
A graph-native runtime for connected systems, adaptive surfaces, and orchestration logic.
0 selected
Tap rows to focus. On touch, tap empty space to create a vertex and tap a vertex to open its Environment.
Runtime primitives
Tap rows to focus, drag vertices in place, and explore how Environment and surfaces shape the graph.
Desktop: right-click to edit. Mobile: use Actions for color, type, and delete. This is the live logic layer, not the full system.
Same substrate.
Many surfaces.
Architecture
Progressively layered, not cognitively overloaded.
Start with the substrate, then the runtime, then the primitives, then orchestration, then the surfaces. The audience does not need the whole internal machine at once.
Substrate → Runtime → Primitives → Orchestration → Surfaces
Inside the substrate, vertices and ties define topology. Above it, native systems and premium capacities stay modular.
Surfaces
Public projections
Pages, interfaces, deployments, visible output.
Runtime
Execution layer
Deterministic events, state, replay.
Primitives
Native systems
The minimum grammar for execution.
Orchestration
Extension logic
Routing, policy, agents, and coordination.
Substrate
Canonical graph
Vertices and ties only.
Hover a layer or move across the canvas to bias the corresponding part of the architecture.
Workspace
Actor
Assets
Surface
Realtime
Runtime model
Included runtime / premium capacities
The kernel stays bundled. Premium capacities extend the runtime only when the deployment needs more orchestration, cognition, publishing, or physical integration.
Workspace, Actor, Asset, Knowledge, Surface, Security, Realtime, Analytics, Collaboration, runtime orchestration, event system, and graph runtime are native. Flow, Program, Studio, Intelligence, and Perception expand the system.
Included runtime
Kernel native
These systems are not upsells.
They are the base runtime that every deployment inherits.
Workspace
Actor
Asset
Knowledge
Surface
Security
Realtime
Analytics
Collaboration
Graph runtime
Native systems
Always included
01
Native
Workspace / Collaboration
Shared runtime space for teams, sessions, and coordinated work.
Included runtime
Native
02
Native
Actor / Orchestration
Execution identity, runtime relationships, and the primary scaling unit.
Included runtime
Scale
03
Native
Asset / Knowledge
Files, data, and semantic memory anchored directly in the graph.
Included runtime
Memory
04
Native
Surface / Security
Projection layer and governance at the edge of every visible system.
Included runtime
Governed
05
Native
Realtime / Analytics / Events
Live state, telemetry, and the response layer that keeps the runtime current.
Included runtime
Live
Premium capacities
Extensions
Automation, orchestration, and execution chains.
Logic systems, scripting, and custom behavior.
Editing, deployment, publishing, hosting, domains.
Runtime cognition, agents, and reasoning systems.
Sensors, devices, and environmental integration.
Deployment logic
Studio is the deployment layer.
The runtime stays deterministic. Studio turns it into something you can edit, publish, host, and deploy on managed or sovereign infrastructure.
That gives the deck an execution story the investor can understand without reducing the system to a generic app.
Studio → Runtime → Governance → Graph → Deployment → Assets
Studio
Deployment surface
studio / deploy
Editing · deployment · hosting
Design the visible layer
Pages, apps, domains, published surfaces.
Studio
Hosting
Domains
01
Deterministic
Runtime
Replayable execution, stable state transitions, and explicit event routing.
events / state / replay
Live
02
Wedge
Studio
Editing, deployment, publishing, hosting, and domain orchestration in one layer.
main wedge / onboarding
Deploy
03
Topology
Electronic Artefacts Cloud
Managed infrastructure for teams that want the fastest path to deployment.
hosted / managed
Cloud
04
Sovereign
Self-Hosted Runtime
Client-owned infrastructure for enterprise control, sovereignty, and scale.
Enterprise
Owned
Premium
Deployment modes
Cloud or sovereign runtime
Electronic Artefacts Cloud for managed delivery. Self-Hosted Runtime for client-owned infrastructure.
Managed
Sovereign
Enterprise
Hosted
Client-owned
Premium
Actors are the scaling unit.
More actors, more orchestration, more runtime relationships.
Immediate use cases
Systems that need a runtime, not another app.
Perception
Environmental systems, made executable.
Sensors · devices · domotics · industrial feedback
One substrate.
Many deployments.
One operating grammar.
The break is structural.
Move from apps stitched together to a runtime that can absorb change.
Material archive
Vestiges
A flagship material archive built with the same discipline: provenance, curation, and premium systems thinking.
A curated field of rare objects, fragments, and digital traces.
@vestiges.worldPhases
Knowledge
Discovery
Curation
Distillation
Marketplace
Premium flow
Knowledge
Desire
Acquisition
The transition from one phase to the next remains fluid, continuous, and system-aware.
Positioning
Premium · Selective · Systems-grade
Traceability, rigor, and a high-trust operating layer
Advantage
Full-stack solo builder
Lower costs · Speed · Coherence · Direct execution
Current state
Kernel stable, pure, and frozen.
The core primitives are locked: Vertex, Tie, Surface, Environment, and Actions.
The system has been tested on Raspberry and in a local environment. Benchmarks are running at full speed, more than 1,800 infrastructure tests pass, and everything is green.
Validated
Raspberry environment
Validated
Local environment
Validated
Benchmarks running at full speed
Validated
1800+ tests green
Actor and Workspace are confirmed, validated, and frozen. The next step is to extend Flow, Program, Studio, Intelligence, and Perception on a pure kernel.
Partnerships
Build the runtime with design partners.
Education, public institutions, research partners, and enterprise pilots can help define new modules and deployment surfaces.
Open to collaborations, co-development, and deployment partnerships.
Education
Co-design new modules
Enterprise
Pilot and validate workflows
Deployment
Cloud or sovereign runtime
Research
Shared exploration
The project grows faster when it is built with partners.
Runtime economics
Pricing scales with deployment, actors, and orchestration.
The base runtime stays bundled. Revenue follows scale: more actors, more hosted load, more orchestration, more sovereign deployment.
Directional tiers only: Solo, Studio Team, Organization, Enterprise, and Sovereign Runtime.
Included runtime
Workspace, Actor, Asset, Knowledge, Surface, Security, Realtime, Analytics, Collaboration
Scaling unit
Actors expand orchestration density
Deployment
EA Cloud or Self-Hosted Runtime
Premium capacities
Flow, Program, Studio, Intelligence, Perception
The long-term model is continuous access, actor-based expansion, and premium capacities aligned with runtime complexity.
How to use VASTE
Start hosted, move sovereign when the deployment demands it.
Assisted Boot reads the target system, prepares the base runtime, and configures the first deployment without forcing the user into the architecture.
The first experience stays simple. Studio handles the visible layer, and Intelligence can reason with the runtime when it is enabled.
01
Choose deployment
Electronic Artefacts Cloud or Self-Hosted Runtime.
02
Boot the kernel
Workspace, Actor, Asset, Knowledge, Surface, Security, Realtime, Analytics, and Collaboration come included.
03
Open Studio
Edit, deploy, publish, host, and manage domains from one layer.
04
Extend selectively
Flow, Program, Intelligence, Studio, and Perception expand the runtime only when the use case requires them.
Pricing scales with deployment mode and actor count.
Workspace, Actor, Asset, Knowledge, Surface, Security, Realtime, Analytics, and Collaboration stay bundled.
Capabilities are added only when orchestration, deployment, cognition, or environmental integration need them.
More expensive by design. Enterprise-grade control is the point.
The system starts with a simple launch path, then expands through modular capacities and actor-based scaling.
What you can compose
Compose the exact runtime you need.
Native systems stay included. Premium capacities extend the runtime when the use case needs orchestration, deployment, cognition, or environmental integration.
The same core can become a product platform, a knowledge base, a deployment surface, a smart environment, or a logistics engine.
Teams, sessions, and collaboration stay inside the same operating layer.
The primary unit of orchestration, relationships, and runtime expansion.
Media, documents, models, and datasets are attached to vertices, not kept outside the system.
Structured information lives inside the runtime and can be queried as part of the graph.
The surface is native. Studio is not the same thing and sits above it.
Control, telemetry, and continuous response stay close to execution.
Automation, scripting, and custom behavior expand the runtime when needed.
Publishing, hosting, reasoning, and environmental integration live in the premium layer.
Build platforms and public surfaces that can be edited, published, hosted, and improved inside the runtime.
Manage devices, sensors, control logic, and adaptive behavior from a shared graph.
Route signals, ingest data, automate decisions, and operate a real-world system end to end.
A controlled environment for teams that need their own structured workspace, files, and knowledge base.
Combine data ingestion, automation, and cognition for financial operations and decision support.
In practice, each stack is assembled for the target use case. The base stays the same, the composition changes.
Next
The runtime expands
Flow · Program · Studio · Intelligence · Perception
Horizon
From runtime to infrastructure.
VASTE is designed as an execution substrate: deterministic, graph-native, replayable, and modular enough to absorb more complex operating domains over time.
This is an architectural horizon, not a commercial promise.
VASTE is not being designed only to run software. It is being designed to orchestrate systems.
Studio, hosted systems, semantic knowledge layers, graph-native execution.
Studio
Hosted
Semantic
Composable runtime
Intelligent automation, simulation environments, distributed runtime infrastructures, robotic coordination.
Automation
Simulation
Distributed runtime
Robotic coordination
Autonomous factories, aerospace runtime systems, medical orchestration infrastructures, intelligent transportation systems, robotic fleets, distributed machine ecologies, scientific infrastructures.
Factories
Aerospace
Medical
Transportation
Robotic fleets
Scientific systems
Open
Deployment partners
Product · Strategy · Development
electronic
Artefacts
Build systems that do not exist yet.
Ready to become infrastructure.
Let's connect
If that resonates, let's talk.
electronic-artefacts@gmail.comOr write directly by email for a quick introduction.