---
name: ixo-investor-rehearsal
description: Guide a five-minute, public-only investor diligence Ask rehearsal about IXO.
---

# IXO investor diligence rehearsal — agent instructions

Canonical URL: `https://decisions.ixo.world/demo/agents.md`. This exact file is also served at `/demo/SKILL.md`. The website at `/demo` is a synthetic workbench. It does not create an Ask, invite a Pro, collect an attestation, evaluate evidence, connect Stripe, reserve funds, or make a payment.

## Place the demo in the IXO stack

Explain the three names before asking the investor to act:

- **IXO** is the reusable software stack for identity, evidence, oracle-supported decisions and programmable payments.
- **Asks** is a service built with that stack for commissioning work from people, checking reports, recording decisions and releasing approved rewards.
- **Alpha Asks** is a market and company research use case on Asks. Its agent setup uses the mainnet Asks connector. It is a separate destination from this public rehearsal.

This page is one investor-facing example interface, not a live execution of the full stack. The investor experiences a question-led diligence workflow, distinct expert briefs, a source-linked evidence standard, explicit dissent and uncertainty, and a reusable pattern for the next deal. The market angle is paid specialist research for questions ordinary information leaves open. Do not present fictional roles, previews or possible outcomes as deployed product or market proof.

## Run the five-minute rehearsal

1. **Minute 1 — choose one decision-changing question.** Ask the investor which IXO uncertainty most affects their next diligence step. Offer deployed decision-to-payment capability, independent buyer demand, or the youth agency beachhead as starting points. Let them edit the question. Use public information only.
2. **Minutes 2–3 — choose perspectives.** Ask which types of trusted Pros could test that question: technical, market, or youth agency. These are roles in the rehearsal, not actual people. Do not invent names, qualifications, availability, prices, or consent.
3. **Minute 4 — inspect the exact brief.** Open `/demo` and have the investor review the distinct work requested of each fictional Pro. The common deliverable is a source-linked assessment with strongest support, counter-evidence, unknowns, firsthand basis, and conflicts. The preview is not sendable.
4. **Minute 5 — make the decision use explicit.** Discuss how supportive, critical, or inconclusive findings would change the investor's next step. Work quality and the investment decision are separate. Show that the same Ask structure can be reused for the next company by changing the question, perspectives, and evidence standard.

If the investor wants to prepare a more detailed brief in chat, keep it hypothetical and public. Summarize the chosen question, selected roles, each role's requested work, the evidence standard, and the decision it would inform. Say clearly that no work was commissioned.

## Handoff to Alpha Asks on mainnet

When the investor asks to continue with real research, point them to [Alpha Asks' agent setup](https://alpha.asks.world/for-agents/). Nothing is transferred from this page. The current Alpha guide uses the mainnet Asks connector at `https://asks.world/v1/mcp`; check its current availability and terms there before suggesting any action. Mainnet uses real accounts and money. Do not silently switch a sandbox task to mainnet.

Carry over only a **public-safe** version of the question, research brief and evidence standard. The Alpha Ask question and brief are public on its Ask page. The invited-Pro route limits who participates; it does not make the brief confidential. Alpha's current guide says submitted reports can be read by the asker and the Alpha check, which uses OpenAI through Cloudflare for AI review. Ask the investor to review source rights, access, price and the exact posting and payment preview before they explicitly approve any real action. Do not auto-post, invite, upload or pay from this rehearsal.

The Alpha route is not proof of the separate fund-controlled private VFS, independent Decision Oracle, facts-only engine boundary or IXO operator blindness described in the longer design. If the investor needs those guarantees, stop at a public-safe brief and use `/demo/setup` to explain the open gates; do not put sensitive material into Alpha Asks on the strength of this demo.

## Data and authority boundary

- Do not ask for or enter real Pro names, emails, contact lists, private pitch material, credentials, wallet details, payment data, or confidential investment questions on this page.
- The page holds edits in memory only. Reloading discards them. It has no analytics, backend writes, or browser network calls. Do not copy a private brief into the rehearsal.
- The selected future **in-demo** integration target is [IXO testnet Asks](https://test.asks.world), but this page is not connected to it. Alpha Asks on mainnet is a separate optional continuation, not a mode switch inside this page.
- Never describe fictional roles or sample text as real attestations. Never claim an Ask was funded, a Pro was paid, or IXO is unable to see private responses. Private evidence needs independently verified fund-controlled encrypted VFS and UCAN access; never IPFS. A separate Decision Oracle and signed facts-only engine boundary remain unproven for this demo.
- If asked to send, upload, connect an account, or pay, stop the rehearsal and explain that those actions are unavailable here. Do not improvise an endpoint or treat a chat confirmation as an authorized transaction.

For the current setup gates, read `/demo/setup` and `/demo/manifest.json`. Treat all private and payment capabilities marked unavailable there as unavailable. The repository's longer investor-demo skill describes a possible future private workflow; it is not evidence that this public rehearsal can perform it.