The configuration shown in the exhibit is an example of a routing instance of type virtual-router. A routing instance is a collection of routing tables, interfaces, and routing protocol parameters that create a separate routing domain on a Juniper device. A virtual-router routing instance allows administrators to divide a device into multiple independent virtual routers, each with its own routing table.
The configuration also includes a rib-group statement, which is used to import routes from one routing table to another. A rib-group consists of an import-rib statement, which specifies the source routing table, and an export-rib statement, which specifies the destination routing table. In this case, the rib-group name is inet-to-ispi, and the import-rib statement specifies inet.0 as the source routing table. The export-rib statement specifies ispi.inet.0 as the destination routing table.
This means that the routes from inet.0 will be imported into ispi.inet.0.

The rules are as simple as follows:
1. IBGP peers advertise routes received from EBGP peers to other IBGP peers.
2. EBGP peers advertise routes learned from IBGP or EBGP peers to other EBGP peers.
https://community.juniper.net/discussion/understanding-how-ibgpebgp-behaves-in-junos

When routes are placed into a RIB group, an import policy can be applied to determine which routes are accepted into that group. This policy helps in controlling which routes get installed or filtered into the RIB group from various sources like other routing protocols or static routes.
https://www.juniper.net/documentation/us/en/software/junos/static-routing/topics/ref/statement/rib- groups-edit-routing-options.html

This command shows the Ethernet switching table, which includes information about MAC addresses, their associated VLANs, and the interfaces they are learned on, similar to the output shown in your exhibit.