wiki/projects/abracadoo/implementation-and-runtime

Rendered from markdown source. Open raw source on GitHub.

Implementation and Runtime

This seam holds the complete app runtime seed for Abracadoo: the browser shell, HumanKey contact flow, local vault adapters, backup path, and PWA packaging that makes the app a usable local-first surface instead of a static mockup.

Current Shape

• 3 app runtime bundles.

Representative Files

• Abracadoo HumanKey seed scaffold v2.zip · archive copy
• Abracadoo HumanKey seed browser shell v4.zip · archive copy
• Abracadoo HumanKey seed runtime bundle v9.zip · archive copy

Working Read

The earlier seeds show the runtime becoming real in stages: first the scaffold, then the browser shell, then the finished runtime bundle. The current seed wires a browser UI around contact creation, QR-code generation, code verification, local backup import/export, and IndexedDB-backed storage. The app surface is therefore more than a mock landing page: it is a runnable HumanKey-first runtime with a visible local state boundary.

This page stays separate from the public site-variant rail so that code lineage, copy lineage, and design lineage can move independently.

Related Links

• Abracadoo
• Architecture and Trust
• Brand and Overview
• Site Variants
• Abracadabracadoo

Next Actions

1. Keep the runtime seed separate from the public-facing site bundles.
2. Add future code bundles here only if they remain part of the same implementation seam.
3. Split again only if a second durable runtime branch appears.