Definitions for terms used in Nebula's current product.
Engagement
A Nebula workspace for source material, its Reading, participants, delivery items and recorded activity for a body of work.
Agreement
A source document used in the Agreement room. Nebula can read uploaded agreements and supporting documents; its Reading remains for review and does not itself grant authority.
Just me
An engagement with one joined organisation and no live invitation. Its members can use the authorised workspace and invite the other party later from the Parties area.
Shared workspace
An engagement whose other party has joined. Members of its party organisations use the same authorised workspace. Journal, question and answer entries retain the author and acting organisation.
Position
A participant's recorded statement, such as grounds for disputing a claimed delivery. Recording a position does not bind the other party or decide whether it is true.
Commitment
An obligation Nebula identifies in source material. After the agreement is signed, it can become a delivery item. A manually created item may have no Reading source.
Authority
A recorded organisation permission for a specified action. Nebula can apply it to agreement and baseline signing, variation approval, payment certification, notices and item disputes, including a recorded approval value limit.
Baseline
The signed and locked delivery starting point. Nebula records each baseline signature and the lock time; later variation and date-change records remain separate.
Variation
A proposed change to scope, cost, time or affected delivery items. The Variations register records its submitter, status, stated effects and decision details. A supported approval can update recorded dates, budget or items while retaining the proposal and decision.
Deadline
A date recorded on a delivery item or a response window. It may come from the Reading, manual entry or an approved change. The relevant screen shows the date and its current workflow state.
Evidence
An item-attached file, such as a photograph or report. Its record keeps the file name, optional description, uploader and upload time. A submission round has a separate review state, and upload alone does not establish truth.
Anchor
A proof record for a supported recorded event. It can be local, pending or confirmed. With an anchor ID, anyone can check each available network result in the public verifier.
Verified
In the public verifier, a result where the selected network commitment matches the expected hash. When saved event data exists, Nebula also recalculates its hash first. Older records without that data receive a network-only check.
When Polygon and Nebulad records are both available, their results remain separate. The pair is fully verified only when both results verify. Verification does not establish the truth, fairness or authority of the business statement.
Reliability score
One overall score calculated from five area scores: reliability, responsiveness, timeliness, collaboration and documentation. Each area starts at 75 in the calculation. The overall score is their rounded, equal average.
Each qualifying movement records its area, point change, reason and time. Proof is separate from the score calculation, and the Reputation and marketplace event lists do not show proof beside every movement.
Tier
The marketplace directory band derived from recorded reputation events: Elite, Established, Trusted or Emerging. Until a qualifying event is recorded, the signed-in directory shows No recorded history yet.
In that directory, an owner or administrator can approve a request to release the exact score, five areas and recent event reasons. A tier is a discovery aid, not a finding of truth or legal responsibility.
Certify
A public profile available when an organisation has published Certify. It shows organisation details, overall and area scores when recorded history exists, aggregate delivery measures and limited proof links.
Anyone with its URL can open it without a Nebula account. The profile does not show the raw reputation event list.
Marketplace
The signed-in directory and opportunity area where organisations can view directory tiers, request reputation detail, post opportunities and submit tenders.
Companion
The signed-in panel that shows a brief and recent signals for the current engagement, or a portfolio brief outside one engagement. In a two-party engagement, it also opens the project message thread.
Companion brief lines come from loaded delivery records and link to related product areas when a link is available. Companion does not perform a controlled project action for the user.
Extension of time (EOT)
A recorded request by a project party for a later completion date. It keeps the reason, requested days and date, optional evidence and status. An assessment can add the other party's decision and rationale.
If approved for an item, its due date moves forward to the approved date.
Defects liability period (DLP)
A recorded period for defects after delivery. When its duration is set and all non-voided items are verified or closed, Nebula records the start from a resolved source trigger when available, otherwise from the completion moment.
The stored duration determines the end date. The Defects area shows the period when the Reading supplies a duration or defect records already exist.