Native Studio
Native Studio is Bookcicle's installed writing workspace for macOS and Windows. It combines a long-form editor with project search, comments, collaboration, history, authorship, and local-first proof tools.
It is the best choice when you want to spend substantial time inside the manuscript, continue drafting when offline, or keep stronger evidence about how changes entered the editor.
Who Native Studio is for
Native Studio works well for:
- authors drafting novels, nonfiction, or screenplays
- editors reviewing sections and leaving comments
- co-writers collaborating on the same project
- authors who want Writing Coach and reviewable AI edits
- anyone who wants local history and portable proof capsules
The workspace
The workspace is organized around:
- Files, for the manuscript, sections, notes, and supporting project material
- Editor tabs, for the manuscript or an individual section
- Split panes, for viewing more than one file or section at once
- Drawers, for tools such as History, Comments, and Collaboration
- Writing Coach, which can stay docked or open in its own window
- Status information, including save, collaboration, authorship, and background activity
The full manuscript preserves the project order. A focused section tab lets you work on one chapter or scene without losing its place in the larger draft.
A good daily writing workflow
- Open the project and select the manuscript or section you want to work on.
- Draft normally. Studio saves changes and creates history checkpoints according to your settings.
- Use comments for questions that should be discussed before the text changes.
- Use local or project search to check names, details, repeated phrases, and continuity.
- Ask Writing Coach for analysis when you want guidance rather than a direct rewrite.
- Use an AI editing action when you want a proposed textual change.
- Review every AI change before accepting it.
- Create a milestone or proof capsule before a handoff or major rewrite.
Search and replace
Native Studio has two levels of search.
Search the open section
Use local search when you know the text is in the section you are editing.
- macOS:
Command–F - Windows:
Ctrl–F
Local replace is:
- macOS:
Command–R - Windows:
Ctrl–R
You can move through matches, replace the current match, or replace all matches in the open section.
Search the whole project
Use project search when you need to find a name, phrase, comment, storyboard item, or earlier Writing Coach discussion across the project.
- macOS:
Command–Shift–F - Windows:
Ctrl–Shift–F
Project replace is:
- macOS:
Command–Shift–R - Windows:
Ctrl–Shift–R
Opening a result takes you to the matching section and passage. Review project-wide replacements carefully, especially for character names and phrases that may have more than one meaning.
History and restoring work
History records meaningful states of each section. Use it to answer:
- What changed?
- When did it change?
- Which text was retained from an earlier version?
- Is authorship evidence available for this version?
- Does this version have a local proof, receipt, or proof capsule?
Compare a version
Open a history item to compare it with the current section. The comparison can show inserted, removed, and retained text. When compatible authorship evidence exists, retained text can also be summarized by Human, AI, Collaborator, Imported/Pasted, and Unknown origin.
Restore a version
Restore creates a new transition back to the selected content state. It does not erase the later history. Authorship from the restored version is preserved where it can be verified, while the person performing the restore is recorded separately.
Why some versions say “Authorship unavailable”
Older, imported, or partially synchronized versions may have valid content history without a compatible authorship checkpoint. Studio keeps those claims separate: missing authorship evidence does not make the content history false.
Comments
Use comments when you want discussion without immediately changing the manuscript.
Typical uses include:
- asking an editor whether a passage is clear
- leaving a continuity reminder for yourself
- requesting a source check
- proposing a change for a co-writer
- attaching Writing Coach observations for later review
Select the relevant text and choose Add Comment. Replies remain in the thread. Resolve the thread when the question is settled.
A comment is not a content edit. Adding, replying to, or resolving a comment does not make the commenter the author of the passage.
If the underlying section changes after a comment or AI proposal was prepared, Studio may ask you to review it again rather than applying stale advice to new text.
Collaboration
The Collaboration drawer lets a project owner start or manage a live session and invite other people. During a session you can see connection state and participant information.
Keep these behaviors in mind:
- a participant's edit is attributed to that participant when their identity is available
- the session host is not automatically treated as the author of everybody's edits
- an unidentified remote contribution remains an Unknown collaborator contribution
- temporary disconnection can move the session into offline or reconnecting state
- expired or ended sessions require a new invitation
Before a major collaboration session, create a named version or proof checkpoint. This gives everyone a clear starting point and makes later comparison easier.
Writing Coach
Writing Coach is available in Native Studio for eligible plans and requires an internet connection.
Use Writing Coach when you want analysis, questions, or guidance grounded in the project. It can help with areas such as:
- character motivation and consistency
- pacing and scene purpose
- continuity across sections
- structure and outline questions
- finding relevant passages or storyboard context
- preparing proposed comments or edits for your review
Writing Coach keeps conversations in sessions. You can return to earlier sessions, search them, start a new session, dock the coach beside the manuscript, or open it in a separate window.
Coach advice versus manuscript changes
A Coach answer does not change the manuscript. If the Coach offers an edit or comments, Studio asks for confirmation before applying them. This keeps discussion separate from accepted content.
When you confirm a proposed edit:
- AI-created replacement text remains AI-authored
- your confirmation is recorded as a Human review decision
- text you subsequently rewrite yourself becomes Human-authored for the replaced spans
Native AI editing
Native Studio offers reviewable AI actions from the editor. Depending on whether text is selected, an action applies to the selection or the current section.
Available actions include:
- Proofread for spelling, grammar, and mechanical corrections
- Copy Edit for clarity, consistency, and sentence-level polish
- Line Edit for voice, rhythm, flow, and style
- Rewrite for a more substantial alternative
- Ask Writing Coach when you want discussion instead of an immediate edit proposal
AI editing requires an internet connection and an eligible plan.
Review before accepting
An AI edit is prepared against a specific section revision. Review the proposed changes and policy warnings before accepting them. If the section changed while the proposal was being prepared, refresh the proposal instead of applying a stale edit.
Accepting an AI edit does not convert it into Human-authored text. Studio records AI as the origin of the accepted replacement and records you as the reviewer. Rejecting it contributes no text. Manually changing it later creates Human authorship only for the spans you replace.
Authorship and input evidence
Native Studio records two related but separate things:
- Token authorship: who or what originated the text that remains.
- Input evidence: where and how the change entered Studio.
This prevents misleading claims. For example, Studio can know that you performed a paste without claiming that you wrote the pasted paragraph.
Native action-to-authorship map
| Action | Authorship consequence | Recorded input evidence | What a proof can say |
|---|---|---|---|
| Type with keyboard or IME | New/replaced text → current Human author | native · keyboard · human_asserted | Human input in Native Studio; no injection evidence was observed |
| Use in-app speech-to-text | New/replaced text → current Human author | native · speech · human_asserted | Human speech input in Native Studio |
| Use Voice Control or assistive input | New/replaced text → current Human author | native · accessibility · human_asserted | Human accessibility input; assistive technology is not treated as AI |
| Paste text | New/replaced text → Pasted/Unknown | native · paste · unverified | The user performed a paste; original token author is not claimed |
| Native OS reports injected input | New/replaced text → Unknown | native · unknown · suspected_automation | Probabilistic native injection evidence was observed |
| Screen sharing, recording, or Accessibility permission alone | No authorship consequence | No input event | Permission or an indicator alone is not automation evidence |
| Accept an AI proposal | New/replaced text → AI; unchanged text keeps its prior origin | native · ai · unverified plus Human review | AI originated the accepted text; the Human reviewer approved it |
| Reject an AI proposal | No accepted-content change | Optional review audit | Rejected text did not enter the manuscript |
| Rewrite AI text manually | Retained spans stay AI; your replacement spans become Human | Current Human input evidence | Mixed AI and Human authorship at the token level |
| Receive an identified collaborator edit | New/replaced text → originating Human collaborator | native · remote · unverified | Privacy-safe collaborator attribution |
| Receive an unidentified collaborator edit | New/replaced text → Unknown collaborator | native · remote · unverified | Remote contribution with unavailable identity |
| Delete text | Deleted tokens and their author runs are removed | Current input modality and trust | Who performed the deletion; remaining text keeps its origin |
| Format without changing canonical text | Author map unchanged | Optional system operation | No new content-authorship claim |
| Save with no content change | Author map unchanged | No new event; deduplicated | Existing evidence remains current |
| Restore an earlier version | Restore that version's verified author map | Restore transition | Which version returned and who performed the restore |
| Sync with valid provenance | Preserve incoming authorship | Verified sync evidence | Original authorship survives the transfer |
| Sync without provenance | Incoming content → Unknown/Remote | external · sync · unverified | Content arrived remotely; author is unavailable |
| Import without valid authorship proof | Imported content → Unknown | external · unknown · unverified | The importer is known separately from the original author |
| Import with valid authorship proof | Preserve verified authorship | Verified import evidence | Portable authorship survives import |
| Open, read, navigate, or preview | No authorship consequence | None | Viewing is not authorship or approval |
Native automation detection is deliberately conservative. macOS and Windows provide different low-level input signals, and Bookcicle treats either as suspicion—not proof. Process identity, keystrokes, text, and window metadata are not retained for this signal.
Notary and proof capsules
History and Notary work together around exact content states.
From a meaningful history snapshot you can:
- inspect its local proof status
- add a Bookcicle cloud attest when available
- compare proof metadata with the content
- open or save a
.bkclpproof capsule - verify a capsule later
A proof capsule may contain a content proof and a separate authorship statement. Verification reports them independently. This matters for older or imported drafts: the exact content can verify even if some authorship is Unknown or unavailable.
Create proof capsules at moments that matter, such as:
- before sending a draft to an editor
- after completing a revision pass
- before and after a collaboration session
- at submission or delivery
- before a substantial AI-assisted rewrite
For file and folder watchers, automatic attest, and the persistent Notary agent, see Notary in Bookcicle Desktop.
Working offline
You can continue local drafting when disconnected. Local saves, local history, and local project tools remain available. Cloud collaboration, cloud synchronization, Writing Coach, AI editing, and cloud attest require connectivity.
If a cloud action fails, keep writing and retry it after reconnecting. An unavailable optional authorship or cloud service should not block saving the manuscript.
Practical safeguards
- Create a named version before large replacements or AI edit passes.
- Read every AI change in context before accepting it.
- Use comments when you want discussion rather than immediate modification.
- Treat Unknown authorship honestly instead of assigning it to the nearest user.
- Export a proof capsule for important handoffs.
- Keep the app updated so authorship and verification readers understand the latest evidence format.