summaryrefslogtreecommitdiff
path: root/docs/registry.typ
diff options
context:
space:
mode:
Diffstat (limited to 'docs/registry.typ')
-rw-r--r--docs/registry.typ14
1 files changed, 9 insertions, 5 deletions
diff --git a/docs/registry.typ b/docs/registry.typ
index 40af056a..4d386f1c 100644
--- a/docs/registry.typ
+++ b/docs/registry.typ
@@ -153,6 +153,10 @@
#v(0.8em)
+*Historical decision record.* Entries retain their original source references
+and states. For the current filesystem and transport interface, use
+`docs/fs.md`; FUSE and the proof-of-concept examples are no longer supported.
+
#context {
let es = query(<reg>).map(e => e.value)
let order = ("open", "investigating", "blocked", "decided", "deferred", "landed", "rejected")
@@ -488,21 +492,21 @@ rejected whole.
Buildable, and much cheaper than anyone assumed. But it is a SECOND
FIRMWARE IMAGE, not a second role for this one: the editor owns UART0
bidirectionally (`esp32p4.zig:611`, `uart.zig:43-44,122-130`) and JP1
- exposes no second P4 UART (`board_memory.zig:382-383`). The board is either
+ exposes no second P4 UART (`board9p.Header`). The board is either
an editor or a filesystem at any one time. Say that plainly rather than
implying both.
]
#note("review", "2026-08-27")[
The reframing the draft misses: the board already exposes `Peek`, `Poke`,
- `Hexdump` and `Gpio` as acme words (`src/board_memory.zig:306-349,410-472`,
- registered `src/builtins.zig:1009,1025,1038`). All four cap at 4,096 bytes
+ `Hexdump` and `Gpio` as acme words (`src/builtins.zig`, `Board` namespace).
+ All four cap at 4,096 bytes
per command and the cap's stated reason is the 115200 console. So the whole
2³² address space is already reachable — by *typing a word into a tag*,
with the answer landing in an output pane. Nothing is machine-readable and
nothing is remote. A 9P tree is that same capability with names instead of
verbs, and `mem/`, `gpio/pinout` and `prof` are backed by functions that
- exist today (`board_memory.readWord:136`, `:368-390`,
+ exist today (`builtins.Board.readWord`, `builtins.Board.gpio`,
`pardes_esp32p4_frame_prof` at `esp32p4.zig:985`, already exported).
Four more files need one new C-ABI extern each; four have no
implementation at all. That inventory belongs in the note, not a wishlist.
@@ -1022,7 +1026,7 @@ Three of those four are achievable. One is not, and `9P-20` says which.
`.lsp_resp`, `.pipe_resp` (`src/pardes.zig:6896-6907`). `pull_wait_input`
cannot become an event because it is how events arrive. That leaves two:
`pull_gpio_toggle`, whose answer is only used to set a message row
- (`board_memory.zig:422-428`), so deferring it a frame is invisible; and
+ (`builtins.Board.gpio`), so deferring it a frame is invisible; and
`pull_tty_taken`, which is reached from `takesCommandLine`
(`pardes.zig:6465-6469`) at four call sites, two of which loop over all 16
panes — 16 probes per call, collapsing to ONE read if `proc` is a single file