What this context does

The “under-the-hood” mode for power users — exposes the project’s working tree (files + directory structure) and the per-project DB (table list, schema, paginated rows) read-only, through TalkIDE BE. Most users never open this. It exists for debugging, transparency, and because the project’s .git/ history lives where Mara works.

Scope boundary

• Owns: file tree listing, file content read, DB introspection (table list, schema), DB paginated row read.
• Does not own: file editing (Mara does that through subagents), DB writes (the user app does that), Git history UI (post-MVP).

Main entities

No new entities. Files: read directly from the project’s NFS subdir. DB: introspected via JDBC against the per-app DB (read-only credentials).

Use cases

Component diagram

{/* Image missing: UC-07 Project Explorer — Component View (../../assets/diagrams/uc07Components.svg) */}

Dependencies on other contexts

• UC-03 Project Management — Project must exist; explorer is project-scoped.
• NFS — files come from the per-project subdirectory mounted into the BE pod.
• Per-app Postgres DB — DB Explorer connects with a separate read-only role.

Cross-cutting

• Read-only by design. The explorer is observational; mutation is exclusively Mara’s job (via UC-04).
• Path safety — file paths are resolved within the project subdir; traversal outside is rejected at the BE.
• Pod identity — the BE pod runs as non-root UID 1000+ because the NFS mount uses root squashing; this is also why the BE pod can read the project subdir at all.