Skip to content
SynthWorldDeterministic identity benchmarks
Esc
↑↓navigate↵open⌘Jpreview
On this page

Roadmap

This is a navigation view, not a release promise. The canonical repository direction is ROADMAP.md. Current capability and publication facts come from the generated registries; issue state alone never changes maturity.

Now

  • Complete the documentation ownership transition so the Blume site is the detailed user surface and root files stay concise.
  • Preserve frozen benchmark bytes while enforcing publication, provenance, and evaluator-boundary controls.
  • Validate the shipped generated enterprise-agentic smoke, standard, and longitudinal tiers through reproducible external-adapter workflows without claiming arbitrary compiled-universe composition or published-benchmark status.
  • Keep C08 v2 benchmark artifacts in their governed candidate state until explicit publication gates are satisfied.

Next

  • Deepen deterministic graph and temporal profiles for lifecycle, authority, and longitudinal evaluation (#3, #2).
  • Extend Explorer beyond its shipped Asteria and generated-smoke projections with large-world filtering, tier comparison, and longitudinal navigation against the V2 generated contract.
  • Improve reproducible consumption of external-adapter results and evidence receipts while keeping offline evaluation distinct from live-lab claims.
  • Continue adversarial evidence and relationship hardening without silently changing existing frozen benchmark identities.

The Enterprise Identity Planning guide records the current journey. Generated enterprise-agentic smoke, standard, and longitudinal paths are available; standard and longitudinal use the separately versioned V2 contract introduced in 0.17.0. The governed benchmark family remains a candidate, and Explorer currently supports Asteria and generated smoke rather than the larger V2 tiers.

Later

  • Explore LLM/RAG and agent-memory privacy packs (#8).
  • Explore digital-wallet and verifiable-credential packs (#9).
  • Explore disaster identity-continuity scenarios with a bounded adapter boundary (#10).

Use the benchmark catalogue for governed current state and GitHub Issues for accepted future scope.

Was this page helpful?