Companies leave a record of their work across conversations, documents, and project tools. Making that information useful requires deciding which evidence is current, what it supports, and who is allowed to see it.

The work

My company-brain work explores how to turn that scattered information into useful operating context: facts, commitments, decisions, and the evidence behind them. The implementation work includes permission-aware retrieval and checks on what can be shown or shared with a particular audience.

Company sources → Authorized context → Supported decisions

A boundary that matters

Access to an answer and access to its underlying evidence are related, but they are not interchangeable. A citation can reveal a private document title or mailbox even when the answer itself appears harmless.

The project’s verification records document checks on source attribution, retrieval, and delivery. They include filtering evidence before it enters model context and checking the destination audience before publishing an output.

What this required

This work connects product design to the details that determine whether a system can be trusted inside a company. The product question is what people need to know. The engineering question is how to provide that knowledge without crossing an information boundary.

The decision: check access before retrieval and before delivery

I built checks around both the person asking and the audience receiving an answer. A private source can be appropriate for one person and inappropriate for a shared channel. Filtering before model context and checking again at delivery adds complexity, but it preserves a boundary that checking the final wording alone would miss.

Scope: this story is based on internal implementation and verification records. It does not claim company-wide adoption, a fully complete product, or measured customer ROI. Adaptive runtime ideas remain design work where they have not been verified as implemented.

Related essay: Your company remembers what happened. Does it remember why?

Technical detail: why permissions must follow the answer to its audience.

Explore the work   ·   Work with me through Measured Intuition