← The systems / 01

Business Brain · Business knowledge

Keep the knowledge. Know what changed.

A source-aware knowledge system for the facts, decisions and exceptions behind a business.

Inside Business Brain

01Receive the source
02Check its version
03Ingest the change
04Record the result

The source stays connected to the state of its delivery.

The problem

The right answer needs the right source.

The answer is often in a document, an old conversation, or the owner's head. An assistant needs the right source—and a way to tell when that source has changed.

Treat a knowledge update as a delivery, with a source and a recorded state. Saving a file is only the beginning.

What I built

The connections
make the system.

I built an ingestion path that fingerprints an upload, passes it to the knowledge service, and marks it processed only after that handoff succeeds. An unchanged processed source is skipped. A changed source can be ingested again. A failed ingestion remains pending.

01Receive the source
02Check its version
03Ingest the change
04Record the result

What happened

A result you can trace.

The implementation handles unchanged sources, changed sources and failed delivery explicitly. That makes the knowledge handoff inspectable instead of hiding it behind an upload confirmation.

Source behavior, reviewed September 11, 2026

Same processed sourceSkip unchanged content
Changed sourceIngest the new version
Ingestion failsLeave pending for retry
Implementation summary from the saved handler and adjacent tests. This is a description of code paths, not a measurement of answer quality.

The engineering decision

An upload is not a successful handoff.

The sync handler checks the content version, not just the filename. It records processed only after ingestion succeeds. That leaves an operator a useful distinction: received, processed, unchanged, or still pending.

Evidence and scope of this case

Source version handling, tenant-scoped access and pending failure states are visible in the reviewed sync handler and adjacent tests.

Implementation evidence. The source and its test cases show the behavior; they do not establish an assistant's answer accuracy or a customer's time savings.

These are saved operating records and implementation checks. Customer data and private repositories are not published here.

Work with me

Start with the work
that needs to get done.

I run a business.

Let's look at how customers find you, contact you and take the next step. We’ll decide what’s worth fixing first.

Talk through your business

Prefer a written website review? Get your free Brand Pass.

I'm building a system.

Bring the workflow, the existing tools and the part that gets stuck. We'll work out the useful next move and its scope.

Discuss a system