Skip to main content

Document Registry

The registry is the validated ledger of processed documents used for operations and exports.

Registry upload entrypoint​

You can feed registry data through:

  • manual document uploads,
  • connected folder ingestion,
  • reparse/review actions from document preview.

After ingestion, each item remains review-driven before final registration.

Lifecycle states​

Typical flow:

  • DISCOVERED / NEW
  • PARSED
  • REVIEWED
  • REGISTERED
  • EXCLUDED

REGISTERED entries are treated as finalized for downstream workflows.

Register and period binding​

When registering, the UI may request an open period.

  • If open periods exist, choose one before confirming
  • If none exist, registration can proceed without explicit period selection (subject to environment policy)

Locked documents​

A document may appear locked if policy or lifecycle rules prevent edits.

Common reasons:

  • finalized status in current workflow,
  • subscription/policy restrictions,
  • role scope limitations.

When locked, use review or support path rather than force-editing.

Manual control rules​

Zeno does not auto-confirm registry entries. Final state changes are user-driven.

Export readiness​

Registry exports should be produced from reviewed/registered scope to preserve audit traceability.

See Exports & Sharing for format and handoff guidance.