1
00:00:00,040 --> 00:00:03,720
It may be the fact that no one's
listening to this podcast, and 

2
00:00:03,720 --> 00:00:07,520
it's probably a bit of a bubble,
but it feels like right now 

3
00:00:07,520 --> 00:00:10,360
there's another zeitgeist in the
world of AI emerging. 

4
00:00:11,200 --> 00:00:15,320
And it's hard to give AI systems
true 24/7 contexts of everything

5
00:00:15,320 --> 00:00:18,880
in your life, your projects, and
to create what you could 

6
00:00:18,880 --> 00:00:22,200
describe as a true memory system
or a personal AI operating 

7
00:00:22,200 --> 00:00:25,320
system for your clod. 
And this second brain isn't 

8
00:00:25,360 --> 00:00:27,520
really for you, it's for your 
agents. 

9
00:00:27,840 --> 00:00:31,800
Most of the content online about
productivity and planning and 

10
00:00:31,800 --> 00:00:37,000
organization is optimising for 
human readability with good ways

11
00:00:37,000 --> 00:00:39,400
for us to take notes in 
different systems. 

12
00:00:39,400 --> 00:00:43,920
But the world is no longer for 
us and our second brain, it's 

13
00:00:43,920 --> 00:00:45,640
for agents having a second 
brain. 

14
00:00:46,320 --> 00:00:49,000
By the end of this episode, 
you'll have your own personal AI

15
00:00:49,000 --> 00:00:53,040
operating system by building a 
second brain for your agents, An

16
00:00:53,040 --> 00:00:56,480
exact file structure to copy the
different sections that you're 

17
00:00:56,480 --> 00:00:59,640
going to create to create a the 
different sections that you're 

18
00:00:59,640 --> 00:01:04,319
going to build to give fantastic
scalable structure for your 

19
00:01:04,319 --> 00:01:08,280
agent to do more work for you. 
And a daily routine that you can

20
00:01:08,280 --> 00:01:12,280
eventually automate, which will 
keep this continually updated. 

21
00:01:12,920 --> 00:01:14,240
This in the loop with Jack 
Horton. 

22
00:01:14,240 --> 00:01:32,120
I hope you enjoyed the show. 
So let's start where this wave 

23
00:01:32,760 --> 00:01:36,480
has come from, this like drive 
to build AI operating systems. 

24
00:01:37,360 --> 00:01:42,120
Now it hit mainstream popularity
recently because of Andre 

25
00:01:42,120 --> 00:01:46,320
Capathi posting online about his
MLM knowledge kind of wiki in 

26
00:01:46,320 --> 00:01:48,680
early April. 
And it's basically how he 

27
00:01:48,680 --> 00:01:51,240
organized his own notes so AI 
can read them. 

28
00:01:51,480 --> 00:01:54,200
And he sparked an explosion of 
different people and thought 

29
00:01:54,200 --> 00:01:57,840
leaders and influencers sharing 
how essentially they create 

30
00:01:57,840 --> 00:02:00,560
their own note system but for 
agents to read from. 

31
00:02:01,040 --> 00:02:05,360
But in reality, this has come 
from coding, as I said a good 

32
00:02:05,360 --> 00:02:08,240
number of episodes ago, probably
all the way back to that called 

33
00:02:08,240 --> 00:02:12,040
Co work episode. 
The huge revolution that hit 

34
00:02:12,720 --> 00:02:16,360
coding is just going to hit the 
entire rest of the world over 

35
00:02:16,360 --> 00:02:19,440
the next 12 to 18 months. 
And a big part of that has been 

36
00:02:19,440 --> 00:02:22,600
your structure of information 
that you feed to an agent. 

37
00:02:23,400 --> 00:02:24,520
Now I've started to touch on 
this. 

38
00:02:24,520 --> 00:02:27,200
I touched on the Co work 
episode, I touched it on the 

39
00:02:27,200 --> 00:02:31,840
skills episode, I touched it on 
the episode discussing automated

40
00:02:31,840 --> 00:02:34,160
scheduled tasks and and other 
new features they've just 

