Built into every Program — nothing to install

Knowledge & Company

in every Program

The layer every Program draws on: structured facts about your business with how sure Pencel is about each one, the documents you keep, the rules you set, and what it remembers — with gaps left visible instead of guessed.

Shown with the RFP crew — works in every room

Q
Qualifierasks for the facts only you can confirm
D
Drafterfiles what you add and drafts against it
5 levels
Of confidence on every fact, from system-of-record to inferred
Every change
Logged — created, changed, confirmed, deprecated
0
Gaps quietly filled in with a guess

See it happen

What it looks like with this running.

Monday · 9:12 AM

#rfp-ops
RoomResultsKnowledge
Q

Qualifier9:12 AM

The VA transit RFP asks for two comparable contracts. Your Company page lists one — county fleet, 2024, document-backed. Is there a second?

Company · Past performance

1 fact on file · backed by a document · needs 2 for this requirement.

weak1 of 2 neededdocument
You

You9:14 AM

Adding it — here’s the 2023 Port Authority contract.

port-authority-fleet-2023.pdf · kept as material for #rfp-ops

D

Drafter9:14 AM

Filed. Past performance now lists two comparable contracts. The new one is document-backed — confirm it and it counts toward critical requirements.

Confirm as a company fact?

Port Authority fleet maintenance, 2023 · $940K · source: the contract you just added.

I’m confirming thisVerify later
You

You9:16 AM

Rule: whenever we claim past performance, cite the contract number.

Q

Qualifier9:16 AM

Saved as a standing rule for #rfp-ops. Every draft from here on will cite it.

Standing rule saved

Applies to this room’s future drafts. Edit or remove it any time from the room’s Knowledge tab.

#rfp-ops onlyEditable in Knowledge
Message #rfp-ops — “@” to point at a file or teammate

End to end

The whole loop, start to finish.

Every step below runs today. Nothing here is a mock-up of what is coming.

  1. 1ProposePencel researches what it can and Programs surface facts they find — each with a confidence level.
  2. 2ConfirmYou confirm or dismiss, right in the room. Observed never becomes confirmed without you.
  3. 3UseEvery Program reads from it on every run. A missing fact shows as missing, never guessed.
  4. 4TrackEvery change is logged — created, changed, confirmed, deprecated — and open work that depended on the old version is flagged.
  5. 5SharpenStanding rules, saved knowledge, and memory make each Program’s next draft better than its last.

Capabilities

Everything it does, named.

One line each. No adjectives — every one is a specific thing you can go and watch it do.

  • Keeps one structured record of what your business is — products, capabilities, certifications, bid policies, people, projects and organizations — readable by every Program.
  • Carries a confidence level on every fact (system of record, confirmed, document-backed, observed, inferred), and only confirmed or system-of-record facts can satisfy a critical requirement.
  • Shows coverage as known, weak or missing per category — the same read a Program uses to tell you what it lacks — and asks “how do you know this?” whenever you add a fact yourself.
  • Puts the confirm-or-dismiss card in the room where the question came up, and your answer updates the Company record everywhere it is used.
  • Indexes a folder on your own machine into a searchable knowledge base, with every fact linked back to its source file.
  • Keeps a file dropped into a room as standing material and a “remember: …” rule scoped to that room alone, so an RFP rule never leaks into your inbox room.
  • Saves any fact from a result with a snapshot of the source it came from, editable from the room’s Knowledge tab.
  • Logs every change to a fact and flags open work that depended on the old version, while your preferences and decisions carry across runs in Memory.

Inputs and outputs

What it reads, and what you get back.

What it connects to

Your Company pageFolders on your machineDocumentsEach room’s Knowledge tabSettings → Memory

What lands in your hands

  • A coverage view: what’s known, weak, or missing per category
  • A fact ledger with source, confidence, and history
  • Per-room knowledge and rules that never leak into another room
  • Drafts grounded in your facts, with sources cited

A week with it running

Day one to steady state.

What the first day looks like, what the quiet days look like, and when it comes to find you.

  1. Day 1Pencel researches what it can and proposes facts. You confirm or dismiss each one.
  2. Every runPrograms read from it. A fact that isn’t there shows as missing — never filled with a guess.
  3. When a Program finds a factIt asks you to confirm, right in the room. The Company record updates everywhere it’s used.
  4. Over timeSaved knowledge, standing rules, and memory make every Program’s drafts sharper.

Guardrails

Where it stops for you.

The line between what it does on its own and what it will never do without you, stated plainly.

Waits for you

Confirming a fact. A document or an overheard mention never becomes “confirmed” until you say so.

Never does

Invent a fact to fill a gap, or quietly treat something observed as certain.

Local-first: documents, facts, and memory stay in your workspace on your machine.Set up your Company page

Get started

Three steps to your first real result.

  1. 1Download Pencel and open Knowledge.
  2. 2Point it at a folder of your own documents, or let it propose what it can find.
  3. 3Confirm the facts that matter. Every Program reads from them on its next run.

macOS, Windows and Linux. No invite code.

Read the docs first →