Domain Bridge Handshake — Detailed Specification

The Domain Bridge Handshake establishes a cryptographic trust binding between a customer’s domain and Firetip’s sovereign routing layer. This operation is required before any Outbound Dispatch can be authorized.

Purpose

Validates domain ownership, initializes a trust anchor, and assigns a sovereign routing profile for all future outbound traffic.

Operational Flow

The handshake performs the following internal operations:

• Domain Validation: Confirms the caller controls the domain being provisioned.
• Signature Verification: Validates the request using the Firetip HMAC signature header.
• Routing Assignment: Allocates a sovereign routing path (primary, redundant, or high‑throughput).
• Authority Locking: Locks the domain to its routing profile to prevent spoofing or cross‑tenant contamination.
• Provisioning Record: Writes a permanent ledger entry to the Firetip trust layer.

Endpoint

POST /api/v1/bridge/provision

This endpoint accepts a provisioning request and returns a signed confirmation that the domain has been successfully bound to its routing authority.

Headers

X-SC01-Signature: <derived_hmac_signature>

Header Description

X-SC01-Signature is a request‑level HMAC signature generated using the caller’s Firetip API key. It ensures:

• Authenticity — proves the request came from a valid Firetip client.
• Integrity — prevents payload tampering.
• Replay Protection — includes a timestamped nonce inside the signature.

Payload

{
"target_domain": "example.com",
"routing_path": "primary"
}

Payload Field Documentation

• target_domain — The domain being provisioned. Must match DNS ownership records.
• routing_path — Determines which sovereign routing lane the domain will use. Valid values: primary, redundant, high-throughput.

Response

{
"status": "PROVISIONED",
"authority_level": "DOMAIN_LOCKED",
"timestamp": 1719920041
}

Response Field Documentation

• status — Indicates provisioning success. Possible values: PENDING, PROVISIONED, FAILED.
• authority_level — Defines the trust state of the domain. DOMAIN_LOCKED means the domain is now cryptographically bound to its routing profile.
• timestamp — Unix epoch timestamp marking the exact moment the trust binding was finalized.

Post‑Provisioning Behaviour

Once provisioned, the domain gains access to:

• Outbound Dispatch Channels
• Telemetry & Verification Streams
• Campaign Execution Pipelines
• Sovereign Routing Guarantees

Firetip PHP SDK — Official Documentation (HMAC‑SC01 Edition)

The Firetip PHP SDK provides a secure, hardware-aligned interface for interacting with the Firetip sovereign dispatch engine. All requests use the HMAC‑SC01 Signature System, ensuring zero API key exposure, payload integrity, and replay protection.

1. Installation

composer require firetip/sdk

2. Initialization

<?php
use Firetip\SDK\Firetip;

$client = new Firetip('FT_LIVE_xxxxxxxx', '123', 'example.com');
?>

3. Authentication Model (HMAC‑SC01)

Firetip no longer uses Authorization: Bearer. All requests must include:

X-SC01-Signature: <hmac_signature>
X-SC01-Timestamp: <unix_epoch>

Signature Generation Steps

1. Convert the payload to JSON.
2. Generate a timestamp nonce.
3. Build the canonical string:
   <timestamp>\n<json_payload>
4. Compute:
   HMAC_SHA256(api_key, canonical_string)
5. Send the hex‑encoded signature in the header.

For the full specification, see Firetip Signature Spec.

4. Error Handling

<?php
try {
    $client->sendDirectEmail(...);
} catch (FiretipException $e) {
    echo $e->getMessage();
    echo $e->getFiretipCode();
}
?>

5. Core SDK Methods

5.1 Capture Lead

$client->captureLead('user@example.com', [
    'full_name' => 'John Doe',
    'country'   => 'UK'
]);

Captures a subscriber into the active campaign.

5.2 Send Direct Email

$client->sendDirectEmail(
    'customer@example.com',
    'Welcome!',
    '<h1>Hello</h1>'
);

5.3 Delivery Status

$status = $client->getDeliveryStatus('MSG_8842');

5.4 Fetch Logs

$logs = $client->fetchLogs(50, 'errors');

5.5 Node Health Check

$health = $client->checkNodeHealth();

5.6 Provision a Domain Bridge

The PHP SDK allows you to provision a domain directly from your backend. This operation binds the domain to Firetip’s sovereign routing layer using the Domain Bridge Handshake.

$client->provisionDomain('example.com', 'primary');

This performs the following:

• Validates domain ownership
• Assigns a sovereign routing path
• Creates a hardware‑anchored trust binding
• Enables outbound dispatch for the domain

Parameters

This method uses the HMAC‑SC01 signature system automatically and communicates with:
POST /api/v1/bridge/provision

For the full handshake specification, see: Domain Bridge Handshake.

6. Multi‑Tenant Domain Routing

$dispatcher = new Firetip($apiKey, '123');

$dispatcher->setDomainKey('alpha-marketing.com');
$dispatcher->sendDirectEmail(...);

$dispatcher->setDomainKey('faigen-media.net');
$dispatcher->sendDirectEmail(...);

Each domain maintains independent warmup, reputation, and routing lanes.

7. Architecture Notes

The PHP SDK is synchronized with the Firetip sovereign dispatch engine, SC01 hardware trust layer, and sCloud routing matrices. This ensures deterministic routing, hardware‑anchored identity, and zero shared‑cloud dependencies.

8. Full Example

<?php
use Firetip\SDK\Firetip;

$client = new Firetip('FT_LIVE_998x81723acb', '123', 'scloud.xyz');

$client->sendDirectEmail(
    'user@test.com',
    'Welcome to sCloud',
    '<p>Hello!</p>'
);
?>

Campaign Delivery Pipeline — Detailed Specification

The Delivery Pipeline establishes a persistent streaming channel for high-volume outbound workloads. It is optimized for real-time queue parsing and sovereign-priority execution.

Protocol

WebSockets / Server-Sent Events (SSE)

Channel

/stream/v1/dispatch/execute

Operational Modes

• Standard Delivery
• High-Velocity Blast
• Sovereign Prioritized Queueing

Example Stream Payload

{
  "campaign_id": "CMP-4421",
  "batch_size": 5000,
  "priority": "sovereign"
}

Live Verification Listener — Detailed Specification

The Verification Listener receives real-time confirmation events for opens, validations, and identity checks. It is designed for millisecond-accurate telemetry.

Callback Type

POST <your_webhook_url>

Event Frame

LISTENING FOR VERIFICATION

Example Webhook Payload

{
  "event": "OPEN",
  "message_id": "MSG-9912",
  "timestamp": 1719921123,
  "user_agent": "Mozilla/5.0"
}

Emergency Cluster Triage — Detailed Specification

The triage controller provides administrative-level control over active dispatch clusters. It is used to pause, flush, or isolate nodes during abnormal load or failure conditions.

Endpoint

PUT /api/v1/cluster/triage

Commands

• PAUSE_BLASTER
• FLUSH_QUEUES
• ISOLATE_NODE

Example Payload

{
  "command": "ISOLATE_NODE",
  "node_id": "SC01-442",
  "reason": "latency_spike"
}