41
00:02:34,160 --> 00:02:37,320
released. 
And essentially this is a set of

42
00:02:37,320 --> 00:02:41,640
folders on your computer which 
are MD files, So plain text 

43
00:02:41,640 --> 00:02:44,440
files arranged in a particular 
order. 

44
00:02:44,720 --> 00:02:49,320
So whenever an agent you're 
working with starts its session,

45
00:02:49,320 --> 00:02:51,680
it can access it and then it 
will follow that folder 

46
00:02:51,680 --> 00:02:54,880
structure to only get the 
relevant information it needs at

47
00:02:54,880 --> 00:02:58,000
that exact moment. 
Now inside that folder going to 

48
00:02:58,000 --> 00:03:01,800
leave four kinds of thing. 
And once you see them as four 

49
00:03:01,800 --> 00:03:05,000
separate jobs, the architecture 
of this folder structure makes 

50
00:03:05,000 --> 00:03:07,960
sense. 
And just before I get into this,

51
00:03:09,080 --> 00:03:12,680
if you remember, for those that 
have been using Co work now, for

52
00:03:12,680 --> 00:03:16,120
those that are in, you know, in 
IDE and to do coding, you're 

53
00:03:16,120 --> 00:03:17,720
going to be very familiar with 
this. 

54
00:03:18,040 --> 00:03:22,400
But essentially local files on 
your desktop or your laptop is 

55
00:03:22,400 --> 00:03:24,200
the folder of this type of 
system. 

56
00:03:24,520 --> 00:03:27,280
So a folder structure. 
And essentially you're going to 

57
00:03:27,280 --> 00:03:30,080
have different folders within, 
or should I say subfolders 

58
00:03:30,080 --> 00:03:32,480
within a master folder. 
And for some of you that might 

59
00:03:32,480 --> 00:03:35,000
go well, that doesn't seem that 
special, but it's exactly how 

60
00:03:35,000 --> 00:03:38,480
the most efficient organizations
in the world are running the 

61
00:03:38,480 --> 00:03:41,480
system. 
It's how we run a lot of our 

62
00:03:41,480 --> 00:03:44,040
teams. 
Now there's a caveat to this, 

63
00:03:44,040 --> 00:03:46,720
which I think this is a moment 
in time and this is something 

64
00:03:46,720 --> 00:03:49,240
that you should use, but I mean 
mindset, this is the product 

65
00:03:49,240 --> 00:03:51,920
that we're currently building to
help with product development. 

66
00:03:51,920 --> 00:03:56,440
So engineering design, product 
management, which is a system to

67
00:03:56,440 --> 00:03:59,160
take us away from just relying 
on local files just, and it's an

68
00:03:59,200 --> 00:04:03,280
infinitely more scalable, but 
for a personal operating system,

69
00:04:03,920 --> 00:04:26,070
it's really, really powerful. 
So the first folder, or let's 

70
00:04:26,070 --> 00:04:30,710
say job, is identity. 
So that's the file that tells 

71
00:04:30,710 --> 00:04:34,110
the agent who you are, how you 
work, what you never do. 

72
00:04:34,710 --> 00:04:36,710
You know the bit that just 
shouldn't really ever change. 

73
00:04:36,710 --> 00:04:38,470
It might include your 
communication style, your 

74
00:04:38,470 --> 00:04:41,830
decision principles, maybe you 
know some of the rules that 

75
00:04:41,830 --> 00:04:44,470
you'd never break. 
The second is context. 

76
00:04:44,880 --> 00:04:47,080
So what's, what does the world 
look like today for you? 

77
00:04:47,360 --> 00:04:49,600
You know, what are the key 
projects that you're working on 

78
00:04:49,600 --> 00:04:51,840
over the next one, three, six 
months? 

79
00:04:52,360 --> 00:04:54,520
Who are the key people in that, 
in that world? 

80
00:04:55,080 --> 00:04:57,120
You know, who's your boss, who's
your colleagues? 

81
00:04:57,120 --> 00:04:58,800
What do they like? 
What do they don't like? 

82
00:04:59,320 --> 00:05:03,240
They might also be commitments 
you've made and you refuse to 

