edictum-oss

Implement and maintain Edictum OSS core for tool-contract governance.

29|6|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/acartag7/edictum --skill edictum-oss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: edictum-oss
Source: https://github.com/acartag7/edictum/tree/main/.claude/skills/edictum-oss
Command: npx skills add https://github.com/acartag7/edictum --skill edictum-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implement and maintain the Edictum OSS core to standardize tool-contract governance.

Core Features & Use Cases

  • OSS core scope covers pipeline, envelope, contracts, YAML engine, adapters, audit, session, CLI, telemetry, and related protocols.
  • Use cases include adding new core modules, extending adapters across frameworks, and enforcing tool-call contracts in production environments.
  • Real-world workflow: evolve the core while keeping ee/ imports disallowed and ensuring modular boundaries.

Quick Start

Review CLAUDE.md and implement or adjust the Edictum OSS core components under src/edictum/.

Frequently Asked Questions about edictum-oss

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

FAQPage Schema
What is tool-contract governance and when do I need to standardize it in a pipeline?

Tool-contract governance standardizes how tools interact within a pipeline. You need it when enforcing modular boundaries and consistent tool-call protocols across adapters in production environments.

How do I implement CLI and audit modules for a YAML configuration engine?

Implement CLI and audit modules by adjusting core components under the src/edictum/ directory, following project conventions and testing guidelines to standardize tool-call contracts.

Can I extend framework adapters while maintaining strict separation from enterprise code?

Yes, you can extend adapters across frameworks while maintaining strict separation. Enterprise imports remain disallowed, ensuring modular boundaries between OSS core and enterprise code.

What's the best way to add new core modules to an existing pipeline and envelope structure?

The best way to add core modules is to review project conventions in CLAUDE.md and implement adjustments directly within the src/edictum/ directory structure.

Does this approach to tool-contract governance work without external dependencies?

Yes, the OSS core standardizes tool-contract governance with zero external dependencies. It relies entirely on internal protocols for pipeline, envelope, and YAML engine operations.