— HOW IT WORKS

Six stages, one governed lifecycle.

From the moment a conversation happens to the moment an auditor checks the record, every stage feeds the next — and every stage leaves evidence.

01 · CAPTURE
Every session, at the source
IDE chats, web sessions, CLI runs, and artifacts ingest in real time from verified capture clients — 1.86 s p95 from conversation to recallable, stored as typed transcript parts with code and file metadata.
02 · CURATE
Structure before it shapes behavior
AST-aware chunking and policy-based filters structure the knowledge. Review queues, decay policies, and trust classification decide what becomes durable memory — under maker–checker where policy requires.
03 · RETRIEVE
Precise, minimal context
Hybrid retrieval and context policy assemble the smallest reliable payload for the task — tri-state include/exclude control over what any model sees, compiled into a hashed, receipted block.
04 · ORCHESTRATE
Actions under supervision
MCP tools and governed action libraries execute through the two-phase gate: authorize, approve where destructive, execute, verify post-state, sign the receipt. Per-project allowlists bound what agents may even request.
05 · ANALYZE
Time-travel over the record
Apache Iceberg tables power SQL-friendly, point-in-time analysis: token economics, retrieval hit ratios, disclosure history — what the organization knew, believed, and spent, at any moment.
06 · GOVERN
Policy, enforced and evidenced
Row-level isolation, encryption, RBAC, and immutable audit trails enforce enterprise policy — and the enforcement itself generates the signed evidence your auditors verify offline.
ONE REQUEST, END TO END
SESSION MEMORY GATE EXECUTE VERIFY approval receipt AUDIT

See a request trace, live.

Request a demo Explore the platform
Also from Neurabyte: Cupel
Lore's core mechanisms are patent-pending. Product names are trademarks of their respective owners; listing an integration doesn't imply a partnership.
© 2026 NEURABYTE INC.