authority-resolution

Name: authority-resolution
Availability: InStock
Author: centaurioun

Classify file paths into canonical, manuscript, archival, or reference authority domains.

Updated Apr 18, 2026

Search Tags:#archival #canonical #manuscript #data-governance #file-mapping #authority-resolution

Ready to run

npx skills add https://github.com/Centaurioun/osteogenesis_imperfecta --skill authority-resolution

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: authority-resolution
Source: https://github.com/Centaurioun/osteogenesis_imperfecta/tree/main/.claude/skills/authority-resolution
Command: npx skills add https://github.com/Centaurioun/osteogenesis_imperfecta --skill authority-resolution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ambiguity in file ownership across canonical, manuscript, archival, and reference data is a common source of errors. This skill provides a robust mapping to authoritative versus supporting data, reducing misclassification and data bleed.

Core Features & Use Cases

Authority disambiguation: Classifies paths into canonical, manuscript, archival, or reference domains and outputs an authoritative vs. supporting vs. excluded map.
Auditable governance: Produces deterministic outputs that support reproducibility and compliance across replication cycles.
Use Case: When a task references files from 01_data, Manuscript_Data, and 99_archive, generate a coherent authority map to enforce correct data lanes.

Quick Start

Provide a list of file paths to classify and generate a canonical authority map.

Frequently Asked Questions about authority-resolution

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

FAQPage Schema

What is file authority resolution and how does it prevent data bleed?▼

File authority resolution classifies file paths into canonical, manuscript, archival, or reference domains to prevent data bleed. It generates an authoritative versus supporting versus excluded map, ensuring consistent and auditable data governance across multiple domains.

How do I generate a canonical authority map for paths across multiple domains?▼

To generate a canonical authority map for paths across multiple domains, you provide a list of file paths for classification. The system labels each path as authoritative, supporting, or excluded based on its domain, ensuring coherent data lanes and preventing misclassification.

When do I need to classify files into canonical, manuscript, and archival domains?▼

You need to classify files into canonical, manuscript, and archival domains when a task references paths across multiple domains. This disambiguation avoids data bleed and enforces correct data lanes for strict validation of file authority.

Does this authority resolution approach support auditable governance and compliance?▼

This authority resolution approach supports auditable governance and compliance by producing deterministic outputs. It generates an authoritative versus supporting versus excluded map that ensures reproducibility across replication cycles.

What's the best way to enforce correct data lanes for files from 01_data and 99_archive?▼

The best way to enforce correct data lanes for files from 01_data and 99_archive is to classify paths into canonical, manuscript, archival, or reference authority. This generates a coherent map to avoid misclassification and data bleed across domains.