Product Architecture

Scope & Capture Rules.

Built on a strict, structural separation between what is captured and what is explicitly excluded.

Current Capabilities

Slack / Microsoft Teams

VERYTIS captures the textual content of conversations within spaces explicitly authorized by the organization.

  • Text messages & Threaded replies
  • Context (Channel, Timestamps, Participants)
  • Explicit signals sent by users
Strict Exclusions
  • Private messages (DMs)
  • Files (PDFs, Docs, Images)
  • Unauthorized channels

Email Protocol

VERYTIS never captures email content.

We record only tracking signals and metadata:

Sender
Recipients
Sent Date/Time
Subject
Message ID
Open Status
Reply Status
Privacy Guarantee
  • Body is NEVER read or stored
  • Attachments are NEVER captured

Why this Architecture?

Collaboration Tools

Environments where decisions are made, actions validated, and processes executed.

Files & Documents

Belong to other governance systems. VERYTIS tracks the *decision* to approve the file, not the file itself.

Email

Remains a personal channel requiring maximum restriction. Metadata only.

Product Direction

No dates, no commitments. Just clear intent.

1. Expansion to Tools

Audit processes where they actually occur.

  • GitHub / GitLab
  • Stripe / Billing
  • Internal Business Tools

2. Metadata Enrichment

Enrich records without analyzing content.

  • Action / Decision Type
  • Org-defined Categories
  • Linked Actions

3. Explicit Signaling

Reduce ambiguity, don't enforce workflows.

  • Simple Markers
  • Configurable Signals
  • User-triggered Actions
* VERYTIS is designed to expand beyond messaging tools while preserving its core principles.

What Will Not Change

No access to private messages
No capture of files or PDFs
No email content (Body)
No use of data for AI training
No scraping outside authorized scope

Objective

Audit of processes, actions, and decisions.