Commens
Product

A shared, authoritative knowledge layer for enterprise AI.

Commens turns scattered enterprise context into agent-ready knowledge: curated, structured, permissioned, versioned, and continuously improved through feedback and real usage. It sits upstream of models, agents, and orchestration, shaping and governing the knowledge they all depend on.

Architecture position

Models generate. Agents execute. Commens shapes the intelligence all of these depend on.

Commens sits upstream of IAM, runtime policy engines, orchestration platforms, and AI inventory tools. It shapes and governs the intelligence that makes action more reliable before it is ever attempted. It works with those adjacent layers rather than replacing them.

When an orchestration layer asks what an agent should be allowed to do, the answer comes from Commens. When an agent needs organizational context, constraints, or policy, that knowledge comes from Commens. When a model needs to act within bounds, those bounds are encoded in the authoritative knowledge Commens provides.

THE AI STACK: WHERE COMMENS FITS

The AI Stack: Where Commens Fits

INTERFACES
NATIVE AI
CUSTOM UIS
BUSINESS APPS
AGENTS · MCP · TOOLS · APIS
YOUR AGENTS
VENDOR AGENTS
THIRD-PARTY
AGENT EXECUTION & ORCHESTRATION Models, tools, planning, reasoning, recovery
ENTERPRISE APPLICATIONS & DATA
SaaS · systems of record · data warehouses
"Commens governs the knowledge that shapes AI behavior, upstream of execution, across every layer."
Core capabilities

Seven things AI needs to know, delivered as one layer.

CORE CAPABILITIES

Core Capabilities

MEMORY
Authoritative context, curated and versioned.
POLICY
Rules as knowledge, not gates.
FEEDBACK
Real work becomes better knowledge.
OVERSIGHT
Reviewed, approved, refined by teams.
IDENTITY
Who is acting, what they can know.
AWARENESS
Context across tools and agents.
"Six dimensions of governed knowledge."

Authoritative context

AI needs to know

Goals, preferences, constraints, history

Structured knowledge store: curated, versioned, and trusted as the source of record for every agent that needs to reason about your organization.

Policy as knowledge

AI needs to know

Rules, boundaries, compliance, organizational constraints

Policy encoded in context so agents internalize bounds rather than hitting gates after the decision has already been attempted.

Feedback intelligence

AI needs to know

What worked, what failed, how to improve

Structured feedback loops that turn experience into durable knowledge: reviewable, auditable, and reusable across teams.

Usage-driven curation

AI needs to know

Tacit context, decisions, and review artifacts revealed while completing work

Capture and distill real human-AI interactions, approvals, exceptions, and rationales into reusable knowledge and precedents.

Collaborative oversight

AI needs to know

Reviews, approvals, exceptions, escalations, rationales

A shared oversight layer where teams review context, approve exceptions, refine policy, and turn review decisions into reusable artifacts instead of one-off thread replies.

Organizational identity

AI needs to know

Who is acting, what they are permitted, what applies to them

Identity and permissions treated as context that shapes behavior upstream, beyond a separate access-control layer bolted on after the fact.

Cross-system awareness

AI needs to know

Context that spans tools, agents, and workflows

Knowledge governance that extends across the organizational surface, so context does not fragment back into per-tool silos.

The knowledge store

A curation system, not a repository.

Commens normalizes scattered inputs, preserves provenance, encodes permissions, maintains freshness, and turns successful use into reusable intelligence.

Memory

Curated context: goals, preferences, history, institutional knowledge, and source-of-record context with freshness and provenance. Structured, evolving, authoritative knowledge rather than raw data, documents, or prompts.

Policy

Organizational rules, compliance requirements, constraints, and boundaries encoded as knowledge that agents internalize. When AI knows your policies, it acts within bounds because the bounds are part of what it knows, without a gate to stop it.

Identity & permissions

Who is acting, what they are authorized to access, what boundaries apply. These function as context that shapes behavior upstream, beyond simple access controls.

Usage traces

Task-level interactions, clarifications, and resolved ambiguity, together with the approvals, exceptions, escalations, and recorded rationales that sit alongside them. First-class inputs, the raw material for better future knowledge and reusable precedents.

Feedback loops

Every interaction refines the knowledge driving the next one.

A shared, reviewable mechanism for capturing what worked, what failed, what should change, and how the system should improve, including evaluation signals, validation outcomes, exceptions, and reliability evidence. Structured, reviewable, auditable feedback turns AI from a one-off tool into a continuously improving system.

Collaborative oversight

Where teams review, approve, and refine, and the decisions become durable.

Oversight is an operating mechanism, not a philosophical layer. Teams review the context agents act on. Stakeholders approve exceptions and escalate edge cases. Subject matter experts refine policy. Every non-routine decision (the approval, the exception, the rationale, the precedent) is captured, versioned, and made reusable, so the next similar case inherits the judgment of the last one.

ARCHITECTURE POSITION

Architecture Position

INTERFACES
Chat · IDE · Apps
AGENTS
Research · Review · Ops
ORCHESTRATION
Runtime · Routing · Tools
ENTERPRISE DATA
SaaS · Records · Warehouses
COMMENS · GOVERNED KNOWLEDGE CURATION LAYER
MemoryPolicyFeedbackOversightIdentityAwareness
"Models generate. Agents execute. Commens governs the intelligence."
Compared to

Why Commens is a different kind of layer.

Compared to

Runtime policy engines

Policy engines police actions at the gate. They are reactive, brittle, and limited to the scenarios they anticipate. Commens shapes the intelligence upstream so agents behave correctly across every scenario, including ones no filter was written for.

Compared to

Model-specific memory

ChatGPT memory and Claude Projects are locked to a single provider, siloed to one user, opaque to the team. Commens provides model-agnostic, authoritative, organizational knowledge infrastructure.

Compared to

Prompt engineering tools

Prompt tools optimize individual inputs rather than governing the knowledge layer. Commens makes every prompt smarter by governing the context every prompt draws from.

Compared to

RAG and search

Search finds documents. Commens governs and shapes the intelligence agents act on: structured, current, permissioned, and improved through use.

Compared to

Compliance-only governance

Audit and blocking are necessary but insufficient. Commens makes AI behave correctly in the first place, reducing the need for after-the-fact intervention.

What Commens is not

An honest product boundary beats a vague one.

Commens works alongside IAM, runtime policy engines, orchestration platforms, and AI inventory tools. It sits upstream and shapes the knowledge, policy context, permissions context, and review artifacts they rely on.

  • Not IAM
    Feeds IAM the permissions context that shapes what an actor can know.
  • Not a runtime policy engine
    Gives gates the authoritative rules and rationale they enforce.
  • Not an orchestration platform
    Supplies the memory and policy agents draw on during execution.
  • Not an AI inventory tool
    Turns inventory data into reviewable knowledge about where AI is actually used.

Better-shaped, better-curated knowledge improves judgment, execution, learning, trust, and control at once, as the same motion.

The sanctioned path has to be better than the ad hoc one. That is the bar Commens is designed to meet.