Web Studio
Web Studio is Bookcicle's browser-based writing and review workspace. It lets you open a project without installing the desktop application and is especially useful for quick edits, shared review, and collaboration.
Web Studio records that a change came through the Web surface. It can anchor that edit into authorship and history, but a browser cannot reliably prove whether ordinary-looking keyboard input came from a physical keyboard or an outside screen-control application.
Who Web Studio is for
Web Studio works well for:
- authors moving between computers
- editors or co-writers joining a shared project
- reviewers who need comments and history without installing an app
- authors making quick changes from the browser
- people creating or inspecting browser-based proof records
For long offline writing sessions, native AI editing, Writing Coach, or stronger device-level input evidence, use Native Studio.
Opening a project
Open a project from Projects & Tasks, then choose the Studio or editor action available for that project. Access depends on your account, project role, and whether an invitation has been accepted.
Inside Web Studio you work with the same basic structure as Native Studio:
- the complete manuscript
- individual sections such as chapters or scenes
- focused section tabs
- project files and supporting material
- workspace panels for available history, comments, and collaboration tools
A good browser workflow
- Open the project and confirm you are in the intended section.
- Draft or revise the text.
- Use comments for questions that should not alter the manuscript yet.
- Check History before restoring or replacing substantial work.
- During collaboration, confirm the session and participant state before editing.
- Create a named version at a meaningful milestone.
- Export a proof capsule when you need portable evidence outside the browser.
Search
Web Studio supports search within the active editor and project search when that workspace tool is available.
Use section search for a word or phrase in the text you are currently editing. Use project search when you need to find the same character, place, phrase, or continuity detail across several sections.
Project search results take you back to the matching section and passage. If replace is available, review broad replacements carefully before applying them across a manuscript.
Browser and operating-system shortcuts can overlap. If the browser opens its own page-search box, use Studio's search control inside the workspace.
History
History lets you inspect earlier states of a section and compare them with the current draft.
Depending on the project and rollout, you may see:
- local browser snapshots
- cloud history versions
- named milestones
- redline comparisons
- authorship information for retained text
- local proof or cloud receipt information
- proof capsule actions
Restore safely
Restoring an earlier version creates a new history transition. It does not erase the intervening record. Verified authorship from the restored snapshot is preserved where possible, while the person performing the restore is recorded separately.
Missing history or authorship
Legacy sections and imports may have content without compatible authorship evidence. Web Studio should show that evidence as unavailable or Unknown rather than inventing a Human author.
Comments
When comments are enabled for the project, use them to discuss a passage without changing it.
Comments are useful for:
- editorial questions
- fact-check reminders
- requests for clarification
- co-writer discussion
- notes that should be resolved before a rewrite
Adding or resolving a comment does not change token authorship. If the surrounding text changes substantially, reread the thread in context before acting on it.
Collaboration
When real-time collaboration is enabled, the project owner or host can create a session and invite participants. A participant may join through a Bookcicle invitation or session link, depending on project settings.
During collaboration:
- identified participant edits are attributed to that participant
- unidentified contributions remain Unknown collaborator content
- the host is not automatically made author of all edits
- temporary connectivity problems may show reconnecting or offline state
- an expired or ended session requires a new invitation
Create a named version before a major session if you want a clear comparison point. End or leave the session when the shared review is complete.
Authorship and input evidence
Web Studio anchors content changes with surface = web. That makes Web and Native edits distinguishable in compatible history and proof views.
The authorship record still separates token origin from input method:
- typing can be Human-authored
- pasted text is Pasted/Unknown
- AI-generated text remains AI-authored after acceptance
- collaborator text belongs to the originating collaborator when known
- imported or remote content without valid provenance remains Unknown
Web 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 | web · keyboard · human_asserted | The authenticated Web Studio session asserted a Human edit |
| Type in the desktop Quick Edit webview | New/replaced text → current Human author | web · keyboard · human_asserted | Web-surface edit anchored by the native host |
| Use in-app speech-to-text | New/replaced text → current Human author | web · speech · human_asserted | Human speech input in Web Studio |
| Use Voice Control or assistive input | New/replaced text → current Human author | web · accessibility · human_asserted | Human accessibility input; assistive technology is not treated as AI |
| Paste text | New/replaced text → Pasted/Unknown | web · paste · unverified | The user performed a paste; original token author is not claimed |
| Outside software drives the browser using normal input | Currently appears as current Human author | web · keyboard · human_asserted | Web Studio cannot reliably distinguish it from ordinary browser typing |
| A trusted bridge explicitly marks suspected automation | New/replaced text → Unknown | web · unknown · suspected_automation | The edit was explicitly marked as suspected automation |
| Screen sharing, browser permission, or an OS indicator alone | No authorship consequence | No input event | An indicator alone is not automation evidence |
| Accept AI-generated text | New/replaced text → AI; unchanged text keeps prior origin | web · ai · unverified plus Human review | AI originated the accepted text; a Human accepted it |
| Reject AI-generated text | 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 | web · keyboard · human_asserted | Mixed AI and Human authorship |
| Receive an identified collaborator edit | New/replaced text → originating Human collaborator | web · remote · unverified | Privacy-safe collaborator attribution |
| Receive an unidentified collaborator edit | New/replaced text → Unknown collaborator | web · remote · unverified | Remote contribution with unavailable identity |
| Delete text | Deleted tokens and their author runs are removed | Current Web input evidence | 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 |
What “Human asserted via Web” means
It means the authenticated Web Studio session recorded the change as direct Human input and anchored it into history. It does not prove physical keyboard use.
Browser event flags can catch some simple scripts, but sophisticated software can control the real mouse and keyboard and produce ordinary browser events. For this reason, Web Studio does not claim the same device-level automation evidence as Native Studio.
AI-created project content
AI workflow output should arrive with service provenance that identifies it as AI-created or AI-derived. Opening, saving, or approving that output in Web Studio does not convert its existing tokens into Human authorship.
When a Human changes the output:
- unchanged AI spans remain AI
- Human replacement spans become Human
- deletions remove the deleted author runs
- a review decision can record who accepted or modified the proposal
Writing Coach and native inline AI editing are Native Studio features. Web Studio may display AI-generated project results and their provenance without offering the same native editing tools.
Notary and proof capsules
Web Studio can create local browser proofs for compatible history snapshots and can attach cloud attest information when available.
From a supported history item you may be able to:
- inspect the local proof
- add a Bookcicle cloud attest
- review the receipt state
- export a
.bkclpproof capsule - verify the capsule later
Browser proofs are stored locally in browser storage until they are exported or connected to a cloud flow. Clearing browser data, using private browsing, or changing browsers can remove locally stored material, so export important capsules.
Content and authorship evidence verify independently. A capsule can prove exact content even when part of the authorship map is Unknown or unavailable.
For one-off file proofs outside Studio, see Notary in the Web UI.
Connectivity and feature availability
Web Studio requires connectivity for project loading, cloud history, collaboration, and cloud proof actions. Available drawers and actions can depend on:
- your plan
- your project role
- whether you own the project or joined it
- the project's feature configuration
- the current product rollout
If History, Comments, or Collaboration is not shown, that does not imply the manuscript is damaged. It means the optional workspace capability is unavailable for that project or environment.
Practical safeguards
- Export important proof capsules instead of relying only on browser storage.
- Confirm the active project and section before editing.
- Create a named version before broad revisions or collaboration sessions.
- Treat pasted and unverified imported content as Unknown.
- Do not describe Web input as physically verified typing.
- Review AI-origin labels before making publication or disclosure claims.