Trace

Trace is for the moment when someone says, "We have an app, but I do not trust it."

That sentence shows up constantly. Sometimes it is a legacy codebase. Sometimes it is an AI-built prototype. Sometimes it is a thing that technically works, but everyone is nervous to touch it.

What It Does

Trace scans the codebase and tries to answer three questions:

• What is actually broken?
• What is risky but not obvious?
• What should we fix first?

I like it because it turns vague dread into a list. A list is not a solution, but it is a much better starting point than vibes.

The System Under It

Trace is the umbrella for the codebase-health products that all orbit the same first question: can this thing be trusted?

• Audit Report is the security-shaped front door for existing teams.
• Triage Brief is the rescue-shaped front door for founders with a working prototype and no confidence.
• Floe looks for security failures AI code loves to leave behind.
• Drift measures the coordination cost and team-health side of AI acceleration.
• Traverse and Watchtower are the review and governance paths that can grow out of the same scan.

The scan engine is designed to run several passes in parallel, then turn the result into a readable report instead of a pile of scanner output.

Why I Built It

Every rescue project has a foggy beginning. People know something is wrong, but the first few hours are usually spent separating real risk from noise.

Trace is my attempt to make that first pass less mystical.

Try It

The public entry point is linked from the card. It should feel like a small diagnostic, not a massive enterprise workflow: upload context, get a health score, see the risky categories, and know whether the next step is a fix, an audit, or a rescue plan.