---
since: 1.0.6
---

# Integration Boundaries

`djangoplay-cli` deliberately keeps Django internals outside the Python import
graph. The host application is treated as an external process boundary.

## Subprocess integrations

```text
dplay
 │
 ├── python manage.py collectstatic
 ├── python manage.py runserver
 ├── python manage.py runserver_plus
 ├── python -m celery -A paystream worker
 ├── python -m celery -A paystream beat
 ├── python paystream/security/encrypt_env.py
 ├── redis-cli flushall
 └── openssl / platform certificate tools
```

## Current host assumptions

The implementation currently assumes:

```text
repository root/
└── webapp/
    ├── manage.py
    ├── paystream/
    │   └── security/
    │       └── encrypt_env.py
    └── logs/
        └── *.log
```

Celery is currently invoked with:

```text
-A paystream
```

Therefore the CLI is **Django-framework decoupled**, but it is not yet a
generic Django project launcher.

This distinction is important for future refactoring.