Knowledge entries

Knowledge entries are durable reference materials that Altertable assistants can search while answering questions or running tasks. Use them for context that should be remembered exactly, such as metric definitions, operating procedures, product terminology, customer notes, or repository documentation.

Knowledge entries complement memories. Entries are written or connected by your team; memories are learned from agent runs and feedback.

Entry types

You can add knowledge in two common ways:

• Direct entries: notes, explanations, and small documents created inside Altertable.
• Repository syncs: connected GitHub repositories that make Markdown, text files, and dbt metadata available as searchable context.

Use direct entries for business rules and lightweight guidance. Use repository syncs when the source of truth already lives in code, analytics projects, or operational documentation.

What to include

Good entries are specific and reusable:

• How your company defines revenue, activation, churn, and retention.
• Which tables are authoritative for common analyses.
• Known caveats in source systems or ETL jobs.
• Product terminology and internal names that do not appear in schemas.
• Investigation playbooks for recurring incidents or workflows.

Keep entries current. Stale guidance can be worse than missing guidance because agents may confidently apply the wrong rule.

Learn more

• Semantic Layer: define metrics and dimensions directly on models.
• Memories: understand learned context from agent work.
• Ask AI: use knowledge during conversational analysis.