Repository navigation
Add the policy-engine and continuous-access-evaluation pages - #1
Conversation
These were written in the monorepo against `website/`, on the branches for authkestra#310 and authkestra#309, and never reached authkestra's main. The subtree split that created this repository ran on 2026-09-13 and carried everything in `website/` at that time — so it could not pick these up: they existed only on feature branches. Both were removed from those branches when `website/` was merged away, which is what surfaced the gap. Recovered from the monorepo's history (authkestra 8fecf89f and a2a2bf3c) and edited for what has changed since: - Both pinned `version = "0.7"` in their install snippets, for features that exist in no released version at all — the `policy` feature, `authkestra-policy` and `authkestra-ssf` are all still in unmerged PRs. A reader copying either snippet got a resolution failure. Repinned to 0.12, the release they are expected to land in, and each page now carries a "Not published yet" note saying so and pointing at the PR branch for anyone who wants it sooner. - The policy page referenced RFC-005 twice. That number collided with rfc-005-executor-composable-stores.md once both were in one tree, and the policy RFC was renumbered to 008; both references updated. - The CAEP page had no status marker, unlike the policy page's "Proof of concept" caution, so nothing told a reader that only the *receiving* half exists — signals are validated, but nothing acts on them. Made that explicit. Sidebar: neither page fits the existing sections, so both go under a new "Authorization & Continuous Trust" group carrying a Preview badge. Both are Phase 3 roadmap items and neither has shipped, so grouping them behind a badge seemed more honest than filing them beside released features. Verified with `pnpm build`: 25 pages (was 23), both new routes emitted, the new sidebar group and its links present in the output.
|
Converted to draft — do not merge until authkestra#309 and #310 are both in and 0.12 is released. These pages document features that have not shipped. The Not published yet notes make them honest as forward-looking pages, but the install snippets pin Status of the two upstream PRs:
When 0.12 ships, two things to re-check before merging this:
|
Both crates were released in 0.11.1, not the 0.12 these pages guessed at — release-plz cut a patch, and authkestra-ssf-v0.11.1 and authkestra-policy-v0.11.1 are both tagged. The snippets pinned a version that does not exist, which is worse than the stale 0.7 they replaced: 0.7 at least resolved. - Repinned both install snippets to 0.11. - Dropped both "Not published yet" notes. They are simply false now. - Dropped the "Receiving only" caution this branch had added to the CAEP page. It restated, less well, the "Not implemented yet" section already on the page directly above it — three specific bullets and the same issue link. The page did have a status marker all along; it just sits further down than the frontmatter, which is why the earlier pass missed it. The policy page keeps its "Proof of concept" caution: still accurate, as nothing calls the engine yet and the API is expected to change. Verified with pnpm build: 25 pages, both routes emitted.
|
Unblocked and corrected — ready for review. Both upstream PRs merged (authkestra#309, authkestra#310) and both crates shipped. The pins were wrong and are now fixed. I had guessed Both Not published yet notes are gone — they are simply false now. Also dropped the Receiving only caution this branch had added to the CAEP page. It restated, less well, the Not implemented yet section already on the page directly above it — three specific bullets (no session update on revocation, no middleware rejection, no wired routes) and the same issue link. That page had a status marker all along; it just sits further down than the frontmatter, which is why my first pass added a duplicate. The policy page keeps its Proof of concept caution — still accurate: nothing calls the engine, and the API is expected to change. Verified with |
Two pages that were written in the monorepo but never made it here.
Why they were missing
They were authored against
website/on the branches for authkestra#310 (Cedar policy engine) and authkestra#309 (SSF/CAEP), and never reached authkestra'smain. The subtree split that created this repository ran on 2026-09-13 and carried everything inwebsite/at that time — so it could not have picked these up, because they only ever existed on feature branches.The gap surfaced when
website/was merged away on both branches (it no longer exists in the monorepo, so the pages could not stay there either). Recovered from history at authkestra8fecf89fanda2a2bf3c.Edited for what has changed since
version = "0.7"in their install snippets — for features that exist in no released version at all.policy,authkestra-policyandauthkestra-ssfare all still in unmerged PRs, so a reader copying either snippet got a resolution failure rather than a working build. Repinned to0.12(the release they are expected to land in), and each page now carries a Not published yet note saying exactly that, with a pointer to the PR branch for anyone who wants it sooner.RFC-005twice. That number collided withrfc-005-executor-composable-stores.mdonce both were in the same tree, so the policy RFC was renumbered to 008. Both references updated.Sidebar
Neither page fits the existing groups, so both sit in a new Authorization & Continuous Trust section with a
Previewbadge. Both are Phase 3 roadmap items and neither has shipped — badging the group reads more honestly than filing them next to released features.Verification
pnpm build(the repo uses pnpm — there is nopackage-lock.json): 25 pages, was 23, both new routes emitted, and the new sidebar group and its two links present in the built HTML.Note on merge timing
These document features that have not shipped. They are accurate as forward-looking pages given the Not published yet notes, but if you would rather the site never describe unreleased work, this should wait until authkestra#309 and #310 merge and 0.12 is out.