Scoring & Tiers

Before Prometheus dispatches a task, it scores it. The score determines the tier, and the tier determines how many agents get involved and how much review the work receives before it ships.

The Fire Scoring System

Every task is scored across seven factors, each worth 0-3 points.

Factor	What It Measures
Files	How many files the change touches
Components	How many distinct system components are involved
Dependencies	How much the change relies on or affects other systems
Familiarity	How well-understood the code or domain is going in
Reach	How many users or systems are affected downstream
Reversibility	How hard the change is to undo if it’s wrong
Security	Whether the change touches auth, credentials, or sensitive data

The seven scores sum to a total between 0 and 21. That total maps to a tier.

Tiers

Tier	Score	Description	Response
Ember	0-2	A spark	Automata or single Hephaestus roundtrip
Flame	3-5	Needs attention	Hephaestus roundtrip, optional Daedalus
Blaze	6-8	Serious heat	Athena scope → Hephaestus → Daedalus
Blaze+	9-12	Demands respect	Full reconnaissance, multi-agent
Conflagration	13+	Everything burns if wrong	Full panel including Eris and Moirai

Review Panel Tiers

Scoring also determines the size and shape of the review panel that checks the work before it ships:

• Glance — a quick pass, appropriate for Ember-tier work
• Standard — a normal review, appropriate for Flame-tier work
• Thorough — deeper scrutiny, appropriate for Blaze-tier work
• Full — the complete panel, appropriate for Blaze+ and Conflagration-tier work
• Security-Primary — led by Argus, triggered whenever the security factor scores high regardless of overall tier

Note

The key insight: scoring isn’t bureaucracy — it’s how Prometheus decides how many eyes watch the fire. A one-line config change and a schema migration touching production data are not the same kind of risk, and they shouldn’t get the same review.