retold 4.0.1 → 4.0.2

package/.claude/settings.local.json

@@ -52,7 +52,33 @@
       "Bash(kill:*)",
       "Bash(wait)",
       "Bash(while read d)",
-      "Bash(do echo \"Cleaning: $d\")"
+      "Bash(do echo \"Cleaning: $d\")",
+      "Bash(git pull:*)",
+      "Bash(git push:*)",
+      "Bash(git add:*)",
+      "Bash(git rebase:*)",
+      "Bash(git commit:*)",
+      "Bash(cd:*)",
+      "Bash(node source/cli/Meadow-Integration-CLI-Run.js:*)",
+      "Bash(bash:*)",
+      "Bash(npm test)",
+      "WebFetch(domain:stevenvelozo.github.io)",
+      "Bash(git ls-tree:*)",
+      "Bash(npx mocha:*)",
+      "Bash(pkill:*)",
+      "Bash(ln:*)",
+      "Bash(timeout 10 node:*)",
+      "Bash(npm ls:*)",
+      "Bash(node -e \"\nconst proc = require\\(''child_process''\\).spawn\\(''node'', [''server.cjs''], { cwd: ''/Users/stevenvelozo/Code/retold/examples/todo-list/server'', stdio: ''pipe'' }\\);\nlet output = '''';\nproc.stdout.on\\(''data'', \\(d\\) => { output += d.toString\\(\\); }\\);\nproc.stderr.on\\(''data'', \\(d\\) => { output += d.toString\\(\\); }\\);\nsetTimeout\\(\\(\\) => {\n  const http = require\\(''http''\\);\n\n  // Test 1: Static HTML serving\n  http.get\\(''http://localhost:8086/'', \\(res\\) => {\n    let data = '''';\n    res.on\\(''data'', \\(c\\) => { data += c; }\\);\n    res.on\\(''end'', \\(\\) => {\n      console.log\\(''=== Test 1: Static HTML ===''\\);\n      console.log\\(''Status:'', res.statusCode\\);\n      console.log\\(''Contains RetoldExampleTodoWebClient:'', data.includes\\(''RetoldExampleTodoWebClient''\\)\\);\n\n      // Test 2: API list\n      http.get\\(''http://localhost:8086/1.0/Tasks'', \\(res2\\) => {\n        let data2 = '''';\n        res2.on\\(''data'', \\(c\\) => { data2 += c; }\\);\n        res2.on\\(''end'', \\(\\) => {\n          let tasks = JSON.parse\\(data2\\);\n          console.log\\(''''\\);\n          console.log\\(''=== Test 2: API Reads ===''\\);\n          console.log\\(''Tasks returned:'', tasks.length\\);\n\n          // Test 3: Create\n          let postData = JSON.stringify\\({Name:''CJS test'',Status:''Pending'',LengthInHours:1}\\);\n          let req = http.request\\({hostname:''localhost'',port:8086,path:''/1.0/Task'',method:''POST'',headers:{''Content-Type'':''application/json''}}, \\(res3\\) => {\n            let data3 = '''';\n            res3.on\\(''data'', \\(c\\) => { data3 += c; }\\);\n            res3.on\\(''end'', \\(\\) => {\n              let created = JSON.parse\\(data3\\);\n              console.log\\(''''\\);\n              console.log\\(''=== Test 3: Create ===''\\);\n              console.log\\(''Created ID:'', created.IDTask, ''Name:'', created.Name\\);\n\n              // Test 4: Update\n              let putData = JSON.stringify\\({IDTask:created.IDTask, Name:''CJS test \\(updated\\)'', Status:''Complete''}\\);\n              let req2 = http.request\\({hostname:''localhost'',port:8086,path:''/1.0/Task'',method:''PUT'',headers:{''Content-Type'':''application/json''}}, \\(res4\\) => {\n                let data4 = '''';\n                res4.on\\(''data'', \\(c\\) => { data4 += c; }\\);\n                res4.on\\(''end'', \\(\\) => {\n                  let updated = JSON.parse\\(data4\\);\n                  console.log\\(''''\\);\n                  console.log\\(''=== Test 4: Update ===''\\);\n                  console.log\\(''Updated:'', updated.Name, updated.Status\\);\n\n                  // Test 5: Delete\n                  let req3 = http.request\\({hostname:''localhost'',port:8086,path:''/1.0/Task/''+created.IDTask,method:''DELETE''}, \\(res5\\) => {\n                    let data5 = '''';\n                    res5.on\\(''data'', \\(c\\) => { data5 += c; }\\);\n                    res5.on\\(''end'', \\(\\) => {\n                      let del = JSON.parse\\(data5\\);\n                      console.log\\(''''\\);\n                      console.log\\(''=== Test 5: Delete ===''\\);\n                      console.log\\(''Deleted count:'', del.Count\\);\n                      console.log\\(''''\\);\n                      console.log\\(''=== ALL TESTS PASSED ===''\\);\n                      proc.kill\\(\\);\n                      process.exit\\(0\\);\n                    }\\);\n                  }\\);\n                  req3.end\\(\\);\n                }\\);\n              }\\);\n              req2.write\\(putData\\);\n              req2.end\\(\\);\n            }\\);\n          }\\);\n          req.write\\(postData\\);\n          req.end\\(\\);\n        }\\);\n      }\\);\n    }\\);\n  }\\);\n}, 3000\\);\n\")",
+      "Bash(node -e \" const _origStderrWrite = process.stderr.write; process.stderr.write = function \\(pChunk\\) { if \\(typeof pChunk === ''string'' && pChunk.indexOf\\(''Setulc''\\) !== -1\\) { return true; } return _origStderrWrite.apply\\(process.stderr, arguments\\); }; const blessed = require\\(''blessed''\\); const libPict = require\\(''pict''\\); const libPictApplication = require\\(''pict-application''\\); const libPictTerminalUI = require\\(''pict-terminalui''\\); const libViewLayout = require\\(''/Users/stevenvelozo/Code/retold/examples/todo-list/console-client/views/PictView-TUI-Layout.cjs''\\); const libViewHeader = require\\(''/Users/stevenvelozo/Code/retold/examples/todo-list/console-client/views/PictView-TUI-Header.cjs''\\); const libViewTaskList = require\\(''/Users/stevenvelozo/Code/retold/examples/todo-list/console-client/views/PictView-TUI-TaskList.cjs''\\); const libViewStatusBar = require\\(''/Users/stevenvelozo/Code/retold/examples/todo-list/console-client/views/PictView-TUI-StatusBar.cjs''\\); console.log\\(''All console-client .cjs modules loaded OK''\\); console.log\\(''Views:'', [libViewLayout, libViewHeader, libViewTaskList, libViewStatusBar].map\\(v => v.default_configuration.ViewIdentifier\\).join\\('', ''\\)\\); process.exit\\(0\\); \")",
+      "Bash(node Stricture.js:*)",
+      "Bash(timeout 15 node:*)",
+      "Bash(npm update:*)",
+      "Bash(awk:*)",
+      "Bash(/Users/stevenvelozo/Code/retold/examples/todo-list/model/data/fix_csv.py << 'PYEOF'\nimport re\n\nINPUT_FILE = '/Users/stevenvelozo/Code/retold/examples/todo-list/model/data/seeded_todo_events.csv'\n\nwith open\\(INPUT_FILE, 'r'\\) as f:\n    lines = f.readlines\\(\\)\n\nheader = lines[0].strip\\(\\)\noutput_lines = [header]\n\n# Pattern for the last 3 fields: date, number, status\n# DueDate is YYYY-MM-DD, LengthInHours is a number \\(int or float\\), Status is one of three values\ntail_pattern = re.compile\\(r',\\(\\\\d{4}-\\\\d{2}-\\\\d{2}\\),\\([\\\\d.]+\\),\\(Pending|In Progress|Complete\\)\\\\s*\\)\n\nfor i, line in enumerate\\(lines[1:], start=2\\):\n    line = line.strip\\(\\)\n    if not line:\n        continue\n\n    # Find the tail \\(DueDate, LengthInHours, Status\\) from the right\n    match = tail_pattern.search\\(line\\)\n    if not match:\n        print\\(f\"WARNING: Line {i} does not match expected tail pattern: {line[:80]}\"\\)\n        output_lines.append\\(line\\)\n        continue\n\n    tail_start = match.start\\(\\)\n    due_date = match.group\\(1\\)\n    length = match.group\\(2\\)\n    status = match.group\\(3\\)\n\n    # Everything before the tail is \"Name,Description\" \\(with possible extra commas in Description\\)\n    front = line[:tail_start]\n\n    # Split front into Name and Description at the first comma\n    first_comma = front.index\\(','\\)\n    name = front[:first_comma]\n    description = front[first_comma + 1:]\n\n    # Strip any existing surrounding quotes from the description\n    if description.startswith\\('\"'\\) and description.endswith\\('\"'\\):\n        description = description[1:-1]\n\n    # Escape any double quotes inside the description \\(double them per CSV standard\\)\n    description = description.replace\\('\"', '\"\"'\\)\n\n    # Reconstruct the line with the description properly quoted\n    fixed_line = f'{name},\"{description}\",{due_date},{length},{status}'\n    output_lines.append\\(fixed_line\\)\n\nwith open\\(INPUT_FILE, 'w'\\) as f:\n    f.write\\('\\\\n'.join\\(output_lines\\) + '\\\\n'\\)\n\nprint\\(f\"Processed {len\\(output_lines\\) - 1} data rows \\(plus header\\).\"\\)\nprint\\(\"File written successfully.\"\\)\nPYEOF)",
+      "Bash(for f in architecture.md fable.md meadow.md orator.md pict.md utility.md modules.md examples.md todo-list.md todo-list-model.md todo-list-server.md todo-list-web-client.md todo-list-console-client.md todo-list-cli-client.md)",
+      "Bash(do [ -f \"/Users/stevenvelozo/Code/retold/docs/$f\" ])",
+      "WebFetch(domain:registry.npmjs.org)"
     ]
   }
 }

