Knowledge
Reference
What has the business written down?
Focused documents with prices, policies, hours, FAQs, or other stable facts, shared with the teammates that need them.
AI Teammates · Knowledge, memory & learning
Know the truth. Carry the judgment forward.
Knowledge is what your business supplies. Memory is the context worth keeping. Learning is the judgment distilled from review. Loquent separates all three so each can be useful without becoming invisible.
Knowledge base
Weekend service policy · supplied by the business
Contact memory
Maria prefers text after 5 PM · remembered with the person
Learned policy
Confirm the date before offering a time · learned from review
Three kinds of context
Different sources. Different controls.
Calling everything ‘memory’ makes trust harder. Loquent gives each kind of context a clear origin and purpose.
Memory
Continuity
What fact should survive the next conversation?
Durable teammate facts and long-lived Contact facts, with history and restrictions where needed.
Learning
Judgment
What pattern has review taught the role?
Repeated corrections and decisions become versioned behavior guidance rather than hidden prompt drift.
Learning without a black box
A correction becomes useful when it becomes a pattern.
Loquent does not market every edit as instant transformation. It gathers structured review signals, looks for agreement, and keeps the resulting policy under human control.
-
Review
You edit a draft or answer a question.
The difference between the proposed work and your judgment becomes a structured signal.
-
Repeat
Related lessons begin to agree.
Learning is based on repeated or corroborated evidence, not a single stray edit.
-
Digest
The useful lesson becomes behavior guidance.
The teammate’s learned policy is versioned so changes remain inspectable and reversible.
-
Approve or undo
You keep the final say over what sticks.
Review, edit, reject, undo, roll back, or pin what the teammate must never change.
The owner controls
Improvement should remain reversible.
Choose whether learning waits for approval. Read the proposed policy, edit it, reject it, undo a change, roll back the policy, or pin a fact the teammate may never overwrite.
Approve first
Hold proposed learning until a person reviews it.
Edit or reject
Correct the lesson before it changes future work.
Undo or roll back
Return to an earlier version when judgment changes.
Pin
Lock a non-negotiable fact against teammate changes.
Keep exploring
See how the rest of the system connects.
Give the team your truth. Keep the lessons accountable.
Request an invitation and we’ll map the business reference, durable context, and review controls your first teammate needs.