القائمة
Implement features in the Edictum OSS core (src/edictum/). Use when the task touches pipeline, adapters, YAML engine, CLI, audit, envelope, or session. Core NEVER imports from ee/.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Fix a single audit issue in a git worktree. Creates a feature branch, follows fix-bug procedure, and creates a PR. Designed for parallel execution by spawned agents.
Transform a feature spec into audited, implementation-ready prompts. Use when starting a new feature, designing a new adapter, or turning a design doc into sequenced build steps. Covers spec audit against project rules, gap identification, decision collection, and prompt generation.
Sync documentation with code changes. Use on every PR that touches library code to keep docs accurate and consistent.
Manage files in the workspace directory
Make API requests and parse JSON responses
A helper for bird watching
| name | edictum-oss |
| description | Implement features in the Edictum OSS core (src/edictum/). Use when the task touches pipeline, adapters, YAML engine, CLI, audit, envelope, or session. Core NEVER imports from ee/. |
Read CLAUDE.md first. Understand the boundary principle before writing code.
Everything under src/edictum/ is the core library (MIT). This includes:
pipeline.py) — CheckPipeline, PreDecision, PostDecisionenvelope.py) — ToolCall, Principal, create_envelope()rules.py) — @precondition, @postcondition, @session_contract, Decisionyaml_engine/) — loader, evaluator, compiler (including sandbox compilation), templatesadapters/) — all 7 framework adaptersaudit.py) — AuditEvent, StdoutAuditSink, FileAuditSink, RedactionPolicysession.py) — Session, MemoryBackendcli/) — validate, check, diff, replay, testtelemetry.py) — OTel spans, GovernanceTelemetryserver/) — client components for connecting to edictum-serverTwo deployment units:
pip install edictum) — runs fully standalone. All 4 rule types (pre, post, session, sandbox), pipeline, 7 adapters, CLI, local audit, local approval.edictum-server) — separate deployment, coming soon. The Server SDK (pip install edictum[server]) provides the client-side connectivity.Core provides protocols and interfaces. The server SDK provides HTTP-backed implementations.
Most features work without the server. These require it:
| Feature | Core | Server |
|---|---|---|
| Rule evaluation (all 4 types) | Yes | -- |
outside: block / action: block | Yes | -- |
outside: ask / action: ask (dev) | Yes (LocalApprovalBackend) | -- |
outside: ask / action: ask (production) | -- | Yes (ServerApprovalBackend) |
| Audit to stdout/file/OTel | Yes | -- |
| Centralized audit dashboard | -- | Yes (ServerAuditSink) |
| Session tracking (single process) | Yes (MemoryBackend) | -- |
| Session tracking (multi-process) | -- | Yes (ServerBackend) |
| Hot-reload rules | -- | Yes (ServerRuleSource) |
## Scenarios section## When to use this section (see .docs-style-guide.md page structure pattern)tests/test_behavior/test_{module}_behavior.pypytest tests/test_docs_sync.py -vpytest tests/test_adapter_parity.py -vpytest tests/ -v then ruff check src/ tests/from __future__ import annotations in every filetests/test_{module}.pypytest tests/test_docs_sync.py -v catches thispytest tests/test_adapter_parity.py -v