Livia Bennett

1. Documentation tends to go stale silently. A file changes, the docs do not, and nobody notices until the docs are actively misleading.

Writulos now tracks this. Each file shows how many commits it has drifted from its last generated documentation, so outdated docs are visible before they cause confusion. This adds no extra cost and requires no setup.

I started building LineageLens because I kept asking a question that nobody on my team could answer: if a CVE gets traced back to an AI-generated line in production next week, what evidence do we actually have?

Not "we use Copilot and review everything." Machine-readable evidence: which model generated which lines, with what prompt, at what confidence, and whether a human reviewed the AI context before it shipped.

For most teams, the answer is nothing. The Cloud Security Alliance put a number on it this month: 81% of organizations have no complete visibility into where AI-generated code lives in production. That gap grows larger every sprint.

LineageLens intercepts AI tool traffic at the proxy layer to capture provenance records at generation time -- the only moment when model, prompt, file path, and edit context all coexist. Then the blame engine maps those records onto current file contents:

On a Tuesday, the first enterprise question is usually not can you capture AI code? It s who can see the records, how long do they live, and what happens when a policy blocks a change?

That s the part LineageLens is built for. Base gives you local capture. Lite gives a shared team record. Plus and Max move the data into a backend where auth, permissions, retention, and policy live next to the provenance records instead of around them.

The useful thing here is not another dashboard. It s a self-hosted record of prompt, model, tool, file, and outcome that engineering, security, and platform teams can actually govern on their own infrastructure.

I keep seeing AI governance tools start with visibility, then discover that the real enterprise questions are identity, retention, and review. If the record cannot be scoped, retained, and exported on your side, it is not really governable.