2.1 KiB
SQL protocol knowledge base for 1C configuration storage
This directory is the durable, evidence-first record for the 1C SQL adapter. It complements the general format specification. Do not put all observations into one chronological note: add a fact to the document for its layer, object type, codec, operation, or experiment.
Non-negotiable runtime rule
The adapter works only through SQL. It may decode and encode only what was observed in the target database and proven by round-trip checks. It must never invent a metadata object, physical path, BSL fragment, form element, join, codec, or cryptographic value. Unknown or ambiguous work returns an explicit unsupported/protocol-incomplete result.
The Configurator remains a human-operated consumer of the saved-state overlay. The adapter does not start it, automate it, or claim to change its in-memory state.
Map
- Rules and evidence discipline
- Agent contract: do not invent
- Configuration SQL layers
- Extension saved-state overlay
- Common form and BSL module handling
- Object component graph and child selectors
- Report object-module carrier
- Payload envelope codec
__configinfomap and service atom- Configurator refresh behaviour
- Reproducible
upo_test/test2experiment - Known dead ends and prohibited shortcuts
- Template for the next experiment
- Current adapter component map
Maintenance rule
After every material protocol investigation, record all three outcomes:
- proven direction and the exact evidence;
- failed direction and why it failed;
- remaining unknowns and the next safe experiment.
Keep raw payloads and credentials out of git. Reference private learning artifacts by opaque ID or SHA-1 only.