AethrionX uses specific language for product work. These terms appear across the product, the documentation, and the team's writing — they're worth defining once, in one place, with stable URLs you can link to.
The durable record of why something was built, decided, or rejected. Institutional memory is what survives team turnover and tool migrations. In AethrionX it captures decisions, overrides, capacity calls, and customer history automatically, and surfaces relevant context the moment a related action is about to be taken — so the team stops re-litigating decisions and stops repeating shipped mistakes.
The unified store of tickets, signals, decisions, customer context, and pull-request summaries that lets AethrionX reason across them. The product brain is what every AethrionX surface reads from — auto-assignment, X chat, semantic search, voice intents, change visualization. One reasoning substrate, many interfaces.
AethrionX's conversational interface. X chat opens as a side panel on the tickets page or as a full-page workspace and lets you ask questions about tickets, customers, decisions, and shipped work in natural language. Answers cite the underlying tickets and memories they're drawn from.
The moment a piece of customer signal stops being a note and becomes an assigned, owned ticket. Most product workflows leak signal at the boundary between intake and action. AethrionX measures and shortens that gap — every signal has a clear path to being made operational, or being declined with a captured reason.
A user decision that contradicts a system suggestion. AethrionX captures overrides as first-class signals — not failure modes — because they encode product knowledge the system didn't have. Patterns across overrides update auto-assignment, prioritization, and the institutional memory surfaced before future decisions.
The system AethrionX uses to weight customer signals by source. A signal from a top-revenue account, a long-tenured user, or a high-impact channel carries more weight in prioritization than a passing comment from an anonymous contact. Authority weighting is tunable per organization and visible in the reasoning shown next to every prioritization decision.