A unified Git workflow for developers.
Working on issues through separate branches
The main working branch is "develop"
The branch name is associated with the issue (e.g., feature/1234). All changes to the issue—code, tests, configurations, migrations—should be committed to this branch.
Do not develop directly in develop or main.
Before pushing, you must merge with develop and resolve any conflicts, if any.
Verify that everything builds and tests pass.
A unified Git workflow for developers.
Working on issues through separate branches
The main working branch is "develop"
The branch name is associated with the issue (e.g., feature/1234). All changes to the issue—code, tests, configurations, migrations—should be committed to this branch.
Do not develop directly in develop or main.
Before pushing, you must merge with develop and resolve any conflicts, if any.
Verify that everything builds and tests pass.
It would be advisable to let me know what you plan to work on before starting work. @Annaklychev

Repository: https://github.com/Annaklychev/CleanArchitecture.Template

ID: FT-1
#Task
Set up CI to run tests automatically

Configure Continuous Integration (CI) so that all unit and integration tests run automatically on every pull request. Ensure that the CI pipeline fails on test failures and provides clear feedback to developers.

Priority: High

Status: ✅ Done

Assignee: @Mr_Ravshanbekk

ID: FT-2
#Task
Set up infrastructure for Redis and Kafka

Provision Redis and Kafka services for development and testing environments. Ensure they are configured according to best practices and are ready for integration with the application. Include basic connection tests and documentation for developers.

Priority: High

Status: 📉 In Progress

Assignee: @Mr_Ravshanbekk, @kapilkaushall

ID: FT-3
#Task
Configure Docker and Docker Compose

Set up Docker and Docker Compose to provide a reproducible development environment. Tasks include:
Create a single docker-compose.yml with:
- Postgres (for EF Core)
- Redis
- Kafka
- Enable environment variables via a .env file.
- Configure HealthChecks for all services at this stage.
- Provide instructions for running the environment locally.

Priority: High

Status: ✅ Done

Assignee: @kapilkaushall

Application is a use case orchestrator.
#Note
It answers the question: "What does the system do?", not "How" or "Where is it stored?"

Application owns the contracts. Infrastructure/Backend adapts to them.

Domain = Enterprise Business Rules
#Note
Domain:
Knows NOTHING about:
- UI
- Web / HTTP
- EF Core
- DB
- Kafka
- Redis
- Identity
- ASP.NET

Can live:
- in the console
- in tests
- in another application
- in 10 years

📌 If you throw out everything except the Domain, the business should still make sense.

I compiled a summary table that describes what the project CAN reference and what it SHOULD NOT
#Note

ID: FT-4
#Task
Implement a user fingerprint identification mechanism without violating Clean Architecture principles

Implement all necessary migrations in the Migrations project

Domain Task:
- Describe the fingerprint model
- Define invariants
- Formulate business rules

Application Task:
- Orchestration
- Validation
- Domain ↔️ Infrastructure Relationship
- Contracts live in the Application, implementation is below

Infrastructure Task:
- Contract implementation
- Integrations
- No business logic

Persistence Task:
- EF Core
- DbContext
- Entity configuration

WASM Task:
- Fingerprint collection
- Sending to the API

Priority: High

Status: 🟢 New

Assignee: @Annaklychev