Aromatic is an early demonstrator.

It is intended for technical evaluation, protocol review, and real-world operator feedback—not for blind production deployment.

The design goal is durable low-bandwidth transport for unattended systems over Tor, but the current implementation should be treated as an evaluation artifact, not hardened infrastructure software.

Please do not deploy Aromatic as the sole communication path for:

• safety-critical systems
• life-safety infrastructure
• medical systems
• industrial control paths requiring formal certification
• emergency response systems
• any environment where software failure could directly cause harm

Use independent validation and redundant control paths.

Aromatic is designed around:

• durable local queue semantics
• authenticated message delivery
• explicit ack-before-delete behavior
• topology independence through Tor
• minimizing public network exposure

It is not designed to be:

• a general remote administration platform
• a replacement for formal industrial control certification
• a complete security boundary by itself

Tor provides transport properties. Aromatic provides delivery semantics. Operators remain responsible for system-level security and operational review.

If you discover a security issue, please do not open a public issue first.

Please report security concerns privately to:

Contact: aromatic@dosaygo.com

Include:

• affected version
• environment
• reproduction steps
• impact assessment if known

We would prefer responsible disclosure and will respond as quickly as practical.

The goal is boring reliability, not cleverness.

Security issues are usually created by unnecessary complexity.

If something feels too magical, it probably should be simpler.