Observation & diagnostics

Core · Interfaces & runtime guarantees · Back to layer index

Symbol	Kind	Purpose
CoreDiagnosticRecord	interface	Persisted data is untrusted: normalization checks the current envelope, not arbitrary payloads.
CoreEvent	type	A recorded Core fact. Every variant carries the same envelope: a version marker, unique event id, producing span's identity, a per-producer monotonic sequence, the occurrence instant and optional reported sub-steps. subStepsDropped/subStepsTruncated state that reported detail was bounded.
coreEventCatalog	constant
CoreEventDescriptor	interface	Event classification used when deciding whether a sink accepts an event. metadata events carry identity, timing and status only; content events may carry user, model or tool content and therefore require an explicit acceptance decision.
CoreEventName	type	Union of every Core event name; the key set of CoreEventPayloads.
CoreEventPayloads	interface	Payload of every Core event, keyed by event name. Fields are the event's own facts only.
CoreLogOutput	interface	Destination for recorded facts; implementations decide filtering and durability.
createDiagnostics	function	Configure the optional log consumer of the shared execution fact source.
CreateDiagnosticsOptions	interface	Options for creating a root diagnostic scope.
DebugStepsOutput	interface	Debug material a handler contributes to a diagnostic event.
DiagnosticContext	interface	Recording scope bound to one execution identity. A child scope inherits the sink and observer of its parent; only identity changes.
diagnosticError	function	Convert a thrown value into a plain record suitable as a log payload.
DiagnosticIdentity	interface	Execution identity only: never message, account or HTTP identity.
DiagnosticSpanFields	type	Identity fields a child span may override; the parent supplies run, span and parent span.
NodeReportingContext	interface	Reporting surface handed to a node or tool for the duration of one visit.
normalizeDiagnosticEvent	function	Validate a persisted diagnostic record and return a detached copy. Persisted data is untrusted, so the envelope version, event type, identity, ordering and the bounded sub-step shape are checked; the payload itself is not interpreted. The copy is deep cloned, so a store cannot hand back a record that later shares structure with the caller.
RecordedSubStep	interface	A step already accepted by a logger, carrying recorder-assigned bookkeeping fields.
ReportedStep	interface	One step as reported by a node; fields beyond identity are optional detail.
ReportedStepStatus	type	A status a node may report; derived from the catalog, never declared separately.
reportedStepStatusCatalog	constant
reportedStepStatuses	constant
ScopedSubFlowLogger	class	Non-inheriting delegate. Stores only the original logger and its bound subnode identity.
ScopedSubFlowStepInput	type	Scoped writes cannot supply or override the identity bound by their delegate.
SubFlowLog	interface	Common read/write surface for both independently implemented logger classes.
SubFlowLogger	class	Full execution-owned recorder. Owns its store and may issue restricted delegates.
SubFlowStepFix	interface	Explicit revision whitelist: identity, grouping and business type are never patchable.
SubFlowStepInput	interface	Input accepted by write; the logger assigns the step id and sequence.
SubFlowValue	type	JSON-like value accepted in reported payloads; depth and size are bounded by the recorder.
SubStepProgress	interface	Compact progress notification emitted for each accepted sub-step write or fix.