I’m angelcrown.
AGCRN is where I ship the software I maintain.

Why this root domain exists

HaloBench, PicFit, and myOS solve different problems and need different product identities. Separate subdomains keep their interfaces, canonical URLs, search indexes, release decisions, and product policies understandable.

AGCRN is the shared publisher record behind them. It provides one stable place to verify who operates the services, compare their data models, find current product links, read build decisions, and report a problem.

How I choose what to build

A project starts with a task that repeats often enough to be frustrating. The first release must complete its core job without making a user study a complicated workflow or click an advertisement.

• Start with the task. A working conversion, schedule, or image package matters more than a promotional landing page.
• Use the smallest suitable data model. Local browser work is preferred when continuity or collaboration is unnecessary.
• Document a different model when it is necessary. Encrypted synchronization is not described as local-only processing.

Three products, distinct data boundaries

HaloBench handles short utility input, and PicFit performs the image conversion workflow on the user’s device. myOS needs continuity across devices, so workspace content is encrypted in the browser before synchronization.

Each project record explains the boundary in plain language and links to the product-specific privacy information. Calling every product “local-first” would be inaccurate.

How the products are funded

Some eligible public pages may use clearly separated advertising, and products may later offer optional paid features. Funding does not change a calculation result, require an ad click, or intentionally expose private working input.

Advertising is decided screen by screen. Authentication, recovery, error, and other screens without meaningful publisher content are not used merely to create more ad placements.

What “maintained” means here

I review broken core flows, inaccurate policy statements, preset and formula changes, accessibility problems, security reports, and major browser regressions as product issues. A feature can have a known limit; that limit should be written down rather than hidden behind a broad promise.

Current product records