observed-invocation-loop

Wrap Arcanum invocations into privacy-safe envelopes with telemetry signals.

20|3|Updated May 14, 2026
One-click install
npx skills add https://github.com/cyberAlchemyAI/Arcanum --skill observed-invocation-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observed-invocation-loop
Source: https://github.com/cyberAlchemyAI/Arcanum/tree/main/.claude/skills/observed-invocation-loop
Command: npx skills add https://github.com/cyberAlchemyAI/Arcanum --skill observed-invocation-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Observed Invocation Loop guarantees post-run observability by wrapping Arcanum-managed invocations, converting each into a safe envelope, appending a single telemetry signal, updating reflection counters, and routing to reflection when thresholds are met.

Core Features & Use Cases

  • Guaranteed post-run observability handoff for all invocations.
  • Envelope generation and telemetry emission to support reflection routing.
  • Supports codex workflows for skills, sigils, and spells with repository-local observability.

Quick Start

Integrate the Observed Invocation Loop into your Codex workflow to enable automatic telemetry handoff after every managed run.

Frequently Asked Questions about observed-invocation-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add telemetry and observability to Arcanum workflow invocations?

To add observability to Arcanum workflow invocations, you wrap each managed run to generate a privacy-safe envelope, append a telemetry signal, and update reflection counters for post-run validation.

What is post-run reflection routing for skill, sigil, and spell invocations?

Post-run reflection routing is an observability mechanism that tracks telemetry signals from skill, sigil, and spell invocations, automatically routing to reflection when defined thresholds are met.

How do I guarantee consistent telemetry handoff across different workflow run types?

You guarantee consistent telemetry handoff by wrapping all workflow run types into a standardized safe envelope, appending a single telemetry signal, and maintaining observability state using repository-local tooling.

Does the observed invocation loop require external dependencies for telemetry emission?

No external dependencies are required for telemetry emission; the observed invocation loop maintains observability state and routes reflection using entirely repository-local tooling.

When do I need to route to reflection during codex workflows?

You route to reflection during codex workflows when updated invocation counters meet predefined thresholds, triggering guaranteed post-run observability validation for the managed run.

What is the best way to ensure privacy-safe observability for automated workflow runs?

The best way to ensure privacy-safe observability is converting each automated workflow run into a safe envelope before appending telemetry signals, ensuring no sensitive data leaks during reflection routing.