HINT for Knowledge Librarians

Your assistant summarizes fast. HINT keeps every claim tied to its source.

HINT keeps source notes and curated knowledge in plain Markdown. Your assistant sees the claims, decisions, relationships and open questions that apply to the topic without treating every nearby document as equally authoritative.

Where it helps

Three situations your team will recognize

Before: A summary repeats a confident claim but loses where it came from.

Claims retain provenance

Each important assertion points back to a source note, so readers can inspect the evidence and its limits.

Before: An old decision keeps resurfacing after the team replaced it.

Supersession is explicit

Typed links show which decision replaced another without deleting the history that explains the change.

Before: A broad search floods the assistant with unrelated notes.

Topic scope filters the library

Folder context and ranked local search return the smallest useful set for the topic being maintained.

See it

A real source note from the demo

The Knowledge Wiki demo records what one paper actually supports before that claim reaches a topic page.

demo-knowledge-wiki/raw/attention-is-all-you-need.md.hint ↗

# source Attention Is All You Need {#source_vaswani_2017}

Vaswani et al., 2017, arXiv:1706.03762.

# claim Transformer removes recurrence from sequence transduction

The source describes an architecture based solely on attention mechanisms.

Confidence: high for the architecture proposed by this paper.

What your assistant does next

It may summarize the scoped claim and link it into the wiki, but it preserves the paper reference and the stated confidence boundary.

What your AI assistant receives
<source name="Attention Is All You Need">…</source>
<claim name="Transformer removes recurrence from sequence transduction">
  …
</claim>

Your boundaries stay visible

What it will never do

  • Turn an interpretation into a sourced fact.
  • Hide that a newer decision supersedes an older one.
  • Resolve an open question without evidence.

FAQ

Questions knowledge librarians ask

Is this a replacement for a wiki?

No. It is a context layer for files in a repository and can govern the Markdown that feeds your existing publishing system.

Can it distinguish sources from claims?

Yes. The vocabulary gives each a separate role and lets topic notes link back to immutable source records.

Does it require embeddings?

No. Retrieval uses deterministic path scope and local lexical search.

For your technical colleague

The vocabulary

A hintbook is a vocabulary for your profession—installed, not written by you.

source
Records an identifiable source and its provenance.
concept
Defines an idea in the vocabulary used by the repository.
entity
Names a person, organization, system or other subject.
claim
States an assertion with its support and confidence boundary.
decision
Records a conclusion and the reason it was accepted.
openquestion
Keeps an unresolved question visible without guessing an answer.
supersedes
Links newer knowledge to the item it replaces.
relates
Creates an explicit typed connection between topics.

Manual setup

Bootstrap is read-only: it prints instructions for the assistant. The assistant performs the installation.

npm install -g @openhint/cli
hint config
hint add @openhint/hintbook-librarian
hint apply

Hintbook repository ↗ · Demo repository ↗

Works with