Build Notes: how the systems work.

The problem

A rate on its own settles very little when two holdings do not share a horizon. The calculator’s example set includes $50,000 of T-Bills at 4.8% for two years and $250,000 of real estate at 6.5% for ten. The T-Bills compound to $54,915.20; the real estate compounds to $469,284.37. Comparing 4.8% to 6.5% does not make those positions comparable, and comparing their ending dollar values is worse.

AlcorFinance gives every row a common alternative. It compounds the same principal at a stock-market baseline over that row’s own term, then subtracts the asset outcome. At a 10% baseline, the real-estate alternative is $648,435.62, so the gap is $179,151.25, or 27.63% of the stock outcome. The T-Bill gap is $5,584.80, or 9.23%.

What the working version does

You enter a class name, amount, annual rate, and term in years. Every row reports the asset future value, stock-baseline future value, opportunity cost, and the gap as a percentage of the baseline future value. A two-year instrument and a ten-year holding can occupy the same table because the baseline is recomputed over each row’s own term.

The baseline is an input, not fetched market data. Change it and every row plus the portfolio summary recomputes on each keystroke. Dropping the baseline from 10% to 6.5% makes the example real-estate row’s opportunity cost $0 because the two rates now match, while positions above the baseline become negative opportunity costs and render green.

The calculator is a WordPress must-use plugin exposing one shortcode. Its math is compound interest applied twice per row: once at the asset rate and once at the baseline rate. It has no persistence layer, no network request, no local storage, and no dependency. The numbers entered into the calculator stay in the browser; the page around it still carries the site’s ordinary analytics.

Run AlcorFinance in the browser →

First, the naming collision

AlcorOS means two things at Alcor. The Products & Projects page uses the name for the desktop environment and AlcorApps. This note is about the WordPress plugin. They share a naming scheme, not a codebase.

The problem

A WordPress site needs tracking, a contact path that is not a spam funnel, and a way to inspect basic health. On many sites those become unrelated plugins with separate settings, tables, mail paths, and assumptions. AlcorOS takes the other approach: one plugin, a shared settings row, and apps that can be enabled per site.

What is in the current production build

AlcorAnalyticsowns its event and blocklist tables. Its inline tracker records pageviews, delegated clicks, and form submissions for logged-out visitors. GA4 and Meta are optional; with their IDs blank, the site runs first-party tracking only. The public ingest route accepts three event types and soft-limits each IP to 120 events per active burst; the counter resets after that IP has been quiet for a full minute. Blocked IPs are refused; watched IPs are accepted and flagged.

AlcorContactrenders the short homepage form and the longer buyer-page form. It scores a hidden honeypot, unrealistically fast completion, excessive links, repeated posts, and the IP blocklist. Clean submissions receive a per-render UUID, are written to the structured opportunity store, deduplicated, emailed with Reply-To set to the sender, and only then become a conversion signal. Attribution is stored from an allowlist that excludes the person’s name, email, company, website, and freeform message.

AlcorSiteManagerprovides local health probes, seven-day event counts, page links, and route visibility.AlcorDemorenders the dock, taskbar clock, draggable windows, and screenshot-backed app views on the public demo page. The window system is interactive; the desktop applications shown inside those windows are captures rather than browser-hosted copies.

How the app contract works

The core registers bundled apps, then can load deployed apps fromwp-content/alcoros-apps. An app is a class with a static initializer, a file, a label, and a description. Cross-app calls are guarded, so the contact form does not require analytics to be enabled.

Administrator-only deployment routes stage zip payloads, reject traversal-like entries, optionally lint PHP when a CLI is available, back up the current target, and restore that backup if the copy fails. That is useful plumbing, but it is not presented here as a reviewed third-party extension marketplace: there is no client-facing UI, no published security review, and no third-party app deployment history behind the claim.

The design constraint

A default QR code scans and looks like nothing in particular. That is usually fine on a screen. On packaging, a menu, an event sign, or a campaign surface, the code is part of a layout somebody paid to make coherent. Branding it is not only recoloring: the symbol has to survive the logo or styling placed on top of it.

What the sample proves

The published PNG is a decodable symbol rather than a decorative mockup. Its payload ishttps://alcor-industries.com. The symbol reports version 4, a 33×33 module grid, mask pattern 6, and error-correction level H.

Level H is the load-bearing choice. It provides the highest Reed–Solomon recovery level, commonly described as roughly 30% of data codewords. That is not permission to cover 30% of the visible square: finder, timing, and format patterns still have to survive. A center logo spends part of the recovery budget, so the practical sequence is to choose H first, keep the logo away from structural patterns, and use only a fraction of the available redundancy. The logo tile in the published sample covers a few percent of the grid.

The build request therefore starts with two concrete questions: what should the code point at, and where will it be printed? The quote can name the file formats, dimensions, and testing surface before work starts.