Beever Atlas v0.1 has launched! Star us on GitHub
Beever AtlasBeever Atlas

Data Models Reference

Overview

Beever Atlas uses a hierarchical knowledge model with three tiers:

  • Tier 0: Channel Summary - Overall channel narrative
  • Tier 1: Topic Clusters - Grouped related facts
  • Tier 2: Atomic Facts - Individual extracted knowledge units
  • Graph: Entities and Relationships - Knowledge graph

AtomicFact

A single extracted fact stored in Weaviate (Tier 2).

Fields

Prop

Type

Example

{
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "memory_text": "The team decided to use JWT tokens for authentication with a 1-hour expiration.",
  "quality_score": 0.85,
  "tier": "atomic",
  "cluster_id": "cluster_123",
  "channel_id": "C12345",
  "platform": "slack",
  "author_id": "U12345",
  "author_name": "Jane Smith",
  "message_ts": "2026-04-13T10:30:00Z",
  "thread_ts": null,
  "source_message_id": "1234567890.123456",
  "topic_tags": ["authentication", "security"],
  "entity_tags": ["JWT", "OAuth"],
  "action_tags": [],
  "importance": "high",
  "graph_entity_ids": ["entity_jwt_decision"],
  "fact_type": "decision",
  "source_lang": "en"
}

TopicCluster

A Tier 1 topic cluster grouping related atomic facts.

Fields

Prop

Type

Example

{
  "id": "topic_123",
  "tier": "topic",
  "channel_id": "C12345",
  "title": "Authentication System Migration to JWT",
  "summary": "The team migrated from session-based auth to JWT tokens. This decision was driven by scalability needs and better mobile support.",
  "current_state": "Migration complete, JWT tokens in production with 1-hour expiration.",
  "open_questions": "Token refresh strategy still under review.",
  "impact_note": "Affects all API clients and requires re-authentication flow updates.",
  "status": "active",
  "member_count": 15,
  "staleness_score": 0.1
}

ChannelSummary

A Tier 0 channel-level summary consolidating all topic clusters.

Fields

Prop

Type


GraphEntity

An entity node in the Neo4j knowledge graph.

Fields

Prop

Type

Entity Types

  • Person: Team members, stakeholders
  • Decision: Decisions made, conclusions reached
  • Project: Projects, initiatives, work streams
  • Technology: Tools, frameworks, libraries
  • Team: Teams, groups, departments
  • Meeting: Meetings, standups, reviews

GraphRelationship

A relationship edge in the Neo4j knowledge graph.

Fields

Prop

Type

Relationship Types

  • DECIDED_BY: Person decided Decision
  • PARTICIPATED_IN: Person participated in Meeting
  • WORKS_ON: Person works on Project
  • USES: Project uses Technology
  • MEMBER_OF: Person member of Team
  • RELATED_TO: General relationship

WikiPage

A generated wiki page with enhanced Markdown content.

Fields

Prop

Type

WikiPage Types

  • fixed: Standard pages (overview, people, decisions, etc.)
  • topic: Pages generated from topic clusters
  • sub-topic: Nested topic pages

WikiCitation

A source citation for wiki page content.

Fields

Prop

Type


EntityKnowledgeCard

Cross-channel aggregation of all knowledge about a single graph entity.

Fields

Prop

Type


Model Relationships

ChannelSummary (Tier 0)
    ├─> TopicCluster[] (Tier 1)
    │       └─> AtomicFact[] (Tier 2)
    │               └─> GraphEntity (via graph_entity_ids)
    │                       └─> GraphRelationship
    └─> WikiPage
            └─> WikiCitation (cites AtomicFact)

Storage

  • Weaviate: AtomicFact, TopicCluster (Tier 1-2)
  • MongoDB: WikiPage, WikiMetadata, ChannelSummary
  • Neo4j: GraphEntity, GraphRelationship (knowledge graph)
How is this guide?

On this page

Ready for production?

Ship to production with SSO, audit logs, spend controls, and guardrails your security team will approve.

Talk to the team

or email hello@beever.ai