Skip to content

Milestones

List view

  • Everything KERI as pure, platform-agnostic logic — key-state machine, escrow verdicts, duplicity/superseding, delegation, receipts, custody traits. DECIDED 2026-07-05 (K0): lives in a sibling `keri` crate in THIS repo (workspace), published as keri-rs 0.x, versioned independently of frozen cesr-rs, sharing the flake/fuzz/differential infra, consuming ONLY cesr public API. No db, no runtime, no config — those live in the thin keri binary / bombay M4 above. keripy is the SEMANTIC oracle (K9 vectors), never the architecture template. House style: GATs, zero-copy Bytes, no_std+wasm green. Order: K0 first, then K1–K9.

    No due date
    2/14 issues closed
  • Scope + policy decisions that are breaking (or expensive) to change after 1.0. Fed by the 2026-07-05 cross-repo roadmap review: settle the serder ilk scope, the delegation-validation layer boundary, the crypto surface (X25519 sealed box), the last keripy parity gap, and the written stability policy consumers pin against. When this closes → cut 1.0.

    No due date
    0/5 issues closed
  • The deterministic scheduled-watcher engine that replenishes the backlog (keripy-sync + crypto/design/devx).

    No due date
    0/3 issues closed
  • Adopt better crypto crates/algorithms; stay current. Ongoing, watcher-fed.

    No due date
    0/2 issues closed
  • Prelude/flatten, examples, error ergonomics. Refine the public surface now the freeze is lifted.

    No due date
    6/6 issues closed
  • Allocation audit, base64 fast path, borrowed stream parsing. The paramount goal, pursued once Phase 0 instruments exist.

    No due date
    4/4 issues closed
  • Benchmarks, fuzzing, and differential tests — the measurement + guardrails that must exist before performance work.

    No due date
    6/8 issues closed
  • Reach + track parity with keripy's current CESR/KERI code tables (fed by the keripy-sync watcher).

    No due date
    1/1 issues closed
  • agency drops commons/cesr-*+keri-* and depends on cesr; bombay (#72) and nexus (if it needs KERI) wire it in.

    No due date
  • Re-establish the FROZEN API policy post-extraction; pick the git-dep/version strategy consumers pin to.

    No due date
    1/1 issues closed
  • Confirm cesr builds no_std + wasm32 for on-device KERI (lite-bombay). std/alloc/crypto behind features; verify P-256 path for Secure Enclave.

    No due date
    1/1 issues closed
  • filter-repo the CESR/KERI history out of agency into ONE cesr crate with feature-gated modules (core/crypto/stream/utils/keri/serder); merge Cargo.tomls; rewrite imports; preserve frozen public API as module paths.

    No due date
    4/4 issues closed