Nebula extracts requirements from the documents that define the work, builds a shared delivery plan, and applies industry know-how to manage the engagement throughout its lifecycle.
It builds a working view of the engagement
An agreement, scope, brief, grant, specification, correspondence or operating record can help define the work. Nebula reads that material into one working context for the people, requirements, responsibilities, dependencies, dates, commercial positions, risks and evidence involved.
Each interpretation remains linked to the source wording. Source observations, Nebula's interpretations, participant positions, accepted decisions, disputes and unresolved matters remain distinct. For private work, choose Just me when creating the engagement. See What Nebula reads.
It keeps the working context current
Nebula evaluates how requirements and events affect the wider engagement. It identifies dependencies, emerging risk and unresolved questions, then updates the working view as documents, guidance, decisions and delivery evidence change.
It builds the delivery plan
Nebula organises source-backed requirements into a plan for the work. Relevant participants can review the plan, contribute their own positions and accept the coordination that applies to them. Acceptance remains attributable and does not erase a different position or create authority beyond its scope.
It manages delivery
Nebula connects deadlines, responsibilities, budget positions, risk, evidence and activity in the engagement workspace. It sends reminders, surfaces exceptions, supports approved changes and routes actions through the controls and authority that apply to them.
It preserves change and decision history
Revised documents, variations, extensions, guidance and delivery events update the working engagement without silently rewriting earlier sources, positions or decisions. Each change remains connected to what it affects and to the participant or process that accepted or determined it.
It creates proof you can check
Eligible recorded events can enter the proof path, with Polygon and Nebulad confirmation states reported independently. Verification can establish the integrity and timing of a retained record. It does not by itself establish that a disputed claim is true, fair or authorised. See Proof you can check.
It builds a contextual track record
Eligible, attributable delivery events contribute to an organisation's track record. The supporting engagement context, evidence grade, proof coverage and dispute state remain available, and an affected organisation can challenge a record through the applicable review path. The organisation controls release of its detailed profile. See Reliability scores.
Where to next
- Proof you can check explains the tamper-evident record.
- Reliability scores explains the evidence and context behind a track record.