Skip to main content

Trust and reputation

Make delivery trust inspectable.

Nebula keeps source material, participant positions, authority, evidence and recorded outcomes connected, then turns eligible delivery history into checkable proof and contextual reputation.

Explore the trust architectureVerify a record

The trust architecture

Context stays attached from source to reputation.

Trust is built through the engagement, not added at the end. Each layer carries enough context for the next one to be understood, governed and reviewed.

  1. Source

    The wording and evidence that define the work.

  2. Positions

    Who said what, with party, person and time attached.

  3. Authority

    The decision path that governs each effect.

  4. Action

    The recorded event and the context in which it occurred.

  5. Proof

    Checkable confirmation records for eligible events.

  6. Reputation

    Contextual delivery history carried forward.

Neutral coordination

One engagement can hold distinct positions.

Nebula preserves the difference between source wording, its own interpretation, what each participant says, what an authorised person decides and what remains disputed. Shared coordination never depends on silently converting one participant’s position into everybody’s position.

Source material
The wording and supporting evidence remain available beside the delivery view.
Nebula interpretation
A source-grounded proposal remains reviewable and attributable to its reading.
Participant positions
Each contribution keeps the party, person, time and context that supplied it.
Authorised decision
The decision maker, scope and applicable authority remain part of the record.
Dispute and review
A challenge, response and resolution stay attached to the history they address.

Effect-specific authority

Authority follows the effect.

Reading, coordination and material action carry different consequences. Nebula applies the control and recorded authority appropriate to the action being taken.

  1. Understand and organise

    A participant can work with its own source material and position within the access available to it.

  2. Coordinate shared work

    Relevant participants confirm the coordination that applies to them, without erasing a different position.

  3. Cause a material effect

    Money, rights, formal notices, enforcement and reputation follow the authority and decision path for that effect.

Checkable proof

Two records. Two independent checks.

Eligible proof events can follow the Polygon hash path and the signed Nebulad event path. Nebula reports each available confirmation state independently, and anyone can use the verifier without an account.

A proof confirms the integrity and timing of the retained record. Truth, fairness, authority and legal effect remain questions for the evidence and the people empowered to decide them.

DELIVERY PROOFConfirmation reported independentlyDELIVERY EVENTProposed to acceptedtwo distinct confirmation pathsPOLYGONPublic confirmationPublic hash recordedindependently checkableNEBULADNebula confirmationSigned event recordevent details stay linkedBoth checks completeTwo separate confirmation records, each checked against its matching saved source data.

Scroll across to inspect the proof path.

Polygon
Polygon receives a cryptographic hash. Nebula retains the canonical preimage used to recompute that hash.
Nebulad
Nebulad receives a signed canonical event payload that can include internal identifiers, title, description, dates, status and supporting evidence file hashes.
Document boundary
Source document files are not included in the proof payload.
Independent checks
The paths use different payloads and hashes. Each is checked against its matching canonical preimage, so verification does not require the two hashes to be equal.

Public verification

Check a record now.

Inspect an anchor or proof-bundle manifest, or confirm the registered organisation behind a released record. The result reports the confirmation available for each matching path.

Open the full verification page

Paste an anchor ID or manifest to check the public-chain records, or enter an Australian business number to confirm the registered party.

Earned reputation

Let good delivery become useful trust.

Eligible, attributable delivery events contribute to a contextual track record. Buyers can assess the role, evidence, proof coverage and state behind released information, while reliable organisations can carry a stronger account of their work into the next engagement.

Claimed, accepted, certified, disputed and determined states remain distinct. Affected organisations can use the applicable review or appeal path when information is incorrect or missing required context.

CLAIMED / ACCEPTED / CERTIFIED / DISPUTED / DETERMINED

Eligible event
The recorded delivery event that can contribute to the track record.
Attribution
The organisation, role and engagement context connected to the event.
Evidence
The material and verification state supporting the recorded movement.
Proof coverage
The independently checkable record available for an eligible event, shown separately.
State
Whether the event is claimed, accepted, certified, disputed or determined.
Review
The challenge, correction, annotation or appeal history attached to the record.

Trust in context

Inspect the engagement and the service around it.

Engagement trust

Source context, distinct positions, authority, evidence, proof and earned reputation.

Security and data handling

Where Nebula runs, how access is checked and how customer content is protected.

Review security

Public verification

Check available confirmation records without entering an engagement workspace.

Open public verify

Build trust through the work itself.

Start with the source material and carry context, authority and evidence through delivery.

Get started