Four builds, and what they do not prove

The draft is the product, not the post

The flow ends at an editable draft the writer still owns. Generation does not publish, and the wording stays the writer's responsibility — which is why editing is part of the documented flow rather than an afterthought.

Voice and persona are an explicit choice

Choosing a voice, persona or style sits next to the topic input instead of hiding in a settings page. The person sees what shaped the draft and can change it before anything is kept.

Drafting and scheduling are separate steps

Scheduling is part of the public feature description, but it comes after review. A draft that still needs a human read is not something that should be able to publish itself.

The source view sits beside the answer

A generated response is read next to a source or document view rather than behind a link. Keeping the material in view is the difference between a claim you can check and one you can only take on trust.

Citations point at a page or section

A citation that only names a document is decoration. Citing a page or section gives a reader somewhere specific to go, which is what makes inspection practical.

Documents are added deliberately

The person asking chooses which documents or PDFs the system works from. That keeps the scope of what can be answered visible and deliberate.

A timeline you can see, not only a config file

Visual timeline editing is part of the documented scope, so the sequence being rendered is inspectable in the tool rather than only in code. That is what makes a frame range reviewable.

Determinism before throughput

The engineering focus is deterministic output at a known frame and time. Browser, font, codec, resolution and long-composition behaviour are treated as validation work — the parts that decide whether a render matches the previous run.

Two output paths, one authoring model

The documented scope pairs a WebCodecs video export with an HTML-native HyperFrame path. Same scene description, different destination, which keeps the authoring work independent of the export path.

Retrieval is the product, not the capture

The clipboard history is easy to write and hard to make useful. Getting an older clip back by ID, searching parameterised queries, pinning and keyboard selection are what turn a log into a tool.

The database lives where the platform expects it

Using the platform app-data directory for the database path avoids writing into a location the OS or user may later treat as disposable.

A global shortcut must not be able to crash the app

Shortcut collisions are handled rather than assumed away, and async listeners are cleaned up — the two places a desktop utility of this kind most easily leaves a stale handler behind.