10. Operational Bounds & Constraints

The Stealth Orchestrator operates within defined scope bands and acknowledges explicit limits. These boundaries provide realistic expectations for throughput, cadence, and resilience.

10.1 Scope Bands

• Concurrency: per-domain inflight requests capped at human-plausible levels ($M$ small, constant)
• Duty cycle: long-run request rates are governed by $D = A/(A+C)$, where bans trigger cooldowns instead of retries
• Resolution: DNS lookups follow bounded cache lifetimes and refresh deterministically with transport changes
• Fingerprint/session reuse: browser identities and cookies are reused for bounded lifetimes, then rotated in controlled fashion
• Transport diversity: outbound traffic reuses stable proxy paths per domain, with TLS signatures drawn from a small set of real browser profiles

10.2 Known Limits

• Blind spots:

  • Systems that require hardware-bound keys or device certificates (cannot be faked by software)
  • Web application firewalls that issue one-off challenges tied to a specific device session
  • Internal enterprise DNS setups that intentionally give different answers to the same query (split horizon)
  • Rapid browser/TLS updates that introduce new handshake patterns not yet in the curated profile set

• Non-goals:

  • Extracting or enriching page content
  • Building or renting large proxy pools
  • Solving CAPTCHAs, proof-of-work challenges, or similar interactive tests
  • Bypassing legal access controls or lawful processes

• Failure cases:

  • Too few proxy endpoints can still make traffic stand out
  • Over-use of the same fingerprint can make sessions too long-lived
  • DNS cache misconfiguration can cause stale or inconsistent answers

10.3 Guardrail Principle

These scope bands and limits are not optimizations but guardrails. They state what the system can reproducibly guarantee, what it explicitly does not cover, and how plausibility is maintained when operating under defensive pressure.