01 Source wording
The wording and evidence that define the work stay attached.
Trust and reputation
See the evidence behind delivery
Nebula keeps sources, party positions, authority, evidence and outcomes together, so delivery history can support checkable proof and earned reputation.
Verified
Verified by Nebula
Illustrative, in the verifier's own fields.
Public confirmation
- Event
- Commissioning complete, week 36
- Engagement
- Transformer delivery and commissioning
- Confirmed
- 17 July 2026, 11:42 AEST
- Checkable by
- Anyone, without an account
Independent check
Open public verificationHow trust is built
Follow the work from source to outcome
Each stage preserves the context needed to review what follows.
02 Parties and decisions
What each party says stays separate from who can make each decision.
03 Authorised action
Each action keeps the context and authority that allowed it.
04 Proof
Some events can produce a confirmation anyone can check.
05 Reputation
Relevant delivery history can support the next engagement.
Working across parties
Each party can keep its own position
Nebula keeps source wording, interpretation, party responses, authorised decisions and disputes separate. Collaboration never turns one position into consensus.
What the record keeps
Original wording and evidence stay beside delivery
Nebula's suggested interpretation, party responses and authorised decisions remain separate.
- Source material
- The agreement's own words, and the evidence attached to them.
- Nebula interpretation
- Nebula's suggested interpretation stays separate beside its source.
- Each party's position
- Each contribution keeps its author, party, time and context.
- Authorised decision
- The record keeps who decided, what they could decide and the authority.
- Dispute and review
- Challenges, responses and outcomes stay with the history.
Authority for each action
Different actions need different authority
Reading, coordination and material actions have different consequences. Nebula applies the recorded authority and controls for each action.
Understand and organise
A participant reviews available source material and states its position.
Coordinate shared work
Participants confirm what applies to them. Other positions remain separate.
Approve a material action
Money, rights, notices, enforcement and reputation follow the authorised decision-maker.
Checkable proof
Two records, two independent checks
Where proof is switched on, an event can create a public record and a second record kept independently. Nebula reports each separately, and anyone can check it without an account.
A confirmation establishes the record existed, unchanged, at the time shown. It does not decide truth, fairness, authority or legal effect. The people empowered to decide those questions use the evidence.
Public chain
The event is recorded on a public chain outside Nebula, and Nebula keeps the record it was made from.
Nebula's ledger
A signed record of the same event stays in Nebula's ledger, with its title, dates, status and file hashes.
Document boundary
Your source files are never published.
Independent checks
The two are made separately, so their values are not expected to match.
Public verification
Check a record now
Enter an anchor ID, proof manifest JSON or ABN. Nebula reports the available matching confirmation.
Open the full verification pageEarned reputation
Review the delivery history behind reputation
Another organisation initially sees a tier or no recorded history. After an owner or administrator approves access, released detail can show the exact score, five areas and recent event reasons.
A supported contest or resolution keeps the earlier change and adds an offsetting correction. Affected organisations can request review or appeal when a record is wrong or lacks context.
- Area
- Point change
- Reason
- Recorded time
- Related work
- Qualifying event
- A recorded event that can change one area score.
- Organisation and work
- The related engagement, item or source when available.
- Reason
- The reason recorded for the movement.
- Separate proof
- Some item events can create a separate proof record.
- Score movement
- The area, point change, reason and recorded time.
- Contest and resolution
- Supported contests keep the earlier change and add an offsetting correction.
Staff access transparency
Nebula records its own access
When Nebula staff enter an organisation's work through support access, Nebula records who entered, the stated reason, the organisation, each engagement actually reached, and when access started and ended. The affected organisation can review that read-only record in its account.
Trust in context
Review the engagement and Nebula
Review the engagement, security, privacy and terms
Security and data handlingWhere Nebula runs, checks access and protects customer content.PrivacyPersonal information and customer instructions.Terms of serviceTerms governing access and use.Security and trust white paperProduct, architecture and controls.
Security questions and vulnerability reports: security@nebulaplatform.com.au
Every record here can name where it came from
Keep sources, decisions and evidence connected through delivery.