83
00:05:03,240 --> 00:05:05,920
relegate them. 
And they could also include the 

84
00:05:05,960 --> 00:05:09,200
active projects in flight. 
The third is your skills. 

85
00:05:09,200 --> 00:05:11,560
So these are repeatable 
workflows. 

86
00:05:11,640 --> 00:05:13,600
You know, we've talked about 
skills a few weeks ago. 

87
00:05:14,520 --> 00:05:17,600
There are multi step processes 
about how you approach different

88
00:05:18,080 --> 00:05:20,560
problems and situations and 
scenarios, whether it's a 

89
00:05:20,560 --> 00:05:25,240
script, an e-mail, a deal 
review, a weekly e-mail summary 

90
00:05:25,240 --> 00:05:26,640
to your boss, whatever it might 
be. 

91
00:05:27,200 --> 00:05:30,840
And the 4th is memory. 
So that's what happened, what 

92
00:05:30,840 --> 00:05:35,000
you decided, what open decisions
there are still essentially it's

93
00:05:35,000 --> 00:05:37,760
a session log from yesterday 
that the agent will pick up from

94
00:05:37,760 --> 00:05:40,520
every single day. 
This part in particular is where

95
00:05:40,520 --> 00:05:43,400
what we call Memex, our new 
product that it were releasing 

96
00:05:43,400 --> 00:05:47,120
at the moment, is essentially 
scaling because as you can 

97
00:05:47,120 --> 00:05:50,360
imagine, the amount of decisions
getting logged to give your 

98
00:05:50,360 --> 00:05:54,080
agent a second brain is insane. 
So that's where we've had to 

99
00:05:54,080 --> 00:05:57,440
build our own internal tool to 
fix because we've got an entire 

100
00:05:57,440 --> 00:06:00,000
company trying to manage this 
type of system. 

101
00:06:01,080 --> 00:06:04,600
Anyway, to summarize those types
of jobs you've got, essentially 

102
00:06:05,040 --> 00:06:09,800
identity is going to capture the
unchangeable and then context 

103
00:06:09,800 --> 00:06:12,320
captures the things that are 
going to perish. 

104
00:06:12,320 --> 00:06:14,680
So you're going to update and 
change them every month, 3 

105
00:06:14,680 --> 00:06:18,280
weeks, 2 days, six months. 
Skills capture the things that 

106
00:06:18,280 --> 00:06:22,160
are very repeatable and memory 
captures the historical 

107
00:06:22,160 --> 00:06:23,640
conversations that you've been 
having. 

108
00:06:24,360 --> 00:06:29,720
So 4 jobs all sitting inside one
parent folder structure that any

109
00:06:29,720 --> 00:06:33,680
agent can read. 
Now the shape of that parent 

110
00:06:33,680 --> 00:06:36,480
folder, in case you're, you 
know, on a walk you're trying to

111
00:06:36,480 --> 00:06:38,760
imagine this is, is roughly as 
follows. 

112
00:06:39,480 --> 00:06:43,400
At the top of that folder is 
what we call a master file. 

113
00:06:44,400 --> 00:06:47,680
So essentially by convention in 
core code that's called the claw

114
00:06:47,680 --> 00:06:50,160
dot MD. 
But in other tools, the same 

115
00:06:50,160 --> 00:06:53,120
content goes as essentially a 
set of instructions or folder 

116
00:06:53,120 --> 00:06:55,880
instructions that essentially 
tells the agent how to 

117
00:06:55,880 --> 00:06:58,640
understand and navigate the 
folder structure. 

118
00:06:59,280 --> 00:07:02,600
That master file holds the 
identity layer plus pointers to 

119
00:07:02,600 --> 00:07:04,720
everything else. 
So essentially you're directing 

120
00:07:04,720 --> 00:07:08,080
the AI when and when not to use 
these sets of systems and 

121
00:07:08,080 --> 00:07:12,040
information. 
Alongside it sits A context 

122
00:07:12,040 --> 00:07:13,480
folder. 
So that will hold files are 

123
00:07:13,480 --> 00:07:18,400
active projects dot MD, recent 
decisions dot MD, stakeholders 

