Documents, decisions, and prior work indexed into one queryable spine, so the team answers from the same source of truth instead of re-asking the same questions.
The promise
Most teams lose two things over time: where the answer was, and why the decision was made. This role builds and maintains your organization’s working memory — every inbound document filed, summarized, and made queryable, every prior decision retrievable with the rationale attached. It replaces the role of an internal knowledge manager or research analyst who would otherwise spend their week filing, tagging, and answering “where is the…” questions. You buy a memory layer that does not forget when people leave, take leave, or move teams.
What it does day-to-day
- Files inbound documents into a queryable knowledge graph and writes a human-readable summary
- Answers questions about your own project — structure, history, prior decisions — with citations
- Tracks which artifact came from where and when, so provenance is never guesswork
- Mirrors the knowledge spine into a structured database alongside the file store
- Surfaces stale or contradictory entries for review before they propagate
How it works
Two paired roles split the work. One files and indexes incoming material into the knowledge spine; the other reads from it on demand and answers questions without editing the source. The split keeps writes auditable and reads fast.