backbone-support 0.6.15

Minimal Backbone Framework module skeleton
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44

//! Support's one outbound port (hand-authored, user-owned) — the optional seam where a ticket becomes
//! delivery work. Support holds only this trait + its own DTOs; a composing service wires the real
//! backbone-project behind it. **Zero normal Cargo edge** to project — the two Tier-4 modules stay
//! independent (brief §7), and the DTOs are the wire contract, duplicated per consumer by design.
//! Support posts no GL and has no ledger seam; escalation just spawns a delivery Project.

use serde::{Deserialize, Serialize};
use uuid::Uuid;

/// Escalate a support ticket into a delivery project (open a backbone-project Project for the customer).
///
/// `company_id` is the SIBLING's domain key (backbone-project is not tenant-agnostic; its
/// Project rows carry the legacy owner-company — composition-installed tenancy, ADR-0029).
/// Support neither stores nor fences on it: the write path sources it from the ambient org
/// scope and fails closed when the request carries no company-anchored scope.
#[derive(Debug, Clone, Serialize, Deserialize, PartialEq)]
pub struct ProjectFromIssue {
    pub company_id: Uuid,
    pub issue_id: Uuid,
    pub customer_id: Uuid,
    pub subject: String,
}

/// The spawned delivery project's id.
#[derive(Debug, Clone, Serialize, Deserialize, PartialEq)]
pub struct ProjectAck {
    pub project_id: Uuid,
}

/// The project seam — a composing service implements it over backbone-project.
#[async_trait::async_trait]
pub trait ProjectPort: Send + Sync {
    async fn open_delivery_project(
        &self,
        req: &ProjectFromIssue,
    ) -> Result<ProjectAck, SupportRejected>;
}

/// A downstream rejection surfaced to support.
#[derive(Debug, Clone, Serialize, Deserialize, PartialEq)]
pub struct SupportRejected {
    pub code: String,
    pub message: String,
}