►
From YouTube: Community Standup: 3/25/2020
Description
These community standups are open to all interested in participating in the NRE Labs project. Information on the schedule for these standups as well as how to join can be found here:
https://discuss.nrelabs.io/t/about-nre-labs-weekly-standups/84
B
C
Yes
and
I:
let's
see,
there's
a
few
things
that
I
could
show,
but
we'll
go
through.
Let's
go
through
some
of
the
stuff,
that's
on
the
let's
go
through
some
of
the
stuff.
That's
on
the
agenda.
First,
that
way
we
can
know.
Well,
we
can
cover
that
at
least
for
the
recording
and
then
when
we
get
to
the
antidote
core
update.
I
can
maybe
share
some
specific
with
you.
You
might
find
interesting.
Cuz
I
did
make
some
progress
on
those
things,
so
the
first
thing
is
a
new
stats
page.
C
C
We
actually
export
from
antidote
to
influx
DB,
and
then
we
visualize
that
through
graph
Anna
I,
have
a
sort
of
a
dashboard
of
my
own
that
I
look
at,
but
obviously
that's
sort
of
a
separate
thing,
and
it's
not
as
easy
to
find
that
and
it's
it's
just
a
whole
thing,
and
so
what
we
ended
up
doing
was
exporting
stats
also
to
a
spreadsheet
which
I
showed
last
week,
a
Google
Docs
spreadsheet
and
that
works.
But
the
problem
is
not.
Everybody
has
access
to
that.
C
So
what
Lisa
asked
me
to
look
into
was
basically
making
a
new
page
on
the
site
that
embeds
these
stats
so
that
it's
easy
to
find,
and
so
that's
what
I
did.
So
if
you
go
to
community
this
is
the
page
community
/
you
want
to
get
there,
you
can
click
on
community
and
then
you
go
here
to
enter
a
lab
statistics
or
you
can
go
to
the
bottom.
I
think
it
adds
it
yeah
yeah,
you
can
click
on
this
one.
It
looks
like
I
need
to
add
some
featured
images
for
those
but
yeah.
C
If
you
click
on
that
and
the
way
these
are
configured,
is
they
show
data,
that's
been
accumulated
over
the
last
seven
trailing
days,
that's
sort
of
the
view
that
I
usually
look
at
so
basically,
this
is
lesson
launched
in
the
past
seven
days
and
that's
that's
seven
days
literally,
like
seven
days
mine
from
from
today,
not
like
not
like
last
week,
not
Sunday
to
Saturday
it's
it's.
You
know
literally
seven
days
from
today
and
lessons
start
time.
C
That's
another
metric
that
we
that
were
kind
of
it's
pretty
important,
because
it's
it's
an
isometric
to
being
able
to
start
lessons
that
quickly.
So
anyway,
that's
being
shared.
Now,
if
you
you
feel
like
you
want
to
see
something
else,
maybe
we're
gathering
it.
Maybe
not,
but
let
me
know
and
I'll
see
about
adding
it.
We
have
a
few
other
things
we
could
add,
but
more
than
likely
that
will
require
some
augmentation
to
antidote.
So
we'll
see.
C
Oh
update
on
SEO
improvements,
so
just
a
quick
update
on
that.
If
you
go
to
any
labs
Google
any
labs
you
can
see,
looks
like
enough.
Not
much
has
changed
since
last
week,
but
that's
good
because
right
now
it's
showing
up.
So
we
don't
want
a
huge
change.
I
think
the
big
thing
that
I
wanted
to
do
was
just
show
that
the
search
results
were
coming
in
yeah.
So
things
are
progressing.
I
know
that's
right.
Last
week,
I
showed
that
there
are
these
43
errors.
I,
don't
remember
what
those
came
from
open
report.
C
Oh
yeah,
I
think
these
were
indexed
like
the
day.
I
made
the
change.
Okay,
yeah!
There's
all
these
all
these
subpages
that
were
marked
no
index
and
apparently
they
the
last
time
that
they
were
indexed
was
the
day
I
made.
The
change
was
March
4th,
so
I
just
missed
it
and
I
asked
Google
to
re
index
so
we'll
see
it
says
it
says
it
started
to
revalidate
those
so
we'll
see
how
those
go.
A
C
C
Okay,
a
user
survey,
so
Lisa
couldn't
make
the
meeting
this
morning,
but
basically
that
what
she
and
I
have
been
discussing
in
the
last
week
is:
let's
basically,
let's
basically
wait
for
a
little
bit
on
the
survey.
We
the
engagement,
that
we
that
we
got
the
work
that
were
likely
to
get
is
going
to
be
low,
so
we're
probably
gonna
wait
at
least
a
few
weeks
on
launching
that,
but
I
could
tell
you
the
the
the
draft
is
done.
C
She
even
sent
me
a
survey
monkey
link
so
as
soon
as
as
soon
as
this
all
kind
of
dies
down
or
gets
a
little
bit
better,
we'll
probably
consider
sending
that
back
out
so
we'll
see,
and
then
curriculum
v1
one
two.
We
are
the
the
current
target
date
for
that
is
the
first
of
April
and
we're
still
go
for
that.
C
A
C
C
Let
me
go
to
the
PR
that
I've
been
working
on
so
I
showed.
Let's
see
the
last
meeting
that
you
were
in
Olivier
I
had
the
ability
to
show
effectively
using
this
tool
to
insert
state
to
replace
syringe,
be
mock,
so
that's
kind
of
cool
I
haven't
done
much
with
that
since
then,
but
that's
still
there
so
yeah.
If
you
went
on,
if
you
want
to
take
a
peek
at
that
again,
we
can,
but
that's
basically
the
same
as
last
time.
C
C
There
were
a
lot
of
abstractions
that
I
had
in
the
code
this
that
I
wrote
when
I
when
we
women,
when
it
was
basically
when
I
was
first
working
in
this
thing
and
and
I
had
the
idea
that
those
things
would
be
useful,
some
of
which
became
useful,
but
others
didn't
so
they
were.
Basically,
it
was
basically
a
bunch
of
like
ideas
to
try
in
in
the
codebase.
C
A
lot
of
this
is
just
sort
of
you
know,
details
of
doing
all
of
that.
Oh
I
added,
open
tracing
instrumentation
yesterday
I
had
a
pull
request
previously
to
do
this,
but
that
was
more
of
like
just
playing
around
with
it
so
and
like
experimenting
this
time.
I
kind
of
knew
it
I
what
I
wanted
and
what
I
was
doing
so
I
just
went
through
and
implemented
it.
It
turns
out
that
it's
actually
pretty
pretty
straightforward
to
do
and
I
have
now
now
this
isn't
finished,
but
I
do
have
traces
being
exported
from
antidote.
C
C
It
becomes
very
difficult
to
figure
out
with
it.
You
know
who's
who's,
doing
what
the
cool
thing
about
these
traces
is.
Everything
is
stored
with
you,
know,
sort
of
high
cardinality
data,
and
so
you
can
drill
down
into
things
like,
oh
well.
I
I
just
want
to
get
traces
from
this
session,
ID,
for
instance,
ut3
c-65,
blah
blah
blah
or
this
source
IP,
which
localhost
obviously,
but
in
the
real
world
it
would
be
a
useful
IP
things
like
that.
C
I
mean
indirectly
sure
what
I'm,
what
I'm
hoping
this
does
is.
This
provides
a
fundamental
sort
of
like
a
foundation
for
just
activity
and
and
and
to
be
honest,
like
we
might
not
even
need
influx
TV
at
this
point,
because
this
kind
of
shows
startup
times
and
and
which
lessons
are
being
used
and
by
who
and
all
that
kind
of
stuff.
C
That
basically
says:
look,
let's
you
know,
let's,
let's
see,
let's
see
who's
used,
which
lessons
and
and
for
how
long
and
let's
see
if
they,
if
they
bothered
going
between
stages,
like
that,
that's
the
kind
of
data
you're
gonna
be
able
to
get
out
of
this,
because
you
can
do
things
like
you
know
basically
say
like
give
me
all
of
the
traces
with
antidotes
session.
Id
equals
this
and
you
can
make,
and
you
can
make
sure
that
a
certain
session
ID
is
associated
with
the
user.
C
You
know,
for
instance,
and
then
you
can
in
debt
you
can
you
could
query
this.
The
system
and
say
you
know,
show
me
all
the
traces
from
that
and
that
way
you
can
see.
You
know
everything
that
that
that
session
is
done.
We
could
like
I
said,
though
we
could
also
build
tooling.
On
top
of
this,
I
mean
Jaeger
has
an
API.
If
we
wanted
to,
we
could
build
it.
We
could
build
a
simpler
tool
on
top
of
Jaeger
and
say,
like
you
know,
make
it
make
it
much
easier
to
see
specific
pieces
of
data.
C
My
goal
here
isn't
to
be
super
opinionated
on
that.
My
goal
is
actually
just
to
get
as
much
data
as
possible,
because
that's
kind
of
what
Jaeger
is
designed
to
do
it's
designed
to
be
sent
sort
of
all
the
traces
you
you
can
you
can.
You
could
fathom
and
then
query
after
the
fact,
it's
sort
of
like
an
external
database.
A
C
C
If
there
are
problems
specifically,
if
like
say
like,
we
have,
we've
had
some
issues
with
the
V
key
effects
image
in
the
past
and
so
sometimes
a
lesson
just
won't
start.
But
the
problem
is
I.
Don't
know
that
because
I
won't
know
that
that's
happened
unless
I
go
back
and
grep
for
the
grep,
the
logs.
For
like
a
specific
error
message,
it
doesn't
tell
me
trend.
C
This
makes
it
a
lot
easier.
So
I'm
gonna
be
coupling
this
with,
hopefully,
I
don't
know
about
in
the
next
day,
I
don't
release,
but
perhaps,
and
then
the
one
after
that,
a
sort
of
a
dialog
box
that
you
can
click
to
get
help
and
what
it'll
do
is
it'll.
Allow
you
to
basically
describe
what
you're,
seeing
what's
going
wrong
and
it'll
go
somewhere
to
some
cue
and
and
it'll
send
along
with
that
message.
C
It'll
send
all
of
the
relevant
information
like
the
session
ad,
the
live
lesson
ID
and
all
that
stuff
to
let
me
or
whoever's
admitting
the
the
instance
turn
around
and
go
into
this
dashboard
and
drill
into
details
to
see
what
happened
so
I'm
really
excited
about
this.
This
has
been
something
I've
wanted
to
do
for
a
while.
C
That's
one
other
thing:
I
wanted
to
show,
so
that's
sort
of
the
syringe
D
set
set
of
things.
Oh
man,
I,
keep
saying
it
so
syringes
is
no
more.
As
I
mentioned
an
MP
one,
syringe
is
going
away
in
terms
of
name
we're
just
going
to
call
it
antidotes.
If
you
hear
me
say
syringe
D
again,
call
me
out
one
more
thing:
I
want
to
show
with
the
antidote
rewrite,
so
that
was
more
on
the
server
side
of
things.
C
If
you
go
to
so,
if
you
go
to
the
my
PR
you'll
see
that
there
are
three
binaries
now
there's
a
Anti
CTO,
which
is
the
sort
of
the
admin
tool
that
I
showed
you
a
few
weeks
ago,
where
we
sort
of
manually
inserted
some
live
lessons
for
testing.
So
that's
still
there
antidote
D
is
the
one
I
just
showed.
C
Well,
it's
basically
the
server.
It's
the
thing
that
powers
the
whole
thing:
it's
it's
the
replacement
for
syringe,
D
and
then
antidote,
which
is
kind
of
a
new
tool.
So
antidote
is
where
it's
sort
of
like
now,
the
user
facing
tool.
This
is
what
this
is.
What
I'm,
what
I'm
trying
to
do
is
get
make
this
put
more
functionality
into
this
tool
and
make
it
more
useful
for
users
for
actual
like
lesson,
contributors
and
one
of
the
ways
that
we
have
been
doing.
C
C
So
now
it's
antidote
validate
and
the
functions
most
of
the
same
way,
basically
validates
a
curriculum,
and
unless
you
know
if
there
are
any
problems,
but
what
I'm
going
to
be
doing
is
I'm
going
to
be
adding
on
to
that
in
terms
of
functionality,
I'm
going
to
be
adding
more
more
tools
into
that
into
that
command,
so
that
you
can
do
more
with
it.
One
of
one
of
those
is
creation
wizards.
C
C
You
are
entering
this
interactive
wizard.
Now
I've
shown
something
similar
to
this
before,
but
I've
made
a
lot
of
significant
changes
since
then,
so
the
the
interactivity
might
be
not
might
not
be
new,
but
the
the
I
found
a
library
to
do
the
to
do
the
wizard
part
and
it
may.
It
takes
a
lot
of
this.
The
complexity
of
showing
like
help
output
and
all
of
that
stuff
and
showing
a
variety
of
options
totally
off
my
plate,
so
I
think
it'll
make
a
much
a
much
better
experience.
C
The
way
I
did
this
by
the
way
I
kind
of
covered
this
previously,
but
I,
don't
know
how
much
detail
I
went
into.
If
you
look
at
the
new
database
power
DB
package
and
you
go
to
the
look
models
and
we'll
look
at
lesson.
For
instance,
all
of
the
types
within
antidote
have
been
decorated
with
this
JSON
schema
data,
so,
for
instance,
name
is
the
field,
but
we're
going
over.
Now
it
has
a
minimum
length
of
one
which
basically
means
it's
a
required
field,
and
it
has
a
description.
C
If
you
wanted
to
use
something
like
a
description
you
could
or
if
you
wanted,
to
use
a
regular
expression
pattern,
you
could
do
that
so
there's
all
kinds
of
validation
options
for
these
fields.
Now
the
user,
of
course,
doesn't
have
to
deal
with
any
of
that.
What
they,
what
they
see,
is
just
a
simple
wizard
that
iterates
over
these
these
these
fields
and
if
you
wanted
to
get
help,
you
can
hit
a
question
mark
and
it
gives
you
a
lot
of
that
data
here
on
the
command
line.
So
it
tells
you
that
it's
required.
C
It
tells
you
the
type
of
data
that
it
is
a
string.
Then
it
outputs
the
description
for
you,
and
so
you
say,
let's
say,
introduction
to
food
bar
slug.
Oh,
this
is
another
big
change
in
this
version.
So
there's
no
lesson
IDs.
So
when
you,
when
you
are
creating
a
new
lesson,
you're
no
longer
required
to
randomly
pick
some
number
that
may
or
may
not
be
accurate
or
unique,
rather
we're
moving
to
a
model
similar
to
what
you
might
see
in
like
a
website.
C
That
way,
it
makes
it
even
that
much
easier,
but
I
haven't
done
that
yet
so
we'll
see
but
similar
that
you
know
that
has
its
own
options,
you
can
see
required,
string
pattern,
description
that
kind
of
thing
so
foo
bar
this
is
this
is
sort
of
a
delimited
kind
of
thing
and
then
of
course,
the
category.
This
is
an
enum,
but
the
cool
thing
like
I
said
this
is
this:
is
one
of
the
cool
things
about
the
library
that
I
chose
it's.
It
knows
the
options,
and
so
it
actually
gives
you
a
a
scrollable
option.
A
C
C
C
It
is
in
the
sense
that
it
is
translated
to
the
protobuf
types,
and
so
basically
one
of
the
things
that
was
one
of
the
things
that
was
done
in
the
and
one
of
the
things
I'm
doing
in
this
effort
is
I'm.
D
decoupling,
the
the
the
internal
types
that
are
used
for
things
like
this
from
the
API.
So
previously
the
API
was
basically
the
the
data
models
that
were
in
the
API.
C
It
basically
establishes
a
totally
new
set
of
types
that
are
in
this
packages
DD
package
and
it
uses
those
internally
and
then
the
API
when
you
say
when
you
request
a
live
lesson,
for
instance,
a
religious
statement,
lessons
when
you
request
a
lesson.
For
instance,
there
are
functions
in
the
API
that
translate
from
the
database
types
to
the
to
the
corresponding
protobufs
driven
API
types
and
so
they're
very
similar,
but
they're
not
exactly
the
same.
A
C
Yeah
yeah,
yeah
I
think
that's
honestly,
a
lot
of
pretty
much
everything
I'm
doing
is
aimed
at
that
is
aimed
at
making
it
more
straightforward
to
follow.
It
was
even
the
the
the
nature
of
the
project
thus
far
is
in
terms
of
a
proof-of-concept
phase
has
been
very
difficult
to
spend
time
documenting,
because
I
knew
that
it
was
going
to
change
I
like
a
lot
of
this
stuff,
I
knew
was
not
was
not
sort
of
built
as
a
as
a
you
know.
A
C
Yeah,
but
this
so
this
tool
in
general,
this
tool
specifically
just
works
the
local
file
system,
so
it's
precompiled,
so
it
has
all
of
this
type
information
built
into
it,
and
so,
when
you
say
answered
a
lesson
create
it's
designed
to
just
go
through
this,
the
stuff
that
it
already
has,
you
know
built
into
the
code
and
then
export
to
a
local
file
system.
So
it's
like
a
creation,
wizard,
that's
local!
It
doesn't
interact
with
a
an
API
of
any
kind.
B
C
No,
the
the
the
the
JSON
schema
document,
so
if
you
did
one,
if
you
did
want
to
do
something
else
with
this,
all
of
the
all
of
the
information
that
we're
using
to
drive
this
wizard
is
stored
in
I
lost
it.
Where
is
it
here?
We
go
all
of
the
all
of
the
metadata
for
for
how
we're
doing
this
in
the
wizard
is
stored
in
these
tags
and
you
can
export
a
JSON
schema
document
very
easily.
In
fact,
that's
what
we're
doing
in
the
code.
C
So
if
you
go
to
antidote,
the
command-line
client
and
you
go
to
the
lesson
create
wizard.
The
first
thing
we're
doing
is
we're
effectively
pulling
the
schema
document
out
of
that
type.
So
we
create
a
new
instance
of
a
lesson,
a
blank
one.
You
know
nothing's
in
it
and
then
we
create
a
and
then
we
create
a
schema
document
that
we
derived
directly
from
that
type.
C
And
so,
if
you
wanted
to
do
something
totally
delay
and
then
and
then
we
feed
that
into
the
wizard,
but
you
could
do
something
totally
differently
like
if
you
wanted
to
use
this
code
base
and
say
look
I
want
to
I
want
to
do
something
else.
On
top,
perhaps
maybe
a
web
UI
that
does
the
same
thing.
Json
schema
is
very
portable.
That's
one
of
the
reasons
I'm
using
it.
It's
very
portable
there's
nothing
about,
there's
nothing
specific
to
go
that
you
need
to
know
to
use
it.
C
So
you
can.
You
can
use
the
same
data
and
export
this.
The
the
the
schema
document
for
this
type,
using
the
same
method
that
I'm
using
here
and
then
do
something
else
with
it.
Json
schema
is
very
portable
and
I
really
really
like
that.
That
aspect
of
it
I
mean
shoot.
I
could
probably
even
add
a
sub
command
to
Auntie
CTL.
To
do
the
same
thing
you
know.
A
C
Where
you
could
basically
say,
like
you,
know,
literally
print
me,
the
json
schema
document
of
on
this
for
this
type
to
the
you
know
to
the
terminal,
so
we'll
see
it's
all
possible
by
again
my
goal
isn't
to
be
super
opinionated
on
what
people
do
with
these
things,
it's
to
it's
to
sort
of
re
rebase
the
environment
right
provide
a
better
foundation
that
is
truly
more
extensible
and
more
easier
to
add
a
sort
of
more
simple
and
more
easy
to
understand.
That's
that's
my
main
goal.
C
Once
that's
done,
I
think
there's
a
lot
of
cool
things
we
can
do
with
it.
It's
just
been
really
tough
to
do
those
things
thus
far,
because
the
code
base
has
been
kinda
inter
woven
in
weird
ways
and
and
built
using
sort
of
tools
that
people
don't
always
understand
like,
for
instance,
the
the
validation
that
we
were
doing
previously
was
done
through
protobufs
and
not
everybody
knows
how
protobufs
work
and
it
was
using
a
tool
from
from
list
of
all
things
to
do
that
I
mean
they.
C
A
A
So
she's
a
turkey
struggling
with
testing
a
kids
che
because
it's
a
bit
like
antidote,
it's
it's
based
on
furnaces
and
it's
starting
lots
of
services
and
and
staff
to
manage
workspaces
for
developers
that
will
be
working
on
projects
and
so
on,
and
one
thing
we
have
noticed
and
which
is
not
clearly
operational
yet
for
her
private
volumes.
Stuff
like
that.
That
will
save
the
developers,
environments
between
sessions,
yeah,
so
I'm.
A
Thinking
that
such
a
feature
could
be
useful
in
context
of
course
offer
my
my
interest,
which
is
providing
a
platform
for
labs
for
students
where
students
would
work
disconnect.
I
connect
and
I
would
like
to
save
her
documents
all
this
our
workspace.
So
that's
one
somehow
I
think
that
there
could
be
some
value
in
understanding
how
it's
changed,
working
and
which
differences
in
architecture
we
have,
and
maybe,
if
we
can
reuse
part
of
a
cachet
for
antidote,
yeah
op
antidotes
onto
a
keychain,
it
depends
on
what's
more
feasible
yeah.
You.
C
C
C
Yeah
so
one
one
idea
that
we
had
when
we
were
talking
about
potentially
adding
some
sort
of
an
editor
to
the
front
end.
Let
me
see
if
I
can
find
it
because
I'm
pretty
sure
we
added
a
general
proposal
for
this.
Just
never
did
anything
with
it
was
adding
effectively
a
shared
volume,
so,
instead
of
because
right
now,
/
antidote,
if
you
own
to
any
endpoint
/
antidote
is
a
is,
is
unique
to
that
end.
It's
not
shared.
C
C
So
I
think
that
that'll
probably
be
necessary
is
is
adding
adding
a
volume,
and
this
shouldn't
be
that
hard
to
do
to
be
honest,
adding
a
volume
for
that
all
endpoints
can
share.
We
got
to
figure
out
how
to
how
to
figure
out.
We
got
to
figure
out
how
to
manage
things
like
you
know,
right
contention
and
whatnot
I.
C
I,
don't
know
we'll
see,
that's
something
to
work
out
in
a
in
a
what
I
would
like
to
do
is
is
have
is
open
a
discussion
in
like
a
in
like
a
forum
post
or
an
aura
or
an
or
a
pull
request
or
an
issue
where
we
talk
through
the
architecture.
I
think
that's
probably
the
first
step,
but
a
shared
directory
will
probably
be
needed
now
in
terms
of
the
longevity
of
that
directory,
a
really
I,
don't
know
we
have
to
see.
We
have
to
see
how
it
works
out
like
I
said.
C
A
Understand
how
it
keeps
going
with
this.
Obviously,
it's
also
managing
authentication
for
the
users,
and
maybe
I
can
imagine
that
maybe
we
could
borrow
the
authentication
part
and
I
could
directly
ask
for
checking
stuff
plus
workspaces,
those
share
directories
and
instead
of
just
launching
a
web
IDE,
we
would
launch
endpoints
connecting
to
that
in
the
same
house.
It
called
not
environment
the
the
session
of
a
user
in
Copernicus.
A
C
Yeah
yeah,
that
makes
sense,
I
think,
like
I,
said,
I.
Think
the
the
right
thing
to
do
probably
is
once
once
once
the
you
what
it
sounds
like
your
student
is
doing
some
some
sort
of
exploratory
exercises,
but
basically
once
you've
done
with
those
I
think
posting
and
posting
findings
to
either
the
forum
or
an
issue
or
whatever
it
is,
and
we
can
take.
C
Is
a
good
thing:
there's
there's
definitely
options,
there's
definitely
plenty
of
ways
we
could
do
that
of
my
only
the
only
thing
I'm
wondering
about
about
is
what's
the
right
model
in
terms
of
like
long
term
persistence,
because
I
right
now,
there's
not
really
a
strong
guarantee
that
that
a
user
is,
you
know,
gonna
get
into
the
same
environment
that
they
were
in
from
the
beginning.
In
general,
the
session
ID
is
supposed
to
give
some
persistence,
but
not
not
long-term
persistence.
It's
mostly
meant
to
provide.
C
It's
mostly
meant
to
get
you
back
into
the
same
lesson.
That's
already
running
once
it's
cleaned
up
that
guarantees
kind
of
gone,
so
we
might
have
to
make
changes
to
accommodate
more
long-term
sort
of
things.
One
idea
that
I
also
had
was
instead
of
persistently
storing
things
for
a
long
time.
In
the
background,
maybe
we
could
provide
effectively
a
button
that
you
can
click
on
once
you're
done
with
your
lesson,
you
can
click
a
button
in
it.
C
It
allows
you
to
download
all
the
files
that
you
changed
to
your
local
and
that
way
you
you
just
you
handle
it
yourself,
I,
don't
know.
There's
plenty
of
options
there,
none
of
which
are
set
in
stone,
so
I
think,
like
I,
said
that
the
first
step
is
to
open
an
architectural
discussion
where
I
first
stop.