Standards

How ITEA keeps product work grounded.

ITEA uses this page to make the public working standards clear: practical software, careful scope, honest claims, and no platform promises before the work exists.

Current release focus

This page replaces the public release-log concept with a compact standards page for how ITEA presents product work on the website.

Working standards

What the site should reflect

Practical software first

ITEA products should solve clear problems without hiding the useful parts behind unnecessary platform bloat.

Careful scope

Each public page should describe what exists, what is approved to say, and what is intentionally not being promised yet.

Clear public claims

Product copy should stay direct and accurate. No fake maturity, no unsupported claims, and no implied systems that are not built.

No shady behavior

ITEA should avoid dark patterns, misleading calls to action, hidden tracking, and confusing promises about accounts, checkout, licensing, or support.

Local-first where appropriate

When a product is meant to run locally, the website should keep that expectation clear instead of pushing cloud, account, or dashboard assumptions.