Configuration Files

This page is a reference for Deprex’s key configuration files. These files are set up by the 0ai engineer during initial deployment and form the foundation for the FDE’s autonomous operation. PMs do not need to edit them directly, but understanding their contents helps in grasping how the FDE operates.

Configuration File Overview

File	Purpose	Configured By
`repo-registry.yaml`	Tenant, workspace, and channel registration	0ai engineer
`extended-sources.yaml`	Additional memory source definitions	0ai engineer
`scheduled-tasks.yaml`	Scheduled task definitions	0ai engineer (FDE proposes additions)
`auth-multi-tenant-profile.yaml`	External service authentication profiles	0ai engineer
`config/.env`	Tenant environment variables	0ai engineer

repo-registry.yaml

The central configuration file managing the mapping between tenants and Slack workspaces. The FDE uses this to identify tenants, determine notification targets, and resolve content paths.

repos:
  acme:
    display_name: "Acme Corporation"
    slack_workspace_id: "T0123456789"
    dev_channel: "#acme-fde-dev"
    default_notify_channel: "#acme-fde"
    owner_user_ids:
      - "U0123456789"
    content_paths:
      - "app/orgs/acme"

Fields

Field	Required	Description
`display_name`	Yes	Human-readable tenant name
`slack_workspace_id`	Yes	Slack workspace ID
`dev_channel`	Yes	Channel for error and test notifications
`default_notify_channel`	Yes	Channel for business notifications
`owner_user_ids`	Yes	Slack user IDs for important decision notifications
`content_paths`	Yes	Reference paths for tenant content

extended-sources.yaml

Defines additional memory sources beyond the standard memory directories. Used when expanding the information sources the FDE references.

sources:
  - name: acme-tenant-memory
    type: memory
    path: app/orgs/acme/memory
    scope: tenant
    tenant: acme
    description: "Acme-specific business knowledge"

scheduled-tasks.yaml

Defines scheduled tasks per tenant. Initial setup is done by the 0ai engineer, and after deployment the FDE proposes task additions based on workflow observations.

tasks:
  - name: daily_kpi_summary
    schedule: "0 9 * * 1-5"
    command: "Review yesterday's key KPIs and post anomalies and action items to Slack"
    env_file: "config/.env"
    description: "Weekday morning KPI summary"
    enabled: true
    timeout_minutes: 30

Fields

Field	Required	Description
`name`	Yes	Unique task identifier
`schedule`	Yes	Cron expression
`command`	Yes	Natural language instruction for the FDE
`env_file`	No	Environment settings file loaded at execution
`description`	No	Task description
`enabled`	No	Set to `false` to pause
`timeout_minutes`	No	Maximum execution time

When the FDE proposes a new scheduled task and the PM approves, the 0ai engineer or the FDE itself adds it to this file.

config/.env

Defines environment variables per tenant. Contains authentication reference names and service connection settings.

TENANT_ID=acme
SLACK_PROFILE=acme-slack
GWS_PROFILE=acme-gws
DEFAULT_NOTIFY_CHANNEL=#acme-fde

This file is not committed to git by convention. The 0ai engineer manages it securely.

What PMs Should Verify

PMs do not need to edit configuration files, but confirming the following with the 0ai engineer ensures smooth operation:

display_name is a name recognized within the organization
Notification channels are correct (especially for private channels, verify bot membership)
owner_user_ids includes people who can make decisions
Scheduled task execution times are appropriate for business needs

Request configuration changes from the 0ai engineer via Slack.