Clear answers. Defined boundaries.
Where EL begins, what the platform coordinates, and which decisions always remain with the authorized participants.
01What execution problem does Execution Layer solve?
After a contract is signed, execution is distributed across participants, email, documents and separate systems. The factual deal state must be reconciled manually, and one delayed confirmation can affect later actions, documents and settlement. EL creates one controlled execution environment: it turns contract terms into a deal-specific execution structure, connects obligations to owners, dates, evidence and confirmed events, coordinates the next available action and maintains one current state. Its purpose is to make execution structured, understandable and manageable from signed contract to verified outcome.
02What is Execution Layer, and when does it begin?
Execution Layer is execution infrastructure for commodity trade. It begins after a contract is signed, when commercial terms are agreed and performance of the obligations begins. Based on that contract, EL prepares a deal-specific execution structure connecting obligations, owners, prerequisites, dates, documents and required evidence. As the deal progresses, it maintains one current state and makes clear what is complete, what is waiting and what needs to happen next. The signed contract remains the legal source, and authorized participants retain every consequential decision.
03Who is EL built for? Is it limited to agricultural trade?
EL is built for everyone involved in commodity trade: those who produce, sell, buy, transport, store, inspect, finance or support other stages of execution. Execution logic is formed from the key terms of each specific contract and brings obligations, roles, deadlines, documents and confirmations into one current deal state for all authorized participants. EL is not limited to agricultural trade. Sector differences do not change the core operating principle. The current configuration is designed for agricultural commodity trade, while the architecture is applicable to other commodity-trade segments.
04Is EL a marketplace or an ERP / CTRM?
No. EL is not a marketplace or broker and does not replace a company's internal systems of record. Within the Verified Network, participants can find other verified participants worldwide, initiate interaction and publish Execution Interests — structured intentions to buy or sell. An Execution Interest is not a marketplace order and does not itself create a deal: commercial terms and execution remain inside a private deal workspace. EL coordinates execution and connects with existing systems.
05How do KYC, KYB and AML checks reduce the time required to work with counterparties?
Before access is activated, a company completes KYB, its authorized representatives complete KYC and authority checks, and the profile receives a current AML-screening status. Participants can therefore begin with an established verified profile instead of collecting the same basic information from zero for each new deal. This reduces repeated document exchange and may shorten preliminary counterparty onboarding. An EL profile does not replace independent due diligence, ongoing monitoring, bank requirements or additional checks required for a specific transaction.
06Who can see a deal, and how are roles assigned?
Every deal is private. Within a deal, access is limited to assigned participants and infrastructure providers. Buyer, Seller, Broker or infrastructure roles are assigned separately for each transaction. Each authorized participant works from the same current deal state but can view and act only within the permissions assigned to that role.
07Who are Verified Infrastructure Participants, and what value do they add to a deal?
Verified Infrastructure Participants are banks, inspectors, logistics, warehousing, insurance, customs and settlement providers selected by the parties for a specific deal. They confirm the documents, events and statuses within their responsibility directly in EL. This reduces manual data exchange, accelerates execution and helps keep the deal's factual state current as confirmations arrive; with an integration, updates are recorded automatically. Each participant's access is limited to assigned permissions.
08How is Execution Reputation formed, and what value does it provide?
Execution Reputation is formed from a participant's verified execution history in EL: attributable actions, timing and verified deal outcomes. It helps other verified participants assess actual execution discipline from recorded history rather than claims or reviews. The details of individual deals remain private. Execution Reputation is not a guarantee, credit rating, recommendation or substitute for independent due diligence.
09How is an execution timeline created and approved?
EL analyzes the signed contract and prepares a contract-specific graph of obligations, owners, prerequisites, dates and required evidence. Authorized participants review, edit and approve that structure before activation. The example shown on the site is illustrative, not a fixed universal sequence.
10Can AI approve obligations, payments or other consequential actions?
No. AI assists with extraction, structure, checks and signals. Authorized people retain approval authority and every consequential commercial, operational and legal decision. EL does not independently approve an obligation or release funds.
11Does EL hold funds, operate as escrow or replace bank compliance?
No. EL does not hold participant funds, provide custody or operate as escrow. Settlement remains with the parties or authorized external providers. EL does not replace a bank's compliance process and does not guarantee bank approval. ATE (Authorized Trade Entity) is a separate, optional intermediary used only when both parties appoint it; it assumes only the obligations expressly defined for that transaction.
12How does EL connect with existing systems and service providers?
The architecture is designed to connect with ERP / CTRM systems, document tools, KYC / KYB providers, banks or settlement providers, inspectors, logistics systems and other authorized data sources. The exact integrations available depend on the implementation and confirmed provider arrangements.
13What is available now, and which interfaces are illustrative?
The public website presents the EL architecture and product interfaces; screens marked as illustrative are product representations, not proof of a live production feature. Current access, supported sector configuration, functions and integrations are confirmed directly for each request. No certification, integration, SLA or production capability should be inferred unless EL confirms it in writing.