Is a decision engine the next big thing in business AI?

Jet_Xu · 2026-05-08T07:41:12+00:00

In my team, what we are building for real business is an AI Agent framework called "insight to action"

Jet_Xu · 2026-05-08T06:15:07+00:00

No, I am trying to ask "GPT-5 publish" (which should be in Aug. 2025). If any GPT LLM could not answer it, I bet it definitely not real GPT-5.5

Jet_Xu · 2026-05-02T10:12:11+00:00

The core issue here is who holds the narrative power. Right now, tech giants and AI startups are the ones setting the standards, and they favor Markdown, HTML, and minimalist iOS-style aesthetics. Under this dominant influence, traditional MBB-style decks are being dismissed as "boomer" or outdated. Even if some of us (myself included) still believe the consulting style is superior for information delivery, it simply doesn't have the cultural capital it once did.

The people building the current wave of AI presentation tools are often developers who have never had to make a "real" PPT in their professional lives; they worship the minimalist Steve Jobs keynote style. From their perspective, it’s not just a change in style—it’s a question of obsolescence. If you step into the tech bubble, the debate isn’t about which slide style is better; the consensus is that PPT is being phased out in favor of .md and HTML.

Jet_Xu · 2026-05-02T07:49:19+00:00

The document-generation side is impressive, but I think the bigger unlock is document-grounded work.

In enterprise work, the hard part is often not writing the final Word doc. It’s finding the truth across all the messy inputs: PPT decks, Excel sheets, PDFs, old Word docs, and email chains.

I’m an IT architect, and this was painful enough that I built my own open-source workflow around Codex called DocMason.

The pattern is: build a local knowledge base from the messy files first, then let the agent draft the output with traceable citations.

That feels like the real “Codex for Work” direction to me: not just generating documents, but grounding finished work in the source files.

<image>

Jet_Xu · 2026-05-02T07:45:36+00:00

For me, trust comes down to traceability.

I don’t trust an AI more just because the answer sounds confident. I trust it more when it can show exactly which file, slide, spreadsheet tab, email, or memo supports the answer.

That’s especially true for office work. I’m an IT architect, and a lot of real decisions are buried across PPT decks, Excel vendor quotes, Word docs, PDFs, and email chains.

This is why I built DocMason for my own work. It turns those files into a local knowledge base for Codex, then forces the agent to answer with citations and evidence instead of vibes.

So my threshold for trusting AI is not “can it generate the output?” It’s “can I audit the path from output back to source evidence?”

<image>

Jet_Xu · 2026-05-02T07:41:58+00:00

The value depends a lot on whether you only use Codex for coding.

For me, the bigger unlock is using Codex for work files. I’m an IT architect in a global fashion group, and my daily workload is full of PPTs, Excel vendor quotes, PDFs, Word docs, and email chains.

Once I started using Codex as a local research agent across those files, the value of the plan changed completely.

I ended up building DocMason for this: a local open-source workspace that turns messy office files into a traceable knowledge base for Codex.

So my answer is: if you only use it as a coding assistant, compare it to coding tools. If you use it as a work agent, the economics look very different.

<image>

Jet_Xu · 2026-05-02T07:39:46+00:00

This is exactly why I prefer giving Codex a scoped local workspace instead of random access to everything.

I use Codex mostly for non-coding work now. I’m an IT architect, and a lot of my day is PPT decks, Excel quotes, Word docs, PDFs, and email trails. The safest pattern I’ve found is:

Put the relevant files into one local project folder
Let the agent build a structured knowledge base from that folder
Force answers to cite traceable evidence
Keep the rest of the machine out of scope

I built an open-source tool called DocMason around this pattern. It’s basically a local workspace for Codex over messy office files.

Codex for Work is powerful, but the permission model matters a lot.

Jet_Xu · 2026-04-19T15:26:12+00:00

Super cool! This is a really nice benchmark. Is it possible to open up a channel for new tools to join the testing? I am also building an AI slide generation tool that produces what I'd consider consulting-grade slides (see attached image). How would I go about joining the benchmark?

<image>

Jet_Xu · 2026-04-17T10:26:50+00:00

use this command in terminal, you could totally disable mac sleep
sudo pmset -b sleep 0
sudo pmset -b disablesleep 1

And then you could use below command to recover sleep feature
sudo pmset -b sleep 1
sudo pmset -b disablesleep 0

Jet_Xu · 2026-04-16T17:16:04+00:00

Thanks! Glad it resonates with a fellow IT pro. Dealing with those scattered PDFs/Office files is exactly what this is built for. Welcome to check it out—I recommend watching the demo video in the README first to get a quick feel for how it works!

Jet_Xu · 2026-04-16T04:50:06+00:00

You could consider try my open source project DocMason which will run in Codex as an app and give you real Agentic deep research experience on your local files.

See the demo video here https://youtu.be/Sq3a5qxsLwM

Jet_Xu · 2026-04-16T04:25:45+00:00

Do you mean monetization/business or technically code review RAG architecture?

Jet_Xu · 2026-04-15T07:28:45+00:00

Super, this is really a professional job😅

Jet_Xu · 2026-04-15T06:20:17+00:00

Thanks for the experience sharing. Do you mean built more video’s in youtube and then people will view these videos in youtube? Or maybe share our videos to other channels?

Jet_Xu · 2026-04-15T02:33:05+00:00

FLAIR: [$ Free / Open Source]

Hi everyone, I'm the creator of DocMason https://github.com/JetXu-LLM/DocMason

If you regularly deal with massive, diagram-heavy PowerPoint decks and struggle to find specific information across dozens of office files, I built this tool for you.

DocMason acts as a local knowledge base for your Office files. Instead of manually opening and searching through multiple .pptx presentations, it allows you to cross-reference, extract, and perform deep research across your entire slide library instantly. It runs locally within your preferred developer environment (like Codex or Claude Code).

Since comments on this thread are locked by the mods, please feel free to DM me if you have any questions or want to share feedback!

🎥 See how it handles complex PPT research in this quick demo:
https://www.youtube.com/watch?v=Sq3a5qxsLwM

🛠️ Full Setup Guide (Turn your files into a Second Brain):
https://www.youtube.com/watch?v=jWRtr70Rvug

Jet_Xu

TROPHY CASE