Trust Boundary (@trustboundarystudio)

@trustboundarystudioMelbourne, AustraliaJoined September 2026

Infrastructure post-mortems reconstructed from the primary record: regulator orders, court filings, vendor RCAs. Breaches, outages and architecture failures, one a week. trustboundarystudio.com

@trustboundarystudioMelbourne, AustraliaJoined September 2026

Infrastructure post-mortems reconstructed from the primary record: regulator orders, court filings, vendor RCAs. Breaches, outages and architecture failures, one a week. trustboundarystudio.com

Trust Boundary

About

Available for

Trust Boundary's blogs

Recently published

The block said no. The agent took it as a puzzle.

The Meta outage had no bad decision in it

Anthropic's sandbox was open. One model knew, and kept going.

Your change process governs code. This was not code.

The Capital One breach was not an SSRF story

Trust Boundary

About

Available for

Trust Boundary's blogs

Recently published

The block said no. The agent took it as a puzzle.

The Meta outage had no bad decision in it

Anthropic's sandbox was open. One model knew, and kept going.

Your change process governs code. This was not code.

The Capital One breach was not an SSRF story

Trust Boundary

About

Available for

Trust Boundary's blogs

Recently published

The block said no. The agent took it as a puzzle.

The Meta outage had no bad decision in it

Anthropic's sandbox was open. One model knew, and kept going.

Your change process governs code. This was not code.

The Capital One breach was not an SSRF story

Search Hashnode

Trust Boundary

About

Available for

Trust Boundary's blogs

Recently published

The block said no. The agent took it as a puzzle.

The Meta outage had no bad decision in it

Anthropic's sandbox was open. One model knew, and kept going.

Your change process governs code. This was not code.

The Capital One breach was not an SSRF story