Initial project import
This commit is contained in:
@@ -0,0 +1,35 @@
|
||||
# `__configinfo`: file map and service atom
|
||||
|
||||
## Proven map
|
||||
|
||||
The decoded `E__configinfo` text contains logical file-name pairs:
|
||||
|
||||
```text
|
||||
"<object-guid>.0",<base64 of 20-byte SHA-1>
|
||||
```
|
||||
|
||||
The Base64 value is the SHA-1 of the complete raw `BinaryData` stream for that
|
||||
logical file. Updating a module without replacing this map value produces the
|
||||
Configurator error “Ошибка хеш-версии файла конфигурации”.
|
||||
|
||||
The map rewrite is deterministic and losslessly round-trip proven for the
|
||||
studied extension form module.
|
||||
|
||||
## Service atom: current status
|
||||
|
||||
The root block also contains three observed binary atoms: two 48-byte values
|
||||
and a 32-byte value. The 32-byte value changed across manual saves, including
|
||||
when the module bytes returned exactly to a previous SHA-1. A random mutation
|
||||
of its variable part triggered a platform licensing/crypto error.
|
||||
|
||||
Therefore:
|
||||
|
||||
- preserve all service atoms byte-for-byte during the proven incremental
|
||||
protocol;
|
||||
- do not synthesise, randomise, zero, or “recalculate” them;
|
||||
- do not claim their reverse codec is known;
|
||||
- record new observations in an experiment file before changing this rule.
|
||||
|
||||
The `test2` map-update experiment activated successfully while preserving the
|
||||
existing service atom. This is activation evidence for preservation, not for
|
||||
generation.
|
||||
Reference in New Issue
Block a user