Kinoshita Kommander — two-panel filesystem navigator
First-party on-device program #6 (ADR-0042). Status: Stub — design pending.
Charter stub. Kinoshita Kommander is canonical per ADR-0042; this doc is a placeholder until the full design lands. See the program roster.
Identity
Section titled “Identity”A Norton Commander-style two-panel filesystem navigator. The primary place where exfiltrated data lands and is staged, and where files move between the deck, the cartridge, and network targets.
Scope (intended)
Section titled “Scope (intended)”- Dual-panel browse / copy / move / delete across mounts.
- Mounts: device microSD, the inserted cartridge’s SD, and (where a session is live) a remote target via CONDUIT.
- The staging ground for exfil — a mission deposits captured files here.
Interfaces
Section titled “Interfaces”- Launched via
(launch-app :kommander …)(NoshAPI Tier 1, ADR-0005). Draws on the cartridge/content rows per the canonical grid. Authored in KEC Lisp; source underruntime/programs/kommander/. - Missions deposit exfil via
:payload(a file set / virtual mount). The two-panel model maps naturally to “source target ↔ your deck.”
Open questions
Section titled “Open questions”- Which mounts are real vs. in-world (mission-provided virtual filesystems)?
- How does exfil staged here persist — UDS, cartridge save (ADR-0019), or a device scratch area?
- Handoff to DOSSIER (dossier.md) / AmberCalc (ambercalc.md) — does Kommander “open with” a target program?