State why the file is sensitive near the top
The reviewer should not have to inspect the raw path list to know why this row matters.
QI
Files Detail
A file detail page should explain why one path matters: what type of file it is, how often it is touched, which sessions used it, and what broader company context it belongs to.
Use This Page When Asking
Why is this file important to trust, and what surrounding entities make that importance legible?
Open c6 raw detailSessions
3
Touched in several related runs
Operations
5
Mostly reads, one edit
Sensitivity
high
Config / secret-adjacent
Context
auth-service
Belongs to a critical repo lane
Why This Detail Matters
Important Metadata
Sensitive file
This path matches the c6 sensitive-file heuristics and was accessed by more than one session.
Path
/Users/alice/projects/api-refactor/.env
Sensitive
Yes
Extension
.env
Category
config
Endpoint
alice-mbp.local
What This Detail Should Help Decide
Show its neighboring context explicitly
Files make more sense when the page reveals the repo, session, and credential lanes around them.
Use the access table as support, not as the whole page
The detail should still feel like a file story, not just a log excerpt.
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
Category
source
Sensitivity
heuristic match
Last seen
today
Accessed By
Who and what touched the file.
alice@company.comuser
Claude Codeagent
alice-mbp.localendpoint
File Context
What kind of asset this is.
/src/auth.tssource path
authentication logicbusiness meaning
.envadjacent sensitive file
Session Links
How the access happened.
read_filecapability
write_filepossible mutation path
4 sessionsdistinct runs
Exposure Lens
What turns access into a governance issue.
sensitive heuristictriggered
outbound copy riskwatch secondary calls
review access historynext drill-in
Representative Event Chain
The page should show how the item participates in a readable sequence, not just a pile of supporting rows.
- 1
Classification
The path is recognized as more than a generic file
The page should state why the file is sensitive or important immediately rather than making the reviewer infer that from the name.
.envsensitive config - 2
Access pattern
Recent sessions show how the file is being used
Access history matters most when it helps the reviewer tell routine reads from a meaningful shift in behavior.
3 sessionsread_file - 3
Context cluster
Repo, session, and credential adjacency explain consequence
The path should be shown inside its broader auth-related cluster rather than as an isolated artifact.
auth-serviceshared keysession detail - 4
Follow-up
The reviewer pivots into repo or session detail once the file story is framed
The path page should make the next investigative hop obvious instead of leaving the reviewer in a long access table.
repo detailsession detail
c6 Evidence Tables
Access History
The raw detail keeps per-session file interaction explicit.
| Session / User | Operation | Tool | Bytes | Time |
|---|---|---|---|---|
| sess_01XFa9q... / alice@company.com | read | read_file | 1.2KB | 14 min ago |
| sess_01XFa9q... / alice@company.com | read | read_file | 1.2KB | 16 min ago |
| sess_01XG3b... / dave@company.com | read | read_file | 1.2KB | 2 hr ago |
Return To Category
Compare this representative detail against the full category framing and drill targets.
Open Files overviewOpen c6 Raw Detail
Use the original detail page for exact raw evidence after the c12 story framing.
Open c6 raw detailOpen c6 Raw List
Compare this item against the broader c6 entity ledger once the representative story is clear.
Open c6 raw list