Jump To Category Page

Jump To Representative Detail

Files Category View

File inventory should show which paths carry real sensitivity, which sessions touched them, and how those files cluster into meaningful company context.

The category page should do more than list paths: it should help the reviewer see which files are just evidence and which ones anchor the trust or boundary story.

Use This Page When Asking

Which files are routine substrate, and which ones materially change the trust story?

Representative Detail

.env

Open representative detail

Files observed

340

Only a few are high-signal

Sensitive files

Main review set

Shared file cluster

auth + config

Current story anchor

Repo grouping need

high

Paths need business context

Why This Page Exists

This category page should help the reviewer decide what matters in files before the raw table takes over the reading experience.

What This Page Should Make Obvious

The reviewer should know what is routine, what is risky, and what deserves the next click.

Most files are evidence, not the story

The page should clearly separate background paths from the few that anchor company consequence.

Sensitivity needs adjacent context

A file matters more when it appears beside sessions, credentials, or outbound paths.

Expose the surrounding cluster

The refined page should help the reviewer understand the repo or service meaning around a path fast.

Fastest Drill Paths

The next clicks should feel obvious and intentional.

Sensitive config lane

A representative file that anchors the current auth-related trust story.

Open representative detail

Best first click for showing why a single path matters beyond a filename.

Raw file ledger

Reviewers still need the canonical access history and exact path list.

Open c6 raw list

The refined view should sit above the raw ledger, not replace it.

File-Centered Topology

A file map should show access lineage, sensitivity, and the sessions that create exposure.

Useful per file: exact path, category, sensitivity, readers and writers, the endpoint it lives on, and whether the file shows up in risky sessions or outbound flows.

File

/home/alice/projects/api/src/auth.ts

Sensitive application file whose access pattern matters more than raw counts alone.

4 sessions · 12 accesses

Extension

.ts

Accessed By

Who and what touched the file.

3 nodes

alice@company.comuser

Claude Codeagent

alice-mbp.localendpoint

File Context

What kind of asset this is.

3 nodes

/src/auth.tssource path

authentication logicbusiness meaning

.envadjacent sensitive file

Session Links

How the access happened.

3 nodes

read_filecapability

write_filepossible mutation path

4 sessionsdistinct runs

Exposure Lens

What turns access into a governance issue.

3 nodes

sensitive heuristictriggered

outbound copy riskwatch secondary calls

review access historynext drill-in

c6 Raw Reference

c6 shape: sensitivity banner, file map, then file-by-file access ledger.

3 sensitive files accessed

auth.ts, .env, and main.tf match the raw sensitive-file heuristics.

Files observed

Sensitive files

Most active category

source

Top file

/src/auth.ts

Why Keep The Raw Ledger

c12 should still flow back into the raw inventory model. This page frames the question and likely answer; the raw table proves it.

Open c6 Raw List

Use the original category ledger for exact rows, counts, and timestamps.

Open c6 raw list

Raw File Inventory

Path, extension, category, sensitivity, sessions, and access counts.

Path	Ext	Category	Sensitive	Access count
/home/alice/projects/api/src/auth.ts	.ts	source	yes	12
/home/alice/.env	.env	config	yes	2
/home/bob/projects/infra/terraform/main.tf	.tf	infra	yes	7