signal-observer

To generate telemetry after a sigil invocation, you read the invocation envelope, derive behavior-level signals, and append observability telemetry to a repository-local ledger for evidence-driven improvements.

Capturing post-run observability signals requires deriving behavior data from an invocation envelope and appending telemetry to a repository-local observability ledger after the sigil execution finishes, blocks, or fails.

Yes, you need a valid invocation envelope to append telemetry to the observability ledger, which can be provided directly or safely assembled to derive behavior-level signals and generate privacy-preserving telemetry.

To record telemetry when a sigil execution fails or blocks, you process the invocation envelope to derive post-run signals and append privacy-preserving telemetry to the repository-local observability ledger.

Yes, you can route reflection and maintenance recommendations based on post-run signals by deriving behavior-level data from the invocation envelope and appending telemetry to the observability ledger.

Limitations for assembling an invocation envelope for telemetry generation include requiring a safely assembled valid envelope, a repository-local observability ledger, and privacy-preserving telemetry generation to ensure accurate post-run signal derivation.