Answers that name their version. Not a link to a folder.
Three copies of the policy, one of them current. Ask once and get the answer that names the version it read.
The systems you already run, the objects your product declares, and the work your team gets back.
These marks name the kinds of system a source declaration reaches — a picture of the ecosystem, not a fixed menu, and nothing here implies a partnership.
Less asking around. More checking the source.
The current one is labelled
A file enters as an immutable version with a digest, so which copy is current stops being folklore.
Answers you can check
A Function returns the passages and the exact file versions behind them, so checking beats trusting.
Attached, not just indexed
A search box returns ten documents; a policy attached to the product it governs returns the answer.
What teams build. On day one.
Four places this work turns into declared objects, governed reads, and reviewed changes.
Policy lookup
The question you answer twice a week becomes a Function over the approved versions, returning the passage and the version it read.
Document intake
A new handbook, runbook or spec lands as a file version attached to the product it describes, not a folder nobody queries.
Revision review
Editing a wiki page in place leaves no trace. Publishing a version is an Action: the old one is superseded, the author recorded.
Onboarding questions
A new joiner asks in plain language; an agent answers through the same Functions a person would run, citing the same versions.
How it runs. End to end.
The same path every product takes: connect what exists, declare what it means, then publish the reads and the changes.
- 01
Leave the documents where people edit them
Your drive, wiki and ticket tool stay in charge of the originals, and nothing here writes back. Copies arrive at an interval you choose, so an answer is dated: it says when it last saw the document instead of implying it just opened it.
- 02
Attach each document to what it describes
Declare that the runbook belongs to the service and the policy to the product, once, in reviewed product source. Retrieval then follows a link rather than a keyword.
- 03
Publish the questions people keep asking
The questions that keep landing in your inbox become named Functions with typed results and declared sources, so two people asking read one definition.
- 04
Let agents answer inside those limits
An agent reaches documents only through those Functions, under the authority of the person who asked, and cannot open a file that person could not.
Common questions.
Search finds documents. The work you are trying to stop doing is deciding which of them still applies, and who to ask about the one that looks wrong. A document here is an immutable version attached to the thing it describes, so an answer arrives with its version and its owner rather than as ten results to sort through.
You check it, which is the point. A model can still misread a passage and we will not claim otherwise. What the platform adds is that every answer names the exact file versions behind it, so verifying takes seconds rather than an afternoon. It removes the guesswork about which document was read, not the judgement about what it means.
Visibility is declared on the object and on the Function, not added at the search layer, so a document a person cannot open never appears in their results and cannot surface through a summary. The boundary is exactly as good as the declaration behind it, which is why it is reviewed product source and not a runtime setting.
Bring us a process.
We'll build it with you.
A business process, the systems it touches, and the rules it needs to follow.