BUILD NOTES / UPDATED 2026-08-30
Decisions behind the products.
These notes document what a short product card cannot: why AGCRN uses this domain structure, where processing happens, why advertising eligibility differs by screen, and what I mean when I call a product live.
Change record
- 2026-08-30
- Expanded AGCRN privacy, terms, contact, and product records so each service has a concrete workflow, limitation, data boundary, and support path.
- 2026-08-21
- Expanded the root domain from a product directory into a publisher record with detailed pages for the original three live services and their operating decisions.
01 / PUBLISHING STRUCTURE
Why AGCRN uses one root domain and separate product subdomains
HaloBench is a catalog of utilities, PicFit is a focused image workflow, and myOS is an account-based personal workspace. Combining them into one application would make navigation, search results, policies, and release decisions harder to understand.
Each product therefore receives a dedicated subdomain and product identity. The root domain is the publisher record: it lists only products with a public working version, identifies the operator, compares their data-handling models, links to policies, records known limitations, and provides one contact point.
A new service is added here with its working link, plain-language workflow, data boundary, limits, and support route. A name and “coming soon” card are not enough.
02 / PRIVACY ARCHITECTURE
Local processing and encrypted synchronization solve different problems
HaloBench is designed for short, task-specific input. Most calculations and conversions run in the page, and favorites remain in browser storage. PicFit handles larger and potentially sensitive source images, so decoding, cropping, resizing, conversion, and ZIP packaging happen on the device.
myOS needs continuity across devices. The browser encrypts workspace and account-vault records before synchronization, while authentication and operational metadata are handled separately. Optional AI features contact the provider selected by the user only when that feature is run.
03 / MONETIZATION
Advertising follows meaningful publisher content, not every reachable screen
An application can have many routes without every route being an appropriate advertising surface. Empty states, sign-in, recovery, loading, errors, and private communication do not become useful publisher content because an advertisement appears beside them.
On eligible pages, ads remain visually and functionally separate from tool controls, results, downloads, account actions, playback, and messaging. An ad click is never a step in completing a workflow. Tool input, source images, readable workspace records, vault fields, and room messages are not intentionally added to advertising requests.
04 / OPERATIONS
What “live and maintained” means for an independent product
A live AGCRN product has a reachable public URL, a complete core workflow, readable mobile and desktop layouts, product-specific policy information, and a working support path. Its product record describes present behavior rather than a speculative roadmap.
Maintenance does not mean constant feature expansion. It means broken core flows, inaccurate claims, changed formulas or presets, security reports, accessibility problems, and major browser regressions are treated as product issues.
Known limits remain visible. HaloBench results can become inaccurate when a rule or formula changes. PicFit presets can age when a platform changes requirements. myOS depends on authentication, cryptography, storage, and selected AI providers. Precise reports are easier to verify than broad claims that something “does not work.”