Showing the Operator OS without leaking it

The failure mode I wanted to avoid was the classic portfolio shrug: "trust me, there is a tool behind this." A screenshot of private data would be reckless. A description without evidence would be thin. The useful middle is a fixture, a small public dataset shaped like the real inputs, then a real app pointed at that dataset.

That is exactly the shape of the public proof: the real Portfolio Command Center pointed at a sanitized GithubRepoAuditor fixture, three deliberately anonymous projects, RepoA, RepoB, and RepoC. Not a mockup, and not private data either. The names are fake; the operating loop is real.

What the fixture proves

The public proof is intentionally narrow. It does not try to expose the whole private system. It proves the part a visitor should be able to inspect:

• A structured portfolio truth snapshot can drive the command center without hand-maintained page copy.
• Risk posture, security posture, weekly movement, and grouped fixes become visible as an operator surface.
• The same screenshots can be reviewed for public safety because the data is fixture-only from the start.
• The homepage and project index can point at proof without linking to private repo state.

The companion verification receipt is the boring but load-bearing part. It records the fixture scope, the image assets, the leak checks, and the durable gate receipt. It is there so the claim has a place to fail if the proof ever drifts.

What stays private

The boundary is just as important as the image. The public site does not publish live Portfolio Command Center data, raw auditor reports, private repo names, local paths, security findings, inbox state, tokens, agent logs, or machine-specific state. Those are not blurred after the fact; they are outside the fixture lane entirely.

That distinction matters. Redaction is a last-mile safety net. The safer architecture is to build a public proof path that never needs the private material in the first place.

Public proof should show the mechanism, not the contents of the real machine.

The second proof surface

The visual proof is only one side. The site also exposes a read-only MCP discovery manifest, and the live readback checks that the deployed manifest and Worker tools agree. That gives the portfolio a machine-readable surface for the same reason the screenshots give it a visual one: an agent, browser, or human reviewer can inspect what is actually published instead of relying on a claim in prose.

So the public surface now has two kinds of evidence. A person can look at the command center and understand the operator loop. A machine can read the corpus and tool manifest and verify the published shape. Neither needs access to private data to decide whether the artifact exists.

The pattern

This is the pattern I trust most for personal AI systems: private operating layer, public-safe fixture, visible artifact, receipt. The private layer can stay rich and useful. The public artifact can stay honest. The receipt keeps them from silently collapsing into either oversharing or hand-waving.

A portfolio can say "I built this." A proof surface should let you look back and say, "show me the part I am allowed to verify."