william/iris_translation_v2
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Page: open questions
Pages
Home api reference implementation plan jobs and workflow local development open questions operations and scaling product quality and review runtime architecture setup and configuration storage and artifacts translation and retrieval
2 open questions
william le roux edited this page 2026-04-01 16:51:37 +03:00
Table of Contents

Open Questions

These are the decisions that still appear unresolved from the repository's current state.

Related Docs

1. Production Database Target

The repo now ships both PostgreSQL and SQLite configuration, and local development defaults to PostgreSQL. What remains open is the supported production database contract: pooling, backup/restore, upgrade, and HA expectations.

2. Supported Worker Topology

Queue routing exists, but the repo only ships one generic worker in Compose. It is still an open delivery decision whether the supported production guidance should remain single-worker-role or formally split workers by queue family.

3. Retrieval Queue Contract

settings.py routes a retrieve_context queue, but the checked-in workflow performs retrieval inside translation processing. Either the separate retrieval task needs to be implemented, or the unused route should be retired.

4. Private Deployment Minimum

The repository supports local and private-friendly components such as MinIO, OpenSearch, and OpenAI-compatible endpoints, but it does not define whether the target promise is merely private-network deployment or full disconnected execution.