retold 4.0.1 → 4.0.3

package/docs/examples/todolist/todo-list-server.md

@@ -0,0 +1,128 @@
+# Todo List: API Server
+
+> Part of the [Todo List Application](examples/todolist/todo-list.md) example.
+>
+> **Source:** [`examples/todo-list/server/`](../examples/todo-list/server/)
+
+The server demonstrates the standard Retold API assembly: Fable for dependency injection, Meadow for data access, Meadow Endpoints for automatic REST route generation, and Orator for the HTTP server. It also shows how to create a custom Fable service for database initialization and CSV seeding.
+
+## Running
+
+```bash
+cd examples/todo-list/server
+npm install
+npm start
+```
+
+The server starts on **http://localhost:8086** and serves both the REST API and the web client's static files.
+
+### Running with Docker
+
+From the `examples/todo-list/` directory, run `./docker-run.sh` to build the Docker image and start the server. The web client is pre-built inside the image, so you can open **http://localhost:8086** immediately. See the [main quickstart](examples/todolist/todo-list.md) for details on the interactive shell.
+
+## How It Works
+
+```mermaid
+graph TB
+    subgraph startup["Startup Sequence"]
+        direction TB
+        s1["1. Create Fable instance<br/><i>Settings, logging, SQLite config</i>"]
+        s2["2. Register service types<br/><i>Orator, SQLite provider, DB init service</i>"]
+        s3["3. Connect database<br/><i>Open or create todo.sqlite</i>"]
+        s4["4. Create tables<br/><i>From compiled Stricture DDL</i>"]
+        s5["5. Seed data<br/><i>CSV → Meadow doCreate (if empty)</i>"]
+        s6["6. Create Meadow DAL<br/><i>Task entity with schema</i>"]
+        s7["7. Create Meadow Endpoints<br/><i>Auto-generate REST routes</i>"]
+        s8["8. Start Orator<br/><i>HTTP server + static files</i>"]
+
+        s1 --> s2 --> s3 --> s4 --> s5 --> s6 --> s7 --> s8
+    end
+```
+
+The server file (`server.cjs`) is intentionally thin. Most of the behavior comes from Retold modules -- the server's job is to wire them together in the right order.
+
+### Step 1-2: Fable and Service Registration
+
+A Fable instance is created with settings for the product name, API port, and SQLite file path. Service types are registered for the HTTP server (Orator + Restify), the SQLite connection provider, and the custom database initialization service.
+
+### Step 3-5: Database Setup
+
+The `DatabaseInitializationService` is a custom Fable service (extending `fable-serviceproviderbase`) that handles three tasks:
+
+1. **Connect** -- Ensures the `data/` directory exists and opens the SQLite file through `meadow-connection-sqlite`
+2. **Create tables** -- Passes the compiled Stricture model to the provider's `createTables()` method, which generates SQLite DDL
+3. **Seed data** -- Checks if the table is empty; if so, reads the CSV file, parses it, and inserts each row through the Meadow DAL using `doCreate()` queued with Fable's Anticipate service
+
+Because seeding goes through the Meadow DAL, every record gets automatic GUID generation, audit timestamps, and default values.
+
+### Step 6-7: Entity and Endpoints
+
+A Meadow DAL instance is created for the Task entity, configured with the schema from `MeadowSchema-Task.json`. Meadow Endpoints then wraps this DAL to generate the full REST API automatically.
+
+### Step 8: HTTP Server
+
+Orator initializes with Restify, connects the auto-generated endpoints, adds a static file route pointing to `../web-client/dist/`, and starts listening.
+
+## API Endpoints
+
+Meadow Endpoints auto-generates these routes from the Task entity:
+
+| Method | Endpoint | Description |
+|--------|----------|-------------|
+| GET | `/1.0/Tasks/{Begin}/{Cap}` | List tasks with pagination |
+| GET | `/1.0/Tasks/FilteredTo/{Filter}/{Begin}/{Cap}` | List with sort, search, filter |
+| GET | `/1.0/Task/{IDTask}` | Read a single task |
+| POST | `/1.0/Task` | Create a task |
+| PUT | `/1.0/Task` | Update a task |
+| DELETE | `/1.0/Task/{IDTask}` | Soft-delete a task |
+| GET | `/1.0/Tasks/Count` | Total record count |
+| GET | `/1.0/Tasks/Count/FilteredTo/{Filter}` | Filtered record count |
+
+### FilteredTo Query Syntax
+
+The FilteredTo URL segment accepts tilde-delimited filter stanzas that the server parses into SQL through FoxHound. This is how all three clients request sorted, filtered, and paginated data.
+
+**Sort stanza:**
+
+```
+FSF~{Column}~{Direction}~0
+```
+
+Example: `FSF~DueDate~DESC~0` sorts by DueDate descending.
+
+**Filter stanzas:**
+
+```
+FBV~{Column}~{Operator}~{Value}       (AND)
+FBVOR~{Column}~{Operator}~{Value}     (OR)
+```
+
+Common operators: `EQ` (equals), `LK` (LIKE), `GT` (greater than), `LT` (less than), `IN` (IS NULL), `NN` (IS NOT NULL).
+
+**Combined example:**
+
+```
+/1.0/Tasks/FilteredTo/FBV~Name~LK~%25garden%25~FBVOR~Description~LK~%25garden%25~FSF~DueDate~DESC~0/0/50
+```
+
+This searches for tasks where Name or Description contains "garden", sorted by DueDate descending, returning the first 50 results. The `%25` is the URL-encoded `%` wildcard for the LIKE operator.
+
+## Dependencies
+
+| Module | Role |
+|--------|------|
+| `fable` | Dependency injection, configuration, logging |
+| `orator` | HTTP server abstraction |
+| `orator-serviceserver-restify` | Restify implementation for Orator |
+| `meadow` | Data access layer (ORM) |
+| `meadow-endpoints` | Auto-generated REST routes |
+| `meadow-connection-sqlite` | SQLite connection provider |
+| `fable-serviceproviderbase` | Base class for DatabaseInitializationService |
+
+## Files
+
+| File | Purpose |
+|------|---------|
+| `server.cjs` | Main entry point -- wires Fable, Orator, Meadow, and SQLite together |
+| `database-initialization-service.cjs` | Custom Fable service for table creation and CSV seeding |
+| `data/todo.sqlite` | SQLite database file (auto-created on first run) |

