observability-derivation

Name: observability-derivation
Availability: InStock
Author: cyberAlchemyAI

Derive typed metric-obligation inventories from DomainSpec aspect docs.

20|3|Updated May 14, 2026

Search Tags:#metrics #observability #governance #telemetry #domain-spec #rule-method #instrumentation-neutral

Ready to run

npx skills add https://github.com/cyberAlchemyAI/Arcanum --skill observability-derivation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: observability-derivation
Source: https://github.com/cyberAlchemyAI/Arcanum/tree/main/arcana/observability-derivation
Command: npx skills add https://github.com/cyberAlchemyAI/Arcanum --skill observability-derivation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Derive a deterministic, runtime-neutral set of metric obligations directly from a feature's DomainSpec aspect docs, enabling consistent observability planning without writing instrumentation code.

Core Features & Use Cases

Derives O1–O16 obligations from aspect anchors and domain clauses.
Produces a traceable, domain-faithful inventory that can be consumed by any backend.
Keeps instrumentation runtime out of scope, focusing on the formal obligations.

Quick Start

Provide the DomainSpec aspect docs for a feature and run the observability derivation to produce a runtime-neutral metric obligation inventory.

Frequently Asked Questions about observability-derivation

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

FAQPage Schema

How do I derive observability obligations from domain specs?▼

You derive observability obligations by processing DomainSpec aspect docs to produce a runtime-neutral inventory of typed metric obligations, formalizing one obligation per matching clause O1–O16 with source anchors for traceability.

What is a runtime-neutral metric obligation inventory?▼

A runtime-neutral metric obligation inventory is a deterministic set of observability requirements extracted from DomainSpec aspect docs, designed to be consumed by any backend without coupling to specific instrumentation code.

Can I use derived observability obligations with any telemetry backend?▼

Yes, you can use the derived observability obligations with any telemetry backend. The inventory is explicitly instrumentation-neutral, keeping runtime code out of scope so the formalized O1–O16 obligations remain backend-agnostic.

How do DomainSpec aspect docs map to O1–O16 observability obligations?▼

DomainSpec aspect docs map to observability obligations by matching domain clauses to the O1–O16 framework. Each matching clause generates one typed obligation tagged by fidelity, health, and effectiveness with source anchors attached.

What is the best way to plan metrics without writing instrumentation code?▼

The best way to plan metrics without writing instrumentation code is to derive a typed metric-obligation inventory from DomainSpec aspect docs, formalizing observability requirements deterministically while remaining runtime-neutral.

Do I need specific monitoring dependencies to generate a metric obligation inventory?▼

No, you do not need specific monitoring dependencies to generate a metric obligation inventory. The derivation operates solely on DomainSpec aspect docs and outputs a runtime-neutral set of formalized obligations without requiring external libraries.