\u2190 Defensibility ledger
Guardian \u00b7 Defensibility ledger \u00b7 drill-down

Raw HTML shell

THE HUSKtrivial to copynegligible business value

What this is

Every buddy homepage and the dashboard itself ship as plain HTML, CSS, and JavaScript. There is no obfuscation, no DRM, no compiled binary standing between a curious visitor and View Source.

That is a deliberate architectural choice, not an oversight: the pages are meant to be fast, portable, and hostable anywhere — including GitHub Pages, which is exactly where they live.

Why it sits here on the chart

Far right on the chart: trivial to copy. Anyone can save the page, and the markup tells them exactly how it was built. Near the bottom: the shell itself carries negligible business value — it is the husk around the seed.

Small bubble: even if someone clones the shell pixel-for-pixel, they have cloned nothing that matters.

Current risk \u0026 defensibility

Risk: accepted, by design. Copying the shell does not copy the data behind it, the sync that feeds it, or the agents that act on it. The exposure is total and the damage is nil — the one combination Guardian is completely comfortable with.

The failure mode to avoid is believing the shell is protection. It is not, and no plan should assume it is.

Guardian\u2019s recommendation

Do not spend one dollar protecting the markup. No obfuscation, no anti-scraping theater, no legal threats over HTML. Put every unit of defensive energy behind the API boundary instead — that is where the business actually lives.

Next action: none. This bubble is correctly placed and correctly deprioritized.