package/docs/README.md

@@ -148,13 +148,14 @@ _Fable.log.info('Retold application started.');
 
 ## Learn More
 
-- **[Architecture](architecture.md)** — Detailed layer-by-layer breakdown of the module stack
+- **[Architecture](architecture/architecture.md)** — Detailed layer-by-layer breakdown of the module stack
 - **[Getting Started](getting-started.md)** — Building your first Retold application
-- **[Fable In Depth](fable.md)** — The core ecosystem and service provider pattern
-- **[Meadow In Depth](meadow.md)** — Data access, schemas, and query generation
-- **[Orator In Depth](orator.md)** — API servers and endpoint generation
-- **[Pict In Depth](pict.md)** — MVC tools for browser and console UIs
-- **[All Modules](modules.md)** — Exhaustive list of every Retold repository
+- **[Examples](examples/examples.md)** — Complete runnable applications including the Todo List full-stack example
+- **[Fable In Depth](modules/fable.md)** — The core ecosystem and service provider pattern
+- **[Meadow In Depth](modules/meadow.md)** — Data access, schemas, and query generation
+- **[Orator In Depth](modules/orator.md)** — API servers and endpoint generation
+- **[Pict In Depth](modules/pict.md)** — MVC tools for browser and console UIs
+- **[All Modules](modules/modules.md)** — Exhaustive list of every Retold repository
 
 ## License
 

