00:00
Intro: AI as Copilot
Using AI, like GPT-5, to augment human cognition and improve overall processes.
00:42
AI Stack Orchestration
The theme of the month in the GSD lab, using AI tools effectively.
00:50
Version Thinking Prompt
Applying 'version thinking' to challenges and reverse-engineering success with GPT-5.
01:22
GPT-5 Context Window
GPT-5's improved context window and its impact on pattern recognition from data.
02:26
ConsciousStack Integration
Using GPT-5 with a dedicated folder for the ConsciousStack framework.
03:05
Identifying the Biggest Risk
GPT-5 identifies 'chronic overextension' as the main risk to ConsciousStack.
04:20
Applying the 6-3-1 Rule
Using the 6-3-1 rule for conscious stack design, tool categorization, and experimentation.
04:41
GPT-5's Stack Suggestions
GPT-5 suggests stacks for ecosystem growth engine with diagnostic, product, and community components.
05:07
Experimentation Limits
Limiting experimentation to two ideas max to avoid brand bleed and overextension.
06:44
Actionable Insights & Notion
Turning GPT-5 insights into actionable steps and integrating with Notion.
07:20
Core Stack Design
Knowing your core stack of tools to layer everything else on for efficiency.
07:56
AI Agents Orchestration
Incorporating AI agents and understanding core stacks for efficient automation.
08:48
StackMapper Tool
Introducing StackMapper: A tool for GSD lab members to map goal intents.
10:09
Manual vs. Digital Stacks
Balancing manual engagement with digital tools for a better understanding.
Summary
CopyDetected: English
Copy transcript
00:01
What's up, everybody?
00:02
So first up, I'm just gonna get my headphones connected.
00:08
So we are connected now.
00:10
But, yes, today, I wanna take you through how I use ChatGPT and, specifically, GPT five to use it more as a copilot as opposed to just a task master, for myself.
00:23
Because I think the biggest opportunity for AI and humans in terms of coming together is to actually help one another improve overall, right, and for us to be consciously aware of this.
00:35
So even though we're feeding a lot of data to AI, I think we can also use it as a way to improve our cognition.
00:42
And this month in our GSD lab, membership, the theme is AI stack orchestration.
00:50
And so often, when I'm on Twitter, I will see prompts that people share, and then I will actually go and try it out.
00:58
And if I find that it's good, I'll then add it to the GSE lab, resources library so that other members can try it out.
01:06
So this particular prompt, that you can see here, applying version thinking to my biggest challenge.
01:11
Instead of solving it directly, how would I guarantee failure?
01:15
Ask me a series of questions one by one about my current biggest challenge, then identify all the ways it could fail and then discuss how I can reverse engineer success.
01:22
So this is actually a great use of a prompt and use of AI, especially GPT five.
01:28
Because of GPT five, we now have a much larger context window, which means that it can look into patterns, a lot better than previous models based on your historical data.
01:41
Alright?
01:42
And so I've been testing this out over the the last week since GPT five came out, and the outputs, the results have actually been quite good.
01:51
It's really interesting because I'm seeing a lot of folks on the Internet essentially say that, like, oh, GPT five sucks.
01:58
It's not that much better.
01:59
But it goes back again to the sort of activities or tasks or prompts that you use with GBTs or AI in general.
02:09
And it's not about its ability to just do automation things better.
02:15
Because if that was the case, I think even automations that were available even pre AI might actually be better than some of what, you know, people are expecting now.
02:26
So I then went and asked, GPT five about this.
02:31
And you can see here, use the attached prompt on this problem.
02:35
Whatever you think is my biggest problem in regards to my entire ConsciousStack universe.
02:38
So ConsciousStack being part of my ConsciousStack design framework and methodology.
02:43
And then this is actually tied into a folder that I have dedicated to my entire conscious stack brand ecosystem universe with specific files that are part of the methodology and framework.
02:55
So inside GPT five, I'm asking this prompt within that folder so it has even more context.
03:02
Right?
03:02
But it can still tap into everything else that we've chatted about.
03:05
And so you can see here, your biggest risk, to making the entire ConsciousStack universe a true long term success is chronic overextension without a unifying operational spine.
03:15
And you can see that it is tapping into, a bunch of files that I already have in my framework and methodology.
03:23
K?
03:23
So instead it says in CSD terms, you've got a resonant innovator mind, but your operational system is still acting like a siloed innovator.
03:30
K?
03:31
Now what this tells me is that my mind, is operating at much higher levels, but my own stack is has still not caught up with where our mind is at.
03:44
And this is why I built conscious stacks, or conscious stack design because I wanted to allow users, allow people to have the ability to see what tools they're actually using, to see that mirror, and then to be able to reflect it back so that they can make conscious decisions around what to change, and why.
04:04
Okay?
04:05
So Brilliant Pilots, but without an always on mechanism that pulls them into coherent monetizable core stack.
04:10
If you solve that by building the operational equivalent of your six three one rule for the entire CSC ecosystem, the rest compounds all almost automatically.
04:20
Okay?
04:20
So it then used my own six three one rule for conscious stack design, which is essentially six total tools in a stack or category, three supporting tools, and then one anchor tool.
04:34
And that'll leave you about two tools within that stack or category to experiment with.
04:40
Okay?
04:41
And so anchor, the core spine, the one system everything flows into and out of, the CSC framework and certification pathway.
04:48
Right?
04:48
So this is great.
04:49
The supporting stacks, ecosystem growth engine.
04:52
So it's saying here diagnostic engine, product engine, and community engine.
04:56
Alright?
04:57
And because this is GPT five, you can see that it's actually pulling in other information from chats we've had in my entire chat g p t ecosystem.
05:07
Allowed experiments.
05:08
So this is innovation.
05:09
So this would be essentially any new ideas I have to help limit me also if I have a new idea to give myself just a two max to experiment with.
05:17
And if I'm if I find myself running any more than that, then that is a signal for me to stop.
05:23
K?
05:23
So it says it says here why this works for you.
05:25
Stop fragmentation.
05:27
You always know which bucket a project belongs in and which to kill quickly.
05:31
Compounds authority.
05:32
All content tools and offers reference the same core methodology.
05:36
Scales with integrity.
05:37
Experiments still feed your innovator energy without bleeding the brand.
05:41
Okay?
05:42
So this is essentially the stack that it's providing.
05:45
Now it says it can map your current entire CSD universe.
05:48
Alright.
05:49
So now it's going even into more specifics.
05:52
Right?
05:53
So it can give me the actual products that I should have for each of these stacks.
05:57
So this is actually applying conscious stack design not just to the tools, but you can see how it can be applied to the products and the product ecosystems.
06:05
Product engine.
06:06
Right?
06:06
Focus monitor app, c stack SaaS, etcetera.
06:09
Community engine.
06:11
Digital wayfinder inner circle, practitioner network, and then a lot of experiments, AI GSD challenges, which I'm currently running, and then Ring of Fire series.
06:19
And I like this, because this ties into a much larger, broader, mission that I have.
06:25
Down below are just some more ideas, and you can see here.
06:30
What this fixes immediately, you now have one home for every moving part.
06:34
No more orphan projects.
06:35
You have a rule based kill switch for overextension.
06:37
Nothing lives outside the 61 rule, and you can start aligning your own ops the same way you do for clients, which is a credibility boost.
06:44
Okay?
06:44
And, so then after, you know, going through this, this is when I would actually start to look at, okay.
06:54
How can I then turn this into something actionable?
06:56
And I'll ask questions to g p t five for that, and then I'll actually put pull all this stuff straight into my Notion.
07:02
So I actually have a plug in, called Save to Notion.
07:06
So here, I can select specific Notion databases that I can save my chat sessions directly into.
07:13
So here, if I wanted to, say, put this into my chat g p t to Notion, I can automatically do that.
07:20
And this is the way that I kind of close the gap within my own stack with the tools that I use the most.
07:26
Okay?
07:27
And so, for conscious stack design, this is, you know, imperative.
07:32
Right?
07:32
Knowing what your personal stack is of tools, then using that to layer everything else on or over.
07:40
And, from this, this should give you an idea of how to leverage things in the moment, use AI to support what you're already doing, and to ask deep questions that can lead to actions at the end of it.
07:55
Alright?
07:56
So this is, you know, just an example of how I use AI.
08:01
You can take this a step further by actually incorporating some of the, agents.
08:05
So there's an agent mode here where you can actually bring in or connect in other tools and add some of the stuff directly into those tools.
08:14
And that's actually parts of this month for our GSD lab members where we're looking at AI agent orchestration.
08:23
And, essentially, after you know what your core stack is, you can then start to layer in all these other agents to automate things even more.
08:29
Alright?
08:30
But if you don't know what your core stack is either with yourself or your team, it makes things very hard, very difficult to be able to coordinate at scale.
08:37
And I've seen this time and time again for businesses where they start trying to bring in, the latest and greatest, without really knowing what their core is, and that's just a recipe for disaster.
08:48
So if we go to Mapper, there is a tool, that I have available for GSD lab members.
08:56
But if you would like to get access to this, just let me know in the comments.
09:00
It's called StackMapper, and this will essentially allow you to, you know, put in your goal intent.
09:05
So it's like what?
09:07
Create an AI MVP, and you can start applying the six three one rule to essentially all your stacks.
09:18
Right?
09:18
So if my goal is to create an AI MVP, then I can start putting the categories or the substacks, that are related to that and start putting in the the tools that I use.
09:28
So let's say for LMs, let's say, chat g p t five.
09:34
I'll say here Claude Opus 4.1.
09:39
Let's see.
09:40
What else can I put?
09:41
I can put in Gemini 2.5 pro.
09:44
Right?
09:45
So on and so forth.
09:46
AI agents.
09:47
You know, I could put here Wind Surf, Cascade.
09:50
I could put ClientBot.
09:53
I can put, Cloud Code.
09:56
Right?
09:57
And so on and so forth.
09:59
So, you know, there's, like, vibe coding tools.
10:02
Right?
10:03
So this allows you to take a look at all the tools that you may be needing for a specific goal or intent.
10:09
And we actually already do have a tool, that can help you resolve some of this actually in real time, so it's automatically picking up on the tools that you use.
10:20
But I usually reserve that for clients or members after we've gone through this manually so that you can actually get a feel for what's going on with your tools before you start layering in all the digital aspects.
10:30
Because when you when you disengage your own senses from some of these tech aspects, you do not get a feel again for for what's going on.
10:40
And sometimes, this can lead to really large issues, down the track.
10:44
Because human beings, we need to engage our senses to remember.
10:48
And if we outsource too much, that becomes a problem.
10:50
So Vibe coding tools, you know, there are ones like Lovable, v zero dot dev, bolt dot new.
11:00
Right?
11:01
Rocket dot new.
11:03
Create dot x y z has has now become create anything, so I think that's called anything.
11:10
And so you'll see here, right, if I put in more what are some other ones?
11:15
Lovable, Bolt, v zero, Rocket.
11:19
I would just call it test one.
11:22
Right?
11:23
So we've maxed out, the six for our stack, and this is based out of the six three one rule.
11:29
So you can see how we have six max tools, three supporting, one anchor, and then two here are the, like, remaining experimental ones.
11:37
Okay?
11:39
So, with this, this is where you're able to see what your stacks are for your goal or intent.
11:46
And using the six three one rule, both horizontally and then even vertically, you'll see here on the life on the on the left, our actual stack.
11:55
Right?
11:55
So as I'm filling out these categories, it's doing the vertical work for you here.
12:00
And so the actual stack for this is looking at the anchor tools across each, substack or category, and it's putting that under your actual stack.
12:12
Okay?
12:13
Because there's a lot of multidimensionality, taking place, right, with tools and their interactions.
12:20
And the whole idea behind contra stack design is to help you get a better grasp around that, so you can feel it and then use technology, after the fact, right, consciously.
12:32
K?
12:32
So if you have any questions about this at all, let me know in the comments, and, hopefully, this was useful.
12:37
If you want a, the prompt as well, I can put it in the comments also.
12:42
Speak soon.
Made with Bullet