Memory that shows its work.

Allura gives agentic systems a governed way to retain evidence, review what becomes reusable knowledge, and preserve the context behind every retrieval.

_{Product-support diagram. Allura’s published capabilities and implementation boundary are documented below.}

Allura is the governed memory layer for AI. It gives teams and agents a trusted memory, connected context, and the tools to turn work into intelligent outcomes. The memory engine sits at the center; Team RAM, Team Durham, Allura Plugins, and Curator & Governance feed it evidence and draw governed context from it, and everything converges on the apps, agents, and outputs the system produces.

Team RAM is the engineering workforce inside Allura: architecture, coding, testing, governance, routing, and self-improving workflows. You define the goal; the team builds it, verifies it, and makes it better.

Team Durham is the design, brand, and experience workforce inside the Allura ecosystem: strategy, UX, content, visual design, accessibility, and presentation quality — turning ideas into experiences that are clear, beautiful, inclusive, and on-brand.

Every task flows through the same governed loop: memory understands intent and retrieves context, the workforces build and shape, governance verifies, and feedback strengthens memory for the next task.

_{Ecosystem infographics. Allura’s published capabilities and implementation boundary are documented below.}

Allura is built as a reusable agent framework and harness for enterprise software delivery — the same capabilities that let engineering teams design, compose, test, and operationalize agentic workflows with correctness, composability, governance, and testability at scale.

Every capability above is code, not copy — each maps to named source paths in FRAMEWORK.md, and the engineering narrative is in the engineering case study.

Allura_Memory is the authoritative public product repository. Its code and documentation define the engine boundary, memory lifecycle, governance rules, supported interfaces, and current implementation status.

For a framework-level view of orchestration, memory patterns, policy hooks, harnesses and evaluation, and SDK design, read FRAMEWORK.md.

_{The evidence model in six plain-language visuals — conceptual patterns the ecosystem implements, not a live system.}

Every action leaves proof	Access has boundaries
People review important changes	Memory keeps its history
Test before release	An answer can show its work

The Memory Command Center is not a second memory system. It may inspect and request governed actions, but it cannot bypass the engine or own canonical state.

Bumblebee is a governed supply-chain threat-intelligence plugin: a pinned upstream scanner wrapped as a deterministic, policy-gated Allura agent tool. It is the framework above in production form — orchestration, least-privilege credentials, fail-closed ingest, policy-gated promotion, and evidence retained at every step.

From scan to trusted exposure	Zero trust by design
Role-based access and scoped authority	A vulnerability has to prove itself
Bad scans never replace good inventory	Bumblebee runs on the governance layer

_{Product infographics for the bumblebee plugin. The pinned scanner, ingest pipeline, and policy gates behind every claim are in the bumblebee repository.}

• Evidence before completion claims.
• Human approval before governed promotion.
• Provenance before reuse.
• Tenant boundaries before retrieval.
• Explicit degraded or unknown states.
• Reproducible verification for public claims.

GitHub may display other public repositories owned by this organization. Some are supporting experiments, delivery harnesses, or reserved namespaces; visibility does not make them equal parts of the Allura product.

Allura is memory that shows its work. Its public claims should do the same.