01 Source wording
The wording and evidence that define your work stay attached.
Trust and reputation
Your delivery record keeps its evidence
Your delivery history carries its proof and earns your 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
Your work stays connected, source to outcome
Each stage keeps the context you need 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 give you a confirmation anyone can check.
05 Reputation
Delivery history can back your next engagement.
06 Private by design
Your engagement is visible only to its parties. Every action is attributed and stands in its audit trail. Your confirmed reading corrections can guide later agreement readings inside your organisation only.
Working across parties
Each party can keep its own position
Your reading stays yours, on the record. Working together never turns your position into consensus.
What the record keeps
Original wording and evidence stay beside delivery
Nebula's interpretation stays beside the source, never over it.
- 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 who said it, for which party, and when.
- Authorised decision
- The record keeps who decided, and under what authority.
- Dispute and review
- A challenge and its outcome stay with the history.
Authority for each action
Different actions need different authority
Nebula holds each action to the authority recorded for it.
Understand and organise
You review the available source material and state your position.
Coordinate shared work
You confirm what applies to you; other positions remain separate.
Approve a material action
Anything with real consequences follows the authorised decision-maker.
Checkable proof
Two records, two independent checks
You accept agreements and schedules through your signed-in identity, and Nebula records the signer, organisation, role and time. Formal notices carry their own sender block and anchor hash.
Where proof is switched on, an event leaves two independent records. Anyone can check them without an account.
A confirmation tells you the record existed, unchanged, at the time shown. It does not decide truth, fairness, authority or legal effect. Take that evidence to the people empowered to decide.
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 the file hashes it can be checked against.
Document boundary
Your source files are never published.
Independent checks
The two are made separately and are not expected to match.
Public verification
Check a record now
Enter an anchor ID, proof manifest JSON or ABN. Nebula reports what it finds.
Open the full verification pageAuthorised engagement verification
One deterministic record. Authority stays with the parties
You and the other party retrieve the same versioned, read-only verification snapshot through your own signed-in sessions.
Deterministic snapshot
The same governed engagement state produces one fingerprinted, versioned record.
Authorised retrieval
You retrieve the read-only snapshot through your own user session, and so does the other party.
No delegated authority
The snapshot cannot approve, settle or act for either party.
The snapshot keeps your requirements, milestones, evidence and recorded outcomes together. It cannot approve, settle or act.
Earned reputation
Your organisation controls released reputation detail
Another organisation first sees your tier, or no recorded history. After an owner or administrator approves access, released detail can show your exact score, five areas and recent event reasons.
A supported contest or resolution keeps the earlier change and adds an offsetting correction. Ask for review or appeal when a record about your organisation is wrong or lacks context.
The tier you rely on is defended. Nebula raises duplicate identifiers and suspicious adaptation patterns as flags for human review.
See what a movement records
- 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, the point change, the reason, the recorded time and the related work.
- Contest and resolution
- Supported contests keep the earlier change and add an offsetting correction.
Staff access transparency
You can see when Nebula staff enter your work
When Nebula staff enter your work through support access, the entry is recorded: who entered, the reason they stated, every engagement they reached, and when the session started and ended. Your account keeps that read-only record.
Trust in context
Review the engagement and Nebula
Security and data handlingWhere Nebula runs and how your content is protected.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
Run your next engagement on the record.