Product guide
How Dileo works.
From a private purchase order to a reviewed, buyer-confirmed opportunity and an escrow-backed funding lifecycle.
The short version
A company brings a purchase order and its supporting documents. Dileo turns them into an attributable record, shows what is supported or missing, and lets an independent reviewer approve the exact public version. The named buyer confirms that order. Capital providers can then contribute through X Layer escrow.
Roles are permissions on a deal
A wallet does not register forever as a “buyer” or “capital provider.” What it can do depends on the deal. Any wallet can browse and fund; only the wallet assigned as this deal’s buyer can confirm it.
| Role | What they do | Authority |
|---|---|---|
| Company | Creates a private draft, supplies the order and evidence, and requests capital. | Its verified wallet owns the draft and later receives released capital. |
| Reviewer | Checks private evidence and approves one exact public Deal Blueprint. | Only the allowlisted reviewer can register, open, release, or cancel the demo deal. |
| Buyer | Confirms that the purchase order belongs to the named transaction. | Only the wallet assigned as buyer for that deal can confirm it. |
| Capital provider | Reads an approved opportunity and decides whether to contribute. | Any connected wallet can fund; no application or permanent funder role is required. |
Each person’s journey
Company
- Connect and verify a wallet.
- Create or resume a private draft.
- Add the order, buyer, amount, and supporting PDFs.
- Run analysis and submit the Blueprint for review.
- Receive released capital and later repay principal.
Reviewer
- Connect the allowlisted wallet.
- Inspect claims, source pages, conflicts, and missing evidence.
- Approve one exact Blueprint or request changes.
- Register it, then open funding after buyer confirmation.
- Release capital only after the deal is fully funded.
Buyer
- Receive the focused confirmation link from the company or reviewer.
- Open it without creating a workspace or account.
- Connect and verify the wallet named on that deal.
- Read the statement and confirm the exact Blueprint on X Layer.
Capital provider
- Browse the approved deal without connecting.
- Connect any wallet when ready to act.
- Claim test dUSDC, approve only the contribution, and fund.
- Track escrow and transaction evidence.
- Claim repayment or an available refund.
What each page is for
| Page | Purpose | Access |
|---|---|---|
| Explore | Public opportunities | No wallet required |
| Your deals | Wallet-owned active deals and resumable drafts | Verified company wallet |
| Deal tabs | Overview, Blueprint, source evidence, uncertainty, intelligence, and funding | Public summary; private evidence remains controlled |
| Review | Evidence review and exact Blueprint approval | Allowlisted reviewer wallet |
| Buyer confirmation | A focused shared-link confirmation | Named buyer wallet |
Evidence Intelligence
Dileo treats every PDF as untrusted data. The model extracts candidate facts with a document, page, and excerpt. Dileo then validates the structure and independently recalculates amounts, dates, conflicts, completeness, and missing requirements before anything is shown.
- Choose a suggested question.It fills the question field; press Ask to submit it.
- Read a grounded answer.The response comes only from the validated deal record and lists its evidence IDs.
- Expect an honest refusal.If the evidence cannot support an answer, Dileo says so rather than inventing one.
The capital lifecycle
| Stage | What the user does | What Dileo enforces |
|---|---|---|
| Prepare | Company uploads supporting PDFs. | Files remain private; Dileo extracts source-linked facts. |
| Analyze | Company runs Evidence Intelligence. | AI proposes facts; Dileo rechecks money, dates, conflicts, and completeness. |
| Review | Reviewer accepts the exact Blueprint. | That version is committed for the later contract actions. |
| Confirm | Buyer opens the shared link and confirms. | The named buyer wallet confirms the exact Blueprint on X Layer. |
| Fund | Capital providers approve test dUSDC and contribute. | Capital stays in escrow; the target is all-or-nothing. |
| Settle | Reviewer releases; company repays principal. | Contributors claim repayment, or claim refunds after cancellation. |
Buyer confirmation recognizes the purchase order. It is not a guarantee of repayment, authenticity, or business performance.
When something does not work
- Wrong wallet
- Use the wallet control to switch to the address assigned to that action. The connected wallet can still browse or fund.
- Wrong network
- Switch to X Layer Testnet before submitting a transaction.
- Rejected signature
- No transaction occurred. Reconnect and retry the free session signature.
- Rejected transaction
- Nothing is shown as complete. Read the wallet error, correct gas, allowance, role, or state, then retry.
- AI unavailable
- No result is published. The canonical demo can use its clearly labeled, previously validated fallback.
- Not fully funded
- After cancellation under the contract rules, contributors pull their own refunds.
Privacy and production boundaries
Original documents, extracted text, contact details, and reviewer notes remain private. Wallet addresses, commitments, transaction timing, contributions, and lifecycle events are public blockchain data.
The hackathon uses one allowlisted reviewer so approval has a clear accountable authority. The recommended production model is a policy-governed underwriting multisig: named operations and risk reviewers approve through threshold signatures, with an auditable reviewer registry, revocation, and separation from custody. Legal onboarding, KYC/AML, sanctions checks, independent security review, monitoring, and incident controls are required before real-value use.