Files
MikrotikManager/docs/bandwidth-fixed-registry-transaction.md
T

58 lines
3.8 KiB
Markdown

> Снято с реализации 29 октября после уточнения пользователя и аудита Astra. Неподключённые методы, continuation, пять тестовых файлов и runner-профиль удалены из активных исходников. Снимок: `tmp/withdrawn-fixed-registry-20261029/manifest.json`. Текст ниже — история проектирования, не текущий API и не требование speed-test.
# Fixed registry transaction on one physical owner
Implementation/verification in progress. **OP-M4 and S3-06 remain open.**
The next operator path combines a genuine fixed continuation with an internal
core-source owner entry. It does not upgrade a public metadata result into
authority. The public registry metadata facade remains exactly `inspect` and
`close`; no query handle, lifetime field or transaction method is added to it.
The continuation issuer accepts only the existing branded original-authority
reader and external fencer. Its original capability, signed grant, wall and
monotonic horizon and cancellation are pinned before acquisition. Inspecting
the continuation checks current original authority without Q; verifying it
checks that authority before the actual external Q and performs only
synchronous liveness checks after Q. Public JSON cannot create a continuation.
The core source creates the public metadata lease internally and looks it up
in its own private WeakMap. Only that entry supplies the actual raw lease,
physical PID, lifetime signal and same-session exclusive registry lock. The
continuation is claimed once for this owner identity and matching root. It
cannot be moved to another lease or rebound after closure.
The initial fixed transaction surface is `begin`, `lockedSnapshot`, `inspect`,
`close`. BEGIN and fixed transaction settings require actual command ACKs.
Every state effect is bracketed by current metadata/ownership and fresh Q;
these checks have not been fused into shared boundaries. The locked snapshot
uses the existing bounded fixed SQL/parser and derives managed/external kind
and subject from the original grant. The only input is a validated claim hash.
It returns an opaque private snapshot capability, not caller-editable rows,
MACs, SQL or an enrollment plan. In particular an input hash is not accepted as
proof of a genuine RouterOS license observation.
This surface cannot apply enrollment, commit, publish a receipt or register
runtime callers. Destroying the physical connection retires the unfinished
transaction; the component does not invent a ROLLBACK acknowledgment. A later
closed controller must consume its own snapshot capability and genuine native
observation, perform the two key phases and fixed DO, and preserve UNKNOWN from
COMMIT dispatch onward.
The core validates a captured signed bootstrap envelope, current public core
files and actual role/catalog/source/root. It does not know the node bootstrap
pathname. Fresh node-bootstrap file checks remain a node-wrapper integration
requirement. Neither an additional node lease nor a callback claiming current
authority can substitute for that requirement.
No new pool, role, migration, process or TTL is introduced. BEGIN and settings
are counted as actual state effects; the earlier nine/eight-scan candidate is
not established by this implementation. Whole-path measured latency, Docker
stop/recovery, all-writer/caller activation and the installation's maximum 2 GB
load acceptance remain outstanding.
The exclusive test runner profile is `--fixed-registry-transaction` and rejects
mixed flags or `--restore` before cluster creation. It uses one disposable
PostgreSQL harness. External Q remains an explicit synthetic fixture boundary;
real backend/Docker/CHR actions are excluded from this profile.