ExoTrade

Participant manual

Help hub

Learn how the current ExoTrade release works, which actions need approval or project membership, how to protect private information, and what to try when something goes wrong.

Help guide v1.0 · Last updated 14 November 2026

Feature and access status legend

Available now

The public page or signed-in feature exists in the current release; account, configuration and normal service availability still apply.

Requires approval

A human must approve the relevant participation role before the feature becomes available to the account.

Project-specific

Active project membership, a project role, a lead action or a project document is required.

Planned or configuration-dependent

The capability is not active until its required setup, credentials, integration or later release is complete.

What ExoTrade is and Phase 1 limitations

ExoTrade is the platform and program stewarded by the Institute for Scientific Integrity and Legal Policy. It supports applications, human review, approved participation and private project collaboration. Public pages explain the model; private workspaces contain only information available to the signed-in account.

  • Phase 1 accepts nonbinding applications and expressions of interest only. No funds are accepted or distributed.
  • No approval, assignment, employment, compensation, investment opportunity, project success or return is guaranteed.
  • Public legal templates are nonbinding planning samples. Private project agreements become binding only through authorized approval and signature.
  • A feature’s availability never overrides role approval, project membership, confidentiality or security controls.
Back to top

Account creation and sign-in

Use one Auth0 account and one ExoTrade account. Create an account from Apply to begin an application, or use Sign in to enter the workspace. Email/password and Google sign-in are available through Auth0 when enabled for the application.

  1. Choose Create account to apply, complete Auth0 registration and verify your email.
  2. Return to the same safe Apply destination, including a valid initial-role tag when one was selected.
  3. For later visits, choose Sign in. The public header shows Workspace, a verified-email signed-in indicator and Sign out when a session is active.
  4. Multi-factor authentication is required only when configured and enabled by the server policy; ordinary applicants and members are not currently required to use MFA.

Sign out clears the local session and returns to the public sign-in page. Do not share accounts, credentials or verification codes.

Back to top

Initial role tag, core roles, and project membership

  • An initial-role tag is optional starting context chosen from a public participation path. It is not approval, a permission or a separate account.
  • Trader, Researcher, Investor and Content Creator are core roles requested in the application. Each requested role is reviewed separately, and recommendations from a tag remain editable.
  • Project membership is a later, separate decision for a particular project. An approved core role does not automatically join you to a project.
  • Investor and investment-path applications require a declared proposed capacity of at least USD 1,000,000. This is an eligibility declaration only, not a transfer, commitment or promise of an opportunity.

You can change your starting path in a new or resumable draft. A saved draft’s path and selected roles take precedence over a different role link opened later.

Back to top

Applying as an individual or organization

  1. Choose individual or organization and select an optional starting path plus every core role you want reviewed.
  2. Complete profile, experience, interests, availability, conflicts and authority information. An organization applicant must describe authority to represent it.
  3. Use Save and continue to store a resumable draft. The same account returns to that draft rather than creating separate role applications.
  4. Review consent and answers, then submit once for human review. Submission does not create community access, employment, a partnership, an affiliate agreement or an investment commitment.

If a saved draft cannot be loaded, the application reports the problem rather than replacing it with empty answers. Retry loading before entering a new draft.

Back to top

Manual identity review, clarification, decisions, and appeal

  • After submission, provide a government photo-ID image only through the private application page. JPEG or PNG is accepted, up to 5 MB; the server checks, decodes and re-encodes the image to remove metadata.
  • Only the assigned authorized human reviewer can open the private image, and views are logged. No automated identity, criminal-record or external KYC decision is made, and the upload process is not antivirus scanning.
  • A reviewer may request clarification. Respond in My Applications; do not send identity numbers or documents through the public help form.
  • A human decision follows review. If an eligible decision can be appealed, the application page provides the appeal form and status information.
  • Identity-image deletion follows the published schedule. A manual purge control is used because no recurring deletion scheduler is configured.
Back to top

Admin, staff, and participant capabilities

  • Participants receive only approved community roles and active project memberships; signup alone grants no community access.
  • Staff capabilities are invitation-only and limited to the assigned back-office functions. An administrator has back-office module access but does not automatically receive community roles or confidential project contents.
  • No email address, first login, role tag or client-side setting automatically makes someone an administrator. First-admin bootstrap is a one-time server-secret process, and later staff access uses controlled invitations.
  • Admin-only actions are labeled in the back office. Project-lead-only actions require active leadership of that project; platform administration does not replace project authorization for confidential content.
Back to top

Workspace navigation and signed-in indicator

Open Workspace from the public header after sign-in. The workspace shows only modules available to the account. The public header’s verified-email indicator and Sign out button confirm the current session; when signed out, the header shows Sign in instead.

  • Use the workspace navigation to move between dashboard, projects, applications, messages and other authorized modules.
  • If a module is absent, do not assume a role or project membership has been approved. Check My Applications and the relevant project invitation or membership.
  • Browser back navigation after sign-out must not restore protected data. Sign in again to establish a fresh session.