package/docs/_sidebar.md

@@ -1,10 +1,20 @@
 - Getting Started
 
-  - [Architecture](architecture.md)
   - [Getting Started](getting-started.md)
-  - [All Modules](modules.md)
+  - [Architecture](architecture/architecture.md)
+  - [Ecosystem Architecture](architecture/module-architecture.md)
+  - [All Modules](architecture/modules.md)
 
-- [Fable — Core Ecosystem](fable.md)
+- [Examples](examples/examples.md)
+
+  - [Todo List Application](examples/todolist/todo-list.md)
+  - [Todo List: System Model](examples/todolist/todo-list-model.md)
+  - [Todo List: API Server](examples/todolist/todo-list-server.md)
+  - [Todo List: Web Client](examples/todolist/todo-list-web-client.md)
+  - [Todo List: Console Client](examples/todolist/todo-list-console-client.md)
+  - [Todo List: CLI Client](examples/todolist/todo-list-cli-client.md)
+
+- [Fable — Core Ecosystem](modules/fable.md)
 
   - [fable](/fable/fable/)
   - [fable-serviceproviderbase](/fable/fable-serviceproviderbase/)
@@ -13,23 +23,22 @@
   - [fable-uuid](/fable/fable-uuid/)
   - [fable-log-logger-bunyan](/fable/fable-log-logger-bunyan/)
 
-- [Meadow — Data Access](meadow.md)
+- [Meadow — Data Access](modules/meadow.md)
 
-  - [meadow](/meadow/meadow/)
-  - [foxhound](/meadow/foxhound/)
   - [stricture](/meadow/stricture/)
+  - [foxhound](/meadow/foxhound/)
+  - [bibliograph](/meadow/bibliograph/)
+  - [meadow](/meadow/meadow/)
+  - [parime](/meadow/parime/)
   - [meadow-endpoints](/meadow/meadow-endpoints/)
-  - [retold-data-service](/meadow/retold-data-service/)
   - [meadow-connection-mysql](/meadow/meadow-connection-mysql/)
   - [meadow-connection-mssql](/meadow/meadow-connection-mssql/)
   - [meadow-connection-sqlite](/meadow/meadow-connection-sqlite/)
+  - [retold-data-service](/meadow/retold-data-service/)
   - [retold-harness](/meadow/retold-harness/)
-  - [bibliograph](/meadow/bibliograph/)
-  - [parime](/meadow/parime/)
   - [meadow-integration](/meadow/meadow-integration/)
-  - [meadow-graph-client](/meadow/meadow-graph-client/)
 
-- [Orator — API Server](orator.md)
+- [Orator — API Server](modules/orator.md)
 
   - [orator](/orator/orator/)
   - [orator-serviceserver-restify](/orator/orator-serviceserver-restify/)
@@ -37,29 +46,33 @@
   - [orator-http-proxy](/orator/orator-http-proxy/)
   - [tidings](/orator/tidings/)
   - [orator-endpoint](/orator/orator-endpoint/)
+  - [orator-conversion](/orator/orator-conversion/)
 
-- [Pict — MVC Tools](pict.md)
+- [Pict — MVC Tools](modules/pict.md)
 
   - [pict](/pict/pict/)
-  - [pict-view](/pict/pict-view/)
   - [pict-template](/pict/pict-template/)
+  - [pict-view](/pict/pict-view/)
   - [pict-provider](/pict/pict-provider/)
   - [pict-application](/pict/pict-application/)
-  - [pict-section-form](/pict/pict-section-form/)
+  - [pict-panel](/pict/pict-panel/)
+  - [pict-nonlinearconfig](/pict/pict-nonlinearconfig/)
+  - [pict-section-flow](/pict/pict-section-flow/)
+  - [pict-docuserve](/pict/pict-docuserve/)
+  - [cryptbrau](/pict/cryptbrau/)
+  - [informary](/pict/informary/)
+  - [pict-service-commandlineutility](/pict/pict-service-commandlineutility/)
   - [pict-section-recordset](/pict/pict-section-recordset/)
-  - [pict-section-tuigrid](/pict/pict-section-tuigrid/)
   - [pict-section-content](/pict/pict-section-content/)
