Reputation

Every organisation on Nebula has a reputation score across five

dimensions: reliability, responsiveness, scope_discipline,

payment_discipline, and transparency. The default is 75.

Why default 75

A new organisation is unproven, not bad. Starting at 75 reflects an

expected-good-faith baseline that anchored events move up or down.

How events move it

Reputation events are written by the engines, never by hand. Examples:

• Item accepted on time: +responsiveness event
• Variation responded within deadline: +responsiveness
• Defect rectified within deadline: +reliability
• Resubmission deadline missed: -responsiveness
• Item auto-breached after grace: -reliability

Each event carries a magnitude (typically 1 to 5 points) and a

chain-anchored proof. The magnitudes are documented in

/docs/engines/verify.

Anchored backing

Every reputation event is anchored. That means a third party can

inspect the chain and reconstruct an organisation's score

independent of Nebula. This is the difference between a vanity score

and a trust score.

Cross links

• /docs/engines/certify: the public Certify badge
• /docs/engines/verify: the maths and the per-event proofs