Directory Structure

Deprex’s directory structure is created by the 0ai engineer during initial deployment. The FDE then autonomously populates it with content through its ongoing operation. PMs do not need to directly manipulate files, but understanding the structure helps in grasping how the FDE operates.

Top-Level Structure

app/
  _shared/                    # Skills and rules shared across all tenants
    skills/
    rules/
  orgs/
    acme/                     # Tenant-specific environment (auto-populated)
      skills/
      rules/
      memory/
      config/
      scheduled-tasks.yaml
.deprex/
  harness/
    config/                   # Platform configuration
  brain/
    memory/                   # Repository-wide memory (auto-accumulated)
    extended-sources.yaml

app/_shared/ — Shared Components

Stores skills and rules shared across all tenants. Contains industry-agnostic capabilities like browser automation, data analysis, and image generation.

Developed and maintained by 0ai engineers. The FDE uses these autonomously.

app/orgs/ — Tenant Environments

Each tenant’s autonomous operating environment. Content automatically grows through the FDE’s activities.

app/orgs/acme/
  skills/                     # Skills auto-generated by the FDE
    weekly-kpi-report/
      SKILL.md
      scripts/
    support-triage/
      SKILL.md
  rules/                      # Tenant-specific behavioral rules
    communication.md
  memory/                     # Business knowledge auto-accumulated by the FDE
    INDEX.md
    company-overview.md
    kpi-definitions.md
    stakeholders.md
    reporting-rules.md
  config/                     # Authentication and environment settings
    .env
  scheduled-tasks.yaml        # Scheduled task definitions

Auto-Populating Directories

Directory	How It Grows	PM Involvement
skills/	FDE auto-generates skills from workflow observations	Approve generated skills
memory/	FDE auto-accumulates knowledge from conversations and observations	Review accumulated content

Directories Fixed at Initial Setup

Directory	How Configured	PM Involvement
rules/	Set by 0ai engineer based on PM discussions	Confirm rule content
config/	Set by 0ai engineer	None

.deprex/ — Platform Layer

Manages the FDE’s foundational configuration and shared memory. Not an area tenants interact with directly.

.deprex/
  harness/
    config/
      repo-registry.yaml          # Tenant registration
      auth-multi-tenant-profile.yaml  # Authentication profiles
  brain/
    memory/                        # Repository-wide memory
    cognition/                     # Cognitive logs
      traces/                      # Cognitive cycle traces

Determining Change Scope

The directory location indicates the scope of impact for any change.

Path	Scope	Impact
app/orgs/acme/	Tenant	Acme only
app/_shared/	Shared	All tenants
.deprex/harness/config/	Platform	All tenants
.deprex/brain/memory/	Repository	All tenants

Tenant-specific changes are confined to app/orgs/<company>/. Shared and platform changes are managed by the 0ai engineer.

Important Notes

• Tenant directory content is automatically managed by the FDE. PMs do not need to edit files directly
• Files from one tenant’s directory are never referenced by another tenant
• All file changes are managed via git, making change history fully traceable
• Credentials are securely stored in config/ and never written directly into memory or skills