-  - [pict-panel](/pict/pict-panel/)
+  - [pict-section-form](/pict/pict-section-form/)
+  - [pict-section-tuigrid](/pict/pict-section-tuigrid/)
   - [pict-router](/pict/pict-router/)
-  - [informary](/pict/informary/)
-  - [cryptbrau](/pict/cryptbrau/)
   - [pict-serviceproviderbase](/pict/pict-serviceproviderbase/)
-  - [pict-service-commandlineutility](/pict/pict-service-commandlineutility/)
+  - [pict-terminalui](/pict/pict-terminalui/)
 
-- [Utility — Build Tools](utility.md)
+- [Utility — Build Tools](modules/utility.md)
 
   - [indoctrinate](/utility/indoctrinate/)
   - [manyfest](/utility/manyfest/)
   - [quackage](/utility/quackage/)
-  - [choreographic](/utility/choreographic/)
   - [ultravisor](/utility/ultravisor/)

package/docs/_topbar.md

@@ -1,6 +1,6 @@
 # Retold
 
 - [Getting Started](getting-started.md)
-- [Architecture](architecture.md)
-- [All Modules](modules.md)
+- [Architecture](architecture/architecture.md)
+- [All Modules](architecture/modules.md)
 - [GitHub](https://github.com/stevenvelozo/retold)

package/docs/architecture/module-architecture.md

@@ -0,0 +1,234 @@
+# Ecosystem Architecture - Module Philosophy
+
+Retold modules each embody a specific design philosophy. Together they form a coherent system for building applications — from the stateless service core, through data access and API generation, up to state-driven UI rendering.  At the same time, each module is designed to be used (*and useful*) independently. You can adopt Fable's configuration and logging without using Pict. You can use Meadow for data access without Orator. These modules are decoupled by design, but also fit together in a complementary way.
+
+```mermaid
+graph TB
+	subgraph Clients["Client Applications"]
+		direction LR
+		browser["Browser App<br/><i>Pict + Pict-Application<br/>+ Pict-Views</i>"]
+		console["Console App<br/><i>Pict + Terminal UI</i>"]
+		cli["CLI Tool<br/><i>CommandLineUtility</i>"]
+	end
+
+	internet(("The Internet<br/>☁"))
+
+	subgraph Server["Server / Mid-Tier"]
+		direction TB
+		orator["Orator<br/><i>HTTP Server Abstraction</i>"]
+		endpoints["Meadow-Endpoints<br/><i>Auto-generated REST API</i>"]
+		meadow["Meadow<br/><i>Data Access Abstraction</i>"]
+
+		subgraph DataTools["Schema & Query Tools"]
+			direction LR
+			foxhound["FoxHound<br/><i>Query Generation</i>"]
+			stricture["Stricture<br/><i>MicroDDL → Schema</i>"]
+		end
+
+		orator --> endpoints
+		endpoints --> meadow
+		meadow --> DataTools
+	end
+
+	subgraph Foundation["Foundation (Stateless)"]
+		direction LR
+		fable["Fable<br/><i>DI, Config, Logging</i>"]
+		manyfest["Manyfest<br/><i>Address-Based<br/>Object Access</i>"]
+	end
+
+	Clients -- "HTTP requests" --> internet
+	internet -- "HTTP requests" --> orator
+
+	browser -. "Fable services" .-> Foundation
+	Server --> Foundation
+
+	style Clients fill:#e8f5e9,stroke:#43a047,color:#333
+	style browser fill:#fff,stroke:#66bb6a,color:#333
+	style console fill:#fff,stroke:#66bb6a,color:#333
+	style cli fill:#fff,stroke:#66bb6a,color:#333
+	style internet fill:#e1f5fe,stroke:#03a9f4,color:#333,stroke-width:2px
+	style Server fill:#e3f2fd,stroke:#42a5f5,color:#333
+	style orator fill:#fff,stroke:#64b5f6,color:#333
+	style endpoints fill:#fff,stroke:#64b5f6,color:#333
+	style meadow fill:#fff3e0,stroke:#ffa726,color:#333
+	style DataTools fill:#fff8e1,stroke:#ffcc80,color:#333
+	style foxhound fill:#fff,stroke:#ffcc80,color:#333
+	style stricture fill:#fff,stroke:#ffcc80,color:#333
+	style Foundation fill:#fce4ec,stroke:#ef5350,color:#333
+	style fable fill:#fff,stroke:#ef9a9a,color:#333
+	style manyfest fill:#fff,stroke:#ef9a9a,color:#333
+```
+
+Clients — browsers, terminals, CLI tools — communicate with the server over HTTP. Orator receives those requests, Meadow-Endpoints maps them to data operations, and Meadow executes them against the database. Fable provides the stateless service container that every module on both sides of the network depends on. Manyfest provides the consistent data-addressing language used everywhere.
+
+---
+
+## Fable Is Stateless
+
+Fable draws a hard line between **configuration** and **state**.
+
+In Retold's vocabulary, *state* is **application data** — the records in a database, the items in a shopping cart, the text a user has typed into a form. State changes as users interact with the system. It is the core subject matter of the application.
+
+Configuration is everything else: the address of the database server, the port the API listens on, the log level, the product name. Configuration describes how the application runs in its environment, not what the application is doing. Fable manages configuration. It does not manage state.
+
+This distinction matters because the "Out of the Tar Pit" problem — the paper Fable's design references — identifies uncontrolled state as the primary source of software complexity. By keeping the service container stateless, Fable ensures that the foundation layer has no opinion about your data. Services register with Fable, receive configuration and logging, and operate on whatever data flows through them without Fable holding onto it.
+
+Every Retold module extends `fable-serviceproviderbase` and registers with a Fable instance. That instance provides dependency injection, logging, UUID generation, and shared settings. But the Fable instance itself stores no application data. It is the wiring, not the warehouse.
+
+## Pict Is for State and Transformation
+
+If Fable is deliberately stateless, Pict is deliberately stateful. Pict's job is to hold application state and transform it consistently into output using a templating language.
+
+Pict provides three dedicated state containers:
+
+| Container | Purpose | Example Contents |
+|-----------|---------|------------------|
+| **AppData** | Primary application state | User records, form values, loaded entities |
+| **Bundle** | Supporting reference data | Lookup tables, dropdown options, translations |
+| **TempData** | Ephemeral intermediate data | Chart caches, calculated summaries, UI flags |
+
+All state lives in known locations. Templates reference state through address expressions like `AppData.Tasks[0].Name`. Code accesses the same state through the same addresses. There is one source of truth and one notation for reaching it.
+
+The key insight is that **state and lifecycle are coupled**. Pict's lifecycle phases — Solve, Render, Marshal — all operate on these state containers:
+
+1. **Solve** reads state and writes derived values back into state
+2. **Render** reads state and produces output through templates
+3. **Marshal** collects input and writes it back into state
+
+This cycle is predictable and debuggable. At any point in the lifecycle you can inspect the state containers and know exactly what data the application is working with.
+
+Pict intentionally separates logic from templates. Templates describe *what* to render; code (in views and providers) describes *when* and *how* data moves. You can override templates without altering behavior, and you can alter behavior without touching templates.
+
+## Pict-Application Manages the Lifecycle
+
+Pict-Application is the orchestration layer. It coordinates the startup, data loading, solving, rendering, and marshaling of an entire application composed of multiple views and providers.
+
+The lifecycle follows a defined sequence:
+
+```mermaid
+graph LR
+	init["Initialize<br/><i>Register views,<br/>providers, templates</i>"]
+	data["Load Data<br/><i>Fetch from APIs,<br/>populate AppData</i>"]
+	solve["Solve<br/><i>Calculate derived<br/>values</i>"]
+	render["Render<br/><i>Transform state<br/>into output</i>"]
+	marshal["Marshal<br/><i>Collect input<br/>back into state</i>"]
+
+	init --> data --> solve --> render --> marshal
+	marshal -. "user interaction" .-> solve
+
+	style init fill:#fce4ec,stroke:#ef5350,color:#333
+	style data fill:#fff3e0,stroke:#ffa726,color:#333
+	style solve fill:#e8f5e9,stroke:#43a047,color:#333
+	style render fill:#e3f2fd,stroke:#42a5f5,color:#333
+	style marshal fill:#f3e5f5,stroke:#ab47bc,color:#333
+```
+
+Each view and provider within the application participates in these phases. Pict-Application ensures they execute in the correct order (controlled by configurable ordinals) and provides auto-behaviors to reduce boilerplate — for example, automatically solving and rendering after initialization completes.
+
+The application also manages authentication flows, data loading sequences, and the coordination between views that need to share state. It is the conductor; views and providers are the musicians.
+
+## Pict-View Is Not Just a Screen
+
+A Pict view is any representation of information. It is not a page. It is not a screen. It is not a route.
+
+A single screen might contain dozens of views: a header view, a navigation view, a list view, a detail panel view, a status bar view. Or a single view might render to a log file, a terminal widget, or a test harness instead of a browser DOM. The view is the unit of *rendering*, not the unit of *navigation*.
+
+Each view contains **renderables** — individual render instructions that specify:
+
+- Which **template** to use
+- Which **data address** to read from state
+- Which **destination** to render into
+- Which **method** to use (replace, append, prepend)
+
+This makes views composable. Small views handle small concerns. Larger patterns emerge from combining them. A form section view renders input fields. A recordset view renders a list of records. A content view renders static markup. You assemble an application from these building blocks.
+
+Because views render through a content assignment abstraction, they are not bound to the browser DOM. The same view code can render to a blessed terminal widget, a log stream, or a mock environment for testing — by swapping the content assignment functions. The view does not know or care where its output ends up.
+
+## Orator Abstracts Web Servers
+
+Orator provides a thin abstraction over HTTP servers. Your application code interacts with Orator's interface — defining routes, middleware, and lifecycle hooks — without coupling to a specific server implementation.
+
+The default implementation uses Restify (`orator-serviceserver-restify`), but the abstraction means you could swap in a different HTTP library or use IPC mode for testing without changing application routes or middleware. Orator handles the HTTP lifecycle: receiving requests, running middleware, dispatching to handlers, and sending responses.
+
+Orator also provides static file serving (`orator-static-server`) and reverse proxy capabilities (`orator-http-proxy`), making it a complete server-side HTTP toolkit without being a heavyweight framework.
+
+The philosophy is deliberate thinness. Orator does not dictate application structure. It provides the plumbing for getting HTTP requests to your code and responses back to the client.
+
+## Meadow Abstracts Data Access
+
+Meadow is a provider-agnostic data broker. You define entities once — their fields, types, and relationships — and Meadow handles CRUD operations against whatever database is connected.
+
+The abstraction has real teeth: the same Meadow entity definition works with MySQL, MSSQL, SQLite, and ALASQL (for in-browser use). Switch databases by swapping a connection module. Your application code, entity definitions, and endpoint configurations do not change.
+
+Meadow automatically manages audit columns (who created a record, who last updated it, and when), soft deletes (marking records as deleted without removing them), GUID-based uniqueness, and data marshalling between JavaScript objects and database rows.
+
+The data access pattern is deliberately simple: Create, Read, Reads (list), Update, Delete, Count, and Undelete. These seven operations cover the vast majority of data access needs. When they do not, behavior hooks let you inject custom logic at any point in the operation lifecycle.
+
+## Meadow-Endpoints Connects Data Access to a Consistent API
+
+Meadow-Endpoints takes a Meadow entity and automatically generates a full REST API for it. Define an entity called `Book` and you immediately get `GET /Books`, `GET /Book/:id`, `POST /Book`, `PUT /Book`, `DEL /Book/:id`, and more — with filtering, pagination, sorting, and schema introspection built in.
+
+This is not code generation that produces files you maintain. The endpoints are generated at runtime from the entity definition. Change the schema, restart the server, and the API updates. Add a new entity, wire it to Meadow-Endpoints, and the routes appear.
+
+Behavior hooks provide the extension points. Need authentication? Add a `before` hook. Need to transform data before it reaches the client? Add an `after` hook. Need custom validation? Hook into the create and update paths. The auto-generated API is the foundation; hooks let you customize without replacing it.
+
+## FoxHound Generates Queries
+
+FoxHound is the query generation engine inside Meadow. It provides a chainable API for building queries — adding filters, setting sort order, configuring pagination — and then generates the correct SQL dialect for whichever database you are using.
+
+```javascript
+_Query.addFilter('Status', 'Complete')
+      .setSort('CreatedDate')
+      .setBegin(0).setCap(50)
+      .buildReadQuery();
+```
+
+This same code produces valid MySQL, MSSQL, SQLite, or ALASQL depending on the dialect. Application code never writes raw SQL. FoxHound's job is to be the single translation layer between a database-agnostic query description and dialect-specific SQL.
+
+FoxHound also powers the **FilteredTo** URL syntax used by Meadow-Endpoints, which encodes filters, sorts, and pagination into URL paths for GET requests. This means clients can express complex queries through standard HTTP URLs without POST bodies.
+
+## Stricture Transforms MicroDDL into Schemas
+
+Stricture provides a compact notation — MicroDDL — for defining data models. A MicroDDL file is a human-readable text format where each line defines a column using single-character sigils:
+
+```
+!ID
+@GUIDTask
+#Name
+#Description
+#Status
+&Hours
+%Due
+```
+
+From this terse input, Stricture generates:
+
+- **JSON schemas** for Meadow entity definitions
+- **CREATE TABLE statements** for MySQL, MSSQL, or SQLite
+- **Documentation** describing the data model
+- **Seed data templates** for testing
+
+The philosophy is *define once, generate everywhere*. The MicroDDL is the single source of truth for a data model. Every downstream artifact — database tables, API schemas, documentation — derives from it. Change the MicroDDL, regenerate, and all representations stay in sync.
+
+## Manyfest Provides Address-Based Object Access
+
+Manyfest solves a recurring problem: the same data structure is described and accessed differently at every layer of an application. The database has column names. The API has JSON keys. The frontend has display labels. Business logic has domain terms.
+
+Manyfest unifies this through **address-based access**. An address is a string like `Record.Contact.Email` that describes a location in a nested JavaScript object. Manyfest provides safe accessors that navigate the address without throwing exceptions on missing intermediate objects:
+
+```javascript
+// Safe read — returns undefined if any part of the path is missing
+let email = _Manyfest.getValueAtAddress(pRecord, 'Contact.Email');
+
+// Safe write — creates intermediate objects as needed
+_Manyfest.setValueAtAddress(pRecord, 'Contact.Email', 'new@example.com');
+```
+
+Beyond safe access, Manyfest provides **descriptors** — metadata that maps addresses to human-readable names, short names, descriptions, data types, and hashes. This means a single Manyfest definition can drive:
+
+- API field documentation
+- Form field labels and validation
+- Report column headers
+- Data transformation between layers
+
+The address notation is the same notation Pict uses for template expressions and state access. This consistency means a Manyfest schema defined for the data layer can flow all the way through to form labels in the browser without translation.

package/docs/{modules.md → architecture/modules.md}

@@ -13,25 +13,24 @@ An exhaustive list of every repository in the Retold suite, organized by group.
 | [fable-uuid](/fable/fable-uuid/) | `fable-uuid` | UUID generator supporting RFC 4122 v4 and configurable random strings |
 | [fable-log-logger-bunyan](/fable/fable-log-logger-bunyan/) | `fable-log-logger-bunyan` | Bunyan structured logging provider for Fable-Log |
 
-## Meadow — Data Access Layer (13 modules)
+## Meadow — Data Access Layer (12 modules)
 
 | Module | npm | Description |
 |--------|-----|-------------|
-| [meadow](/meadow/meadow/) | `meadow` | Provider-agnostic data broker with CRUD operations, audit tracking, and soft deletes |
-| [foxhound](/meadow/foxhound/) | `foxhound` | Fluent query DSL generating dialect-specific SQL for MySQL, MSSQL, SQLite, and ALASQL |
 | [stricture](/meadow/stricture/) | `stricture` | MicroDDL schema definition language generating JSON, SQL DDL, and documentation |
+| [foxhound](/meadow/foxhound/) | `foxhound` | Fluent query DSL generating dialect-specific SQL for MySQL, MSSQL, SQLite, and ALASQL |
+| [bibliograph](/meadow/bibliograph/) | `bibliograph` | Key-value record comprehension for change tracking in data ingestion pipelines |
+| [meadow](/meadow/meadow/) | `meadow` | Provider-agnostic data broker with CRUD operations, audit tracking, and soft deletes |
+| [parime](/meadow/parime/) | `parime` | Generic data lake behaviors and services |
 | [meadow-endpoints](/meadow/meadow-endpoints/) | `meadow-endpoints` | Automatic RESTful CRUD endpoint generation from Meadow entities with behavior injection |
 | [meadow-connection-mysql](/meadow/meadow-connection-mysql/) | `meadow-connection-mysql` | MySQL/MariaDB pooled connection provider for Meadow |
 | [meadow-connection-mssql](/meadow/meadow-connection-mssql/) | `meadow-connection-mssql` | Microsoft SQL Server connection provider for Meadow |
 | [meadow-connection-sqlite](/meadow/meadow-connection-sqlite/) | `meadow-connection-sqlite` | SQLite connection provider for Meadow via better-sqlite3 |
 | [retold-data-service](/meadow/retold-data-service/) | `retold-data-service` | All-in-one Fable service assembling schema → entity → endpoints → REST API |
 | [retold-harness](/meadow/retold-harness/) | `retold-harness` | Pre-built API harness with a bookstore demo (8 entities, 10,000+ records) |
-| [bibliograph](/meadow/bibliograph/) | `bibliograph` | Key-value record comprehension for change tracking in data ingestion pipelines |
-| [parime](/meadow/parime/) | `parime` | Generic data lake behaviors and services |
 | [meadow-integration](/meadow/meadow-integration/) | `meadow-integration` | Data integration tools for CSV import, schema mapping, and centralized formats |
-| [meadow-graph-client](/meadow/meadow-graph-client/) | `meadow-graph-client` | Client for pulling related record sets from relational database graphs |
 
-## Orator — API Server (6 modules)
+## Orator — API Server (7 modules)
 
 | Module | npm | Description |
 |--------|-----|-------------|
@@ -41,35 +40,39 @@ An exhaustive list of every repository in the Retold suite, organized by group.
 | [orator-http-proxy](/orator/orator-http-proxy/) | `orator-http-proxy` | HTTP reverse proxy for forwarding requests to backend services |
 | [tidings](/orator/tidings/) | `tidings` | Extensible reporting system for generating HTML, PDF, and other format reports |
 | [orator-endpoint](/orator/orator-endpoint/) | `orator-endpoint` | Pluggable API endpoint base class for reusable route handlers |
+| [orator-conversion](/orator/orator-conversion/) | `orator-conversion` | File format conversion endpoints for Orator service servers |
 
-## Pict — MVC Tools (15 modules)
+## Pict — MVC Tools (19 modules)
 
 | Module | npm | Description |
 |--------|-----|-------------|
 | [pict](/pict/pict/) | `pict` | Non-opinionated MVC module with template expression engine for text-based UIs |
-| [pict-view](/pict/pict-view/) | `pict-view` | View base class with full lifecycle (init, render, solve, marshal), renderables, and CSS |
 | [pict-template](/pict/pict-template/) | `pict-template` | Template handler base class for custom expression types |
+| [pict-view](/pict/pict-view/) | `pict-view` | View base class with full lifecycle (init, render, solve, marshal), renderables, and CSS |
 | [pict-provider](/pict/pict-provider/) | `pict-provider` | Data provider base class for delivering data to views |
 | [pict-application](/pict/pict-application/) | `pict-application` | Application base class coordinating views, state, and lifecycle |
-| [pict-section-form](/pict/pict-section-form/) | `pict-section-form` | Configuration-driven dynamic forms with 13+ input types and data marshaling |
+| [pict-panel](/pict/pict-panel/) | `pict-panel` | Hot-loadable control panel component for browser applications |
+| [pict-nonlinearconfig](/pict/pict-nonlinearconfig/) | `pict-nonlinearconfig` | Pict nonlinear configuration manager |
+| [pict-section-flow](/pict/pict-section-flow/) | `pict-section-flow` | Pict section flow diagram |
+| [pict-docuserve](/pict/pict-docuserve/) | `pict-docuserve` | Single-page documentation viewer built on Pict |
+| [cryptbrau](/pict/cryptbrau/) | `cryptbrau` | Simple in-browser symmetric encryption |
+| [informary](/pict/informary/) | `informary` | Dependency-free browser form marshaling with undo/redo and field-level deltas |
+| [pict-service-commandlineutility](/pict/pict-service-commandlineutility/) | `pict-service-commandlineutility` | CLI utility module built on Commander for Pict-based command-line tools |
 | [pict-section-recordset](/pict/pict-section-recordset/) | `pict-section-recordset` | CRUD record management views from Meadow endpoint schemas |
+| [pict-section-content](/pict/pict-section-content/) | `pict-section-content` | Markdown parsing and content rendering with Mermaid diagrams and KaTeX math |
+| [pict-section-form](/pict/pict-section-form/) | `pict-section-form` | Configuration-driven dynamic forms with 13+ input types and data marshaling |
 | [pict-section-tuigrid](/pict/pict-section-tuigrid/) | `pict-section-tuigrid` | Toast UI Grid integration for tabular data display and editing |
-| [pict-section-content](/pict/pict-section-content/) | `pict-section-content` | Content display sections for static and dynamic content blocks |
-| [pict-panel](/pict/pict-panel/) | `pict-panel` | Hot-loadable control panel component for browser applications |
 | [pict-router](/pict/pict-router/) | `pict-router` | Hash-based URL routing via Navigo with template string route functions |
-| [informary](/pict/informary/) | `informary` | Dependency-free browser form marshaling with undo/redo and field-level deltas |
-| [cryptbrau](/pict/cryptbrau/) | `cryptbrau` | Simple in-browser symmetric encryption |
 | [pict-serviceproviderbase](/pict/pict-serviceproviderbase/) | `pict-serviceproviderbase` | Base classes for Pict services with pre-initialization support |
-| [pict-service-commandlineutility](/pict/pict-service-commandlineutility/) | `pict-service-commandlineutility` | CLI utility module built on Commander for Pict-based command-line tools |
+| [pict-terminalui](/pict/pict-terminalui/) | `pict-terminalui` | Blessed-based terminal interface for Pict views |
 
-## Utility — Build & Documentation Tools (5 modules)
+## Utility — Build & Documentation Tools (4 modules)
 
 | Module | npm | Description |
 |--------|-----|-------------|
 | [indoctrinate](/utility/indoctrinate/) | `indoctrinate` | Documentation scaffolding with content cataloging, label-based filtering, and multi-format output |
 | [manyfest](/utility/manyfest/) | `manyfest` | JSON manifest for consistent data description, validation, and address-based access across layers |
 | [quackage](/utility/quackage/) | `quackage` | Standardized build tool for browser bundles, transpilation, testing, and packaging |
-| [choreographic](/utility/choreographic/) | `choreographic` | Scaffolding for single-run data processing scripts with organized output |
 | [ultravisor](/utility/ultravisor/) | `ultravisor` | Process supervision with scheduled tasks, distributed nodes, and LLM integration |
 
 ## Summary
@@ -77,11 +80,11 @@ An exhaustive list of every repository in the Retold suite, organized by group.
 | Group | Count | Focus |
 |-------|-------|-------|
 | Fable | 6 | Core ecosystem, DI, configuration, logging |
-| Meadow | 13 | Data access, ORM, query DSL, schema, connectors |
-| Orator | 6 | API server, HTTP, static files, proxy, reporting |
-| Pict | 15 | MVC, views, templates, forms, grids, routing |
-| Utility | 5 | Build tools, manifests, docs, process supervision |
-| **Total** | **45** | |
+| Meadow | 12 | Data access, ORM, query DSL, schema, connectors |
+| Orator | 7 | API server, HTTP, static files, proxy, reporting, conversion |
+| Pict | 19 | MVC, views, templates, forms, grids, routing, docs, TUI |
+| Utility | 4 | Build tools, manifests, docs, process supervision |
+| **Total** | **48** | |
 
 ## GitHub Repositories
 

package/docs/cover.md

@@ -10,6 +10,6 @@
 - **Pict** — MVC tools, views, templates, forms
 
 [Get Started](getting-started.md)
-[Architecture](architecture.md)
-[All Modules](modules.md)
+[Architecture](architecture/architecture.md)
+[All Modules](modules/modules.md)
 [GitHub](https://github.com/stevenvelozo/retold)

package/docs/css/docuserve.css

@@ -13,7 +13,7 @@ html, body {
 	font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif;
 	font-size: 16px;
 	line-height: 1.5;
-	color: #333;
+	color: #423D37;
 	background-color: #fff;
 	-webkit-font-smoothing: antialiased;
 	-moz-osx-font-smoothing: grayscale;
@@ -26,12 +26,12 @@ h1, h2, h3, h4, h5, h6 {
 }
 
 a {
-	color: #42b983;
+	color: #2E7D74;
 	text-decoration: none;
 }
 
 a:hover {
-	color: #38a373;
+	color: #256861;
 }
 
 /* Application container */
@@ -45,16 +45,16 @@ a:hover {
 }
 
 ::-webkit-scrollbar-track {
-	background: #f1f1f1;
+	background: #F5F0E8;
 }
 
 ::-webkit-scrollbar-thumb {
-	background: #bdc3c7;
+	background: #D4CCBE;
 	border-radius: 4px;
 }
 
 ::-webkit-scrollbar-thumb:hover {
-	background: #95a5a6;
+	background: #B5AA9A;
 }
 
 /* Responsive adjustments */