Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Govern self-authored tools, skills, and reusable plans as capabilities

未关闭
#488 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
python

调研方向

该 issue 没有列出任何文件、测试或入口点,因此首先梳理 capabilities、authority manifests、qualification 和 invocation history 在 repository 中的表示位置。将验收标准作为 Definition of Done:隔离和独立 qualification、沙箱测试、拒绝扩大 authority、基于证据的撤销,以及可回放的审计历史。

由索引模型根据 Issue 内容生成。

描述

architecture enhancement

Origin

Deferred from the MVP proposed as a fresh realization of #485.

Goal

Allow agents to create, test, share, repair, and revoke tools, skills, and reusable plans safely.

Scope

  • One immutable, versioned Capability contract for tools, skills, and reusable plans.
  • Lifecycle: draft -> quarantined -> candidate -> trusted -> deprecated/revoked.
  • Input/output schemas, exact implementation hash, dependency lock, test/evidence bundle, ownership, and invocation history.
  • Enforced authority manifests for network, filesystem, subprocess, secrets, cost, and side effects; child authority may narrow but never widen.
  • Independent, use-based qualification; authors cannot approve their own capability.
  • Bug reports linked to exact invocations and expected/observed artifacts.
  • New-version repair and revocation rather than mutation or historical deletion.
  • Idempotency and compensation declarations for external effects.

Acceptance criteria

  • A run can author a capability in quarantine and cannot invoke it as trusted before independent qualification.
  • Qualification executes real tests inside the declared sandbox.
  • Authority widening is rejected and recorded.
  • A failing invocation can trigger independent triage and evidence-based revocation.
  • Historical runs remain replayable/auditable after revocation.
主要语言
Python
星标
3
派生
2
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

ContextLab/orchestrator 的其他 Issue

查看 ContextLab/orchestrator 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。