►
From YouTube: 4th SSC Meeting 20th April 2020
Description
Baseline-Protocol.org
The Baseline Protocol is an open source initiative that combines advances in cryptography, messaging, and blockchain to deliver secure and private business processes at low cost via the public Ethereum Mainnet. The protocol will enable confidential and complex collaboration between enterprises without leaving any sensitive data on-chain.
Official Press Release https://consensys.net/blog/press-release/ey-and-consensys-announce-formation-of-baseline-protocol-initiative-to-make-ethereum-mainnet-safe-and-effective-for-enterprises/
Twitter https://twitter.com/baselineproto
Baseline Protocol Documentation https://docs.baseline-protocol.org/
Github https://github.com/ethereum-oasis/baseline
A
A
We
will
be
going
through
here's
the
agenda
I'm
going
to
just
take
one
minute
to
go
through
the
agenda
quickly
and
then
so
as
I'm
going
through
this
please.
This
is
your
opportunity
to
add
items
that
inevitably
we've
missed
in
the
in
the
prep,
so
think
about
things
you
want
to
add
to
the
agenda
we're
going
to
go
through
the
new
SSC
guide
and
proposed
rules
mention
some
new
members
and
by
the
way
those
new
members
are
on
the
call.
It's
a
large
enough
group
you're
going
to
need
to
help
me
with
that.
A
I
don't
want
to
miss
anybody.
We've
got
a
review
of
the
current
project
list,
a
light
prune
on
that
project
list
and
I
will
make
my
phone
stop
doing
that
call
to
action.
It
was
around
setting
accountable
members
for
projects
and
ethics.
We'll
talk
about
that
and
just
we're
going
to
discuss
the
potential
procedural
improvement.
An
opportunity
for
outside
SSC
to
I
involve
I
only
present
on
subject
matters,
and
we
Bill's
got
some
some
things
to
address
and
for
bill
climb
and
we
will
review
a
particular
github
issue.
A
So
we
did
a
bunch
of
writing
and
there
will
be
a
major
push
of
new
content
to
the
docs
site,
Docs
baseline
protocol
org,
and
that
list
that
that
includes
a
number
of
nice
new
features.
One
is
that,
thanks
to
Hudson
Jamison
and
some
others,
we
now
have
a
joint
slack
discourse
telegram
channel,
so
you
can
enter
stuff
into
that
channel
and
it
will
pop
in
every
location
and
we'll
start.
A
There's
a
marketing
communication
community
that
Jack,
who
is
on
the
call
here,
Jack,
wiring
and
others-
are
stepping
up
to
be
accountable
for
we'll
talk
about
accountability
in
a
minute
and
that
lists.
So
so
getting
the
telegram
and
discord
communities
involved,
and
also
we
have
a
discuss
forum
that
Hudson
is
finalizing
right
now,
so
we've
got
all
the
tools
we
have
medium
is
up.
Youtube
is
up,
we've
got
people
that
are
behind
getting
you
know
that
are
now
permissioned
into
editing
stuff
and
putting
it
on
the
YouTube
channel
really
getting
getting
our
act
together.
A
So
people
should
feel
pretty
good
about
that.
I
think
so.
That's
one
change
to
the
to
the
docs.
Everybody
will
be
able
to
see
what
we
can
do,
how
you
get
involved
where
the
front
door
is
you
how
we
add,
and
by
the
way,
where
I
think
we're
trending
towards
four
hundred
people,
just
on
the
slack
and
I
was
checking
the
numbers
they're
not
going
down
they're
going
kind
of
flat
to
up
which
is
kind
of
impressive.
A
A
I
was
expecting
kind
of
a
kind
of
a
longtail
kind
of
a
curve,
and
we
didn't
see
that
specification
steering
that
there's
a
bunch
of
new
stuff
here.
We
reviewed
it
with
the
TSC
just
today
and
they
their
input
was
that,
yes,
we
should
stick
with
the
three
different
telegram,
discord
and
slack
and
see
if
we
can
get
those
working.
A
But
the
really
nice
thing
is,
you
can
be
on
any
one
of
them
and
communicate
to
all
three
at
the
same
time,
just
by
going
into
into
the
into
the
community
Channel
sound
good
community
chat
channel
on
slack
in
particular,
I
think
on
telegram,
because
of
the
way
it's
set
up,
anything
that
goes
in
telegram
will
will
paint
both
of
the
other
two
and
right.
Now,
that's
the
same
for
discord.
A
A
So
there's
a
bunch
of
other
changes:
title
Syrian,
Committee,
maintainer,
x'
members,
one
of
the
things
we're
proposing
is
that
you
go
from
and
general
public
contribution
by
fork
and
pull
request
to
being
a
member
with,
and
this
there's
still
some
discussion
here,
but
either
write
access
or
read
access
and
then
you'd
have
to
be
graduated
to
write
access
on
the
github
SSC
members
need
write
access
in
order
to
do
what
we're
going
to
talk
about
now,
which
is
do
have
accountability
for
projects
and
we'll
discuss
that
now.
So
this
is
the
proposed
structure
effectively.
A
So
if
you
have
your
name
on
one
of
these
buckets
you're
on
the
SSC,
if
we
prune
a
bucket
because
it's
not
nothing's
happening
with
it
and
it's
just
become
a
dead
branch,
then
you
know
and
you're
only
accountable
for
that
one
thing,
presumably,
you
are
gonna,
have
a
hard
time
with
the
fact
that
you're
not
on
the
SSC
anymore.
So
it's
a
really
organic
process
be
accountable
again,
the
SSC
don't
be
accountable,
you're,
not
on
the
SSC
I
thought
that
was
elegant.
Does
anybody
have
any
thoughts
about
that.
A
A
B
B
B
A
A
B
C
A
B
I'll
be
staking
so
that
I
keep
myself
honest.
I
have
a
question
by
the
way,
while
still
speaking,
because
we
are
opening
one
of
these
group
of
questions
here,
I
was
thinking
about
proposing
a
specification
for
a
tool
that
that
I'll
probably
start
building
so
I
guess
this
call
is
the
correct
place
to
ask:
what
do
you
guys
or
how
do
we
normally
proceed
with
specification
of
stuff?
Like
do
you
have
like
specific
rounds
going
through
with
different
people?
A
B
A
A
A
Say
this
so
we
were,
we
were
talking
about
on
the
TSC
we
were
talking
about.
We
were
talking
about.
You
know
priorities,
and
you
know
this
this
project
right
here,
the
sa
P
demo
that
shows
basically
knits
together
s,
AP
and
Microsoft
Dynamics
looks
like
it's
on
track
for
delivery
by
the
end
of
the
of
April,
which
we
will
publicize
the
heck
out
of
it,
because
it's
really
I
think
it'll
be
a
real
wake-up
call
for
lots
of
organizations,
including
a
lot
of
ERP
and
CRM
companies
and
SCM
companies.
A
And
so
that's
that's
the
very
next
thing,
and
alongside
of
that,
we've
got
several
use
case.
Projects
going
up
supply
chain,
trade,
finance
frtb
is
a
really
interesting
one
around
Koba,
that's
already
getting
some
press
and
we're
hoping
to
generate
a
team
for
a
hackathon
Balaji
on.
If
he,
if
he's
on
the
call,
if
he's
not
he's
in
India,
but
he's
been
pushing
this
hard,
but
so
has
Bill
and
Heather
and
lots
of
other
folks
and
you
go
out
and
check
the
I
think
it's
quaint,
Telegraph
wrote
a
hasty
article
about
it.
A
Based
found
the
fact
that
they
saw
the
github
repo
item,
which
tells
you
something
people
are
reporting
off
of
our
github,
that's
interesting
and
yeah.
So
that's!
Those
are
all
things
that
should
feed
specifications.
I
know
that
the
COBIT
project
already
has
two
things
that
we
hadn't
consider.
It
ought
to
be
specs
that
we
wouldn't
have
noticed
if
we
were
just
on
the
supply
chain
project.
B
B
Much
it
it's
just
about
creating
the
right
conditions
for
folks
to
understand
where
they,
where
the
protocol
is
and
the
boundaries
between
the
protocol
for
baseline
and
what
and
how
they
can
extend
it
and
connect
it
to
their
use
case.
And
then
you
know
the
appropriate
mechanism
and
that's
sort
of
like
this.
This
team
or
this
prison.
A
You
know
one
product
that
seems
to
have
money
written
all
over.
It
is
gas
tank
we've
been
calling
it
gas
tank
reprises.
You
know
we
there's,
you
know,
there's
clearly.
No
no
debate
about
this
enterprises
are
not
going
to
want
to
hold
a
lot
of
crypto
a
lot
of
them
won't
in
order
to
power
these
kinds
of
transactions.
So
there's
going
to
need
to
be
a
gas
tank
service.
A
The
question
is:
when
do
you
build
and
release
that
service?
If
you
built
it
now,
I
think
you'd
be
waiting
a
while
for
demand
build
it
too
late
and
you
won't
generate
demand.
It's
an
interesting
problem,
but
that's
only
one
I
mean
I
only
put
that
out
there
as
an
emblematic
of
the
question
of
timing.
A
You
know
what
signals
do
we
watch
for
to
know
that?
The
next
thing
we
need
in
the
the
next
plank
in
the
plan
needs
to
get
nailed
in
so
I
think
this
is
something
that
the
SSC
really
needs
to
be
mindful
of
and
I'll
pause
for,
comment
on
that
Tim
I
mean
this
is
something
you
guys
live
every
day.
What
are
you?
What
are
your
thoughts?
I.
C
Mean
my
initial
reaction
was
build.
A
group
of
concept
person
now,
if
you're
still
talking
with
a
gas
tank
anyway
build
proof
of
concept
version.
Now,
that's
easy
and
you
know,
doesn't
take
a
whole
lot
of
work
and
then
and
then
just
instead
of
trying
to
time
the
market,
just
let
it
let
it
come
and
see
what
happens,
put
more
resources
into
it.
C
B
B
Baseline
development,
so
you
almost
have
an
easy
on-ramp
for
folks
who
want
to
spin
up
their
own
standalone,
whether
it's
a
radish,
POC
or
something
similar.
But
then
we
appropriate
gas
tank
to
help
fund
getting
things
of
going
and
actual
setting
up
transactions
and
making
it
something
that's
useful
yeah.
We.
B
B
A
And
the
other
thing
that
the
other
vector
here
is
there
I
am
now
aware
of
kind
of
a
surprising
number
of
private
product
projects
that
you
know
some,
some
of
which
have
been
fine
with
telling
me
about,
and
others
are
saying
you
know
rightly
so-
that
we
can't
tell
you
about
them.
There
are
private
company
projects,
but
that's
exciting.
So
you
know
that's
probably
yet
another
thing
that
needs
to
happen
for
some
of
these
kinds
of
things.
A
A
The
the
proposal
here
is
that
if
you,
if
you
want
to
be
on
the
SSC,
you
send
a
note
I've
got
it.
We've
got
a
new
slack
channel
called
SSC
membership
requests
you
put
in
your
github
ID
your
name,
optionally,
your
company,
and
you
stipulate
what
or
you
know
very
briefly
state
the
thing
you
intend
to
be
accountable
for
and
then
we
invite
you
to
the
next
meeting.
A
A
Cool
and
so
the
new
SSC
member
QuickStart
would
be
just
you
know,
you
know,
make
sure
that
within
24
hours
of
approval,
you're
gonna
be
sent
an
email
with
instructions,
you'll
be
given
a
higher
level
of
rights
in
the
repo
you'll
have
write
access.
That
means
you
you'll
need
to
assign
the
oasis-c
CLA
and
you're
gonna
want
to
prepare
to.
By
going
to
the
Zen
hub
dashboard,
which
I'm
showing
here.
A
B
B
Yeah
sure
so,
I,
yes,
I
work
a
lot
with
the
tap
Scots
and
the
blockchain
Research
Institute
I
also
run
a
venture
capital
fund
and
both
their
clients
and
my
clients
have
a
lot
of
have
been
trying
to
use
ethereum
for
a
while
and
I've
been
struggling
because
of
privacy
and
usability,
and
a
lot
of
those
people
are
not
very
interested
in
baseline.
So
yeah
I'm,
very
interested
in
what's
going
on
here
and
hopefully
can
help
with
some
of
that
kind
of
messaging
and
pushing
it
out.
A
Thanks
charlie,
so
yeah
I
mean
that's
a
good
example
I'm.
You
know
it's
not
necessarily
that
Charlie's
gonna,
you
know,
write
code
in
here,
but
you
know
the
using
the
bully
pulpit
and,
using
you
know
our
ability
collectively
to
say:
hey,
shiny
objects,
shiny
objects
over
here
we
can
get
a
lot
of
work
done.
There's
400
companies
out
there
that
are,
you,
know,
excited
about
doing
stuff,
400
people
and
the
list
of
the
companies
that
are
sniffing
around
or
are
already
involved
either
secretly
or
publicly.
A
It's
quite
impressive.
So
you
know
all
we
have
to
do
is
say
hey
over
here.
Anybody
remember
the
movie
witness
from
Harrison
Ford
movie.
You
know
it's
like
that.
Amish
barn,
raising
right,
that's
what
we
got
to
do.
We
got
to
get
that
barn
raised,
and
so
we
got
to
say
hey,
you
know
it's
just
an
organic
process
of
saying,
hey,
Lou
yeah
and
you
helped
put
in
this
post
up.
A
C
A
A
A
Unfortunately,
get
book
is
we're
trying
to
fix
this,
but
I've
got
to
do
this
on
the
call,
because
I
can't
share
this
stuff
without
giving
everybody
access
to
it.
I
think
if
you
have
access
to
it,
you
can
push
directly
to
the
public
website
without
going
through
the
maintainer
review
process.
So
I
couldn't
give
a
preview
of
this,
but
if
there's
no
objections
in
24
hours,
this
will
be
merged
to
master
and
be
pushed.
A
A
C
A
A
Think
who
else
the
stage?
Okay,
so
we'll
move
on
from
there.
If
you,
if
I,
didn't
bring
you
up,
please
please
SP
go
okay,
so
new
members
review
of
current
project
list
so
and
a
prune.
So,
as
you
can
see,
we've
got
these
projects
sort
of
nominally
set
up
the
big
one
that
that
seems
to
be
on
deck
right
now.
Is
this
s
AP
dynamics
thing
by
the
way
shout
out
to
to
York
and
and
to
you
know
bright
into
envision
and
I'm,
probably
missing
some
folks,
but
getting
that
together
is
really
exciting.
B
D
D
A
So
if
so,
if
it's,
if
it
rolls
up
to
a
project-
and
you
know-
could
be
clear
that
this
is
imperfect
and
the
maintainer
czar
doing
a
lot
of
work
on
issues,
there
aren't
any
epics
right
now,
as
the
SSC
gets
better
at
that
at
this
will,
and
as
we
have
a
tighter
list
of
projects
in
high
level
epics,
those
will
get
tied
into
issues
and
I'm
sure
anybody
that's
been
part
of
an
agile
process
before
it
knows
that
nothing's
perfect.
But
this.
A
Yeah,
so
that
one
would
want
to
be
in-
and
this
is
what
univer
is
working
on
is
right.
Now
you
it's
sort
of
split
between
SOR
integration
tools
and
this
demo
and
which
is
nice
because
I
mean
doesn't
you
know
you
can
have
two
high
level
projects
with
epics
that
roll
up
to
both
right
say
we
wanted
to
put
it
in
here
and
we
should
do
this
offline,
but
we
can
do
it
in
here.
A
D
A
D
A
A
A
It's
just
doing
this
anyway,
there
is
yeah.
There
is
a
way
it's
actually
not
when
you're
in
edit
you
can.
You
can,
especially
when
you're,
when
you're
working
in
an
issue.
Can
you
can
add
it
to
an
epic,
fair
enough?
Okay,
then
we
have
an
epic,
you
can
add
issues
to
it
when
you're
editing
or
when
you're,
creating
and
I.
D
B
A
Ideally,
by
next
meeting
we
can
just
you
know
the
this
meeting
will
be
walking
down
the
the
projects
I
mean
now
that
we've
got
ourselves.
It
took
us
four
meetings,
but
that's
cool.
It's
actually
ahead
of
the
curve,
we're
pretty
well
organized.
We
have
rules,
we
have
governance,
we
have
all
this.
You
know,
we
know
we
have
channels,
we
have
comms
and
we
have
you
know
a
expanding
group
of
people
that
are
interested.
A
So
now
what
we
need
to
do
is
is
just
regular
eyes
and
the
regular
thing
is
we're
gonna
walk
into
this
meeting
or
you
know
people
are
going
to
be
ready
with
their
projects.
If
there
are
too
many
to
handle,
we
might
you
know
I
think
we
could
expand
the
meeting
up
to
say
two
hours
if
it
needs
to
get
to
that
point.
Four
people
can
dip
in
and
dip
out,
but
we'll
cover
them
in
a
way.
It's
like
a
lightweight
version
of
a
sprint
planning
session
right,
but
where
the
output
isn't
hate.
A
This
is
what
people
have
to
do,
because
it's
open
source,
but
rather
here
the
society
objects
that
we
really
want
to
want
to
spotlight.
That
will
be
the
output
of
the
meeting
and
then
will
will
publicize
those
will
and
Jack
and
others
and
the
team
will.
You
know,
make
a
big
deal
out
of
that
point.
People
at
it
and
say:
hey
look
over
here
got
a
big
plant
to
put
up
anybody
with
nails.
You
know
come
over
here.
B
B
A
A
I'd
like
to
make
a
call
to
action
that
the
Balaji
Shetty
poach,
I
bill
climb
and
Stefan
Bauer
and
others
have
been
noodling
and
I've
put
in
some
input
on
this
as
well
on
the
idea
of
a
code,
basically
improving
the
kovat
19
contact
tracing
protocol
with
baselining,
and
there
is
a
healthcare
hackathon
happening
right
now
and
we
are
looking
for
people
in
our
community
to
step
up
to
help.
Do
that.
A
But
as
a
list
of
topics
that
you're
subscribed
to
watching
for
on
the
main
net
for
a
change
in
status,
that
would
alert
you
that
you
were
potentially
exposed
and
then
you
would
be
able
to
choose
whether
or
not
you
want
to
report
that
to
the
CDC
a
little
less
creepy
approach.
So
that's
that's
an
interesting
project,
and
this
is
my
PSA
to
say
if
you
have
folks
that
are
interested
in
that
we're
definitely
going
to
mount
a
hackathon
entry
on
that
topic.
So
those
seem
to
be
the
two
shiny
objects.
A
B
The
elevator
pitch
is
the
easy
button
for
baselining
or
fun
experiments.
It's
a
container
orchestration
for
the
various
runtimes.
It
deploys
stuff
to
AWS
and
Azure
under
each
organization.
The
network
registries
own
resources,
so
it
actually
would
be
suitable
for
production
if
we're
able
to
get
it
be
suitable
for
production
experiments
put
it
that
way
and
it
you
know
yes,
I-
think
the
real
value
prop
would
is
around
sort
of
getting
getting
a
safe
space
for
these
experiments.
B
A
Right
now
so
I
just
added
a
baseline
server
fast
deployment
project.
You
know
feel
free
to
rename
that
okay
and
if
you
can
get
something,
get
the
relevant
ethics,
yeah
I
mean
I've.
You
know
it
struggles,
you
know
it
would
be
one
way
to
do
it,
but
if
you're
leading
the
charge
on
it,
you
know
get
that
one
out
there
and
see
if
other
people
follow
suit
with
their
own
other
ways
to
do
it.
A
A
A
Like
printer
project
list,
so
are
there
any
projects
in
you
know
what
I'm,
mindful
of
time
so
I'll
say
that
you
know
next
time
around.
What
we'll
do
is
we'll
have
a
prequel
pre-vet
will
do
the
work
to
come
in
with
prevented
set
of
potential
pruning
candidates
and
I'll
take
the
responsibility
to
do
that
with
with
others.
C
Sure,
maybe
not
sure
if
it's
pruning,
but
maybe
maybe
there
is
a
second
look
to
be
to
be
taken
on
how
to
organize
these
projects.
I
mean
for
it
just
seems
fairly
hard
to
kind
of
see
if
I'm
a
business
person
looking
for
these
actual
business
functional
aspects
which,
where
do
I
go
because
that's
totally
different
and
he's
more.
You
know
non-functional
aspects
from
a
business
viewpoint.
The
business
layer
right
system
is
non-functional,
the
actual
layers
underneath
you
know
these
become
functional.
So
it's
it's
we'll
be
fine.
C
A
You
know
real
engineering
issues
and
that
there's
a
lot
of
work,
that's
being
happening.
That's
happening
on
that.
Ideally,
as
we
go
forward,
the
you
know
really
starting
next
time.
We
should
have
a
pretty
good
linkage
between
what
the
maintainer
czar
focused
on
and
being
able
to
see
that
rolled
up
in
the
dashboard
right.
So
there's
there's
that
Eric
also
I,
know
you've
got
thoughts
about
this
sort
of
thing
that
you
know
there
could
be
a
project
level
thing
right
here
called
and
non-functional
requirements,
and
we
have
people
stepping
up
to
that.
A
Saying:
okay,
I'm
going
to
really
be
accountable
for
making
sure
that
we
have.
You
know
good
project
level
efforts
around
non-functional
requirements,
promulgating
them
writing
them
down,
specifying
them
and
and
making
sure
that
we
meet
certain
testing
environments.
I
mean
if
we
had
white
block
on
team,
for
example,
I'm
sure
that
they
would
be
all
over
that
sort
of
thing,
thoughts.
D
You
know
it
kind
of
seems
to
me
this
sedan
speaking
seems
to
me
that
you
know
with
every
project
just
so
we
can
kind
of
speak
to
what
Stefan
and
everyone
is
saying
from
the
business
side,
but
also
John
what
you
said
with
the
technical
side
almost
like
there
needs
to
be
not
an
elaborate
business
case
with
every
epic
and
project,
but
maybe
some
sort
of
you
know,
I,
don't
know
a
paragraph
or
two
kind
of
outlining.
What
are
the
business
considerations
that
this
is
going
to
help
out
and
what
are
the
technical?
B
Might
actually
be
good
to
have
a
template
for
that,
so
it's
really
easy.
You
know.
So
we
could
say:
okay,
regardless
of
the
sector.
If
we're
gonna
have
a
one
slide,
page
you're
gonna,
have
you
know
exactly
what
is
the
business
case?
How
exactly
does
based
on
soul
there?
Something
I've
just
you
know
some
template.
So
it's
really
easy,
then,
for
everyone
else
to
fill
their
own
kind
of
sexy,
yeast
casing.
So.
D
Just
to
kind
of
add
on
to
that
one
I
know
that
so
Stefan
myself,
Karen
and
Jason
have
began
to
discuss
the
business
value
behind
looking
at
looking
looking
at
the
baseline
repo,
along
with
using
radish
as
a
reference
architecture,
John
I
know
that
you
started
this
other
baseline
executive
deck
and
I
think
that
we
merged
the
the
the
two
epics
altogether.
But
this
is
kind
of
you
know
the
beginning
of
the
template.
We
didn't
actually
think
of
it
as
as
a
template
in
mind,
so
I
think
that's
a
really
nice
call-out
yeah.
A
In
so
I
think
we
should
put
the
the
the
template
higher
up
on
the
list,
so
that
was
actually
a
an
action
item
from
before.
So
we'll
make
sure
that
that
is
done
by
next
meeting
and
I
know
what
we
can
work
with
Brian
to
make
sure
that
we
have
that
the
template
is
correctly
inserted
into
the
thing
and
what
we
did
I'll
remind
everybody.
We
did
stipulate
that
the
way
we
do
these
is
primarily
is
one
epoch
underneath
the
product.
A
So
we
can
put
the
so
I've
been
fairly
fast
and
loose
with
adding
project
level
things,
because
it's
just
a
little
placeholder.
The
real
the
real
rubber
meets
the
road
with
an
epic
rain.
So
you,
the
step
one
is
create
one
epic
and
then
sketch
out
the
whole.
You
know
project
opportunity
and
that's
that
tent.
That
needs
a
template,
but
we
said
you
know:
stick
with
one
epic
write
it
all
up.
A
I'll
point
out
at
the
bottom
here
is
a
good
example.
Rebasing
was
something
that
nobody's
on
it
yet,
but
you'll
see
that
the
there's
just
so
many
things
that
have
to
happen
before
you
know
a
rebasing
which
is,
you
know,
described
as
a
way
to
re-establish
a
entanglement
record
if
it's
been
lost.
So
if
you
have
your
databases
and
corrupt
it,
and
you
need
to
rebase
that
record
with
your
counterparties,
how
do
you
do
that?
That's
a
function!
A
That's
a
that's
a
functional
thing
that
the
attribute
that
needs
to
happen
and
you'll
see
that
nobody
has
any
any
thought
that
it's
going
to
be
done
before
this
can
even
be
started
on
until
into
the
June
timeframe.
Maybe
later
so
that's
a
great
example
of
where
we
can.
We
can,
as
an
SSC
say,
you
know
both
during
the
meeting
in
lots
of
meetings,
offline,
say,
okay,
well,
rebasing,
and
what
other?
What
other
features
here?
We've
got
people
that
are
working
on
thinking
about
messaging.
A
There
was
a
big
meeting
with
Nats
and
they
it
looks
like
the
Nats
team
wants
to
come
in
and
join
us.
You
know.
Is
that
the
way
an
approach
to
messaging
I
had
a
big
I
think
it's
actually
just
been
posted,
televised
or
recorded
podcast
of
a
conversation
with
Richard
Campbell
Brown
about
using
kurta
as
a
messaging
protocol
in
a
theorem
which
would
crack
me
up
and
make
me
happy
so
yeah?
These
are
these
are
functional
attributes
and
then,
of
course,
non-functional
attributes.
A
The
each
of
them
can
be
a
project
and
I
know
like,
for
example,
Karen
and
and
and
Steve
have
been
working
on.
Other
projects
and
I
know
that
the
healthcare
team
has
been
working
on
stuff,
so
some
of
those
are
gonna
be
private,
are
could
be,
it
would
be
put
here
because
their
company's
working
on
their
own
but
yeah
Karen.
Do
you
have
any
thoughts
about
that.
A
Now
you
can
see
the
start
of
stuff
right.
Corp
identities
in
here
messaging
is
in
here
gas
pump,
abstraction
generalization,
you
kind
of
writ
large
a
workflow
step
tool.
You
know,
in
other
words,
that
you
know
when
you
want
to
make
a
new
step.
You
know
like
if
you
wanted
to
add
invoicing
to
the
Bradish
34
demo.
How
would
you
do
it
be
nice
to
add
a
little
workflow
step
tool?
There's
all
these
like
ideas
and
being
on
the
SSC
means
you're
accountable
for
one
or
more
of
them.
C
Yeah
and
John
you
had
another
screen
up
some
handwritten
boxes.
The
maidens
were
gasps
yeah
that
blue
one
there
I
think
what
what
I'm
looking
at
that
might
be
helpful
is
really
translating
this
into
an
overall
architectural
view
that
organizes
maybe
around
sort
of
main
groups
of
capabilities
like
gas
tank
is
probably
somewhere
in
a
capability
bucket.
C
That
speaks
to
main
that
the
integration,
whereas
there
is
a
back-end
integration
or
sorrell
integration,
where
maybe
that
that
other
piece
I
mean
what
I'm
trying
to
get
to
is
really
what
are
the
five
or
six
major
big
boxes
on
top
where
you
can
start
organizing
with,
because
organizations
came
to
organize
themselves,
you
know,
according
to
the
to
the
architecture
of
the
product,
maybe
that's
a
way
to
started.
I
think.
A
It's
a
great
point
and
stuff
I
know
that
you've
got
interested
in
this
I
know
that
Eric
has
interested
in
this,
so
I
I
did
put
a
architecture
placeholder
on
the
project
list.
Maybe
that's
something
that
will
I
don't
mind
that
these
things
are
gonna
it.
This
is
supposed
to
be
an
organic
process,
so
I
don't
mind
where
we're
at
with
this
list.
I
would
mind
it
if
this
list
was
where
we
were
at
next
time
and
and
if
we
can
use
sort
of
an
architectural
set
of
meetings
between
now
and
then,
let's
do
it.
A
A
A
D
And
we
only
have
a
couple
minutes:
I
have
a
hard
stop
here:
I
gotta
jump
off
in
three,
but
I
think
that
this
is
just
important
for
us
to
establish
the
baseline
unintended
for
what
it
is
that
we
have
defined
as
maintenance
right
so
and
I'm
just
gonna
put
it
out
there.
You
know
you
know
from
for
better
or
for
worse,
I
know
that
there's
some
documentation
that
I've
read
in
the
past.
D
That
said
that-
and
this
is
I
want
to
date
back
like
say
like
a
year
ago,
but
if
you're
dealing
with
the
private
blockchain
right
the
shared
ledger
among
the
consortium
members,
that's
considered
to
be
maintenance.
It's
not
capital,
M
main
that
right.
It's
not
public
aetherium,
but
at
one
point
that
was
documented
in
some
of
the
things
I
was
reading
as
a
maintenance,
the
definition
that
we
have
in
the
baseline
Docs
of
main.
That
means
you
know
publicly
accessible,
yada,
yada
and
I.
D
D
Action
is
that
I'd
like
for
us
to
come
up
with
a
consensus
as
to
what
this
definition
is.
I,
don't
know
where
we
would
put
that
I,
don't
know
if
it's
just
an
agreement,
and
we
just
you
know
we
just
discuss
it-
I'm,
not
proposing
that
we
need
to
change
it
even
right.
I,
just
think
that
we
need
to
just
establish.
B
A
D
You
know-
and
it's
like
if,
if
it's,
if
it's
available
to
public
blockchains,
the
well
then
which
public
lock
chains
are
excluded
from
it
without
having
to
mention
any
names
right,
I'm
not
trying
to
I'm
not
trying
to
get
into
that
conversation.
But
what
I'm
saying
is
that
it's
good
for
all
of
us
that
are
on
the
SSC
to
know
what
it
is
that
we're
talking
about
right.
Taxonomy
is
important.
A
When
charlie
joined,
you
know,
I
was
talking
with
them
about
this
opportunity.
I
think
one
of
the
things
that
Charlie
this
is
a
project
you
could
put
on
the
board
to
say
you
know,
get
executives
in
big
companies
to
not
be
scared
of
maenette
right.
One
of
the
things
we
need
to
do
to
do.
That
is
a
good
deck.
That
explains
why
they
shouldn't
be
scared
about
being
about
the
main
net
anymore
and
I
know
that's
partly
the
deck
that
we're
working
on,
but
maybe
Daniel.
D
Right
this
simpler
part,
but
I'm
trying
to
get
at
is
what
is
the
main
net
that
we're
talking
about.
Everyone
has
a
different
view
right.
You
look
at
one
color
and
you
could
say
it's
dark
red,
it's
like
red
or
whatever
right,
but
let's
all
just
make
sure
that
we're
talking
about
the
same
thing,
Rena.
A
D
A
D
B
B
A
There
is
we
can
talk
about
that
offline.
A
bit.
I
know
we're
out
of
time,
but
I
will
will
say
that
if
you
go
down
to
baseline
protocol,
you'll
see
that
there's
a
section
on
standards
already
and
you'll
see,
there's
actually
a
document
called
main
it
and
and
so
that
standards
folder
is
right
there
and
we
can
start
putting
stuff
into
that
and
there's
already
a
template
of
sorts,
and
there
is
a
sucess,
a
four
specs,
our
standards
that
they
are.
We
will
get
wired
up
with
in
the
next
two
weeks.
A
A
So
that's
yeah,
that's
it!
There
is
one
last
thing:
I'll
take
30
seconds
to
describe
and
then
I
will
let
us
all
off,
and
that
is
that
there's
a
proposal
to
move
the
TSC
meeting
and
the
SSC
meeting
to
bookend
kind
of
a
loose
sprint
type
thing.
So,
every
two
weeks,
and
as
we
get
into
like
monthly
meetings
in
the
few
by
June,
maybe
or
July,
the
TSC
would
say,
meat
on
Fridays
and
Atia
and
the
SSC
would
meet
on
Mondays.
A
The
SSC
would
be
sort
of
like
sprint
planning,
ish
and
the
TSC
would
be
a
little
bit
like
sprint
review
ish
and
if
you
can
think
about
that
and
provide
any
input,
we'll
will
lock
that
down
the
next
few
days
and
and
when
we
do
that
and
the
next
couple
of
48
hours.
That's
when
I'll
I'll
send
the
invites
for
the
next
meeting.