►
A
Yeah,
okay,
here
we
go
yeah
are
we
here
are
we
live
all
right,
live
from
wonderland,
okay,
so
sweet?
Okay.
So
where
are
we
at?
Well?
Let
me
just
say:
okay,
so
sid's
here
sid
might
be
asking
some
questions
along
the
way,
and
you
want
to
say
I
said
you
just
say
hello,
all
right.
That's
it
sweet!
Okay!
A
Today
we're
going
to
be
looking
at
the
community
standards,
and
so
we're
going
to
be
moving
on
from
the
the
stuff
that
we're
we're
already
moving
into
the
next
the
next
month.
But
you
know
we're
not
really
writing
these
in
order.
So
all
right,
so
we
just
generated
threats,
md
right
and
the
last
chapter
one
is
about
generating
threats,
md
and
and
john
whiteman,
and
I
presented
on
that
at
absent,
pacific
northwest.
A
Was
it
last
weekend
on
saturday?
So
then
that
recording
is
not
yet
live
on
their
youtube,
but
we'll
post
that
when
it
is
so
then,
and
there
in
that
demo
right,
we
saw
some
of
the
work
from
chapter
one
where
we
that
that
tutorial
series
in
chapter
one
that
word
where
we're
doing
to
build.
You
know
the
the
threats
md
files
so
as
to
go
down
the
dependency,
rabbit,
hole
again
right
and
figure
out.
A
What
is
that
tree
of
dependencies
that
are
going
to
be
within
our
threat
model
right,
so
we're
so
we're
just
jumping
ahead
a
little
bit
here
due
to
some
other
stuff
that
I
have
to
do
so.
You
know
we're
we're
taking
what
we
can
we're,
what
we
can
get
where
we
can
get
it
so
right
now
we're
gonna
jump
into
what
we
would
have
otherwise
done
started
next
month,
but
we'll
just
do
them
both
in
parallel.
A
Now
is
the
community
standards
and
trying
to
take
a
proactive
approach
to
the
community
standards.
So
github
has
this
model,
which
you
know
we
all
is.
I
think
it's
great,
this
open
source
guides,
and
so
we
want
alice
to
be
a
proactive,
open
source
guide
right.
A
You
have
some
assurance
on
the
level
of
quality
of
what
you're
getting
right.
So,
let's
dive
into
this.
So
what
so?
What
do
we
need
to
do
this
right?
So
we
need
these
files
and
github
has
already
provided
us
with
some
standard
content
for
these
files.
So
what
we
can
do
is
we
can
just
have
alice
proactively,
go
out
and
we
can
say:
hey.
You
know,
alice
help.
A
Our
alice,
please
contribute.
Let's
see
what
should
we
structure
the
command
as
alice?
Please
contribute
contributor
guidelines
and
then
the
project
url
right
so
that
way
or
no
maybe
we
could
do
alice.
A
A
A
A
What
we're
going
to
do
is
we're
going
to
move
into
writing
the
code
which
will
be
you
know
the
the
product
of
the
tutorial,
which
is
the
docs
page,
that
we've
been
we've
been
editing
right
and
in
that
we
will
basically
take
this
snippet,
which
we
start
with
up
here
right
and
it
won't.
It
won't
work
at
the
beginning
of
the
tutorial
and
then
at
the
end
of
the
tutorial,
it
will
work
right,
and
so
what
is
work
well
work
in
this
case?
A
Is
we
want
alice
to
open
an
issue
with
markdown
with
the
marked
output
formatted
text,
similar
to
the
threats
md
file,
which
we
generated
for
the
living
thread
models
we
want
to
have
it
be
a
sort
of
checklist
which
is
a
meta
issue,
and
that
meta
issue
will
then
open
issues
for
each
of
the
items
in
the
checklist
and
once
when
it
does
that
each
of
the
items
in
the
checklist
will
be
one
of
these
community
standards
files,
all
the
ones
that
are
files,
and
we
can
easily
grab
templates
for
and
make
this
happen,
we're
not
going
to
try
to
do
everything
if
it.
A
If
we
don't
know
how
right
now
we're
just
going
to
sort
of
get
it
get
a
set,
maybe
five
of
them
something
right,
and
so
so,
once
again,
you
know
we're
gonna.
Take
this
proactive
approach,
she'll
open
the
issues
at
our
request,
and
then
she
will
attempt
to
open
pull
requests
for
the
ones
that
that
she
sees
potential
options
for
and
in
the
future,
some
some
options
which
we
could
expand.
This
flow
we
could
potentially
start.
A
You
know
background
tasks
to
then
have
alice,
monitor
those
threads
for
comments
to
actually
interact
with
with
folks
and
and
brainstorm
with
them
on
what
the
content
of
the
the
templated
files
should
be
before
she
raises
the
pr,
but
that
could
be
something
that
we
do
in
the
future.
A
So
all
right
so
yeah
we're
gonna
do
that
for
five
files,
oh
and
so
then,
then
what
we
can
do
is
we
can
split
this
so
so
we
we
focused
heavily
on
overlays,
but
we
need
to
see
some
results
here
first,
so
so
this
is
going
to
be
really.
A
The
focus
of
today
is
is
making
sure
that
we
can
get
those
issues
and
prs
associated
so
that
alice
can
take
a
proactive
approach
to
the
open
source
guides
and
the
fulfilling
of
the
community
standards
for
a
project
right
so
that
she
can
actually
start
helping.
So
then,
after
we
know
that
she
can
help
and
she's
been
successfully
helping
a
project
right,
then
we're
going
to
start
to
split
out
the
the
the
the
the
creation
of
the
issues
and
the
pr's
from
the
rest
of
the
flow.
A
A
Basically,
you
know
rename
some
of
that
stuff
and
make
it
about
the
community
standards
and
add
in
the
issue
the
issue,
creation
and
the
pr
creation
and
then
so,
when
we
go
to
make
it
an
overlay,
we're
just
going
to
pull
those
out
we're
going
to
put
them
in
a
separate
file.
A
Then
we're
going
to
go
back
and
we're
going
to
revisit
volume,
0
right,
where
we,
let's
see
volume,
0,
chapter
1,
where
we're
doing
the
the
the
theory
and
fleshing
that
out
and
really
looking
at
the
architecture
of
alice,
rather
than
the
implementation,
which
is
the
entity
right
and
so
we're
going
to
get
into
that
and
we're
going
to
look
at
how
the
work
that
we
were
doing
in
python
can
already
be
done
on
the
command
line.
A
And
so,
if
we
want
you
know,
if
we
want
to
build
this
ghost
in
the
shell,
then
we're
going
to
think
about.
How
do
we
build
a
shell
and
and
how
do
we
capture?
You
know
all
this?
This
chain
of
system
context
this
this
train
of
thought,
so
we'll
jump
back
into
that
momentarily,
build
that
with
our
cli
command,
so
not
as
fleshed
out
losing
some
of
those
implementations
that
are
stored
in
memory
just
for
now.
A
So
we
can
flush
that
out
and
then
we
will
go
and
let's
see
see,
then
we'll
go
right,
the
shell,
so
that
we
can
capture
the
the
the
history
of
commands
there.
And
then
we
will
do
a
automated
translation
of
these
engineers.
A
So
after
we've
written
a
few
of
these
tutorials,
what
we're
going
to
do
is-
and
we've
gotten
to
this
point-
we're
going
to
write
we're
going
to
write
the
shell,
the
shell
for
the
ghost
and
we're
going
to
have
it
output
right,
because
it
is
a
data
flow
one
of
the
overlays
which
we
will
run
over
it
as
an
output
overlay
will
be
the
synthesis
of
an
ipython
notebook
file
which
we'll
include
in
the
docs
page,
so
that
effectively,
what
we'll
end
up
doing
is
the
training.
A
Well,
we'll
have
a
data
flow
which
is
alice,
which
will
go
through
the
recording
transcripts
and
the
video
recording
and
link
it
up
with
this
notebook
file
so
that
we
can
automatically
generate
that
the
documentation
off
of
our
work,
as
is
recorded
or
streamed.
It
doesn't
have
to
be
to
youtube,
but
we
can
we
can
plug
the
text-to-speech
with
anything
else.
So,
let's
see
okay,
so
that's
the
the
near-field
next
steps
all
right.
A
All
right,
so,
okay,
we
have
the
templates,
so
here
yeah,
so
first,
you
know
what
do
we
do?
Well,
what's
what's
the
generic
process
right?
So
we
we
always
start
with
document
everything
we
know
right
so
so
what
is
everything
we
know?
This
is
basically
our
our
link
dump.
Maybe
our
you
know
from
our
tabs
that
we
did
the
other
day,
let's
just
just
grab
all
the
relevant
stuff
that
we
might
use
as
references.
A
So
what
did
we
talk
about
here
right?
So
we
wanted
to
do
recommended
community
standards.
A
Okay,
we'll
just
put
the
recommended
community.
A
Okay,
so
here's
our
template,
here's
the
list
of
files,
those
are
files
stuff
to
have
or
must
haves.
A
Okay,
so,
and
then
let's
just
write
a
little
note,
what
are
we
doing?
We're
going
to
alice
will
be
taking,
and
I'm
going
to
write
this
in
a
comment,
because
this
is
not
really
something
that
oh.
Why
would
I
don't
this?
This
is
more
of
a
comment
on
what
will
be
the
content
there
now,
rather
than
the
content,
and
it's
important
to
distinguish
the
difference
between
the
the
voice
of
the
the
note
and
the
text.
A
A
Okay,
so
she
will
attempt
to
contribute.
A
Required
or
helpful
community
files
so
as
to
provide
value
as
soon
as
possible
to
the
community.
Okay,
that's
our
immediate,
near
field,
objective.