morteza/TorbatYar
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
735f343e0d
TorbatYar/docs
History
Mortezakoohjani 735f343e0d Mark CRM production deploy verified and harden health wait. 
Document successful CRM 6.3 prod smoke checks and retry CRM /health during deploy.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-07-24 20:37:12 +03:30
..
architecture Ship CRM Core Platform (phases 6.0–6.3) with docs and prod deploy. 2026-07-24 20:32:00 +03:30
decisions Ship enterprise Accounting FE/API with CRUD parity and production wiring. 2026-07-24 15:26:43 +03:30
deployment Ship CRM Core Platform (phases 6.0–6.3) with docs and prod deploy. 2026-07-24 20:32:00 +03:30
development Ship enterprise Accounting FE/API with CRUD parity and production wiring. 2026-07-24 15:26:43 +03:30
frontend Ship enterprise Accounting FE/API with CRUD parity and production wiring. 2026-07-24 15:26:43 +03:30
phases Ship CRM Core Platform (phases 6.0–6.3) with docs and prod deploy. 2026-07-24 20:32:00 +03:30
reference Ship CRM Core Platform (phases 6.0–6.3) with docs and prod deploy. 2026-07-24 20:32:00 +03:30
templates Ship enterprise Accounting FE/API with CRUD parity and production wiring. 2026-07-24 15:26:43 +03:30
architecture.md Ship enterprise Accounting FE/API with CRUD parity and production wiring. 2026-07-24 15:26:43 +03:30
crm-phase-6-0.md Ship CRM Core Platform (phases 6.0–6.3) with docs and prod deploy. 2026-07-24 20:32:00 +03:30
crm-phase-6-1.md Ship CRM Core Platform (phases 6.0–6.3) with docs and prod deploy. 2026-07-24 20:32:00 +03:30
crm-phase-6-2.md Ship CRM Core Platform (phases 6.0–6.3) with docs and prod deploy. 2026-07-24 20:32:00 +03:30
crm-phase-6-3.md Ship CRM Core Platform (phases 6.0–6.3) with docs and prod deploy. 2026-07-24 20:32:00 +03:30
current-architecture-review.md Ship enterprise Accounting FE/API with CRUD parity and production wiring. 2026-07-24 15:26:43 +03:30
database_schema.md Ship enterprise Accounting FE/API with CRUD parity and production wiring. 2026-07-24 15:26:43 +03:30
developer_guide.md Ship enterprise Accounting FE/API with CRUD parity and production wiring. 2026-07-24 15:26:43 +03:30
glossary.md Ship CRM Core Platform (phases 6.0–6.3) with docs and prod deploy. 2026-07-24 20:32:00 +03:30
last_step.md Ship enterprise Accounting FE/API with CRUD parity and production wiring. 2026-07-24 15:26:43 +03:30
module-registry.md Ship CRM Core Platform (phases 6.0–6.3) with docs and prod deploy. 2026-07-24 20:32:00 +03:30
next-steps.md Mark CRM production deploy verified and harden health wait. 2026-07-24 20:37:12 +03:30
progress.md Ship CRM Core Platform (phases 6.0–6.3) with docs and prod deploy. 2026-07-24 20:32:00 +03:30
provider-registry.md Ship enterprise Accounting FE/API with CRUD parity and production wiring. 2026-07-24 15:26:43 +03:30
README.md Ship CRM Core Platform (phases 6.0–6.3) with docs and prod deploy. 2026-07-24 20:32:00 +03:30
roadmap.md Ship CRM Core Platform (phases 6.0–6.3) with docs and prod deploy. 2026-07-24 20:32:00 +03:30
services_contracts.md Ship enterprise Accounting FE/API with CRUD parity and production wiring. 2026-07-24 15:26:43 +03:30

README.md

TorbatYar Documentation

Permanent source of truth for architecture, standards, registries, deployment, and phase planning.

Start Here (every implementation phase)

  1. This file
  2. architecture/ and architecture/adr/
  3. development/project-principles.md
  4. development/coding-standards.md
  5. development/testing-strategy.md
  6. module-registry.md
  7. provider-registry.md
  8. glossary.md
  9. Relevant phases/ docs

If a change affects architecture, APIs, providers, or module boundaries: update documentation first, then code.

Navigation

Status & Planning

Document Responsibility
progress.md Completed work only
roadmap.md Future roadmap only
next-steps.md Immediate next milestone only
crm-phase-6-0.md CRM Service Foundation (Phase 6.0)
crm-phase-6-1.md CRM Core Business Entities (Phase 6.1)
crm-phase-6-2.md CRM Enterprise Sales Process Engine (Phase 6.2)
crm-phase-6-3.md CRM Enterprise Sales Collaboration (Phase 6.3)

Architecture

Document Responsibility
architecture/architecture.md Overview
architecture/module-boundaries.md Ownership boundaries
architecture/database-architecture.md DB architecture
architecture/multi-tenant-architecture.md Tenancy
architecture/deployment-architecture.md Runtime topology
architecture/security-architecture.md Security
architecture/identity-architecture.md Identity
architecture/authorization-architecture.md Authz
architecture/integration-architecture.md Integrations
architecture/event-driven-architecture.md Events
architecture/service-architecture.md Service layering
architecture/ai-architecture.md AI rules
architecture/compliance-architecture.md Compliance
architecture/adr/ ADRs (one decision per file)

Development

Document Responsibility
development/developer-guide.md How to run/develop
development/project-principles.md Mandatory principles
development/coding-standards.md Coding conventions
development/testing-strategy.md Testing
development/branching-strategy.md Git branches
development/release-strategy.md Releases

Reference

Document Responsibility
reference/database-schema.md Schema reference
reference/services-contracts.md Service contracts
reference/api-reference.md API index
reference/event-catalog.md Events
reference/provider-reference.md Provider details

Deployment

Document Responsibility
deployment/deployment.md Deploy overview
deployment/production.md Production
deployment/ssl.md TLS / tenant SSL
deployment/monitoring.md Monitoring
deployment/backup.md Backup
deployment/restore.md Restore
deployment/disaster-recovery.md DR

Registries & Glossary

Document Responsibility
module-registry.md All modules
provider-registry.md All providers
glossary.md Terms

Frontend

Document Responsibility
frontend/README.md Accounting UI & design system index

Decisions, Templates, Phases

Path Responsibility
decisions/ Non-architectural decisions
templates/ Required document templates
phases/ Phase area documentation

Phase Completion Gate

No implementation phase is complete until:

  • Code completed
  • Tests passed
  • Documentation updated
  • ADR updated (if required)
  • Module Registry updated
  • Provider Registry updated (if required)
  • Progress updated
  • Next Steps updated
  • Architecture validation passed
  • No TODO remains
  • Self review completed
  • Final verification completed

Architecture Guard

Before modifying application code, verify consistency with principles, ADRs, registries, tenancy, database architecture, coding standards, and testing strategy. On conflict: stop, explain, correct docs/ADR first.

Deprecated Paths

Older paths may remain as stubs pointing here. Do not add new content to deprecated files.

Related