package/docs/examples/todolist/todo-list-web-client.md

@@ -0,0 +1,177 @@
+# Todo List: Web Client
+
+> Part of the [Todo List Application](examples/todolist/todo-list.md) example.
+>
+> **Source:** [`examples/todo-list/web-client/`](../examples/todo-list/web-client/)
+
+The web client is a browser-based Pict Application with hash routing, data providers, and six views. It demonstrates the standard Pict patterns for building a single-page application: views render templates into DOM containers, a provider manages API communication, and the application class coordinates lifecycle and shared state.
+
+## Running
+
+```bash
+cd examples/todo-list/web-client
+npm install
+npm run build
+```
+
+Then open **http://localhost:8086** in a browser (the API server serves the built files).
+
+The build step uses Quackage to browserify the application source into `dist/`, then copies the HTML shell and CSS theme alongside it.
+
+### Running with Docker
+
+From the `examples/todo-list/` directory, run `./docker-run.sh` to build the Docker image and start the server. The web client is already built inside the image -- just open **http://localhost:8086** in a browser. See the [main quickstart](examples/todolist/todo-list.md) for more options.
+
+## Application Structure
+
+```mermaid
+graph TB
+    subgraph app["TodoList-Application"]
+        state["AppData.TodoList<br/><i>Tasks, ListState, CalendarState</i>"]
+    end
+
+    subgraph providers["Providers"]
+        taskdata["Provider-TaskData<br/><i>API fetch, query URL builder</i>"]
+        router["PictRouter<br/><i>Hash-based SPA routing</i>"]
+    end
+
+    subgraph views["Views"]
+        layout["View-Layout<br/><i>Nav bar + content outlet</i>"]
+        list["View-TaskList<br/><i>Sortable table, search, pagination</i>"]
+        form["View-TaskForm<br/><i>Add / edit form</i>"]
+        week["View-WeekView<br/><i>Seven-day calendar grid</i>"]
+        month["View-MonthView<br/><i>Month grid with day cells</i>"]
+        year["View-YearView<br/><i>Twelve month overview</i>"]
+    end
+
+    app --- taskdata
+    app --- router
+    router --> layout
+    layout --> list
+    layout --> form
+    layout --> week
+    layout --> month
+    layout --> year
+    taskdata --> list
+    taskdata --> form
+```
+
+## Application Class
+
+`TodoList-Application.cjs` extends `pict-application` and is the central coordinator. In its constructor it registers all views, the data provider, and the router. In `onAfterInitializeAsync` it initializes the shared state object (`AppData.TodoList`) and triggers the first data load.
+
+The shared state holds:
+
+- **Tasks** -- the current page of task records from the API
+- **ListState** -- sort column, sort direction, search text, pagination bounds
+- **CalendarState** -- anchor date and pre-computed row data for week/month/year views
+
+The application class also provides action methods called from view templates: `addTask()`, `editTask(id)`, `deleteTask(id)`, `saveTask()`, `changeSortOrder(value)`, `searchTasks()`, `clearSearch()`, `showCalendarView(id)`, `calendarNavigate(unit, delta)`, and `calendarToday(unit)`.
+
+## Data Provider
+
+`Provider-TaskData.cjs` extends `pict-provider` and encapsulates all API communication. Its key methods:
+
+- **`buildReadsURL()`** -- constructs a Meadow FilteredTo URL from the current ListState (sort, search, pagination). This is where the FBV/FBVOR/FSF filter stanzas are assembled.
+- **`loadTasks(callback)`** -- fetches the task list, total count, and (when searching) filtered count in a single `Promise.all` batch
+- **`loadAllTasks(callback)`** -- fetches every task sorted by date for the calendar views
+- **`createTask(data, callback)`** -- POST to `/1.0/Task`
+- **`updateTask(data, callback)`** -- PUT to `/1.0/Task`
+- **`deleteTask(id, callback)`** -- DELETE to `/1.0/Task/:id`
+
+## Routing
+
+`Router-Config.json` defines the hash routes:
+
+| Route | View | Description |
+|-------|------|-------------|
+| `/TaskList` | TodoList-TaskList | Task list (default) |
+| `/TaskForm` | TodoList-TaskForm | New task form |
+| `/TaskForm/:id` | TodoList-TaskForm | Edit task form |
+| `/WeekView` | TodoList-WeekView | Week calendar |
+| `/MonthView` | TodoList-MonthView | Month calendar |
+| `/YearView` | TodoList-YearView | Year calendar |
+
+Navigation links in the layout view set `window.location.hash`, which the Pict Router picks up and renders the corresponding view into the content outlet.
+
+## Views
+
+### View-Layout
+
+The root container. Renders a navigation bar with links to the task list and calendar views, plus a `#TodoList-Content` div that child views render into. The nav bar uses the Sagebrush color theme.
+
+View-specific CSS: nav bar styling only (background, link colors, separator).
+
+### View-TaskList
+
+The main task list with:
+
+- A toolbar with search input, sort dropdown, record count display, and add button
+- A data table with Name, Due Date, Hours, Status, and Actions columns
+- Per-row Edit and Delete action buttons
+- Status badges color-coded by task state
+- TemplateSet iteration (`{~Each:...~}`) to render rows from the Tasks array
+
+View-specific CSS: button sizing overrides for toolbar and action columns.
+
+### View-TaskForm
+
+A form for creating and editing tasks. Fields: Name, Description, DueDate (date picker), LengthInHours, Status (dropdown). The form reads from `AppData.TodoList.SelectedTask` and calls `saveTask()` on submit.
+
+### View-WeekView
+
+A seven-day calendar grid anchored to the current week. Shows task counts per day with navigation buttons (previous/next week, today). All calendar views use `AppData.TodoList.AllTasks` and compute their display data client-side from the full task set.
+
+### View-MonthView
+
+A full month grid with 7 columns (Sun-Sat). Each day cell shows the number of complete and open tasks. Days outside the current month are dimmed.
+
+View-specific CSS: month grid layout, cell styling, day number positioning.
+
+### View-YearView
+
+Twelve month cards arranged in a 4x3 grid, each showing the task count for that month. Below the grid, a summary table lists statistics. The current month is highlighted.
+
+View-specific CSS: year grid layout, card styling, current-month border.
+
+## CSS Architecture
+
+Shared styles live in `css/todolist-theme.css` -- a plain CSS file loaded via `<link>` in `index.html` and copied to `dist/css/` by the build. This file contains the Sagebrush color theme, base typography, buttons, table styling, form styling, status badges, and shared calendar styles.
+
+View-specific styles stay in each view's configuration as inline `/*css*/` tagged template strings. Pict injects these into the page when the view renders. Only styles unique to a single view live here -- anything shared goes in the theme file.
+
+## Build System
+
+The web client uses Quackage (the Retold build tool) to bundle and copy files:
+
+- `npm run build` runs `npx quack build && npx quack copy`
+- Quackage reads `.gulpfile-quackage-config.json` for the browserify entry point and output path
+- The `copyFiles` array in `package.json` maps `html/*` and `css/*` to `dist/`, and copies `pict.min.js` from `node_modules`
+
+## Dependencies
+
+| Module | Role |
+|--------|------|
+| `pict` | Core view and template engine |
+| `pict-application` | Application lifecycle and service container |
+| `pict-view` | View base class |
+| `pict-provider` | Data provider base class |
+| `pict-router` | Hash-based client-side routing |
+| `quackage` (dev) | Build tool (Gulp wrapper for browserify + copy) |
+
+## Files
+
+| File | Purpose |
+|------|---------|
+| `source/TodoList-Application.cjs` | Application class -- registers views, providers, router; manages shared state |
+| `source/TodoList-Application-Config.json` | Pict application settings (main viewport, auto-solve, lazy render) |
+| `source/providers/Provider-TaskData.cjs` | Data provider -- API fetch, FilteredTo URL builder, CRUD methods |
+| `source/providers/Router-Config.json` | Route table mapping hash paths to views |
+| `source/views/View-Layout.cjs` | Root layout with navigation bar and content outlet |
+| `source/views/View-TaskList.cjs` | Paginated task table with search, sort, and inline actions |
+| `source/views/View-TaskForm.cjs` | Create / edit form |
+| `source/views/calendar/View-WeekView.cjs` | Week calendar grid |
+| `source/views/calendar/View-MonthView.cjs` | Month calendar grid |
+| `source/views/calendar/View-YearView.cjs` | Year overview with month cards |
+| `css/todolist-theme.css` | Shared Sagebrush theme stylesheet |
+| `html/index.html` | HTML shell -- loads Pict, the app bundle, and the theme CSS |

