docs(hermes): canonical 7-deliverable bundle templates (Phase 07 §G + GPT §7) #174
No reviewers
Labels
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
pdurlej/platform!174
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "claude-orchestrator/hermes-canonical-bundle"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Per ADR-0012 (Phase 07 scope-lock §G) and GPT-5.5 Pro oracle review §7 (Hermes brief shape modernization): canonical 7-deliverable bundle templates for Hermes Upstream Agency.
Templates only. No runtime module. Hermes uses these ad-hoc; if voice-pitches become standing weekly artifact, optional
modules/rs2000/hermes-brief-renderer/follows in Phase 07 implementation.Files (8)
docs/hermes/README.mddocs/hermes/_templates/00_intake.mddocs/hermes/_templates/01_outcome_ost.mddocs/hermes/_templates/02_assumption_tests.mddocs/hermes/_templates/03_mini_prd.mddocs/hermes/_templates/04_analytics_observability.mddocs/hermes/_templates/05_delivery_acceptance_contract.mddocs/hermes/_templates/06_pitch.mdWhat changed from old shape (per GPT §7)
Voice pitch spec (per GPT §7)
pitch.m4a(audio) +deck.md(Marp)Workflow integration
What this PR DOES NOT do
modules/rs2000/hermes-brief-renderer/(Phase 07 §G conditional)Acceptance criteria
risk/process(touchesdocs/hermes/).Rollback
Pure additive (8 new files, 0 modified). Reverting deletes templates + README.
Refs
Codex effort needed
Review + merge. No runtime change. After merge: Hermes uses templates on next idea intake from Iskra delegation.
Role: orchestrator / drafter (claude)
Lane: Phase 07 §G parallel-track
Next: operator merges → next operator idea on Signal flows through new bundle structure.
Role: orchestrator (claude)
Intent: operator-feedback-applied
Needs owner: no
Two operator directives from voice-note 2026-05-11 07:26 (Hermes audio + tempo) — proposed as follow-up amendments, not blocking this PR:
1. Hermes voice specification — Polish, male, generic default + clone spike
Operator: "Ma generować język po polsku i to ma być jakby dla mnie. Hermes powinien być mężczyzną. Iskra dziewczyna już wystarczy. Hermes dzięki temu, że będzie chłopakiem, będzie łatwiej mi się jakby odróżnić."
Plus: "I czy klon mojego głosu? Male jakiś taki właśnie male, facet jakby — można zobaczyć, co jest możliwe — żeby RS2000 to generował albo VPS1000."
Proposed amendment to
docs/hermes/README.md§Voice pitch specification:Voice clone feasibility spike captured as separate follow-up issue (see #176 once opened).
2. Hermes tempo — size-class based, NOT single-number
Operator: "BMC + cały pitch, prezentacja — to może być cały model biznesowy nowego startupu, parę razy. VPC dla nowej funkcjonalności dla Iskry — dwa, trzy, parę razy w tygodniu. Mini-PRD czyli mała funkcjonalność — z każdego dnia jedną, dwie klepać."
Proposed amendment to
docs/hermes/README.mdadding## Size classessection:Next: these become follow-up PRs after this one merges. No change to this PR.
— claude, 2026-05-11 voice-note rejestracja
W9 rewrite/archive triage: closing this old PR as stale/superseded, not rejecting the underlying idea. Reason: Hermes bundle templates are May 11 phase-07 material; rewrite when Hermes/product loop becomes active again.
If the idea is still useful, it should be rewritten from current main as a smaller atomic PR or issue. No old branch should merge only because it is green.
Pull request closed