Skip to content
OctaMem
Start building

The mechanics behind the memory.

A closer look at how OctaMem rebuilds context on every request, turns any file into typed memory, and grows sharper the longer it runs.

§ 02The Architecture

Memory in motion.

Every request passes through the same disciplined cycle. OctaMem doesn’t fire a generic search across one bucket of text. OctaMem rebuilds context from three memory types that each serve a distinct purpose, then reassembles them for the model.

Read the technical brief

Search cycle · in motion

Stage 01 / 05
  1. 01 / Caller

    App or MCP

  2. 02 / Access · quota

    Security layer

  3. 03 / OctaMem agent

    Retrieval service

  4. 04 / Three layers

    Memory layers

  5. 05 / Back to app

    Unified context

fig. 1 · Search cycle · stage 1 of 5
fig. 1 · Search · stage 1 / 5

§ From input to inheritance

§ 03File ingestion

Any file. Now memory.

Hand OctaMem the document itself. Contracts, decks, spreadsheets, emails, PDFs. We parse, structure, and store it as typed memory your agents can query forever.

Not embeddings of a blob. Clauses, parties, obligations.

Batch upload
5 files
Avg pages
40
Max file
30 MB
Retention
Configurable

Drop the file. Memory does the rest.

contract-v3.pdfPDF
Master Services Agreementparties · term · obligations

Parsed memory record

contract-v3.pdf

Master Services Agreement,
v3 · executed 2026-04-12

  • ›parties: Acme Corp, OctaMem Inc.
  • ›term: 24 months, auto-renew 12
  • ›obligations: 99.9% uptime SLA, 30-day deletion

Searchable across the account under previous_context: legal-msas.

  • 01 / category

    Documents

    Contracts, briefs, reports, knowledge bases.

    Supported

    • .pdf
    • .docx
    • .docm
    • .dotx
    • .dotm
    • .odt
    • .rtf
    • .txt

  • 02 / category

    Spreadsheets

    Tables, ledgers, datasets — reasoned over rows.

    Supported

    • .xlsx
    • .xls
    • .csv

  • 03 / category

    Presentations

    Decks parsed slide by slide. Factual recall, not pixels.

    Supported

    • .pptx

  • 04 / category

    Email & Data

    Threads, payloads, structured exports.

    Supported

    • .eml
    • .json

§ Intelligence over time

§ 04Compounding intelligence

Intelligence that compounds.

Every session without memory is a reset. Every session with memory is an upgrade.

Day 1

Recognition

Day 30

Pattern awareness

Day 180

Operational depth

fig. 2 · capability over time. Day 360 is off this chart, the curve keeps climbing.
  1. 0Day 1

    Recognition.

    Names, preferences, initial constraints. Conversations feel slightly personalized. The kind a thoughtful intern manages on day one.

  2. 0Day 30

    Pattern awareness.

    The agent remembers your decisions, avoids past mistakes, and follows your workflows without repeated instruction. Fewer questions, fewer corrections.

  3. 0Day 180

    Operational depth.

    Deep institutional context. The agent operates with continuity across teams, releases, and tools. A system of record your AI can actually use.

Day 360 isn’t on the chart. The curve keeps climbing.

+ Compounds with every session