Authoritative documentation · English
Deploy and port your Book
Harnesser keeps your Book portable and your deployments customer-controlled. Export and import move your knowledge between devices or archives; deployment bundles publish a validated, immutable release to a self-hosted Runtime.
Book portability
A portable Book package is an integrity-protected transfer artifact. It preserves Book identity, committed Note revisions, source links, temporal facts, OCR provenance, discovery decisions, validation state, and audit lineage. Export and import remain available regardless of commercial state.
The following are intentionally excluded from a portable package:
- Draft Notes and working chats
- Provider credentials and private keys
- Disposable retrieval indexes and transient layout state
- Ephemeral preview or candidate knowledge that has not been validated
Exclusions are recorded as an auditable policy rather than silently dropped. If a Note revision links to a source or target that was deleted, the broken link is preserved as provenance.
Close a Book before export. After import, verify the destination signer classification and rebuild excluded derived indexes locally.
Older packages
Supported older package versions are converted deterministically to the current format. The conversion report records the source version, target version, preserved data, excluded data, warnings, and any unsafe-loss failures. Conversion refuses ambiguous or unsafe changes rather than silently altering validated meaning.
Author self-hosted deployment
Author entitlement includes customer-controlled self-hosted deployment. A deployment bundle is an immutable, validated projection of a Book. It contains only validated knowledge revisions plus the evidence, provenance, and policy snapshots required to reproduce their serving boundary.
Each deployment bundle includes a manifest that binds the release to:
- Its Book and copy identity
- Certified model and policy identities
- The bundle signer
- The intended recipient
- A content digest
- The deployment entitlement
Candidates, rejected items, revoked or superseded revisions, draft-derived knowledge, credentials, and disposable indexes are excluded before the bundle is sealed.
Runtime installation
The self-hosted Runtime verifies the deployment signature, manifest inventory, compatibility, binding, and entitlement before staging or serving any bundle content. If the signer, model certification, or entitlement does not match the selected deployment, import is rejected before content becomes visible.
Activation is atomic from the serving assistant's perspective. Rollback and withdrawal are also atomic, so visitors never see a partial or mixed release.
Commerce boundaries
Author is the only paid application tier. Self-hosted deployment rights are included with Author; there is no separate public serving tier. Monthly and yearly Author plans differ only in billing cadence.
If Author access expires or is refunded, existing Books remain readable and exportable. New paid-only actions wait for a fresh entitlement.
Model-provider usage is customer-funded and separate from Harnesser application entitlement. Provider credentials, usage, and charges are attributable to the customer’s chosen provider.
What is not included
Harnesser does not promise hosted Publisher serving before release-size, provider-cost, abuse, storage, and entitlement economics have been measured and approved. The public Publisher experiment remains a separate future slice and is not enabled by this work.