Factory docs, home
Page navigation

See the input → responsibility → output diagram.

Status: Accepted locally on 1 October 2026; the acceptance receipt and build review record its reviews and checks. CI remains a separate gate. Nothing in the Factory uses it yet.

A crash or a slow request can suggest work. First we need to know where the observation came from, which Product it belongs to and whether we are allowed to keep it.

A round azure bob listening through an ear trumpet.

Meet the listener. Heard, and not yet judged. Records what a product's services report as unassessed Signals, with where each came from. Meet the whole Plumb family.

The bounded intake candidate accepts approved facts from a caller-authenticated source. It records each Signal together with collection progress, so restarting or losing a reply does not make the same observation new. Gaps remain visible. An unavailable source never becomes an empty, healthy result.

Signals are unassessed indications for possible investigation. They do not prove a cause, customer impact, successful repair or permission to change a service. This packet contains no live provider integration or Repair Workflow.

The caller supplies storage, source authentication, current permission, redaction and a clock. Limits stop growth without dropping duplicate history. Data that needs timed erasure is refused because the present journal retains immutable copies. The adoption guide explains the contract and recovery steps; the full design describes the separate work still ahead.

Honest limits:

  • The caller authenticates and redacts observations under current permission; source hashes alone grant no authority.
  • Recorded Signals are unassessed. They prove neither a cause nor customer impact, repair or present health.
  • Timed erasure, live providers and repair workflows are unsupported. CI remains a separate gate.

Shared value implementation: common contracts. Owning errors, limits, stored identities and authority remain as specified above.

The exported operationalPageDigest calculates the intake's canonical page hash without duplicating its ordering rules. The caller still authenticates the source bytes and current permission; a matching digest grants no authority.

Source: docs/guide/operational-signals.md