Building AVENAX.

This is an engineering journal, not a blog. Every entry answers four questions: what changed, why, what we learned, and what happens next.

2026-07

Company documentation system

What: Vision, engineering rules, append-only decision log (ADRs), product requirements, brand constitution.
Why: Decisions must outlive work sessions. Code without recorded reasoning becomes archaeology.
Learned: An append-only ADR log ends re-litigation: a decision is either accepted, or superseded by a new entry — never quietly edited.
Next: Documentation only when implementation demands it. Execution first.

2026-07

What: Token architecture (primitives → semantic → component), self-hosted 100% OFL font stack, twelve UI primitives, dark-first dual theme.
Why: Every future AVENAX product reuses this system. Pages are assembled, not designed.
Learned: License verification is engineering, not paperwork: it caught a font EULA that forbids public-repo distribution, and the display face was replaced before a single component used it.
Next: Sections, then pages — strictly inside the token system.

2026-07

What: Cloudflare Worker + D1. Stores an email, a timestamp, a source tag. Nothing else — no IP, no fingerprinting, no tracking.
Why: A static site needs no server, and trust is the product: collect the minimum, state it plainly.
Learned: CORS protects browsers, not servers — real protection is validation, rate limiting, and a honeypot. Duplicate signups are deliberately indistinguishable from new ones, so the endpoint leaks nothing.
Next: Analytics only behind a hard Performance-100 gate. If performance drops, analytics does not ship.

2026-07

What: The real site: hero, manifesto, Insight introduction, live waitlist. Every framework placeholder deleted.
Why: Visible progress every cycle, and the waitlist is our first validation instrument.
Learned: Our hero entrance animation was delaying the largest paint on slow connections. Brand motion is never allowed to cost performance — the headline now paints instantly and the signature line animates after it. Lighthouse 100 is treated as a product requirement.
Next: AVENAX Insight — Product One: educational AI chart analysis. Private beta follows the waitlist.

The website code is public: github.com/getavenax/avenax-web. Product code stays private; decisions and progress are published here.

AVENAX Trace provides educational analysis and decision support — never financial advice, signals, or investment recommendations.