124
00:07:18,400 --> 00:07:24,080
dot MD, constraints dot MD, and 
then a skills folder. 

125
00:07:25,120 --> 00:07:28,200
And that skills folder will have
the subfolder and it will have 

126
00:07:28,200 --> 00:07:31,240
all the skills inside it. 
So that could be your e-mail 

127
00:07:31,240 --> 00:07:36,000
skill, your shout at someone's 
skill, your apology skill, you 

128
00:07:36,000 --> 00:07:38,680
know, whatever it might be. 
Then finally you've got a memory

129
00:07:38,680 --> 00:07:42,720
folder, which is essentially a 
big memory MD document with 

130
00:07:42,720 --> 00:07:45,800
topic specific files. 
So that will have a daily folder

131
00:07:45,800 --> 00:07:49,440
with one log per session. 
So it might have today's date or

132
00:07:49,440 --> 00:07:52,600
tomorrow's date. 
So then every sets of 

133
00:07:52,600 --> 00:07:54,880
conversations you have with 
different agents, you can update

134
00:07:54,880 --> 00:07:57,600
that log. 
So essentially, there you go, 6 

135
00:07:57,600 --> 00:07:59,920
folders. 
You got one master file to tell 

136
00:07:59,920 --> 00:08:02,280
the agent how to use all of it. 
It's all just text. 

137
00:08:03,440 --> 00:08:06,680
And that's the architecture. 
And by creating that scalable 

138
00:08:06,680 --> 00:08:10,200
system, you don't ever have to 
speak to an agent as if it 

139
00:08:10,200 --> 00:08:11,640
doesn't understand what you're 
trying to achieve. 

140
00:08:11,640 --> 00:08:14,080
It just has all the context you 
need immediately. 

141
00:08:14,480 --> 00:08:17,280
And then when you try and choose
the very best model and have 

142
00:08:17,280 --> 00:08:19,800
maximum reasoning mode on there,
you're going to get the best 

143
00:08:19,800 --> 00:08:22,240
results. 
And because you're not trying to

144
00:08:22,240 --> 00:08:25,600
give it too much context in one 
setting, you can also reduce the

145
00:08:25,600 --> 00:08:28,400
context window and therefore 
have less token usage. 

146
00:08:46,120 --> 00:08:47,960
And now we're going to move on 
one step deeper. 

147
00:08:49,240 --> 00:08:52,760
Let's write the master file 
since you know that's the the 

148
00:08:52,760 --> 00:08:56,400
doorway the agent will step 
through when understanding the 

149
00:08:56,400 --> 00:08:58,320
rest of your personal operating 
system. 

150
00:08:58,880 --> 00:09:00,520
So Section 1 might be a company 
overview. 

151
00:09:00,520 --> 00:09:02,720
You know, two or three sentence 
about who you work for, what 

152
00:09:02,720 --> 00:09:05,600
they do, what stage of the 
business there are Section 2 

153
00:09:05,600 --> 00:09:08,800
will be current priorities. 
So top three or four things 

154
00:09:08,800 --> 00:09:12,000
you're trying to do this next 
quarter specific outcomes rather

155
00:09:12,000 --> 00:09:15,400
than, you know, random, you 
know, themes, you know, maybe 

156
00:09:15,400 --> 00:09:17,040
hire two people by the end of 
March. 

157
00:09:18,200 --> 00:09:21,360
Section 3 is you know your voice
and tone, how you communicate 

158
00:09:21,360 --> 00:09:24,440
the words you band, the style 
references you like to write 

159
00:09:24,440 --> 00:09:27,240
towards. 
For example, I have an entire 

160
00:09:27,240 --> 00:09:29,720
set of information on banned 
words. 

161
00:09:30,880 --> 00:09:33,600
I'll get some of them up. 
Corporate therapist book voices 

162
00:09:33,600 --> 00:09:35,920
banned. 
This is a powerful opportunity 

163
00:09:35,920 --> 00:09:39,400
to lean into our strengths. 
A meaningless conclusion. 

