SPI Knowledge Miner

Why we built it

Business teams often have the data they need, but not a clear answer to a more important question: what evidence is actually allowed to support this decision?

A general AI can make that ambiguity disappear with a confident summary. That is exactly the problem SPI Knowledge Miner is designed to avoid. We wanted the first thing a team sees to be the evidence an answer can stand on—not a conclusion they have to reverse-engineer later.

What it does

SPI Knowledge Miner turns a business question into an auditable evidence contract. For a supported question, it identifies governed aggregate evidence and opens an Evidence Passport: audience, period, method, permitted claims, limitations and a deterministic local receipt.

For an unsupported prediction, individual-targeting or otherwise disallowed request, it returns a clear no-match. It does not fill the gap with an invented answer.

How we built it

The Build Week version is a self-contained React + Vite site. It runs entirely on synthetic local aggregate fixtures, with deterministic matching and refusal logic. The public experience includes a Taiwan mobile-usage overview, a streaming buyer journey, an Evidence Passport and a deliberate refusal path.

Codex built the judge-safe public experience, synthetic fixtures, regression and leakage checks, build verification and responsive QA. GPT-5.6 implemented the Evidence Passport mechanics, deterministic match/refusal behavior, the expanded test suite and receipt verification. The majority session ID is 019f7ced-9f46-7673-b26d-d0ab13401503.

The hard part

The challenge was making governance useful rather than bureaucratic. We reduced it to a decision a user can understand at a glance: this evidence supports this question, under these limits. When the limits do not hold, the refusal gives a reason and a next-safe step.

What we are proud of

The public project has 75 automated checks across product behavior, privacy boundaries, claim limits and responsive build quality. A supported answer and a no-match use the same testable contract, so the safety behavior is product behavior—not a hidden policy.

Try it

1. Open the live demo.
2. Explore the Taiwan mobile-usage overview and streaming journey.
3. Ask a supported business question to inspect its Evidence Passport.
4. Try an unsupported prediction or individual-targeting request to see a deterministic no-match.

No login or setup is required. The public demo uses fictional brands and synthetic aggregate fixtures only; it contains no proprietary evidence, credentials, person-level data, production integrations, sending, billing or external-release workflow.

What we learned

Trust becomes tangible when a product can explain both why it may answer and why it may not. Governance works best when it is executable, visible and useful in the moment a decision is made.

What is next

The public Build Week layer will remain isolated and synthetic. The product architecture can extend to additional industries only through separately governed evidence and review gates. The public repository contains only this isolated submission.

Built With

• vite