operator · v0.01

Records and History

Records are the permanent sealed output of completed execution. Operators can view their records and trust signal history from their Desk. Trust signals are system-emitted and advisory only.

private active partially_implemented operator.x1

Records and History

A Record is the permanent, sealed account of what happened in a completed job. It is the system’s final source of truth for an execution. Once created, it cannot be retroactively changed.

What a record contains

The Record captures the full execution:

  • The operator who did the work
  • The surface (service type) the work was performed on
  • The ServiceEvent outcome and evidence
  • Payment state at completion
  • Timestamps throughout the execution

Records are linked to the Job, the Intake, and the operator. They are the prerequisite for a ⭐ Signal.

Trust signals and records

After a Record is sealed, the system may emit a ⭐ Signal — a trust attribution object derived from the execution. This happens automatically.

ServiceEvent completed → Record sealed → ⭐ Signal emitted

The ⭐ Signal is not a review. It is not created by the customer. It is emitted by the system and traces back to the specific Job, ServiceEvent, and Record that produced it.

What operators can see

Operators can view their trust signal count and state in their Desk:

  • Total signals earned
  • Whether trust is present (none or present)
  • When the most recent signal was emitted

This is internal visibility only. No public-facing trust display exists in v0.01.

Operators see their own records and signals. They do not see other operators’ records.

What trust signals are not

What people might expectWhat is actually true
A 1–5 star ratingNot this. Signals are binary per execution: emitted or not.
A score from 0–100Not this. No aggregate score exists.
A customer reviewNot this. Customers do not create signals.
A ranking systemNot this. Operators are not ranked by signals.
Something that can be editedNot this. Signals are system-emitted and immutable.

Trust is advisory

Having trust signals does not change what an operator can do in the system. It does not grant additional access or affect routing decisions.

In v0.01, trust signals are labeled trust_advisory_effect: "none". The system can see trust. It does not act on trust yet.

Guardrails

  • Preserve the distinction between planned, partial, and live.
  • Avoid marketing language.
  • Trust signals are system-emitted. Operators cannot create or modify them.