> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tendor.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Company Memory
> Use your organisation's evidence-backed memory, fact history, and relationships.
Company Memory turns your organisation's approved Projects, Library evidence, shared mailbox
messages, work conversations, and Company Profile into a shared, evidence-backed wiki. It helps
people and Ask AI reuse what the organisation already knows without replacing the original files
and records.
Company Memory is shared with members of your organisation. **My Memory is not currently
available.** Tendor does not create a separate personal company-fact store or automatically share
private memories.
## What is authoritative?
The original Project, file, message, conversation, profile, or human decision is always the final
authority. Company Memory pages organise that evidence for reuse. Structured facts and
relationships help you inspect time, conflicts, and impact, but they link back to the page and
original source so you can verify important details.
| Item | What it means |
| ----------------------- | ------------------------------------------------------------------------- |
| **Company Memory page** | Shared, readable organisation knowledge with source links |
| **Current fact** | A high-risk fact supported for the current time |
| **Fact history** | Older, superseded, conflicted, or retracted versions |
| **Relationship path** | One- or two-step route to the pages and sources that support a connection |
## Browse pages and sources
Open **Company Memory** to browse the page tree, search for a topic, or open People and Project
knowledge. Source links and footnotes take you back to the original evidence where your permissions
allow it.
When a page supports a bid decision, check the source before relying on a deadline, requirement,
insurance limit, credential, contact, Project/submission status, or receipt. A missing or unavailable
source should be treated as a gap, not as confirmation.
## Review current facts and history
The **Current facts** area shows allowlisted facts that are valid now. Direct, source-backed facts
become current automatically when no live evidence conflicts. Open a fact to see:
* its current status and whether it is direct or source-derived;
* the time range it applies to and when the evidence was observed;
* the Company Memory page that explains the context; and
* the original source and version used.
Use **History** to review how a value changed. A newer policy, addendum, Project update, or human
decision may supersede an older value without deleting the old audit trail.
If two live sources disagree, Tendor withholds the disputed value instead of silently choosing
one. A material exception becomes a Company Action only when someone genuinely needs to change
evidence or make a business decision.
Conflicted, source-changed, and pending-verification assertions stay in the integrity layer and do
not become a Company Memory review queue. The system re-evaluates them as evidence changes.
Low-impact uncertainty stays quiet; high-impact uncertainty that blocks real work is routed to
**Company Actions** with its source context.
## Explore relationships
Relationship views connect explicit People, Projects, buyers, capabilities, credentials,
requirements, submissions, decisions, and actions. Tendor shows direct relationships and evidence
paths of no more than two steps. Each step has its own page and source link.
A path helps you find evidence; it does not prove a conclusion by itself. Open the linked pages and
sources before using the relationship in a submission or decision.
## Gaps and actions
Company Memory may show a gap when evidence is missing, stale, unreadable, or contradictory. It may
also create an action when a person genuinely needs to provide evidence, resolve a requirement, or
follow up a submission. Completing an action does not fabricate the missing fact; upload or update
the original evidence and allow Company Memory to reconcile it.
## Human edits and safe updates
Human page edits use revision checks so a background update cannot silently overwrite a page
changed after it was read. Editing one word does not verify, invalidate, or protect every fact on
that page. Fact authority belongs to each source-backed assertion and changes when its original
evidence changes. Consolidation changes, fact history, relationships, actions, checkpoints, gaps,
and the run report are committed together; if one part fails validation, the update is not
partially applied.
## Keep Company Memory trustworthy
* Keep Project and Library files current, especially certificates, licences, policies, and receipts.
* Replace old evidence rather than uploading ambiguous duplicates.
* Company Memory re-evaluates affected assertions as evidence changes; there is no Memory review
queue to maintain. A Company Action appears only when an unresolved business decision blocks real
work, such as incompatible live evidence that could change a submission.
* Use the source link before relying on a high-risk fact.
* Record corrections against the original evidence rather than editing around it in chat.
Keep reusable source evidence organised and current.
Use Company Memory and current Project evidence in AI work.