Separate source acquisition from interpretation.

Raw source material does not enter HARBINGER Core

1. 01
   Seal the capture request

   Bind organization, user, purpose, subject, permitted sources, time window, and call budget.

2. 02
   Acquire through an isolated worker

   Collect only approved material and prevent duplicate dispatch or unbounded retry.

3. 03
   Retain raw material only under an approved exception

   Raw source material is not stored by default. Only an expressly approved exception may retain encrypted raw material for up to 24 hours outside the Core and separately from its integrity coordinates; the capture receipt follows the applicable retention policy.

4. 04
   Deliver a raw-free observation candidate

   Pass source, digest, time, state, and bounded structure into HARBINGER Core.

An operational deployment must pass five isolation checks

These are requirements of the public security model, not a certification that the documentation deployment already satisfies them. Implementation, configuration, recovery, and audit evidence must be verified before a customer environment opens.

• Organization-isolated environments and work queues
• Per-customer encryption and retention boundaries
• Short-lived workload credentials
• Audit coordinates from request through capture, parser, and observation
• Explicit states for denial, failure, duplicate work, and exhausted budget

Publish trust properties without publishing the attack surface

This page states the boundary a customer needs to evaluate. It does not disclose internal network addresses, storage coordinates, key identifiers, customer source lists, capture schedules, or anti-abuse policy internals.