Palimpsest · Roadmap
What’s planned
Where Palimpsest stands today, why nothing else is scheduled, and what it isn’t going to do.
Where it stands
The full specification is implemented.
That covers the keystroke-path grammar and its canonicalizer, the two-hash enhancement mode, standalone and PAKE-backed modes, OPAQUE integration, rate limiting and lockout, a zero-dependency reference credential store, framework adapters, an accessible fallback flow, optional timing-biometric scoring, and an Auth0 integration with a verifier guard. The canonicalizer is the trust root, and it’s covered by property and fuzz tests.
Planned work
Nothing new is scheduled
Every part of the Palimpsest specification is built, including the optional parts. There’s no open work in the tracker and no queued feature. A credential scheme like this should get its next version from outside review and deployment experience, so there’s no backlog written ahead of time.
Out of scope
Not on the roadmap
If you need one of these, Palimpsest isn’t the right product for you.
-
Replacing your identity provider
Palimpsest is a credential scheme that plugs into one. The Auth0 integration shows how: it runs as a guard inside an Auth0 Action.
-
A password manager
It changes what the secret is. It doesn’t store secrets for you.
-
Security claims without review
The design, threat model and test strategy are written down so people can pick them apart. Don’t adopt it because of a product page.
How this is maintained
Every item above is tracked in our own issue tracker, and this page is rewritten from it. Open bugs and security work are left off. Those stay in the tracker until they’re closed.
Want more detail on something here, or to know where it stands? Write to dmoore@
Next
Put Palimpsest in your pipeline
Ask about hooking it up to the repositories and agents you already run.