Getting started
Nebula reads the documents that define your work, builds the
commitments, and keeps everyone accountable. This page walks you from
sign-up to your first verified anchor in about five minutes.
Sign up to first project
- Go to /register and sign in with your work email.
- After verification you land on /dashboard.
- Click New Project and give it a name. The project belongs to your
organisation; if you're not in one yet, set yours up first under
/organization.
Loading the sample project
Don't have a document handy? Click Load sample project on the
dashboard. Nebula creates a worked example with two documents, thirty
atoms, eight items, and one anchored proof so you can poke around the
engines without uploading anything.
Uploading your first document
From the project page, open the Documents tab and drop in your
document, contract, SOW, scope of work, project brief, specification,
service agreement, MSA, change order, requirements document, design
document, RFP, RFQ, whatever defines what's being delivered. Nebula
extracts atoms in the background; the Atoms tab populates as
parsing completes.
Understanding the seven engines
Nebula's engines act on a typed graph of atoms. Each engine has its own
docs page; here's the one-paragraph summary:
- Extract turns documents into atoms. See
/docs/engines/extract. - Accept brings parties to agreement and locks the baseline. See
/docs/engines/accept.
- Enforce drives item status with deadline-aware ticks. See
/docs/engines/enforce.
- Adapt lets parties co-evolve commitments. See
/docs/engines/adapt.
- Prove dual-anchors trustworthy state to chains. See
/docs/engines/prove.
- Verify lets the public check the chain without an account. See
/docs/engines/verify.
- Certify scores reliability and exposes a public profile. See
/docs/engines/certify.