164
00:09:39,400 --> 00:09:42,880
AI loves meaningless conclusions
at the end of a paragraph. 

165
00:09:43,320 --> 00:09:45,320
You know. 
Ultimately the goal of an 

166
00:09:45,320 --> 00:09:48,440
organization is to be more 
resilient and agile. 

167
00:09:49,120 --> 00:09:51,640
Pointless or the keynote 
punchline. 

168
00:09:51,640 --> 00:09:55,720
Voice the forced negation 
stating the obvious back all the

169
00:09:55,720 --> 00:10:00,040
time over a flattery and 
excessive adverb. 

170
00:10:00,040 --> 00:10:03,520
So I've got an entire I mean, 
gosh, it's so big at this point,

171
00:10:04,160 --> 00:10:06,560
right? 
Maybe 1200 Word document on all 

172
00:10:06,560 --> 00:10:09,320
the things I absolutely hate. 
Section 4 will be your key 

173
00:10:09,320 --> 00:10:10,880
relationship. 
So it might be people at work 

174
00:10:10,880 --> 00:10:15,560
could be people at home. 
So it might be, you know, my CEO

175
00:10:15,720 --> 00:10:18,960
is called X. 
They care about why they respond

176
00:10:18,960 --> 00:10:24,120
better to this and this type of 
and topic area or behaviour. 

177
00:10:24,640 --> 00:10:26,840
So just information that's 
relevant to the people you work 

178
00:10:26,840 --> 00:10:32,080
with and also their skills. 
Section 5 is standing decisions,

179
00:10:32,320 --> 00:10:34,440
so things you've already agreed 
on and don't want the agent to 

180
00:10:34,440 --> 00:10:36,680
have to re question. 
And section 6 is things you 

181
00:10:36,680 --> 00:10:39,760
don't do, the constraints, maybe
the things that you've got out 

182
00:10:39,760 --> 00:10:41,800
of scope you refuse to consider 
doing. 

183
00:10:42,360 --> 00:10:46,560
You know, I don't do X before 
9:00 AM, whatever it might be. 

184
00:10:47,160 --> 00:10:50,360
And that's the template, that's 
the whole file should be about 

185
00:10:51,400 --> 00:10:54,520
150 lines roughly. 
And if something feels like I 

186
00:10:54,520 --> 00:10:58,720
want to add more words than 150 
to 200 lines, you should 

187
00:10:58,720 --> 00:11:00,560
reference the skills. 
And we'll come on to this in a 

188
00:11:00,560 --> 00:11:02,440
minute. 
But you say use X skill under Y 

189
00:11:02,440 --> 00:11:06,200
situation, and that can then 
have many, many more texts or 

190
00:11:06,200 --> 00:11:09,160
lines of text. 
And 200 is the really important 

191
00:11:09,160 --> 00:11:13,360
number here because Anthropics 
actual documentation says that 

192
00:11:13,360 --> 00:11:18,920
any master file over 200 lines 
will essentially just be 

193
00:11:18,920 --> 00:11:22,480
ignored. 
So the agent will only read 199 

194
00:11:22,480 --> 00:11:25,280
or 200 lines of the 200 line and
documents. 

195
00:11:25,280 --> 00:11:30,200
So if you made a 500 word one, 
it won't actually be useful, it 

196
00:11:30,200 --> 00:11:50,760
won't be used by the agent. 
So that's the system, that's the

197
00:11:50,760 --> 00:11:53,080
master file to give your agents 
instructions. 

198
00:11:53,080 --> 00:11:54,600
And I'm going to go into two 
more things. 

199
00:11:54,600 --> 00:11:56,560
So it's going to be the skills 
folder and the structure. 

200
00:11:56,800 --> 00:11:59,240
I'm not going to spend too much 
time here because I actually 

201
00:11:59,240 --> 00:12:02,360
encourage you to go and use or 
listen to the skills episode. 

202
00:12:03,280 --> 00:12:05,840
And I'm also going to describe 
the daily routine you must 

203
00:12:05,840 --> 00:12:07,960
follow to make this entire 
system work. 

204
00:12:08,680 --> 00:12:12,520
So starting with the skills 
folder, essentially this whole 

