Architecture for compiled context, not runtime guesswork

Octoplexity moves source understanding to ingest and refresh time, then serves compact, cited packets through deterministic runtime checks.

01Ingest

02Parse

03Compile

04Weight

05Retrieve

06Serve

07Improve

Docs uploaded or crawled

Files

PDF Product Guide.pdf

DOC Release Notes.docx

PPT Runbook.pptx

MD Security.md

Web

docs.example.com

help.example.com

Document Compiler

StructureHeadings, hierarchy, relationships

ClaimsFacts, statements, guarantees

EntitiesProducts, terms, people, systems

SummariesSection and document summaries

ProvenanceSources, timestamps, authorship

Compiled artifacts

Graph

Claims

Packets

Index

Sources

Context Packet

Cited context

The system supports SSO with SAML 2.0 and OIDC [1]. Audit logs are retained for 365 days [2].

[1] Security.md[2] Runbook.pptx

API / MCP output

{
  "context": {...},
  "citations": [1, 2]
}

Chatbot answer

SSO is supported via SAML 2.0 and OIDC. Audit logs are retained for 365 days.[1][2]

Ingest

Validate sources, store raw files privately, compute content hashes, and create document versions.

Parse

Extract clean text, tables, code blocks, section paths, and source spans from each document.

Compile

Generate claims, entities, summaries, relationships, contradictions, and provenance-linked artifacts.

Weight

Rank artifacts by authority, hierarchy, freshness, entity centrality, usage, confidence, and conflict signals.

Retrieve

Classify intent, apply permissions, choose structural, graph, claim, summary, or vector retrieval paths.

Serve

Assemble a compact context packet with citations, warnings, source freshness, and token-budget controls.

Improve

Use feedback, accepted answers, failed retrievals, and source changes to update weighting over time.

The runtime path stays policy-first.

A request authenticates the subject, resolves organization and project scope, checks plan and source permissions, chooses a retrieval plan, assembles the packet, records usage, and returns context with citations.

QuestionCan this customer use SSO and keep audit history?

Intent: policy or compliancePermission filter: support roleSources: security docs and admin guide

Context packet

SSO supports SAML 2.0 and OIDC. Audit events include member, source, key, billing, and permission changes.

[1] Security.md[2] Admin Guide

Give your AI systems a better context layer.

Bring documentation, support knowledge, sales context, and website answers into one compiled source of truth.

Request access