Skip to main content
Request a pilot

The intelligence cycle, with the discipline built in.

OMAR's mnemonic is a workflow, and the workflow is the cycle analysts already practice. Each stage has something the analyst does and something the system refuses to let slide.

Request a pilotRead the capability catalog

Observe, Map, Analyze, Report.

Observe

Planning and direction; collection

What the analyst does
State the requirement, confirm scope, authorize sources, execute bounded collection, inspect coverage.
What OMAR enforces
Requirement-led tasking. Explicit source authorization. A coverage ledger that records what was and was not searched. Raw bytes sealed and hashed before anything reads them.

Map

Processing and exploitation

What the analyst does
Select and preserve primary material, extract entities, events, locations, and relationships, separate identities that cannot safely be merged.
What OMAR enforces
Discovery metadata kept distinct from preserved evidence. Every extracted object cites an exact span. Mentions stay separate from identities until reviewed.

Analyze

Analysis and production

What the analyst does
Review proposals, resolve identity, judge corroboration and contradiction, explore graph, timeline, and map, monitor for change.
What OMAR enforces
Reviewable assertions with confidence components and contrary evidence. Reversible decisions. Accepted-only projections. Honest no-change monitoring.

Report

Dissemination and feedback

What the analyst does
Assemble accepted claims into a brief, hand off to another analyst, export a signed package, feed new questions back into the case.
What OMAR enforces
Citation validation that re-hashes preserved bytes and re-slices exact spans before publication. Immutable handoff snapshots. Signed transfer manifests.

Ten stages, one ledger.

Work is organized as organization, project, case, chat. Case chats are shared by default. Each completed run ends with a small set of real, state-aware next actions derived from durable case records, not from browser state.

  1. 01

    Requirement

    You: State the question, purpose, desired output, urgency, known facts.

    OMAR: The message becomes a durable run with ordered, replayable events.

  2. 02

    Scope

    You: Confirm subjects, aliases, identifiers, locations, languages, dates, exclusions, source classes, budget.

    OMAR: The deterministic planner produces a versioned, editable plan with exact per-source transport queries.

  3. 03

    Collect

    You: Approve or auto-authorize; watch progress and coverage.

    OMAR: Policy is evaluated server-side; connectors return raw bytes; bytes are sealed and stored before parsing.

  4. 04

    Disambiguate

    You: Separate people, accounts, organizations, and events that cannot be resolved safely.

    OMAR: Mentions stay separate. An ambiguous reference pauses the plan instead of guessing.

  5. 05

    Preserve

    You: Select a candidate and capture the page, document, or archive.

    OMAR: The publisher page, rendered HTML, and screenshot are stored as separately hashed objects.

  6. 06

    Analyze

    You: Run deterministic extraction and optional AI proposals against preserved evidence.

    OMAR: Every proposal cites an exact span in the sealed bytes.

  7. 07

    Review

    You: Accept, reject, qualify, merge, split, or mark contradiction.

    OMAR: Decisions append review and audit events with rationale and version checks.

  8. 08

    Visualize

    You: Explore evidence, graph, timeline, map, narrative, and browser views.

    OMAR: One active item drives all views. Empty views stay empty and say what is missing.

  9. 09

    Monitor

    You: Turn an accepted focus or area into a scheduled watch mission.

    OMAR: Durable cycles; snapshots compare; alerts trigger only on real change or degradation.

  10. 10

    Report

    You: Build a cited brief, hand off, or export.

    OMAR: Claims are validated against re-hashed evidence and exact spans. Outputs render to HTML, PDF, and DOCX.

Who may decide something is true.

The single most important architectural idea in OMAR is a fixed hierarchy. External sources are time-varying inputs. Models are non-deterministic proposal generators. Neither may rewrite the function.

  1. 1

    Mission and law

    Organizational authority, purpose, source rights, handling rules, and deployment domain define what may occur.

  2. 2

    Policy and plan

    Versioned policy decisions and an approved or automatically authorized query plan define how a requirement may be pursued.

  3. 3

    Captured evidence

    Preserved bytes, metadata, digest, retrieval context, marking, and rights define what the system actually observed.

  4. 4

    Deterministic transforms

    Versioned parsers, normalizers, extractors, scoring rules, and citation validators create reproducible derived objects.

  5. 5

    Analyst review

    Authorized people accept, reject, merge, split, annotate, or qualify proposals. Every decision appends history.

  6. 6

    AI proposals

    Models may propose text or structure but cannot outrank any layer above.

Decision = f(case context, analyst directive, query plan, source capability, policy, connector version, captured evidence)

What “nothing found” means.

OMAR distinguishes outcomes that a lesser tool collapses into “no results.” The interface shows every external source query, source health, filters that removed results, and missing source categories, and offers only recovery actions that actually work.

  • A source returned no records.
  • Records were found but failed the exact scope.
  • A source was unavailable, rate-limited, or unauthorized.
  • Discovery records were found but primary content is uncaptured.
  • Material exists but no reviewed assertion is supported.
  • Identities remain unresolved.

It prevents “no result” from becoming “nothing exists,” and prevents a full page of results from becoming “complete coverage.”