FAQ

What AttesTorr is — and what it is not.

A concise guide to the product, stack, cybersecurity thesis, stage, and claim boundaries.

What is the product?

Ephemeral Trust Rooms is the first SKU. The product is a purpose-bound execution environment for one governed execution. Layer ZERO is the underlying execution architecture and commercial anchor.

What does Layer ZERO do?

It governs the declared execution itself: admission, binding, execution, closure, canonical lifecycle evidence, independent closure appraisal, and fresh successor qualification.

Does Layer ZERO do all the cybersecurity work?

No. Cloud Cyber Shield (CCS) addresses surrounding cloud residual-risk posture and control-plane hardening. The proposed AI/NHI IAM Standard governs machine identity, bounded delegation, admissibility, tools, memory, and runtime authority. Technical and Operational Governance supplies owners, decision rights, constraints, policy, and exceptions. Layer ZERO is the execution-integrity and closure anchor.

What is the execution lifecycle?

ADMIT → BIND → EXECUTE → CLOSE → VERIFY → SUCCESSOR. Continuity is not assumed; the successor must establish fresh authority.

Does AttesTorr decide whether an AI answer is correct or safe?

No. AttesTorr does not grade model answers or certify alignment. It governs the declared execution boundary and the evidence of its ending.

Does ephemerality mean nothing can ever persist?

No. Permitted outputs, evidence, and other legitimate persistent information may survive. The goal is to avoid unnecessary persistence and prevent execution-scoped authority from silently becoming permanent authority.

Is AttesTorr unhackable?

No. Ephemeral systems can contain vulnerabilities, and attackers may act during active execution. The proposition is narrower: reduce exposure by limiting the existence, lifetime, authority, retrievability, and continuity of sensitive execution state.

Does AttesTorr replace IAM, Zero Trust, or confidential computing?

No. Those controls remain necessary. AttesTorr is designed to complement them by adding a bounded execution lifecycle and independently evaluable closure.

What is the current stage?

Architecture-complete, pre-revenue, and pre-MVP. The reference implementation has been authorized and initiated, and standalone-verifier design is underway.

Where does AttesTorr start commercially?

Regulated financial services, beginning with one privileged production-cloud identity or access action class. Later embodiment paths are not year-one SKUs.