205
00:12:12,520 --> 00:12:15,880
thing stops obviously being just
static instructions for an 

206
00:12:15,880 --> 00:12:17,000
agent. 
And then it becomes like an 

207
00:12:17,000 --> 00:12:21,320
operating system when you 
essentially have lots of skills 

208
00:12:21,320 --> 00:12:25,160
and scheduled tasks working. 
So you know, every time you have

209
00:12:25,160 --> 00:12:28,600
a workflow that you do more than
two, three times, you should 

210
00:12:28,600 --> 00:12:31,120
turn it into a skill. 
And you're going to have a 

211
00:12:31,160 --> 00:12:34,240
folder that is going to have all
of your skills inside it. 

212
00:12:34,600 --> 00:12:36,680
And the agent should just be 
able to structure it. 

213
00:12:36,680 --> 00:12:41,440
So if you've opened desktop 
Commander or if you're allowed 

214
00:12:41,560 --> 00:12:45,200
the agent to take control of 
your local files, just tell it 

215
00:12:45,200 --> 00:12:48,040
to organize the skills, put it 
inside the folder structure that

216
00:12:48,040 --> 00:12:51,400
you created. 
Again, I would say there's tell 

217
00:12:51,920 --> 00:12:54,840
cords or tell whatever system 
that you're using to do it for 

218
00:12:54,840 --> 00:12:57,600
you. 
It could be discovery and 

219
00:12:57,600 --> 00:13:00,640
conversation prep and you could 
have a skill there that before 

220
00:13:00,640 --> 00:13:05,640
any call generate 5 hypothesis 
LED questions maybe to this 

221
00:13:05,640 --> 00:13:10,320
prospects industry and always 
frame questions as a hypothesis 

222
00:13:10,320 --> 00:13:13,080
to test, not a fact because we 
want them to confirm. 

223
00:13:13,480 --> 00:13:16,200
Could be as simple as that or 
something highly complex. 

224
00:13:16,560 --> 00:13:18,000
Some people have been quite 
ambitious. 

225
00:13:18,000 --> 00:13:22,080
They've got literally like 24/7 
content engine runs going, 

226
00:13:22,440 --> 00:13:25,920
generating ideas, drafting 
scripts, writing SOP's, creating

227
00:13:25,920 --> 00:13:28,320
slide decks, just doing so so 
much. 

228
00:13:28,320 --> 00:13:31,040
But that that's going to cost 
you an absolute fortune. 

229
00:13:31,560 --> 00:13:34,040
And the important thing is that 
once you build this architecture

230
00:13:34,040 --> 00:13:39,400
that I'm describing, you can 
really start to turn it into an 

231
00:13:39,400 --> 00:13:42,600
operating system because 
identity tells the agent who's 

232
00:13:42,600 --> 00:13:45,400
running the workflow, Context 
tells it the current state of 

233
00:13:45,400 --> 00:13:50,320
the world, skills tell it how to
actually run that specific task.

234
00:13:51,040 --> 00:13:54,280
And as I'll come on to it in a 
minute, you'll have a daily log 

235
00:13:54,280 --> 00:13:57,320
system that will keep track of 
all major decisions that are 

236
00:13:57,320 --> 00:13:59,760
made. 
And all of this can be happening

237
00:13:59,760 --> 00:14:03,960
on a scheduled routine. 
So every time the agent is doing

238
00:14:03,960 --> 00:14:05,160
this task, you don't need to 
prompt it. 

239
00:14:05,160 --> 00:14:07,440
It is just taking all the 
information that you've already 

240
00:14:07,440 --> 00:14:10,640
built through this architecture.
And this comes on to the final 

241
00:14:10,640 --> 00:14:14,400
part, which is that daily 
session log loop that I 

242
00:14:14,400 --> 00:14:17,280
mentioned right at the start. 
So before we end every single 

243
00:14:17,280 --> 00:14:19,120
session, we're now going to 
write a session log. 

244
00:14:19,760 --> 00:14:22,520
We're going to literally tell 
the agent write a session log. 

