Source-linked memory
Durable records keep the source, time, state, and history needed to inspect why Actionairy remembers something.
Every durable claim keeps its source. You can control whether external AI may process it, export your memory, and follow deletion through completion.
Durable records keep the source, time, state, and history needed to inspect why Actionairy remembers something.
Mark memory Never send, Redacted only, or Allowed. Denied and restricted records are excluded before external AI processing.
Semantic search stores embeddings and policy metadata in the vector index, not the source text. Every hit is rechecked against the authoritative record.
Delete a source and its dependent memory is reconciled. Delete the account and cleanup retries across configured providers until it completes.
Independent research shows that clear data practices influence both adoption and trust in AI products.
The vector index finds candidates. The source record decides what can actually be used.
Account deletion is placed in a durable queue. If a configured provider is temporarily unavailable, Actionairy keeps the local identity long enough to retry safely, then removes it after provider and local cleanup completes. A capability-protected receipt reports progress without exposing account data.
Privacy depends on the product, plan, settings, and data flow. Large AI providers already make meaningful enterprise privacy commitments. Our narrower advantage is concrete: Actionairy makes operating memory source-linked, per-record controllable, exportable, and deletable with a visible path.
Useful AI needs more than a convincing answer. We evaluate task relevance, engineering readiness, and code implementation separately—and publish the limits alongside the results.
Latest Nebius results and live workflow checks. The dated results below remain available for comparison.
Keep real tasks visible. Let evidence decide what belongs in the engineering queue.
investigated cases passing all checks
Small synthetic set, not measured real-world accuracy.
Recognize when a request has enough context to become engineering work—and when it does not.
correct readiness decisions
Readiness is not plan correctness. Independent plan-quality review is still pending.
Test code changes against a separate, externally defined coding benchmark.
64/113 · full-cohort tasks passed
A separate Compress Cloud run, not a meeting-to-code success rate.
Separate measurements of task relevance, plan preparation and coding. Development fixtures are not independently labeled real-world accuracy. These scores must not be combined into an end-to-end success rate.
Meeting extraction: independently labeled capture precision and recall are not yet available. Transcript-upload acceptance is a user-journey check, not an accuracy estimate.
This archived report does not measure independently reviewed plan quality, human correction time, or a representative meeting-to-code success rate. Historical results do not establish current-model performance or competitor superiority.
The DeepSWE mark identifies Datacurve’s benchmark. Our result is a Light Reach evaluation, not a Datacurve endorsement or an official leaderboard entry.