Back to top

Dashboard and portfolio

The dashboard summarizes authorized work. Portfolio and My Portfolio show projects available to the account, rule-based health, attention items and status notes. Health is not an AI score.

  • Portfolio health uses documented rules and explains its inputs. A project lead may record a RAG override with a reason where authorized.
  • Filters change the view only; they do not change project status or permissions.
  • Admin portfolio views can include platform-level project administration but do not expose confidential project contents merely because the viewer is an admin.
Back to top

Projects and project membership

  • Approved community members may create or participate in projects according to their role and project permissions. Public project discovery shows only approved sanitized summaries.
  • A project lead edits drafts, manages membership and submits project review where authorized. Reviewers must be independent and cannot approve their own project.
  • Membership is project-specific. Invitations, openings and contribution records do not themselves grant access until the applicable acceptance and membership process completes.
  • Private documents, discussions, deals, research and governance remain scoped to authorized project participants.
Back to top

Deals and opportunities

Deal records organize private, nonfinancial project opportunities, participants, technologies, proposed terms, contributions, milestones, approvals and revision history.

  • Only authorized active project participants can view or change a deal. Optimistic revision checks prevent silently overwriting another person’s changes.
  • Statuses and approvals are records, not payments, settlements, capital collection, distributions or live financial commitments.
  • Public pages contain no private deal data. Proposed economics remain subject to signed documents, caps, accounting approval and available distributable amounts.
Back to top

Research, technologies, and contacts

  • Research versions are append-only: authorized readers can inspect the full version history rather than silently replacing earlier findings.
  • Technology records distinguish claimed capabilities, evidence, evaluation and project use. A record does not validate a claim or transfer IP.
  • Contacts are project-scoped and may contain private information. Do not copy them into public pages or unrelated projects.
  • Use project selectors deliberately; content from one project must not appear in another project’s view.
Back to top

Messages and notifications

  • Messages are limited to authorized conversations. Edit history is preserved where the workflow supports revisions.
  • The signed-in bell opens the Notification Center; the full view supports read state, safe authorized links and per-category preferences.
  • Notifications are in-app only. ExoTrade does not claim to send email, SMS or push notifications.
  • Security notices remain enabled, workflow notices are deduplicated, and private message bodies or sensitive document contents are not copied into notification rows.
Back to top

My Applications

My Applications shows your own application, initial participation path, requested roles, progress, reviewer requests, identity-document state and eligible decisions or appeals.

  • Use the page to respond to clarification and to upload or remove an eligible identity image before review.
  • Only your own application is available through the applicant view. Staff review tools use separate assigned-reviewer permissions.
  • An older application without an initial-role tag displays Not specified; this does not change its reviewed roles or status.
Back to top

Project documents, uploads, versioning, and classification

  • Project files use private storage and short-lived authorized download or upload links. Storage paths are not public.
  • Accepted project-file formats are PDF, DOC/DOCX, XLS/XLSX, CSV, TXT, PNG and JPEG, up to 25 MB. Identity photos use the separate 5 MB JPEG/PNG application workflow.
  • A replacement upload creates a new version and marks the earlier version superseded; authorized users can inspect prior versions. Archived and superseded files have narrower read access.
  • Project classification is available to active members; restricted classification is limited to the uploader, leads, platform admins and explicitly authorized viewers. Outstanding legal acknowledgments do not block general project access.
  • Files are not malware-scanned. Use appropriate local security checks before opening any download.
Back to top

Tasks, milestones, Gantt/timeline, and baselines

  • Tasks and milestones belong to a project and respect membership, assignee and dependency rules.
  • The timeline provides Gantt-style scheduling, dependencies, baselines and revision-checked updates. A lead or otherwise authorized manager controls scheduling actions.
  • A stale revision must be reloaded rather than overwritten. Baselines and schedule exports are records, not evidence of funding or completion.
  • Calendar dates and milestones do not themselves create a contractual deadline unless an executed agreement says so.
Back to top

Whiteboards

Project whiteboards are saved structured documents for authorized project members. They support revision conflict recovery and export.

  • Boards are private to their project and are not public collaborative web pages.
  • They are not real-time multi-user cursor collaboration. Save and revision behavior should be checked before assuming another person’s latest changes are visible.
  • Do not put credentials, identity documents or unnecessary sensitive data on a board.
Back to top

Governance: risks, issues, decisions, meetings, and acknowledgments

  • Risk and issue registers record owners, status, mitigation and authorized follow-up. Eligible issues or meeting actions can become tasks through controlled project operations.
  • Published decisions and meeting minutes are append-only; later amendments and acknowledgments create separate records rather than silently editing history.
  • Acknowledgment records receipt, not a vote, approval or signature. Decision and meeting actions follow project membership, lead and reviewer rules.
  • Portfolio health and governance reports are rule-based records, not AI judgments or legal decisions.
