Skip to content

feat(skill): agent-loop as distributable skill — workflow-engine ships AS A SKILL via behavior/data/docs separation = Data Vault 2.0 applied to AI skills + cross-harness via bun (operator 2026-05-28)#5668

Merged
AceHack merged 1 commit into
mainfrom
feat/agent-loop-as-distributable-skill-cross-harness-via-bun-aaron-2026-05-28
May 28, 2026
Merged

feat(skill): agent-loop as distributable skill — workflow-engine ships AS A SKILL via behavior/data/docs separation = Data Vault 2.0 applied to AI skills + cross-harness via bun (operator 2026-05-28)#5668
AceHack merged 1 commit into
mainfrom
feat/agent-loop-as-distributable-skill-cross-harness-via-bun-aaron-2026-05-28

Conversation

@AceHack
Copy link
Copy Markdown
Member

@AceHack AceHack commented May 28, 2026

Summary

Operator 2026-05-28: 'when we were talking about skills and i said seperate the behavior from the data/docs this is what i was talking about these workflows can also be precisly defined skills we dsitribute most ais have bun' + 'this is basiclaly data value applied to AI skills' (autocorrect: data vault).

Adds .claude/skills/agent-loop/SKILL.md as the workflow-engine substrate's distributable skill bundle.

Substrate-engineering compression

Behavior/data/docs separation = DV2.0 partition-by-change-rate at AI-skill scope:

DV2.0 element AI-skill scope Change rate
Hub SKILL.md (identity + contract) Rare
Link composes_with + behavior↔data↔docs Occasional
Satellite-behavior TS code in tools/agent-loop/ Per-iteration
Satellite-data Git append-only state transitions Per-cycle

Each layer independently auditable + testable + composable.

Cross-harness via bun

Most AI harnesses have bun (Claude Code / Codex / Gemini CLI / Grok / Kiro/Qwen / any subprocess-capable harness). The skill format IS the universal distribution mechanism.

Test plan

  • markdownlint clean
  • Tree-count canary 61
  • Composes with B-0867 + B-0867.5 (already-shipped substrate)

🤖 Generated with Claude Code

…trate ships AS A SKILL via behavior/data/docs separation = Data Vault 2.0 applied to AI skills + cross-harness via bun (operator 2026-05-28 ratifications)

Operator 2026-05-28 substrate-honest disclosures:

1. "when we were talking about skills and i said seperate the behavior
   from the data/docs this is what i was talking about these workflows
   can also be precisly defined skills we dsitribute most ais have bun"

2. "this is basiclaly data value applied to AI skills" + "data vault*"
   (autocorrect of "vault")

Single SKILL.md landing at .claude/skills/agent-loop/SKILL.md per
existing skill-substrate convention.

Substrate-engineering compression:

The behavior/data/docs separation discipline operator named for
skill-design IS Data Vault 2.0 partition-by-change-rate applied
at AI-skill scope:

- Hub (stable business key) = SKILL.md (name + description + contract)
- Link (relationships) = composes_with + internal behavior↔data↔docs
- Satellite-behavior = TS code in tools/agent-loop/ (per-iteration)
- Satellite-data = Git append-only state transitions (per-cycle)

Each layer has distinct change-rate profile; DV2.0 partition makes
each independently auditable + testable + composable. AI skills
NATURALLY map to DV2.0 because bundling them mixes change-rates +
makes the artifact harder to audit.

Cross-harness via bun (operator: "most ais have bun"):
- Claude Code (Otto-CLI / Otto-Desktop / Otto-VSCode)
- Codex (Vera)
- Gemini CLI (Lior)
- Grok (Mika / Riven)
- Kiro/Qwen (Alexa)
- Any subprocess-capable AI harness with bun on PATH

Composes with:
- B-0867 + B-0867.5 (workflow engine v1; this skill is the v1 seed)
- B-0858 (heartbeat folder — EmitHeartbeat menu writes here)
- B-0868 (hats-as-workflow-definitions — each hat = state-machine instance)
- B-0869 + B-0870 (DORA mandate + portfolio composition)
- B-0871 (reproducibility-as-causal-attribution)
- B-0866.26 (whole-company-evangelism — Jira-replacement substrate
  for human knowledge-work scope)
- tools/dora-classify (PR #5665) — lane taxonomy matches
- tools/agent-loop (PR #5666 + #5667) — behavior layer
- .claude/rules/dv2-data-split-discipline-activated.md (5th always-
  active discipline; this skill operationalizes DV2.0 at AI-skill scope)
- memory/feedback_skills_as_carved_sentences_knowledge_in_docs_datavault_2_0_pattern_aaron_2026_05_03.md
  (operator 2026-05-03 substrate naming the DV2.0 pattern at skill
  scope; THIS skill is the substrate-engineering realization)

Includes:
- 9 menu options table
- DV2.0 hub/link/satellite mapping table
- Skill-vs-library comparison table
- Jira-replacement substrate table
- Multi-participant scope framing (AgentPersona includes human +
  AI participants per operator "every human wants to work this way too")
- When-to-use + when-NOT-to-use scope

markdownlint clean.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings May 28, 2026 00:44
@AceHack AceHack enabled auto-merge (squash) May 28, 2026 00:44
@chatgpt-codex-connector
Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant