Consolidate same-day Thinkloom devlog entries

2026-08-12 09:11:05 -07:00
parent df66bc5b9d
commit e9f94064bd
4 changed files with 33 additions and 113 deletions
@@ -1,33 +0,0 @@
 _model: devlog-entry
 ---
 schema_version: 1
 ---
 title: Preparing the Build Week submission
 ---
 date: 2026-07-17
 ---
 author: Christopher Chambers
 ---
 summary: The project was packaged with its demo, judging guide, license, collaboration record, and release-oriented documentation.
 ---
 tags: OpenAI Build Week, release, documentation
 ---
 source_commit: 9c2ab17c2508f181ad7adee635cc4d21b37aa2b6
 ---
 body:
 Preparing Thinkloom for OpenAI Build Week required more than producing a working
 binary. The submission needed to explain the problem, demonstrate the product
 without relying on private context, and document how Christopher and Codex
 collaborated during the build.
 This milestone added the submission narrative, a repeatable demo script,
 testing guidance for judges, and the AGPL-3.0 license. It also separated claims
 that could be demonstrated from release gates that still required external
 assets or owner decisions, such as code signing and bundled voice models.
 That distinction remains important to the project: completed functionality is
 documented plainly, while unfinished conformance or distribution work is not
 presented as done.
 [View the submission commit](https://git.labyricorn.com/Labyricorn/thinkloom-openai-hackathon/commit/9c2ab17c2508f181ad7adee635cc4d21b37aa2b6)
@@ -1,31 +0,0 @@
 _model: devlog-entry
 ---
 schema_version: 1
 ---
 title: Making model prompts configurable
 ---
 date: 2026-07-17
 ---
 author: Christopher Chambers
 ---
 summary: Conversation and drafting prompts moved into documented, user-editable JSON files that reload without rebuilding the application.
 ---
 tags: prompts, models, configuration, user-control
 ---
 source_commit: 58e5510445d7ab403d8df0792c29743a933531e0
 ---
 body:
 Thinkloom's model behavior should not be a hidden, immutable part of the
 application. Conversation and drafting prompts were moved into structured JSON
 templates and documented as part of the project configuration.
 The application creates user-owned copies and reloads them before each request,
 so a technical writer can adjust instructions without rebuilding or restarting
 Thinkloom. Validation happens before a request is sent: invalid JSON or missing
 template variables produce a recoverable error and leave the writing unchanged.
 This work reinforced two of the project's recurring principles—model behavior
 should be inspectable, and failure should not silently alter a manuscript.
 [View the configurable-prompts commit](https://git.labyricorn.com/Labyricorn/thinkloom-openai-hackathon/commit/58e5510445d7ab403d8df0792c29743a933531e0)
@@ -2,32 +2,49 @@ _model: devlog-entry
 ---
 schema_version: 1
 ---
-title: Building the native desktop MVP
+title: Building and preparing the Thinkloom desktop MVP
 ---
 date: 2026-07-17
 ---
 author: Christopher Chambers
 ---
-summary: The workspace became a Tauri desktop application with a React interface, Rust service layer, local persistence, provenance, exports, and recovery behavior.
+summary: On one build day, Thinkloom became a native desktop MVP, clarified its local-first boundary, made prompts configurable, and was prepared for Build Week review.
 ---
-tags: Tauri, React, Rust, MVP
+tags: Tauri, React, Rust, MVP, architecture, local-first, privacy, prompts, models, configuration, user-control, OpenAI Build Week, release, documentation
 ---
-source_commit: b5e6eafa1c4e9b787250c15e6453c2d61dc8830c
+source_commit: 9c2ab17c2508f181ad7adee635cc4d21b37aa2b6
 ---
 body:
-The first desktop MVP moved Thinkloom from the workspace framework into a Tauri
+The July 17 build brought together the milestones that turned Thinkloom from a
-2 application. React and TypeScript provided the interaction surface, while the
+writing-workspace framework into a reviewable native product.
 Rust service layer took responsibility for local persistence and native
 operations.
-This milestone connected the main workflow end to end: project state, idea
+First, Thinkloom became a Tauri 2 desktop application. React and TypeScript
-curation, drafting, version history, provider boundaries, exports, backups, and
+provided the interaction surface while the Rust service layer took responsibility
-an inspectable provenance trail. SQLite held live state while canonical files
+for local persistence and native operations. The main workflow connected project
-and hidden Git checkpoints provided durable, reviewable recovery points.
+state, idea curation, drafting, version history, provider boundaries, exports,
 backups, and an inspectable provenance trail. SQLite held live state while
 canonical files and hidden Git checkpoints provided durable, reviewable recovery
 points.
-The goal was not merely to wrap a web interface in a desktop shell. The native
+The product boundary was then narrowed deliberately. Hosted and browser-facing
-boundary made local files, operating-system credentials, atomic writes, and
+scaffolding were removed so Tauri became the sole application target. That made
-offline ownership part of the product itself.
+the local-first promise concrete: manuscripts, project state, and credentials
 belong on the writer's machine.
-[View the MVP commit](https://git.labyricorn.com/Labyricorn/thinkloom-openai-hackathon/commit/b5e6eafa1c4e9b787250c15e6453c2d61dc8830c)
+Model prompts also moved into documented, user-editable JSON templates. The
 application creates user-owned copies and reloads them before each request, with
 validation that leaves writing unchanged when configuration is invalid. That
 keeps model behavior inspectable rather than hidden in the application.
 Finally, the project was prepared for Build Week with its demo, judging guide,
 license, collaboration record, and release-oriented documentation. The
 submission materials separate completed functionality from distribution work
 that still needs external assets or owner decisions.
 Related milestones:
 - [Build the desktop MVP](https://git.labyricorn.com/Labyricorn/thinkloom-openai-hackathon/commit/b5e6eafa1c4e9b787250c15e6453c2d61dc8830c)
 - [Choose the native-only boundary](https://git.labyricorn.com/Labyricorn/thinkloom-openai-hackathon/commit/7866081c7882f8c59d137b126a6fe0278eda87df)
 - [Make model prompts configurable](https://git.labyricorn.com/Labyricorn/thinkloom-openai-hackathon/commit/58e5510445d7ab403d8df0792c29743a933531e0)
 - [Prepare the Build Week submission](https://git.labyricorn.com/Labyricorn/thinkloom-openai-hackathon/commit/9c2ab17c2508f181ad7adee635cc4d21b37aa2b6)
@@ -1,33 +0,0 @@
 _model: devlog-entry
 ---
 schema_version: 1
 ---
 title: Choosing a native-only product boundary
 ---
 date: 2026-07-17
 ---
 author: Christopher Chambers
 ---
 summary: Thinkloom removed its hosted and browser-companion paths so the implementation matched its local-first product promise.
 ---
 tags: architecture, local-first, privacy
 ---
 source_commit: 7866081c7882f8c59d137b126a6fe0278eda87df
 ---
 body:
 During implementation, Thinkloom briefly contained hosted and browser-facing
 scaffolding alongside the desktop application. That created a mismatch with the
 product being described: a native, local-first writing studio with no required
 account or hosted companion.
 The project removed the Sites, Next, worker, and browser-companion paths and
 made Tauri the sole application target. This reduced the deployment surface and
 made the privacy boundary easier to understand: manuscripts, project state, and
 credentials belong on the writer's machine.
 The change was as much a product decision as a technical cleanup. A smaller,
 clearer architecture made it possible to state honestly what Thinkloom was—and
 what it deliberately was not.
 [View the native-only commit](https://git.labyricorn.com/Labyricorn/thinkloom-openai-hackathon/commit/7866081c7882f8c59d137b126a6fe0278eda87df)