package/docs/examples/todolist/todo-list.md

@@ -0,0 +1,162 @@
+# Todo List Application
+
+A complete full-stack example demonstrating the Retold module suite. A single REST API server backed by SQLite is consumed by three separate clients: a browser-based Pict application, a terminal UI built on blessed, and a non-interactive command-line tool.
+
+> **Source:** [`examples/todo-list/`](../examples/todo-list/)
+
+## Architecture
+
+```mermaid
+graph TB
+    subgraph model["Shared Data Model"]
+        mddl["Task.mddl<br/><i>Stricture MicroDDL</i>"]
+        compiled["Task-Compiled.json<br/><i>DDL for table creation</i>"]
+        schema["MeadowSchema-Task.json<br/><i>ORM schema, types, defaults</i>"]
+        csv["seeded_todo_events.csv<br/><i>1,000 sample tasks</i>"]
+        mddl --> compiled
+        mddl --> schema
+    end
+
+    subgraph server["API Server"]
+        orator["Orator<br/><i>HTTP server (Restify)</i>"]
+        endpoints["Meadow Endpoints<br/><i>Auto-generated REST CRUD</i>"]
+        dal["Meadow DAL<br/><i>Task entity ORM</i>"]
+        dbinit["DatabaseInitializationService<br/><i>Table creation + CSV seeding</i>"]
+        sqlite[("todo.sqlite")]
+        static["Static file server<br/><i>Serves web-client/dist/</i>"]
+
+        orator --- endpoints
+        endpoints --- dal
+        dal --- sqlite
+        dbinit --> dal
+        orator --- static
+    end
+
+    compiled --> dbinit
+    schema --> dal
+    csv --> dbinit
+
+    subgraph web["Web Client"]
+        wapp["Pict Application<br/><i>Views, providers, routing</i>"]
+    end
+
+    subgraph console["Console Client"]
+        capp["blessed TUI<br/><i>pict-terminalui bridge</i>"]
+    end
+
+    subgraph cli["CLI Client"]
+        cliapp["pict-service-commandlineutility<br/><i>Commander.js commands</i>"]
+    end
+
+    wapp -- "fetch()" --> orator
+    static -- "HTML + JS + CSS" --> web
+    capp -- "http.request()" --> orator
+    cliapp -- "http.request()" --> orator
+```
+
+All four components share a single [Task data model](examples/todolist/todo-list-model.md) defined in Stricture MicroDDL. The server creates the SQLite table from the compiled DDL, seeds it with sample data through the Meadow DAL, and auto-generates REST endpoints with Meadow Endpoints. Each client speaks to the server over HTTP using the same query DSL for sorting, filtering, and pagination.
+
+## Quickstart
+
+### Prerequisites
+
+- Node.js 18+
+
+### 1. Start the API Server
+
+```bash
+cd examples/todo-list/server
+npm install
+npm start
+```
+
+The server starts on **http://localhost:8086**. On first run it creates a SQLite database, builds the Task table from compiled Stricture DDL, and seeds 1,000 sample tasks from a CSV file. Every seed record passes through the Meadow DAL, so GUIDs, audit timestamps, and default values are applied automatically.
+
+See [API Server](examples/todolist/todo-list-server.md) for details.
+
+### 2. Build and Open the Web Client
+
+```bash
+cd examples/todo-list/web-client
+npm install
+npm run build
+```
+
+Open **http://localhost:8086** in a browser. The server serves the built client as static files. The web client includes a sortable task list with search and pagination, an add/edit form, and week/month/year calendar views.
+
+See [Web Client](examples/todolist/todo-list-web-client.md) for details.
+
+### 3. Run the Console Client
+
+```bash
+cd examples/todo-list/console-client
+npm install
+npm start
+```
+
+A full-screen terminal UI. Use arrow keys to navigate, Enter to view a task, E to edit, S to pick a sort order, / to search, Q to quit.
+
+See [Console Client](examples/todolist/todo-list-console-client.md) for details.
+
+### 4. Use the CLI Client
+
+```bash
+cd examples/todo-list/cli-client
+npm install
+npx todo list
+npx todo add "Water the plants" --due 2026-03-15 --hours 0.5
+npx todo complete 42
+npx todo remove 42
+```
+
+See [CLI Client](examples/todolist/todo-list-cli-client.md) for details.
+
+### Running with Docker
+
+If you have Docker installed you can skip the per-component setup entirely. From the `examples/todo-list/` directory:
+
+**Start the server** (also serves the web client):
+
+```bash
+./docker-run.sh
+```
+
+Open **http://localhost:8086** in a browser. The image builds all four components, so the web client is already compiled.
+
+**Interactive shell** (for the CLI and console client):
+
+```bash
+./docker-shell.sh
+```
+
+A help banner shows available commands on login. Start the server in the background, then use the CLI or console TUI:
+
+```bash
+node server/server.cjs &
+cd /app/cli-client && npx todo list
+node /app/console-client/console-client.cjs
+```
+
+## Components
+
+| Component | Retold Modules | Description |
+|-----------|---------------|-------------|
+| [Data Model](examples/todolist/todo-list-model.md) | Stricture, Meadow | Task entity defined once, shared by all components |
+| [API Server](examples/todolist/todo-list-server.md) | Fable, Orator, Meadow, Meadow Endpoints, meadow-connection-sqlite | REST API with auto-generated CRUD and static file serving |
+| [Web Client](examples/todolist/todo-list-web-client.md) | Pict, pict-application, pict-view, pict-provider, pict-router, Quackage | Browser SPA with views, providers, hash routing, and calendar views |
+| [Console Client](examples/todolist/todo-list-console-client.md) | Pict, pict-application, pict-view, pict-terminalui, blessed | Full-screen terminal UI with modal dialogs |
+| [CLI Client](examples/todolist/todo-list-cli-client.md) | pict-service-commandlineutility, fable-serviceproviderbase | Non-interactive commands for list, add, remove, complete |
+
+## How the Pieces Connect
+
+The server is the single source of truth. It owns the database and exposes a REST API. No client accesses the database directly.
+
+All three clients build query URLs using the same Meadow FilteredTo syntax:
+
+```
+/1.0/Tasks/FilteredTo/FBV~Name~LK~%25search%25~FSF~DueDate~DESC~0/0/50
+```
+
+This URL encodes a LIKE search on the Name column, a descending sort by DueDate, and pagination from record 0 with a cap of 50. The server parses these filter stanzas and generates the corresponding SQL through FoxHound.
+
+The web client fetches data with the browser `fetch()` API. The console and CLI clients use Node.js `http.request()`. All three receive the same JSON responses and use the same API contract.

