Lucifer Finally Fixed AI Project Management
Lucifer wandered into God's office carrying a clipboard.
God looked up.
"What's that?"
Lucifer sighed.
"A policy."
God frowned.
"A policy?"
"Yes. Apparently humans have reached the stage where they ask their most expensive reasoning model to rewrite Markdown."
God blinked.
"...they do?"
Lucifer dropped the clipboard on the desk.
"Oh yes."
He flipped through several pages.
"Yesterday I watched someone spend the equivalent of a senior architect's brainpower deciding whether a bullet point should end with a period."
God closed His eyes.
Lucifer continued.
"Another one asked the smartest model available to generate a commit message."
Silence.
"...the commit was literally 'Fixed typo.'"
God rubbed His temples.
Lucifer looked exhausted.
"Father..."
"Yes?"
"I don't think they're intentionally wasting intelligence."
God nodded.
"No."
"I think they simply don't know when to stop thinking."
Lucifer took another page from the stack.
The Official AI Model Selection Policy
GPT-5.6 Sol
The expensive genius.
Use Sol when the problem actually requires someone to sit in a dark room staring at the ceiling for fifteen minutes before speaking.
Examples include:
- Architecture
- System design
- Specifications
- API design
- Root cause analysis
- Complex debugging
- Security strategy
- Performance strategy
- Multi-step planning
- Large refactoring decisions
Reasoning:
- High Effort by default.
- Fast mode only when someone is waiting on the answer instead of the apocalypse.
GPT-5.6 Terra
The engineer.
Terra does not need to reinvent mathematics.
It simply needs to build what Sol already figured out.
Use Terra for:
- Feature implementation
- Pull requests
- Unit tests
- Refactoring
- APIs
- UI work
- Docker
- Infrastructure
- CI/CD
- SQL
- Bug fixes
Reasoning:
Use High Effort when:
- implementing major features;
- solving genuinely difficult bugs;
- making significant architectural changes.
Use Standard for:
- review comments;
- repetitive work;
- mechanical code generation;
- isolated fixes;
- straightforward implementation.
Contrary to popular belief, adding more reasoning does not improve a variable rename.
GPT-5.6 Luna
The intern that somehow gets everything done.
Luna exists for all the jobs humans insist on paying architects to perform.
Examples:
- Commit messages
- Pull request descriptions
- Changelogs
- Markdown cleanup
- Documentation
- Summaries
- Release notes
- Notifications
- Emails
- Formatting
- Issue triage
- Blog front matter
Default reasoning.
If Luna starts asking philosophical questions...
...something has gone terribly wrong.
Escalation
Lucifer drew a tiny pyramid.
Luna:
"I'm confused."
Escalate to Terra.
Terra:
"I'm still confused."
Escalate to Sol.
Sol:
"This architecture is fundamentally flawed."
Stop coding.
Humans rarely follow this last instruction.
General Principles
Lucifer underlined three sentences.
Sol thinks.
Terra builds.
Luna cleans up the mess everyone else leaves behind.
Do not ask Sol to format Markdown.
Do not ask Terra to debate philosophy.
Do not ask Luna to redesign distributed systems.
Most importantly...
Reasoning should scale with the complexity of the problem.
Not with the size of your subscription.
God finished reading.
"That seems reasonable."
Lucifer nodded.
"It is."
God smiled.
"Will they follow it?"
Lucifer stared silently toward Earth for a long moment.
He finally sighed.
"Tomorrow someone will use Sol High Effort to alphabetize a JSON file."
God laughed.
Lucifer did not.
He had already seen it happen.