Writing from the team

The Journal

Notes, releases and field writing from the Zylvex team. This is the canonical route for the site's writing; the article archive itself still lives at the legacy blog path, and stays linked from here.

Index
What this is

One place for the writing

The Journal is the site's writing hub: the place to find what the team has written about its own work. It is deliberately separate from the documentation, which is reference material, and from the research pages, which hold structured findings.

Nothing on this page is a claim about how much has been written or how often. What exists is what is published, and it is published in one place so a reader can reach it without guessing at paths.

Where the articles are right now

This index renders no article list yet

The article index for this route is served from the existing blog content. Until that index is rebuilt against this path, the writing you can actually read today is the archive, and it remains published at the legacy route /blog/. The legacy route is kept online and kept linked — it is not being hidden or redirected away — so existing bookmarks and inbound links keep working.

No article titles, authors or dates are listed on this page, because this page does not hold them. Open the archive to see what has been published.

Browse the archive

Route note: /journal/ is canonical going forward; /blog/ is the legacy path and stays reachable.

What gets written

Kinds of writing published here

These are categories, not a contents list. Individual pieces are only discoverable through the archive itself.

Release notes

What changed in a given release, what did not change, and what a reader should check before relying on it.

Engineering notes

Decisions, constraints and trade-offs recorded while building the systems — including the options that were rejected and why.

Research notes

Findings from investigations, written up as they stand. Investigations are published whether or not they ever become a product.

Programme updates

Progress on the programmes the company runs. A programme is never presented as something you can buy.

Local ZylForge Technical Assistant

Explainable AI Assistant — Antigravity Philosophy for Physical Engineering