package/docs/getting-started.md

@@ -1,6 +1,6 @@
 # Getting Started
 
-This guide walks through building a Retold application step by step, adding one layer at a time. See the [Architecture](architecture.md) page for a full description of the layer model.
+This guide walks through building a Retold application step by step, adding one layer at a time. See the [Architecture](architecture/architecture.md) page for a full description of the layer model.
 
 > **Working examples:** Each step below has a corresponding runnable example in
 > [`examples/quickstart/`](../examples/quickstart/). Clone the repo and follow
@@ -264,9 +264,10 @@ Supporting the application stack are utility modules like **Manyfest** (schema-d
 
 ## Next Steps
 
-- **[Architecture](architecture.md)** — Understand the layer model in depth
-- **[Fable](fable.md)** — Deep dive into the core ecosystem and service provider pattern
-- **[Meadow](meadow.md)** — Data access, FoxHound queries, and Stricture schemas
-- **[Orator](orator.md)** — Server configuration, lifecycle hooks, and middleware
-- **[Pict](pict.md)** — Views, templates, providers, and application lifecycle
-- **[All Modules](modules.md)** — Every repository in the Retold suite
+- **[Architecture](architecture/architecture.md)** — Understand the layer model in depth
+- **[Examples](examples/examples.md)** — Complete runnable applications, including the [Todo List](examples/todolist/todo-list.md) full-stack example with four clients
+- **[Fable](modules/fable.md)** — Deep dive into the core ecosystem and service provider pattern
+- **[Meadow](modules/meadow.md)** — Data access, FoxHound queries, and Stricture schemas
+- **[Orator](modules/orator.md)** — Server configuration, lifecycle hooks, and middleware
+- **[Pict](modules/pict.md)** — Views, templates, providers, and application lifecycle
+- **[All Modules](modules/modules.md)** — Every repository in the Retold suite

package/docs/index.html

@@ -15,8 +15,8 @@
 		<!-- PICT Dynamic View CSS Container -->
 		<style id="PICT-CSS"></style>
 
-		<!-- Load the PICT library -->
-		<script src="./js/pict.min.js" type="text/javascript"></script>
+		<!-- Load the PICT library from jsDelivr CDN -->
+		<script src="https://cdn.jsdelivr.net/npm/pict@1/dist/pict.min.js" type="text/javascript"></script>
 		<!-- Bootstrap the Application -->
 		<script type="text/javascript">
 //<![CDATA[
@@ -33,7 +33,7 @@
 		<script>mermaid.initialize({ startOnLoad: false, theme: 'default' });</script>
 		<!-- KaTeX for LaTeX equation rendering -->
 		<script defer src="https://cdn.jsdelivr.net/npm/katex@0.16.21/dist/katex.min.js"></script>
-		<!-- Load the Docuserve PICT Application Bundle -->
-		<script src="./pict-docuserve.min.js" type="text/javascript"></script>
+		<!-- Load the Docuserve PICT Application Bundle from jsDelivr CDN -->
+		<script src="https://cdn.jsdelivr.net/npm/pict-docuserve@0/dist/pict-docuserve.min.js" type="text/javascript"></script>
 	</body>
 </html>

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

@@ -190,22 +190,20 @@ Each connection module provides a pooled database connection as a Fable service.
 | [parime](/meadow/parime/) | Generic data lake behaviors and services | `parime` |
 | [retold-harness](/meadow/retold-harness/) | Pre-built API harness with a bookstore demo (8 entities, 10,000+ records) | `retold-harness` |
 | [meadow-integration](/meadow/meadow-integration/) | Data integration tools for CSV import and schema mapping | `meadow-integration` |
-| [meadow-graph-client](/meadow/meadow-graph-client/) | Client for pulling related record sets from relational database graphs | `meadow-graph-client` |
 
 ## All Meadow Modules
 
 | Module | Description |
 |--------|-------------|
-| [meadow](/meadow/meadow/) | Provider-agnostic data broker and ORM |
-| [foxhound](/meadow/foxhound/) | Fluent query DSL with multi-dialect SQL generation |
 | [stricture](/meadow/stricture/) | MicroDDL schema definition and code generation |
+| [foxhound](/meadow/foxhound/) | Fluent query DSL with multi-dialect SQL generation |
+| [bibliograph](/meadow/bibliograph/) | Record-level change tracking |
+| [meadow](/meadow/meadow/) | Provider-agnostic data broker and ORM |
+| [parime](/meadow/parime/) | Data lake behaviors |
 | [meadow-endpoints](/meadow/meadow-endpoints/) | Automatic RESTful CRUD endpoint generation |
 | [meadow-connection-mysql](/meadow/meadow-connection-mysql/) | MySQL connection provider |
 | [meadow-connection-mssql](/meadow/meadow-connection-mssql/) | MSSQL connection provider |
 | [meadow-connection-sqlite](/meadow/meadow-connection-sqlite/) | SQLite connection provider |
 | [retold-data-service](/meadow/retold-data-service/) | All-in-one schema-to-REST-API service |
 | [retold-harness](/meadow/retold-harness/) | Demo API harness with bookstore dataset |
-| [bibliograph](/meadow/bibliograph/) | Record-level change tracking |
-| [parime](/meadow/parime/) | Data lake behaviors |
 | [meadow-integration](/meadow/meadow-integration/) | Data integration and CSV import |
-| [meadow-graph-client](/meadow/meadow-graph-client/) | Relational graph record fetching |

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

@@ -162,3 +162,4 @@ This gives you a full REST API with Create, Read, Reads, Update, Delete, Undelet
 | [orator-http-proxy](/orator/orator-http-proxy/) | HTTP reverse proxy pass-through |
 | [tidings](/orator/tidings/) | Reporting scaffolding for HTML/PDF output |
 | [orator-endpoint](/orator/orator-endpoint/) | Reusable endpoint base class |
+| [orator-conversion](/orator/orator-conversion/) | File format conversion endpoints |

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

@@ -6,6 +6,8 @@ Pict provides a non-opinionated set of Model-View-Controller tools for building
 
 Pict does not impose opinions about what MVC means. It provides discrete tools — Views, Templates, Providers, and an Application class — that you can use individually or compose together.
 
+*Pict is a subclass of Fable*, so does everything fable does.
+
 - **Views** manage lifecycle (initialize, render, marshal data) and render templates into target containers
 - **Templates** are text with expressions that resolve against application state
 - **Providers** fetch and manage data for views
@@ -177,10 +179,25 @@ Toast UI Grid integration for tabular data display. Provides spreadsheet-like da
 
 ### [Pict-Section-Content](/pict/pict-section-content/)
 
-Content display sections for rendering static or dynamic content blocks.
+Markdown parsing and content rendering with Mermaid diagrams and KaTeX math equations. Provides a reusable provider for markdown-to-HTML conversion and a styled view with post-render hooks.
 
 **npm:** `pict-section-content`
 
+---
+
+### [Pict-Section-Flow](/pict/pict-section-flow/)
+
+Flow diagram section for visual workflow and process representations.
+
+**npm:** `pict-section-flow`
+
+## Application Modules
+
+| Module | Purpose | npm |
+|--------|---------|-----|
+| [pict-docuserve](/pict/pict-docuserve/) | Single-page documentation viewer built on Pict with catalog navigation and search | `pict-docuserve` |
+| [pict-nonlinearconfig](/pict/pict-nonlinearconfig/) | Nonlinear configuration manager | `pict-nonlinearconfig` |
+
 ## Supporting Modules
 
 | Module | Purpose | npm |
@@ -191,23 +208,28 @@ Content display sections for rendering static or dynamic content blocks.
 | [cryptbrau](/pict/cryptbrau/) | Simple in-browser symmetric encryption | `cryptbrau` |
 | [pict-serviceproviderbase](/pict/pict-serviceproviderbase/) | Base classes for Pict services with pre-initialization support | `pict-serviceproviderbase` |
 | [pict-service-commandlineutility](/pict/pict-service-commandlineutility/) | CLI utility tools built on Commander | `pict-service-commandlineutility` |
+| [pict-terminalui](/pict/pict-terminalui/) | Blessed-based terminal interface for Pict views | `pict-terminalui` |
 
 ## All Pict Modules
 
 | Module | Description |
 |--------|-------------|
 | [pict](/pict/pict/) | Core MVC module with template engine |
-| [pict-view](/pict/pict-view/) | View base class with full lifecycle |
 | [pict-template](/pict/pict-template/) | Custom template handler base class |
+| [pict-view](/pict/pict-view/) | View base class with full lifecycle |
 | [pict-provider](/pict/pict-provider/) | Data provider base class |
 | [pict-application](/pict/pict-application/) | Application lifecycle management |
-| [pict-section-form](/pict/pict-section-form/) | Configuration-driven dynamic forms |
+| [pict-panel](/pict/pict-panel/) | Hot-loadable control panel |
+| [pict-nonlinearconfig](/pict/pict-nonlinearconfig/) | Nonlinear configuration manager |
+| [pict-section-flow](/pict/pict-section-flow/) | Flow diagram section |
+| [pict-docuserve](/pict/pict-docuserve/) | Single-page documentation viewer |
+| [cryptbrau](/pict/cryptbrau/) | In-browser symmetric encryption |
+| [informary](/pict/informary/) | Browser form marshaling with undo/redo |
+| [pict-service-commandlineutility](/pict/pict-service-commandlineutility/) | CLI utility tools |
 | [pict-section-recordset](/pict/pict-section-recordset/) | CRUD record management views |
+| [pict-section-content](/pict/pict-section-content/) | Markdown parsing and content rendering |
+| [pict-section-form](/pict/pict-section-form/) | Configuration-driven dynamic forms |
 | [pict-section-tuigrid](/pict/pict-section-tuigrid/) | Toast UI Grid tabular data |
-| [pict-section-content](/pict/pict-section-content/) | Content display sections |
-| [pict-panel](/pict/pict-panel/) | Hot-loadable control panel |
 | [pict-router](/pict/pict-router/) | Hash-based URL routing |
-| [informary](/pict/informary/) | Browser form marshaling with undo/redo |
-| [cryptbrau](/pict/cryptbrau/) | In-browser symmetric encryption |
 | [pict-serviceproviderbase](/pict/pict-serviceproviderbase/) | Pict service base classes |
-| [pict-service-commandlineutility](/pict/pict-service-commandlineutility/) | CLI utility tools |
+| [pict-terminalui](/pict/pict-terminalui/) | Blessed-based terminal interface |

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

@@ -38,14 +38,6 @@ npx quack coverage       # Generate coverage report
 
 ---
 
-### [Choreographic](/utility/choreographic/)
-
-Scaffolding for single-run data processing scripts. Provides pre-packaged application services — file reading/writing, logging, and organized output folders — for tasks like data migration, report generation, and batch processing.
-
-**npm:** `choreographic` · **Version:** 1.0.x
-
----
-
 ### [Ultravisor](/utility/ultravisor/)
 
 Process supervision tool for running commands on schedule with LLM integration. Supports distributed nodes, global state, and flexible task types (shell, browser, HTTP, database).
@@ -59,5 +51,4 @@ Process supervision tool for running commands on schedule with LLM integration.
 | [indoctrinate](/utility/indoctrinate/) | Documentation scaffolding with content cataloging and cross-module search |
 | [manyfest](/utility/manyfest/) | JSON manifest for data description, validation, and address-based access |
 | [quackage](/utility/quackage/) | Build tool for browser bundles, testing, and packaging |
-| [choreographic](/utility/choreographic/) | Scaffolding for single-run data processing scripts |
 | [ultravisor](/utility/ultravisor/) | Process supervision with scheduled tasks and LLM integration |