Documentation#
Linux 0.9.0 release and downloads
HyperNetSuite supplies native Page, Mail and Transfers applications, terminal Page viewers and command-line publishing, service and administration workflows. HyperNet runs the separate infrastructure. These manuals distinguish local preview, ordinary client access through accepted relay routes and local operator control.
Start here#
- Check supported platforms and install the client.
- Preview the supplied Page without network access.
- Learn the native browser or terminal browser.
- Read security boundaries before accepting network trust or credentials.
- Prepare a profile, then join through approved routes.
- Keep private state and software separate; use upgrade and recovery when replacing an installation.
Offline preparation does not join a network. The operator must provide trusted bootstrap material, an approved invitation and suitable routes. Membership alone does not grant the capabilities required by each application.
Readers, authors and recipients#
| Task | Manual |
|---|---|
| Select commands, identities and state locations | Client use |
| Browse with a native window and configure display preferences | Graphical browser |
| Navigate in a terminal or produce plain output | Terminal browser, layout and controls |
| Try ready-made local content | Examples |
| Write, submit, review and publish Pages | Pages |
| Understand the declarative document format | HyperPage |
| Import, review and explicitly reveal images | Media, terminal graphics and decoding limits |
| Find native, imported or retained content | Search |
| Publish encrypted content to selected devices | Sealed Pages, recipient identities |
| Read and send encrypted messages in a native window | Native Mail |
| Set up an encrypted mailbox and manage device keys | Private Mail |
| Review and send a Form, or accept typed submissions | Forms |
| Review offers and transfer files in a native window | Native Transfers |
| Accept files or invoke an approved SSH service | Transfers and services |
| Share Pages between separately governed networks | Federation |
Authors should read Pages before Media or Forms. Confidential publishing also requires recipient trust and device setup. Forms use separate Page and Mail permissions; a reviewed Page cannot choose a sender's credentials.
Network operators and application integrators#
These guides assume explicitly provisioned roles and private operator state. They are not extra steps required for local Page preview. Infrastructure hosting and runtime installation are documented by HyperNet.
| Task | Manual |
|---|---|
| Inspect bootstrap policy and prepare independent client trust | Networks |
| Register relays, issue vouchers, join and retain service routes | Private routes |
| Initialise requester state and inspect current governance | Authority inspection |
| Review tier changes, delegate or revoke capabilities | Administration |
| Change network policy with explicit client acceptance | Network policies |
| Replace a healthy authority committee | Authority epochs |
| Recover a network when normal authority is unavailable | Network recovery |
| Back up content and reconcile a restore with current authority | Content archives |
| Inspect or export a bounded local diagnostic summary | Diagnostics |
| Verify, replace or remove installed software | Upgrade and recovery |
| Connect application services and manage local companions | Application streams |
| Connect an installed service to a remote authority | Native authority connector |
| Grant an application its own scoped authority | Application access |
| Disclose exact review data to an external processor | Adapters |
Start operator work with Networks and Authority inspection, then choose the manual for the intended action. Preserve requester floors and unresolved request files. A timeout does not prove that a mutation failed; use its documented exact retry or recovery procedure.
Protocol and implementation reference#
Contracts define obligations and byte formats; they do not certify a deployment. Use the task manuals above for executable procedures and prerequisites.
| Reference | Purpose |
|---|---|
| Requirements | Product scope and intended client behaviour. |
| Contract index | Relationship between shared protocol and policy contracts. |
| Wire | Canonical encodings, signed requests and verified result proofs. |
| Authority | Committee consensus, durable state, time and recovery rules. |
| Policy | Capabilities, publication, custody and consent semantics. |
| Runtime | Management, readiness, relay coverage and replacement contracts. |
| Tiers | Tier administration wire interface and delegation rules. |
| Source layout | Implementation directories and their responsibilities. |
| Dependencies | Locked components, notices and separate licences. |
Terms and command conventions#
| Term | Meaning |
|---|---|
| Bootstrap | Independently authenticated initial network identity and policy material. |
| Profile | Private client trust, identity and accepted network configuration. |
| Capability or grant | Explicit permission scoped to an identity, resource and validity period. |
| Requester floor | Durable verified authority history and request state used to reject stale or conflicting results. |
| Host-readable Page | Approved content that its consenting storage host can read. |
| Sealed Page | Encrypted publication for explicitly authorised recipient devices. |
| Retained view | Previously received content; displaying it again does not establish current permission. |
| Receipt | Evidence for a particular operation or serving effect, with the scope stated by that workflow. |
Examples with /Private/..., uppercase IDs or [online options] are command
templates. Substitute the actual protected paths, exact identifiers and trust
options required by the linked guide; do not paste brackets as shell arguments.
Use HyperNetSuite COMMAND --help to inspect its current arguments.
Expiry options ending in -ms take absolute Unix milliseconds. Mail and Forms
--expires take absolute Unix seconds. Retention options name their own units.
Do not paste private keys, vault contents or credential-bearing profiles into
logs, issue reports or documentation.