Where Inklyne is going, told straight: a Prima Lectio reading that has come of age, a manuscript workspace built to hold a whole book, a story bible, a training ground we are still building toward, and a way to show how your text was written.
The challenge. Getting a structured read on a whole manuscript is rare. Friends are too kind, strangers are too harsh, and a deep workshop pass is slow and scarce.
Our approach. Prima Lectio reads the manuscript chapter by chapter from five angles of analysis (core, structure, scenes, characters, style) and quotes the writer's own text for every remark it makes. It never writes a line for you; it reflects on what is already on the page.
The challenge. A verdict is only useful if it is judged against the right bar, and against a piece that is actually meant to be finished.
Our approach. The writer sets the rigor rung the work is read at, from novice to grandmaster, and declares whether a piece is a finished whole or still in progress, so the reading never judges an ending that has not been written yet.
The challenge. A pile of remarks from one reading is easy to lose. Writers need their own running list of what to fix, not a report that resets every time.
Our approach. Every remark becomes an item on a worklist that survives across readings. The writer adds their own items, dismisses what they disagree with, and a dismissed point does not resurface uninvited.
The challenge. Essays are not judged like scenes. A reading built for fiction's core-structure-scenes-characters-style frame misreads an argument.
Our approach. Essay and micro-essay pieces are read on their own criteria (argument, evidence, concession) instead of being forced through the fiction angles of analysis.
The challenge. The same text needs different modes at different times: exploratory drafting, focused editing, assembly, refinement. A tool that only does one of them gets in the way of the others.
Our approach. A fragment-based editor with autosave on every keystroke, an append-only core to protect writing history, a focus mode for drafting, and paragraph locking to freeze passages you consider settled.
The challenge. Annotations, intentions, the story bible, and version history usually live in separate places a writer has to hunt across while editing.
Our approach. One rail beside the text holds all of it (annotations, the exercise's intentions, the story bible, and version history), so none of it interrupts the writing itself.
The challenge. Losing pages to a bad edit or a client crash is the one failure a writing tool cannot excuse.
Our approach. Every piece keeps its version history, and restoring an earlier version is one click in the Margins. Ending a writing session writes a durable snapshot of everything touched, on top of which encrypted database backups run offsite.
The challenge. A writer's text belongs to the writer, not to whichever app it started in.
Our approach. Bring drafts in from Markdown, plain text, DOCX, ODT, Obsidian archives, or multiple files at once. Take your writing out as Markdown, DOCX, ODT, EPUB, PDF, or a full account export. Nothing is held hostage.
The challenge. Writers often want to study a text they did not write (a classic, a public-domain source) inside the same tools they use for their own manuscript, without confusing the two.
Our approach. A project can hold a text you did not author, with its provenance displayed: original author, translator and year, edition, legal basis. The writing surfaces disappear, and the text never counts toward your own writing record or writer profile. It is there to be read and studied, not written.
The challenge. Keeping track of every character, place, event, and object across a long manuscript, and which of them actually matter, is easy to lose as a project grows.
Our approach. Characters, places, events, and objects each get their own notes and an importance ranking. Mentions in the text are detected automatically and confirmed one by one or in bulk, so the bible stays accurate without manual bookkeeping.
The challenge. Who is tied to whom, and how, gets hard to hold in your head once a cast grows past a handful of names.
Our approach. A readable graph maps every relationship between entities, so the shape of a cast or a network of places is visible at a glance instead of scattered across notes.
The challenge. Story time rarely matches calendar time, and keeping events in the right order, independent of when they were written, is its own kind of bookkeeping.
Our approach. Events are placed on a story timeline that runs on narrative order, not calendar dates, so sequence and continuity stay visible without recomputing them by hand.
The challenge. Typing an entire story bible in by hand, especially for a manuscript that already exists, is a chore most writers skip.
Our approach. Claude, once connected to Inklyne, can derive and refresh the Matière directly from the manuscript's prose, so the bible builds itself from what is already written instead of demanding a second pass of data entry.
The challenge. Deliberate practice needs structure (a brief, a clear intention, and a way to know whether a piece of writing met it) that an open blank page does not provide on its own.
Our approach. A guided track advances in staged movements. Each movement opens with an explicit brief, intentions contracted before writing begins, a verdict against each intention once it is done, and a seal that closes the movement.
The challenge. Classical tale structures are a proven way to practice craft, but most writers have never had a system that walks them through one movement at a time.
Our approach. The Tale Machine is the first track built this way in full: a sequence of classical tale models worked movement by movement, with the writer's own story or a provided scenario as the material. It is the track getting the most attention right now.
The challenge. An exercise without feedback teaches nothing, and a gate that can never be crossed sends the wrong signal about what the exercise is for.
Our approach. Claude returns a verdict against every intention set for the movement. The gate that follows is advisory: the writer can always continue past it and keep writing.
The challenge. Tracking real craft progress over time, across dimensions like structure or dialogue, needs more memory than any single reading can hold, and it should never turn into a score someone else can see.
Our approach. The writer profile tracks standing and trend per craft dimension, built entirely from real verdicts earned in the Atelier. It stays private to the writer: a mirror for their own use, never a public credential or a score anyone else sees.
The challenge. Short, self-paced practice between full exercises is worth having, but it is not where the product's attention belongs while the tracks themselves are still being built out.
Our approach. A bank of short, self-paced drills is already in place and working. It stays in the background while the Atelier's tracks are built out.
The challenge. Sharing unfinished work needs trust and structure: readers need a stable version to read, the writer needs to control what is shown, and feedback needs to land somewhere useful.
Our approach. Share a frozen snapshot of a manuscript, exclude specific pieces from the share, and collect comments anchored to the exact passage they refer to, alongside chapter-level and whole-manuscript feedback.
The challenge. Writing groups provide energy and accountability, but coordinating them by hand (invitations, roles, review rounds) creates enough friction to kill most of them.
Our approach. Small, invitation-only circles run structured review rounds: real submissions, structured peer feedback, and a rhythm the group keeps without a coordinator chasing anyone.
The challenge. Motivation fades between sessions, and writing alone for long stretches needs some visible signal that the practice is holding, without turning it into a scoreboard.
Our approach. Writing sessions, weekly practice streaks, badges, personal commitments, and a weekly digest of the week's work give a quiet rhythm to the practice. Never a points game, just the visible shape of showing up.
The challenge. A writing platform's social layer either feels performative long before there is anyone worth following, or stays absent when a writer finally wants an audience for their practice.
Our approach. Follow other writers, publish your sessions and support theirs. Every post in the feed is a real writing session, never a free-floating post.
The challenge. Anyone can claim they wrote a manuscript by hand; almost nothing can show how it was actually produced.
Our approach. The Writing Journey report reconstructs how a piece was actually written: sessions over time, words typed versus pasted, and per-paragraph provenance (written here, imported, or AI-sourced).
The challenge. A Writing Journey report is a summary; some writers want a stronger, binding link between specific spans of text and the sessions that produced them.
Our approach. An opt-in mode will bind spans of a manuscript directly to the writing sessions that produced them, turning the journey record into a durable attribute of the text itself.
The challenge. A writer who wants to show, publicly and checkably, that a manuscript is their own has no standard way to do that today.
Our approach. A signed, publicly checkable certificate will attest to the writing process Inklyne observed for a writer who opted in. It never judges someone else's finished text and is not an AI detector. It offers strong evidence of authorship, never proof.
Upload your manuscript and get your first Prima Lectio reading, chapter by chapter. The first 7 days are free, and you can extend that to 21 by completing onboarding.