rzen/lanework
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

The corpus index and the Nexus learn the interchange rows — and the import/export doc stops quoting words the owner never said

Browse Source 
DESIGN/15's open-questions bullet claimed the owner's literal word was
"proceed as per your recommendation for v1"; no such message exists. The
rulings were inferred by the implementing session from the card's move to
Approved, and the doc now says exactly that. README gains the 15 row,
11-command-nexus gains File ▸ Import Board… and the three Export rows.

Claude-Session: https://claude.ai/code/session_014PtZdPwqZuqEDLc6wZMtEy
This commit is contained in:
rzen
2026-08-09 08:39:54 -04:00
parent 41380a81d7
commit 55663e855a
3 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
DESIGN/15-import-export.md
+1 -2
View File
@@ -98,5 +98,4 @@ This is a **positioning** note as much as a technical one. "Files-first" is easy
## Open questions
- **The command Nexus owes rows for all four items** — File ▸ Export ▸ (three) and File ▸ Import Board… are not yet in 11-command-nexus.md's inventory. Neither takes a default chord.
- **The v1 rulings on this page were made by the main session on the owner's behalf** (the owner's own word was "proceed as per your recommendation for v1"): the export and import surfaces, the fresh-board-only import, the loss-row posture, the convert-once ruling, and the decision to treat vault interop as documentation. Each is flagged for review on the Pipeline card's comment thread.
- **The v1 rulings on this page were made by the implementing session on the owner's behalf, not by the owner** — the owner filed the brainstorm card and moved it to Approved after the brainstorm was posted; the session read that move as approval of the v1 recommendation and ruled the open questions itself: the export and import surfaces, the fresh-board-only import, the loss-row posture, the convert-once ruling, and the decision to treat vault interop as documentation. Each is flagged for review on the Pipeline card's comment thread.