Nebula turns agreements into business systems that connect people, decisions, delivery and money under the agreement's rules.
Nebula reads uploaded documents, presents a reading for review and creates delivery items from accepted source-backed obligations after the agreement is signed.
Bring existing work together
Consulting deliverables, facilities and maintenance scopes, and software delivery changes need a record of agreed work, responsibility, changes and acceptance. These are engagement examples, not proof that every specialist system or industry process is supported.
With an authorised company Microsoft 365 connection, a person with document upload authority can bring a selected SharePoint or OneDrive file revision into an engagement.
The individual file must be manually mapped to that job. Nebula checks the source and revision, verifies the stored file's hash and keeps the source details.
Supported PDF, Word, Excel and text files can be imported within the 10 MB connected-import limit and the job's upload allowance. Importing does not start a reading or change the accepted plan.
On enabled engagements, an external agent can ask about the record or prepare proposals for a person to review. It cannot confirm, apply, certify or pay.
Its access is limited to one company and one engagement, expires within one hour and can be revoked.
Connect an agent explains the setup and permissions; connecting an agent does not replace a source provider's own consent.
From reading to plan
Nebula's reading view brings together the parties, obligations, dates, amounts, dependencies, risks and evidence requirements it identifies in the current documents.
Nebula adds a source link only when the quoted passage matches a supplied, readable file. Source observations, Nebula's interpretations, participant positions, accepted decisions, disputes and unresolved matters remain distinct.
After the agreement is signed, accepted source-backed obligations can become delivery items. An item can carry an owner, counterparty, resolved due date, evidence requirements and source reference when the reading provides them.
Items with unresolved ownership or low reading confidence remain drafts. Recorded dependencies connect delivery items, and missing dependency references are reported. Project members can also create manual items, which may have no reading source.
While work is being delivered
Each part of delivery has its own view, and the workspace tabs name them.
The owner can claim completion. On a two-party item, the other party can verify the delivery or record a dispute with its grounds.
Project parties use each item's workspace to record journal entries, hours, blockers and questions with answer-by dates. An answering user must belong to the other project party. In a Just me engagement, another project member can answer.
Any recorded completion percentage is labelled as the delivering party's claim, not independent proof.
Specific item actions, blockers and questions can create in-app notifications that link to the related record.
When the work changes
A new document revision, participant statement or update admitted through a supported, source-bound connection remains source-linked evidence. Its arrival alone does not change the accepted plan.
Nebula keeps the source, interpretation, possible consequences and authority to decide distinct until the supported decision path records what follows.
An uploaded document revision stays separate from the accepted reading until an authorised project member chooses to re-read. The revision banner identifies the newer file and offers a comparison before that decision.
A party can submit a variation or extension claim. The authorised other party records its decision and rationale. An approval can apply supported schedule, budget or item changes while retaining the before and after values.
Proof you can check
Where proof is enabled, an eligible recorded event can create up to two confirmation records, one for Polygon and one for Nebulad. Each available record reports its own state.
Anyone with an anchor ID can check available public confirmation records without an account. Verification can establish the integrity and timing of a retained record. It does not establish that a disputed claim is true, fair or authorised.
A bounded reputation record
When a recorded two-party delivery event meets Nebula's eligibility rules, Nebula records a score event that can change one of five area scores. Solo engagements, sample data and events with the same organisation on both sides do not contribute.
For certain dispute, contest and resolution actions, Nebula records a later score event instead of deleting the earlier event.
An organisation can see its own scores and events. Another organisation sees detailed information only after an owner or administrator approves its access request.
Where to next
- What Nebula reads explains how uploaded documents become readings.
- Proof you can check explains the confirmation records.
- Reliability scores explains the recorded events and dimensions behind a track record.