245
00:14:23,640 --> 00:14:27,280
It's going to cover what we 
worked on with the agent, and it

246
00:14:27,280 --> 00:14:28,920
should only be about 3 bullet 
points Max. 

247
00:14:29,160 --> 00:14:32,320
You can turn this into a skill. 
So you can go slash daily log 

248
00:14:32,480 --> 00:14:34,200
and tell it where to store that 
information. 

249
00:14:34,200 --> 00:14:38,000
So store this in X place within 
the file structure I've created 

250
00:14:38,480 --> 00:14:42,080
and label it by the day of the 
week and the time we made it. 

251
00:14:42,760 --> 00:14:44,800
And it should, yeah, as I said, 
it should cover what we that 

252
00:14:44,800 --> 00:14:48,160
what you and the agent worked 
on, the decisions made with any 

253
00:14:48,160 --> 00:14:51,040
reasoning, any open questions 
that are going to be need to be 

254
00:14:51,040 --> 00:14:54,840
covered next time, any files 
that were touched and anything 

255
00:14:54,840 --> 00:14:58,320
in the memory MD that should be 
updated based on the session or 

256
00:14:58,920 --> 00:15:01,160
anything that needs to be 
changed to skills or anything 

257
00:15:01,160 --> 00:15:02,560
else as a result of that 
session. 

258
00:15:03,120 --> 00:15:05,480
So those were very highly 
structured because the agent can

259
00:15:05,480 --> 00:15:09,040
then scan it and we'll just have
that information immediately. 

260
00:15:10,440 --> 00:15:11,480
And you can get quite clever 
here. 

261
00:15:11,480 --> 00:15:14,920
You could run a scheduled task 
called weekly review where on a 

262
00:15:14,920 --> 00:15:18,040
Sunday, for example, where it 
reads all of the daily journals 

263
00:15:18,040 --> 00:15:21,840
or updates or logs, maps them 
against annual objectives, key 

264
00:15:21,840 --> 00:15:26,760
priorities, and essentially give
a review of progress and things 

265
00:15:26,760 --> 00:15:28,160
that we need to make sure we do 
next week. 

266
00:15:29,320 --> 00:15:31,040
So you can do quite clever 
things with this as well. 

267
00:15:31,040 --> 00:15:33,520
So they help progress other 
initiatives you might be trying 

268
00:15:33,520 --> 00:15:36,040
to get through. 
And anytime you you find it 

269
00:15:36,040 --> 00:15:39,400
going wrong, tell it to update 
the master doc, tell it to 

270
00:15:39,400 --> 00:15:41,960
update something in the system 
to improve this. 

271
00:15:41,960 --> 00:15:43,760
So it's continually growing and 
improving. 

272
00:15:44,280 --> 00:15:48,360
So yeah, let's let's wrap up. 
So I guess my call to action to 

273
00:15:48,360 --> 00:15:52,360
everyone listening is go and get
on this properly. 

274
00:15:52,360 --> 00:15:55,840
You know, set up a folder, 
dedicate an hour, I'll put it 

275
00:15:55,840 --> 00:16:01,200
inside a link in the Apple and 
Spotify podcast show notes so 

276
00:16:01,200 --> 00:16:04,320
you can get access to this. 
But go and create that 

277
00:16:04,320 --> 00:16:07,920
substructure or that folder 
structure with those subfolders.

278
00:16:08,160 --> 00:16:12,320
It'll take you less than an hour
and suddenly you'll start to be 

279
00:16:12,320 --> 00:16:14,440
able to create a true AI 
operating system. 

280
00:16:14,920 --> 00:16:17,760
And I bet if you do that, by the
end of the week, the agent's 

281
00:16:17,760 --> 00:16:19,840
going to know more about you and
your work. 

282
00:16:19,840 --> 00:16:23,400
And just save so much time of 
no, don't do it like this, do it

283
00:16:23,400 --> 00:16:27,400
like that type conversations 
that that one hour will save you

284
00:16:27,400 --> 00:16:31,320
many, many more hours. 
Anyway, thank you for listening 

285
00:16:31,320 --> 00:16:32,960
and I'll see you next time.
