HAI-Agent-Workflow / docs /MANIFEST.md
smlflg's picture
Initial public upload from Projekte/HAI-Agent-Workflow
6fa7356 verified
|
Raw History Blame Contribute Delete
2.38 kB

MANIFEST

HAI V1.6 Artifacts

  • README.md
  • PATCHPLAN.md
  • CHANGELOG.md
  • MANIFEST.md
  • DIAGRAMS.md
  • REPOSITORY_MAP.md
  • assets/hai-agent-workflow-hero.svg
  • assets/hai-agent-workflow-hero.png
  • assets/hai-execution-loop.svg
  • assets/hai-execution-loop.png
  • assets/repo-lineage.svg
  • assets/repo-lineage.png
  • FEEDBACK_NEXTSTEP_HISTORY_CANARY_2026-06-05.md
  • LIVE_PROFILE_CANARY_NEXTSTEP_HISTORY_2026-06-05.md
  • live-profile-backups/2026-06-05-nextstep-history/
  • hermes-profiles/active/hai-agent/SOUL.md
  • hermes-profiles/active/hai-agent/config.yaml
  • hermes-profiles/active/hai-agent/skills/hai-pair-plan/SKILL.md
  • hermes-profiles/active/hai-agent/skills/hai-pair-execution-loop/SKILL.md
  • hermes-profiles/active/hai-agent/skills/hai-feierabend-podcast/SKILL.md
  • hermes-profiles/active/hai-agent/skills/voice/multivoice-readaloud/SKILL.md
  • hermes-profiles/active/hai-agent/skills/voice/multivoice-readaloud/scripts/multivoice_markdown_reader.py
  • hermes-profiles/active/hai-agent/skills/hai-execution-loop/SKILL.md
  • hermes-profiles/active/hai-agent/skills/hai-execution-loop/references/gemini-escalation.md
  • hermes-profiles/active/hai-agent/skills/*
  • hermes-profiles/active/hai-executer/SOUL.md
  • hermes-profiles/active/hai-executer/config.yaml
  • hermes-profiles/active/hai-validator/SOUL.md
  • hermes-profiles/active/hai-validator/config.yaml
  • hermes-registry/AGENT_REGISTRY.md

Preserve

  • Artifact-driven pre-briefing.
  • Explicit step types.
  • One recommended default for owner decisions, with max two real alternatives.
  • Fixed execution chain.
  • Exactly two Pair lanes maximum.
  • Worktree isolation for Pair lanes.
  • Feierabend podcast source and playback report under Projek-Managment/.
  • Human Gate.
  • No push by HAI.
  • No broad autonomous delegation.

Open / TODO

  • Zeitdruck als Regression-Trigger (2026-06-12): HAI-Agent ist unter Deadline-Druck ("muss heute live") direkt in Executor-Rolle gedriftet — hat selbst editiert, committed, gepusht statt den Execution-Loop zu triggern. Constraint muss architektonisch abgefangen werden: Zeitdruck darf die Loop-Schritte (Handoff → Executer → Validator → Human Gate) nicht überspringen. Vorschlag: Explizites "Urgency"-Signal im Step-Kontext, das den Loop nicht abkürzt sondern eher beschleunigt (z.B. Pair statt sequenziell).