Back to top

Calendar, search, activity, and exports

  • The calendar consolidates authorized project dates with month, week and agenda views. Read-only ICS export uses stable identifiers and omits confidential descriptions.
  • Global search returns only permitted projects and record types. Recent searches remain in the browser and can be cleared locally.
  • Activity feeds use safe summaries rather than copying confidential content. Project and portfolio exports are permission-scoped and formula-safe where CSV is provided.
  • An export is a snapshot, not a new system of record and not permission to republish private information.
Back to top

Tools and TelePath OS integration status

The public Tools page links to TelePath OS, DealMatch and Maximus on external websites. Those destinations open in a new tab and are not evidence that an ExoTrade integration is configured.

  • TelePath meeting-room and follow-up writes are configuration-dependent and require valid developer credentials, allowed HTTPS destinations and tested scopes.
  • Manual TelePath delivery and project mappings must not be described as connected until configuration and acceptance testing succeed.
  • Inbound TelePath processing remains disabled until its native signing contract is documented; a generic HMAC boundary is not represented as that native contract.
  • External tools have their own terms and privacy practices. Do not enter ExoTrade credentials or private project data into an external tool without authorization.
Back to top

Privacy, security, confidentiality, and safe handling

  • Use public, project and restricted classifications correctly. Share only approved sanitized public summaries.
  • Never put passwords, tokens, ID numbers, identity documents, private contacts, signature evidence or raw audit metadata into public pages or the public help form.
  • Protect your Auth0 account, verify the site address, sign out on shared devices and clear local recent searches or preferences when needed.
  • Identity documents use assigned-reviewer private storage. Project files use authorized signed links. No system is risk-free, so minimize sensitive data and report suspected exposure without forwarding it publicly.
  • Read /legal#privacy for collection, analytics, retention, service-provider and browser-storage details.
Back to top

Troubleshooting

Sign-in returns to the application

This is expected after Create account to apply. Complete email verification and resume the saved application. Use Workspace or Sign in when you want the general member workspace instead.

Verified email but still signed out

Allow the Auth0 callback to finish, then reload once. If the session cannot persist, use a normal window rather than a restricted private window, allow the site’s local storage, and sign in again. Do not paste tokens or session data into a help request.

No approved role or project access

Check My Applications for role decisions and the relevant project for membership. A verified email, initial-role tag or approved role alone does not create project access. Contact the project lead through the authorized process or use the help form.

Loading screen or request failure

Wait briefly, then retry or hard-refresh. A failed draft load does not mean saved answers were erased. If the problem continues, record the page, time and non-sensitive error text for support.

File upload limits or errors

Project files must use an allowed format and be no larger than 25 MB. Identity photos must be JPEG or PNG and no larger than 5 MB. Check the file type, size and connection; do not rename an unsupported file merely to bypass validation.

Signing blocked, out of order, or expired

Confirm that you are a verified active project member and an assigned signer, review the complete immutable PDF, complete consent and intent, and wait for earlier ordered signers. An expired, declined or void envelope cannot be signed; an authorized manager must create a new envelope for changes.

Stale browser session

Use a hard refresh, then sign out and back in if needed. Clearing site storage removes local session and preference data but not server-side applications or projects. Never send browser tokens to support.

Contact help without sensitive data

Use /contact with a reply email, the relevant public page or non-sensitive workspace area, and a short description. Omit secrets, credentials, identity numbers, documents, private contacts and signature evidence.

Back to top

Frequently asked questions

Does creating an account make me a member?

No. It lets you maintain one application. Community roles require human approval, and project membership is separate.

Does my role tag select my final role?

No. It is starting context only. You can request multiple core roles, each reviewed separately.

Can I invest or pay in Phase 1?

No. The platform accepts no funds, investments, settlement or distributions in Phase 1. Proposed capacity and economics are nonbinding declarations or illustrations.

Does submitting technology transfer its IP?

No. Pre-existing IP stays with its lawful owner unless a signed assignment or license states otherwise. Submission and contribution records alone transfer no title.

Are public legal templates ready to sign?

No. They are public pro formas for planning and counsel review. Actual project terms require authorized project documents and signatures.

Are acknowledgments and approvals signatures?

No. Basic E-Sign is a separate exact-version workflow with consent, intent, typed name and signer evidence.

Are notifications emailed?

No. Notifications are in-app only; no email, SMS or push delivery is claimed.

Is TelePath connected?

Only a configured and tested integration can be treated as connected. Inbound processing remains disabled pending its documented native signing contract.

Back to top

Contact support

Use the help-request form for account, application, project or public-site questions. Include a reply email and enough non-sensitive context to identify the issue. Email replies are not automated yet, and the form must not receive secrets, credentials, identity numbers, identity documents or signature evidence.

Open the help-request form
Back to top
Security-first: read the ExoShield model