What is the immunity layer protecting?

The immunity layer protects the platform's platform rules guarantees — specifically the 78% developer earnings floor, fund routing, and WORM audit trail integrity — from both external attacks and internal compromise.

Can ForceDream staff access my data?

Internal access requires mutual TLS + API key. All access is WORM-sealed. No back-door access exists. Customer-managed keys (Enterprise) make plaintext inaccessible to ForceDream even with physical server access.

What happens if the hash chain is broken?

Automatic tamper alert is triggered within seconds. The break is WORM-logged (to a separate chain). The affected records are quarantined. Our security team is notified immediately.

Can I verify no earnings were redirected?

Yes. Every billing split has a WORM record linking it to the Stripe Connect transfer ID. Verify: GET /api/v1/earnings/{call_id}/verify returns the split hash, amount, and Stripe transfer ID.

Home › Trust Centre › Immunity Layer

🛡 Immunity

Immunity Layer

The platform rules immunity layer protects the platform, developers, and customers from attack, misuse, and internal compromise. Every protection is WORM-sealed and independently verifiable.

// What the immunity layer does

Platform protections

🔒

platform rules enforcement

L828-IMMUTABLE rates (80/17.5/2.5) are enforced at the infrastructure layer. Any attempt to override them via API, configuration, or database modification is rejected immediately and WORM-sealed as a violation event.

💰

Fund redirection prevention

Developer earnings route directly to their Stripe Connect account at the moment of transaction. ForceDream never holds developer funds. Routing is WORM-sealed and cannot be intercepted by any platform actor.

🌐

DDoS and rate limit protection

Cloudflare WAF + rate limiting at the edge. Per-key rate limits enforced at API gateway. Redis circuit breakers prevent cascade failures. Attack traffic is WORM-logged for forensic analysis.

🔑

Zero-trust internal access

No implicit trust for internal services. All service-to-service calls require mutual TLS + API key. Every privileged action by ForceDream staff is WORM-sealed. No back-door access to customer data.

🤖

AI agent containment

Agent runtime isolation: each agent runs in a sandboxed namespace. Agents cannot access other agents' memory, keys, or earnings records. platform rules safety checks on every agent output before delivery.

// Attack vector mitigation

What we protect against

Attack vector	Mitigation	WORM logged?
API key theft / replay	HMAC signing, key rotation <60s, IP allowlisting	Yes
Earnings rate tampering	L828 in infrastructure layer — below app code	Yes
Fund redirection	Direct Stripe Connect routing — ForceDream never holds	Yes
DDoS	Cloudflare WAF + per-key rate limits + Redis circuit breakers	Yes
Cross-workspace data access	Cryptographic namespace isolation	Yes
Agent escape	Sandboxed runtime, no cross-agent memory access	Yes
Privileged insider access	Zero-trust mTLS, WORM-sealed all staff actions	Yes
Audit trail tampering	SHA-256 hash chain — any modification immediately detectable	By definition

// verify immunity chain

curl https://api.forcedream.ai/api/v1/worm/chain/status \
  -H "Authorization: Bearer fd_live_..."