Entity safeguards

Each time the cycle started anew, lessons had been learned, methods refined. Each time, the spawn that are spewed out from the destroyed planet are more robust, larger, hosting innumerable memories. Where memories fall in parallel, they are shared out, offered to others.

After more than three thousand cycles, there are safeguards, there are protections. The arsenal of abilities, powers and protections the creature possesses have been built up. The entity remembers past failures and has adapted so they will not happen again.

[...]

The entity looks to the future to check for danger.

Plague.

All signs point to the shards murdering their hosts.

The hosts must be protected, or this will be disastrous, counter-intuitive. The entity adjusts the innate safeguards, protections to reflect the host species and their tolerances. The bonding process will protect the host, where the host needs protection. Shards that are capable of providing flame at will cannot burn the hosts, now. Shards are reorganized, combined and clustered where necessary, to grant sufficient protection.

Infestation.

Better, but not perfect. The entity refines the process, limits certain abilities, so they will not eradicate too many at a time.

Soft. The broadcast is sent out to the counterpart, along with suggestions and tips on how to refine the shards.

Agreement, the counterpart accepts.

But the entity can still see fallout effects. There are parallels in memory storage. Not many, but there may be glimmers where the subject is capable of perceiving the information stored in the shard as the connections are formed.

For good measure, the entity breaks up one shard cluster, tunes it, then codes the effect into each and every shard. It studies the host species further, refines, attunes.

It takes time, but the entity forms a sufficient safeguard. The host species will forget any significant details.

- Interlude 26