Registered External Resource

The Lifecycle

Transitions Explained

The register gives participants a durable account of resources outside the database. A participant can record a newly created resource or adopt one already present under its deterministic key. Recording preserves an existing creation time while replacing the run and supplied state. Removal participants record progress and stamp completion after the provider reports the resource gone.

The diagram describes the intended participant sequence. The persistence interface accepts any declared state regardless of its predecessor, so the diagram does not establish a guarded lifecycle or a terminal deleted state.

What Cannot Happen

The database rejects an undeclared state and prevents duplicate entries for the same resource key. It does not reject a return from deleted or deleting to present. Identifier retirement limits later provisioning at the workspace boundary, rather than enforcing resource transitions.

Concurrency and Timing

The unique key makes repeated recording target one row. State changes have no version precondition or successor assertion, so overlapping writers can replace an earlier result. The product should decide whether this register needs guarded transitions in addition to participant sequencing.