Skip to main content

Source Material, Email, And Files

inrelay works best when source material includes the problem, users, scope, constraints, goals, success criteria, open questions, and any relevant prior decisions.

Supported intake sources include:

  • Slack messages and threads.
  • Slack files.
  • Direct Markdown written in the initiative page.
  • Direct inrelay uploads from an initiative page.
  • Inbound email body text.
  • Inbound email attachments.
  • TXT files.
  • Markdown files.
  • JSON transcripts or generic JSON.
  • DOCX documents.
  • PDF documents.
  • XLSX spreadsheets.
  • PPTX slide decks.

Use direct Markdown when the fastest path is to paste or write a Shape Brief in inrelay. Use direct inrelay upload when the file is already on your machine and belongs to a known initiative. Use Slack when source context is already in a conversation. Use inbound email for longer briefs, forwarded customer conversations, external partner context, or files that are easier to send by email.

Direct Markdown​

Open an initiative and use the written context editor to add Markdown source material. inrelay stores the entry as a source artefact, extracts text for readiness and evidence, and refreshes live readiness after processing.

The editor is Markdown-only in this version. inrelay does not execute embedded components, scripts, directives, or uploaded images from the editor.

inrelay Uploads​

Open an initiative and use the artefact upload control to attach one file at a time. inrelay stores the file, records it as a web_file source, extracts text when supported, and refreshes live readiness after processing.

Unsupported files are preserved as source artefacts but marked as having no extractable text.

Inbound Email​

Each team has an inbound email address based on its ID prefix, for example:

ENG@intake.relay.app

inrelay routes inbound email in this order:

  1. If the recipient local part is an initiative ID, such as ENG-123@intake.relay.app, attach the email to that initiative.
  2. If the recipient local part is a team prefix, such as ENG@intake.relay.app, inrelay looks for an initiative ID in the subject or body.
  3. If no initiative can be matched, the email is recorded as unmatched and is not attached to an initiative.

Recommended subject format:

ENG-123 - customer resend context

Email bodies are stored as source artefacts. Attachments are stored and text-extracted when the file type is supported.