Owned event types

events.iterate.com/capability-host/capability-providedA capability was mounted at a path.payload: { type, path, providerPager, instructions?, types?, flattenNestedPaths? } | { type, pat…emitted by 3 · consumed by 1events.iterate.com/capability-host/capability-provider-pager-connectedA provider client gave this Durable Object a hibernatable Pager: a return channel the host can Page after releasing ordinary RPC references. The event's offset is the Pager's durable identity.payload: {}emitted by 1 · consumed by 2events.iterate.com/capability-host/capability-provider-pager-disconnectedOne exact Capability Provider Pager disappeared. Every live mount referencing its connected event retires atomically; replacement Pagers and their mounts are unaffected.payload: { connectedAtOffset }emitted by 1 · consumed by 2events.iterate.com/capability-host/capability-revokedA dynamic capability was removed.payload: { path, providedAtOffset? }emitted by 1 · consumed by 1events.iterate.com/capability-host/createdCreates a capability-host processor on this stream. The birth certificate records the scope's `fallback`: the itx expression a capability miss follows (usually straight to the project root host), or null at the root.payload: { config, fallback? }emitted by 4 · consumed by 1events.iterate.com/capability-host/preamble-removedRemoves one preamble entry by key; unknown keys reduce to a no-op.payload: { key }emitted by 1 · consumed by 2events.iterate.com/capability-host/preamble-setUpserts one preamble entry: TypeScript injected above every later script in this scope, at typecheck and at execution. Keyed — a re-set at the same key replaces the code but keeps the entry's injection position (first-set offset). Entries recorded through setPreamble were compiled against the scope's assembled preamble at set time; a stale entry that stops compiling later never blocks a script (the run gate downgrades preamble-line errors to unchecked).payload: { key, code }emitted by 1 · consumed by 2events.iterate.com/capability-host/script-run-requestedA script should run in this capability scope. Before any attempt starts, the code is typechecked against the scope's capability types: a script with a PROVABLE error — a syntax error, or a near-miss typo where the compiler names the fix ("Did you mean 'get'?") — settles straight to an error completion carrying the compiler errors, without ever running (no started event). Everything less certain runs: capabilities are provided dynamically and declared types can lag the runtime, so bare property/argument mismatches, unknown/untyped capabilities, non-async block shapes, and checker failures all let the script run unchecked.payload: { code, executionId, expiresAt }emitted by 4 · consumed by 3events.iterate.com/capability-host/script-run-settledThe one durable settlement for a script obligation. Failures classify where execution stopped, whether script code may have run, and whether cancellation can prove external work ended.payload: { executionId, settlement }emitted by 1 · consumed by 2events.iterate.com/capability-host/script-run-startedAn attempt to run the script began. Appended BEFORE the script body executes, so requested-without-started provably never ran (safe to start late) while started-without-settled died mid-run (settled as failure, never re-run).payload: { executionId }emitted by 1 · consumed by 1

Consumes

events.iterate.com/capability-host/createdCreates a capability-host processor on this stream. The birth certificate records the scope's `fallback`: the itx expression a capability miss follows (usually straight to the project root host), or null at the root.events.iterate.com/capability-host/capability-provider-pager-connectedA provider client gave this Durable Object a hibernatable Pager: a return channel the host can Page after releasing ordinary RPC references. The event's offset is the Pager's durable identity.events.iterate.com/capability-host/capability-provider-pager-disconnectedOne exact Capability Provider Pager disappeared. Every live mount referencing its connected event retires atomically; replacement Pagers and their mounts are unaffected.events.iterate.com/capability-host/capability-providedA capability was mounted at a path.events.iterate.com/capability-host/capability-revokedA dynamic capability was removed.events.iterate.com/capability-host/script-run-requestedA script should run in this capability scope. Before any attempt starts, the code is typechecked against the scope's capability types: a script with a PROVABLE error — a syntax error, or a near-miss typo where the compiler names the fix ("Did you mean 'get'?") — settles straight to an error completion carrying the compiler errors, without ever running (no started event). Everything less certain runs: capabilities are provided dynamically and declared types can lag the runtime, so bare property/argument mismatches, unknown/untyped capabilities, non-async block shapes, and checker failures all let the script run unchecked.events.iterate.com/capability-host/script-run-startedAn attempt to run the script began. Appended BEFORE the script body executes, so requested-without-started provably never ran (safe to start late) while started-without-settled died mid-run (settled as failure, never re-run).events.iterate.com/capability-host/script-run-settledThe one durable settlement for a script obligation. Failures classify where execution stopped, whether script code may have run, and whether cancellation can prove external work ended.events.iterate.com/capability-host/preamble-setUpserts one preamble entry: TypeScript injected above every later script in this scope, at typecheck and at execution. Keyed — a re-set at the same key replaces the code but keeps the entry's injection position (first-set offset). Entries recorded through setPreamble were compiled against the scope's assembled preamble at set time; a stale entry that stops compiling later never blocks a script (the run gate downgrades preamble-line errors to unchecked).events.iterate.com/capability-host/preamble-removedRemoves one preamble entry by key; unknown keys reduce to a no-op.

Emits

events.iterate.com/capability-host/createdCreates a capability-host processor on this stream. The birth certificate records the scope's `fallback`: the itx expression a capability miss follows (usually straight to the project root host), or null at the root.events.iterate.com/capability-host/capability-provider-pager-connectedA provider client gave this Durable Object a hibernatable Pager: a return channel the host can Page after releasing ordinary RPC references. The event's offset is the Pager's durable identity.events.iterate.com/capability-host/capability-provider-pager-disconnectedOne exact Capability Provider Pager disappeared. Every live mount referencing its connected event retires atomically; replacement Pagers and their mounts are unaffected.events.iterate.com/capability-host/capability-providedA capability was mounted at a path.events.iterate.com/capability-host/capability-revokedA dynamic capability was removed.events.iterate.com/capability-host/script-run-requestedA script should run in this capability scope. Before any attempt starts, the code is typechecked against the scope's capability types: a script with a PROVABLE error — a syntax error, or a near-miss typo where the compiler names the fix ("Did you mean 'get'?") — settles straight to an error completion carrying the compiler errors, without ever running (no started event). Everything less certain runs: capabilities are provided dynamically and declared types can lag the runtime, so bare property/argument mismatches, unknown/untyped capabilities, non-async block shapes, and checker failures all let the script run unchecked.events.iterate.com/capability-host/script-run-startedAn attempt to run the script began. Appended BEFORE the script body executes, so requested-without-started provably never ran (safe to start late) while started-without-settled died mid-run (settled as failure, never re-run).events.iterate.com/capability-host/script-run-settledThe one durable settlement for a script obligation. Failures classify where execution stopped, whether script code may have run, and whether cancellation can prove external work ended.events.iterate.com/capability-host/preamble-setUpserts one preamble entry: TypeScript injected above every later script in this scope, at typecheck and at execution. Keyed — a re-set at the same key replaces the code but keeps the entry's injection position (first-set offset). Entries recorded through setPreamble were compiled against the scope's assembled preamble at set time; a stale entry that stops compiling later never blocks a script (the run gate downgrades preamble-line errors to unchecked).events.iterate.com/capability-host/preamble-removedRemoves one preamble entry by key; unknown keys reduce to a no-op.