Source-grounded screenwriting / Working Mac application
In active private use / Private demonstrations
The hard part starts before the blank page.
Chronos is a writing environment built for the path from long-form prose to screenplay. It helps a writer recover the dramatic material, resolve a sprawling cast, and carry source decisions into the script without surrendering creative control.
I built Chronos while adapting The Bostonians. Existing screenwriting software gave me a blank page. Analysis software gave me extracted data. Neither carried the living relationship between the book and the screenplay.
01 / The product opportunity
Screenwriting software begins too late.
A novel arrives with hundreds of pages, shifting names, dialogue buried inside narration, events separated by chapters, and characters who may need to be combined or removed. Before the screenplay can work, the writer has to recover and reorganize an entire dramatic system.
Research binders can sit beside the script. Text-analysis tools can produce information about the book. Screenplay applications format the page after many of the hardest choices have already been made. Chronos makes the movement between source and screenplay the product.
02 / The working product
Bring in the source. Leave with a screenplay.
Chronos is already a working application in active private use. It carries one adaptation through four connected kinds of work.
Recover
Find the dramatic material.
Chronos surfaces structure, dialogue, possible identities, and possible speakers from the source for review.
Decide
Make uncertainty explicit.
The writer confirms, corrects, rejects, reclassifies, combines, or leaves a question unresolved.
Write
Let the adaptation become its own work.
Source material stays available as evidence while invented action, changed roles, and the developing screenplay acquire their own authority.
Carry forward
Keep the work portable.
Chronos exports Fountain text so the screenplay can continue into the established screenwriting and production workflow.
03 / Product boundary
No ML agents. No generated adaptation. The writer writes.
Chronos does not use machine-learning agents. It is not agentic or generative software. Its local, bounded analysis can surface structure, dialogue, identities, and uncertainty for review. It does not plan scenes, rewrite the source, or decide what belongs in the screenplay.
The writer accepts, corrects, rejects, cuts, combines, invents, and writes. Human creative authority is not a preference layered over the product. It is the product boundary.
That boundary is commercially useful. Writers, rights holders, educators, and producers need work they can inspect, explain, own, and carry forward without wondering whether a hidden agent became the author.
04 / Proof at book scale
A clean chapter makes a demo. A difficult book makes a product.
Chronos was built under the pressure of a complete adaptation, not around a polished sample passage.
- 42
- source chapters
- 38
- scenes in the July 2026 working screenplay
- One
- writer-directed path from book to script
Henry James supplied dense narration, unstable naming, indirect speech, distant passages that wanted to occupy the same scene, and a cast the screenplay had to reshape. The Bostonians kept exposing difficult cases until Chronos had to hold them.
Chronos did not write the adaptation. I did. The product earned its place by keeping the whole source, the accumulating decisions, and the screenplay close enough to work as one creative problem.
See how The Bostonians shaped Chronos05 / The commercial opening
The wedge is narrow on purpose.
Chronos enters through one expensive, underserved job: adapting a long source work without losing the source or the writer inside the process.
Initial market
Writers with a real book to adapt.
Independent screenwriters, playwrights, and writer-directors working from public-domain or otherwise lawful prose feel the problem directly and choose their own tools.
Position
Own the adaptation, not every production task.
Chronos does not need to replace mature screenplay applications. It can own the source-to-script work and hand a portable screenplay into the tools writers and production teams already trust.
Commercial path
Begin close to the customer.
Private walkthroughs and supported pilots can validate the workflow, willingness to pay, and professional Mac product before broad release.
Expansion
The same problem appears in adjacent rooms.
Stage adaptation, dramatic-writing education, dramaturgy, and rights-controlled development are credible directions to test, not capabilities or revenue claimed here today.
06 / Durable advantage
The advantage accumulates book by book.
The differentiator is not one clever rule for finding quotations. Real books produce shifting names, uncertain speakers, combined roles, broken passages, long-distance relationships, and work that must still make sense when the writer returns months later.
Each hard case adds product knowledge: what can be suggested, what must remain uncertain, what a writer needs to see, and what must survive a change. Chronos has been shaped by a founder using it to finish the work it was built to support. That accumulated behavior is much harder to reproduce than a feature list.
Local project ownership and portable export also lower adoption risk. Trust is part of the product, not a privacy footnote.
08 / Ways in
Bring a real question.
Chronos has no public download, announced price, or release date on this site. I am open to focused conversations with writers bringing an adaptation problem, partners who understand the category, educators or production organizations considering a pilot, and investors interested in specialized professional software.