Keep investigative coordination inside an explicit fleet and custody model.

01 / OPERATING PROBLEM

The protected conversation inherits the system around it.

Investigations can expose identities, strategy, sources, evidence locations and operational timing through general-purpose endpoints, shared accounts, broad administrators, metadata and compromised networks.

Black Swan Net reduces selected dependencies; it does not erase endpoint, human, supply-chain, traffic-analysis, metadata, coercion, availability or authorization risk.

02 / MISSION USE

Use a dedicated path only where the mission justifies it.

• Internal corporate investigations
• Legal and forensic teams
• Protective intelligence
• Small sponsor-defined public-sector teams

03 / OPERATING MODEL

Direct sessions. Explicit identity. Controlled lifecycle.

1. Enroll only authorized endpoints and operators
2. Do not treat network association as identity
3. Use session-specific authorization and constrained file handling
4. Revoke first after loss or capture; investigate the hardware separately

04 / ENGAGEMENT PATH

Begin with a sanitized mission description.

Tell us the sector, approximate fleet size, deployment timing and the security outcome the program must evaluate. Do not send protected information through the public site.

05 / CURRENT CLAIM BOUNDARY

Development status remains explicit.

Black Swan Net is in active product development. It is not represented as certified, government-approved, authorized for classified information, equivalent to a SCIF, anonymous, unhackable, free of metadata, free of endpoint risk, or able to guarantee availability. Component validation, product evaluation, system assessment and customer authorization are different decisions.

NAME DILIGENCE: Black Swan Net is the selected working name. Formal trademark and common-law clearance remains an open legal workstream; no clearance conclusion is claimed.