Zeus Feedback

3) Optional metrics enrichment

If .zeus/scripts/collect-metrics.sh exists, ask for permission and run:

bash .zeus/scripts/collect-metrics.sh

Merge output into feedback evidence.

4) Run attribution analysis

Read:

• completed tasks in .zeus/{version}/task.json
• recent .zeus/{version}/ai-logs/*
• previous feedback history
• recent git commits (git log --oneline -20)

Compute candidate task attribution with confidence score:

• high >= 0.80
• medium 0.50-0.79
• low < 0.50

5) Evaluate evolution signal

Set requires_new_version true when:

• gap is structural (not a normal iteration),
• repeated unmet need appears across feedback cycles,
• target segment diverges from current version strategy.

6) Write feedback artifact

Create .zeus/{version}/feedback/{YYYY-MM-DD-HHmmss}.json including:

• raw data,
• attribution list,
• evolution signal,
• roadmap absorption flag.

7) Append evolution timeline

Append a FEEDBACK record in .zeus/{version}/evolution.md.

8) Write AI log

Create .zeus/{version}/ai-logs/{ISO-ts}-feedback.md.

9) Ask for decision

If evolution signal is true, offer:

• A) start /zeus:evolve
• B) backlog in current roadmap
• C) ignore suggestion

10) Apply selected action

• A: invoke evolve with gap context
• B: append roadmap backlog item
• C: record-only outcome

Output contract

• one feedback JSON artifact,
• one evolution entry,
• one AI log,
• one explicit next-step decision.

Agent collaboration

Use zeus-analyst for attribution scoring and version-evolution recommendation quality.