Technical writing · cybersecurity content · knowledge strategy

We turn complex systems into documentation people can trust.

Aetrix is a technical writing, cybersecurity content, and knowledge strategy practice built for teams whose products are too important to explain badly. We write the manuals, the policies, and the systems behind them.

Did you know?

Documentation mistakes can be costly.

From incorrect interface specifications to outdated recovery procedures, documentation gaps can lead to failed deployments, extended outages, and even failed missions.

01 · PRODUCTION

Documentation and content pages failure in production

According to a story by Spaw in September 2026, a software company reported that an undocumented production dependency caused every documentation and content page to return HTTP 500 errors after deployment. The incident illustrates how systems can fail when technical dependencies and deployment requirements aren't clearly documented and tested.

02 · AVIATION

The Boeing 737 MAX Incident

For 737 MAX, Boeing added a new flight-control system (MCAS) that automatically pushed the nose down under certain conditions. The system was never documented in the pilot manuals, and crews received no training on it. In October 2018, a faulty sensor triggered MCAS on a Lion Air flight. The pilots, unaware the system even existed, fought the unexpected nose-down inputs until the aircraft crashed, killing all 189 people on board. Five months later the same sequence repeated on an Ethiopian Airlines flight, claiming 157 more lives. The absence of clear documentation turned a technical fault into two preventable disasters.

03 · RELIABILITY

GitLab database incident

In GitLab’s major 2017 database outage, the team reached for its documented backup and recovery procedures, only to discover that none of the five mechanisms worked reliably. Hours of production data were lost because the runbooks had never been recently verified. The incident showed that stale documentation doesn’t just create inconvenience; it directly extends outages and multiplies cost.

04 · ENGINEERING

NASA Mars Climate Orbiter

In 1999, NASA lost the Mars Climate Orbiter after a mismatch between English and metric units caused an incorrect trajectory calculation. NASA's lessons learned specifically noted that existing interface documentation required metric units, but the requirement was not properly communicated and followed.

At a glance

Experience that spans products, teams, and content systems.

1,000+Pages migrated to Docs-as-Code
20+Years in technical content
50%Cut in documentation
5+Workflows, one team