Knowledge · Capabilities
What Lontra may claim
The register is the ceiling on everything positioning, copy and every landing page is allowed to say. Nothing below it is permission until a person confirms it.
How the register works
A proposal is a hypothesis read out of a document — never permission. A document describing a roadmap, a competitor, or a customer's request reads exactly like one describing a capability, so confirming is a judgement only a person can make (ADR-0047). Read the quote and decide whether it describes something the product does.
Only available and beta authorise a claim, and a beta claim carries the beta marker. planned never authorises one — a roadmap item is not a promise — and none records something the product deliberately does not do, so a claim about it is refused with a reason rather than for want of evidence.
Every change writes a new version with its reason and its author, so what a capability said when a claim was permitted is a row rather than a reconstruction. Nothing is deleted; every version is on the register tab.
Look for capabilities in the ingested documents
Searches this product's embedded passages and proposes register entries, each quoting the passage it came from.
- Nothing is written to the register by this. It produces proposals; confirming one is a separate, deliberate act.
- A quoted passage that does not appear in the chunk it cites is dropped before anyone sees it — that is a model writing evidence rather than finding it.
- Queued, not immediate: a worker must be running (
npm run worker, whichnpm run devnow starts alongside the app).