How many objects or references are associated with a block variable with static storage duration(in multi-thread)?

void fun(){
  static int value = 0;
}
int main(){
   fun(); // in main thread
  /* fun(); assume in a different thread*/
 /* fun(); assume in a different thread*/
}

we lack the specification for the (block) variable with static storage duration in a similar manner as [class.static.data] p1 did for the static data member. The approach of [class.static.data] p1 is that:

If a static data member is declared thread_­local there is one copy of the member per thread. If a static data member is not declared thread_­local there is one copy of the data member that is shared by all the objects of the class.

The second sentence can imply that we only have one concrete object or reference associated with the static data member regardless of how many threads refers to it.

Don't we need a similar rule for other kinds of variables with static storage duration, non-normative, such as the following:

There is only one object or reference associated with the variable with static storage duration at any time.

Read the example and [class.static.data] p1, then compare its wording with the rules for block variables with static storage duration. Determine whether the draft needs a similar clarification about the number of associated objects or references across threads, and document the resulting standards wording or rationale.