Tag: dev
Documents tagged with dev:
📘 Areas
- AI & LLM Architecture
- App Structure
- Backoffice & Catalog Domain (`schema: backoffice`)Entity dictionary for the Backoffice bounded context — master data, planning, CRM, and the Kalkulations-Engine.
- Commerce & Finance Domain (`schema: commerce`)Entity dictionary for the Commerce & Finance bounded context — sales, payments, capacity, ledger, and tax.
- Communications Architecture
- Communications Domain (`schema: communications`)Entity dictionary for the Communications bounded context — omnichannel inbox, contacts, and automated messaging.
- Customer Intelligence Domain `[future — Phase 3]`[TBD] Entity dictionary for the Customer Intelligence bounded context — Phase 3.
- Design System Architecture
- Documentation GuidelinesDocumentation guidelines covering PARA frontmatter, content model, and AI agent orchestration rules.
- Example: backoffice.tour_templates — role: dispatcher
- Frontend Architecture
- GDPR StrategyGDPR strategy covering TOMs, DPA onboarding, PII scrubbing pipelines, and data subject rights.
- Infrastructure
- Mollie Integration
- Monorepo Optimization
- Observability
- Operations Domain (`schema: operations`)Entity dictionary for the Operations bounded context — fleet execution, dispatching, IoT, offline sync, and compliance.
- PARA ClassificationPARA classification system — category definitions, state transitions, content lifecycle, and placement rules.
- Payments & Billing
- Real-Time & Reactivity
- Roles & Permissions
- Testing Architecture
- Trunk-Based Development
- Unified Domain ModelBounded context map and cross-boundary integration surface for the BusFlow modular monolith. Routes readers to per-context entity dictionaries (spokes).
- Workflow Orchestration
📦 Resources
- ADR-034: Documentation Frontmatter SchemaFormal schema spec for docs frontmatter — mandatory, optional, and ADR-specific field rules.
- ADR-036: Aggregate-Level FK PolicyHard FKs within aggregate boundaries; soft ID references where cross-aggregate lifecycle conflicts exist; hard FKs for stable context references.
- ADR-037: CRM Identity Model — PersonProfile and Booker ConceptRenames PassengerProfile to PersonProfile (role-neutral CRM anchor), adds booker_profile_id on Booking (billing authority), splits communication routing by role.
- Draw.io ViewerVitePress route that renders .drawio files in the Busflow docs hub.
- Idea: Partial Recalculation (Dirty-Flag Engine)
- Invoice Service ProtocolGoBD-compliant invoice lifecycle — generation, issuance, PDF rendering, Storno workflow, period lock immutability, DATEV dual-format export, and BWA/SuSa reconciliation.
- Tax Engine — § 25 UStG Steuer-Engine§ 25 UStG tax engine — strategy resolution, margin calculation, Drittlands-Split, and GoBD recording obligations.