Is it okay to use WebAuthn API for this?

Hi!

I’m working on an open-source, self-deployable coordination layer for
sovereign frontends:
https://github.com/z-base

The key capabilities I’m trying to enable are:

   -

   Fully offline-capable encrypted state reconstruction
   -

   Semantically blind support server (“base station”)
   -

   State recovery and accessibility across devices (via cross-platform
   credentials)

I’m currently using navigator.credentials / WebAuthn as the key depency for
this:
https://www.npmjs.com/package/@z-base/zero-knowledge-credentials

Here is the source code of the class interacting with  navigator.credentials
https://github.com/z-base/zero-knowledge-credentials/blob/master/src/ZKCredentials/class.ts

For additional context, here’s a draft spec that conceptualizes the
architecture (emphasis on: draft):
https://github.com/z-base/z-base/blob/main/docs/specifications/CONCEPT.md

Is there any reason I shouldn’t use navigator.credentials for this? This
isn’t “standard” usage, but it’s also not trying to be. It’s using the API
in an innovative way to solve a very specific problem.

I wanted to run this by you before I build a full-fledged system around it
and later discover that support for something like this won’t remain.

To emphasize: I’m intentionally not using this for identity. The goal is a
fully private, offline-capable, but backed-up and realtime-capable user
space, within which users might control a published DID or similar.

Regards,
Jori Lehtinen