You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: add pane module interface (v0.3.0) and Pane Studio (v0.5.0) to roadmap
v0.3.0 adds interface contract extraction — ReScript interface + Rust
trait defining what every pane module must provide, derived from the 6+
modules built by that point.
v0.5.0 adds Pane Studio as a scaffoldia profile that generates working
module skeletons (component, Tauri command, messages, update handler,
VeriSimDB schema, tests). This becomes the plugin system foundation
for v1.0.0.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: ROADMAP.adoc
+14-1Lines changed: 14 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -132,6 +132,12 @@ PanLL is **not** a generic IDE, framework, or platform. It is a personal neurosy
132
132
* Allow approval/rejection of proposed rules from Pane-W
133
133
* Rationale: Bot orchestration is a core part of the development workflow — it belongs in the workbench.
134
134
135
+
===== Pane module interface contract
136
+
* Extract the common pattern from existing pane modules (panic-attack, VeriSimDB, reposystem, protocol-squisher) into a documented contract
137
+
* Define what every pane module must provide: a Tauri command (Rust), a message type (ReScript), an update handler, a view function, and a VeriSimDB hexad schema
138
+
* Publish as typed ReScript interface + Rust trait — not a tool yet, just the specification
139
+
* Rationale: By v0.3.0 there are 6+ working modules. That is enough to extract the real pattern from facts, not assumptions. This contract is the foundation for the Pane Studio in v0.5.0.
140
+
135
141
==== Should Have
136
142
137
143
* Reasoning trace visualization (show which prover solved what, with what axioms)
@@ -204,6 +210,13 @@ PanLL is **not** a generic IDE, framework, or platform. It is a personal neurosy
204
210
* Attach provenance records to VeriSimDB hexads
205
211
* Rationale: IP protection for work created in PanLL.
206
212
213
+
===== Pane Studio (scaffoldia profile)
214
+
* Build a pane module scaffolder that generates all artifacts for a new module: ReScript component, Tauri command, message types, update handler, VeriSimDB hexad schema, and test stubs
215
+
* Implemented as a scaffoldia profile — not a separate tool. `scaffoldia generate --profile panll-pane --name my-module` produces a working module skeleton that compiles and renders immediately.
216
+
* Uses the pane module interface contract (defined in v0.3.0) as the generation target
217
+
* Includes MiniKanren constraints from scaffoldia to validate module structure (e.g., "every module that writes to Pane-W must define at least one event-chain parser")
218
+
* Rationale: By v0.5.0, 8+ modules have been built by hand. The pattern is proven. Scaffoldia already solves composable template generation — a PanLL profile is a natural extension, not a new tool. This becomes the plugin system foundation for v1.0.0.
219
+
207
220
==== Should Have
208
221
209
222
* Scaffoldia integration (generate new repo structures from Pane-W)
@@ -228,7 +241,7 @@ PanLL is **not** a generic IDE, framework, or platform. It is a personal neurosy
228
241
229
242
==== Should Have
230
243
231
-
* Plugin system for third-party pane modules
244
+
* Plugin system for third-party pane modules (built on Pane Studio from v0.5.0 — third parties run `scaffoldia generate --profile panll-pane` and get a working module skeleton)
232
245
* Multi-platform builds (Linux primary, macOS, Windows via Tauri)
233
246
* Headless mode for CI/CD integration (constraint check + ECHIDNA verification as pipeline gate)
0 commit comments