Skip to content

Prototype inactive mandatory database fence and stamped preparation - #185

Merged
LeiterConsulting merged 1 commit into
mainfrom
review/inactive-database-writer-fence
Nov 16, 2026
Merged

LeiterConsulting merged 1 commit into
mainfrom
review/inactive-database-writer-fence

Conversation

@LeiterConsulting

Copy link
Copy Markdown
Owner

Scope

Reference-only SQL outside active migrations, inactive preparation adapter, regression tests and explicit commissioning gaps. No runtime imports, route, trigger, permission, deployment or publisher activation changes.

The reference fences all five content tables, binds writes to an operation/owner/epoch, promotes via a single admitted event with atomic head/history/admission consumption, and rejects implicit-deletion REPLACE vectors including hidden rowids. Bounded preparation validates canonical bytes and exact rows, uses at most50 inserts per call, and reconciles unknown outcomes without blind replay.

Evidence

Independent review cleared reference-only scope.38 focused tests;694 full tests pass. maintenance:sync and maintenance:verify pass (1453inputs); build retains960records. An earlier concurrent local run hit the existing deadline test's timing-sensitive phase assertion; sequential final candidate passed without modifying that test.

Explicit blockers

NOT a deployable mandatory-writer fix. Authenticated durable admission lifecycle/original artifact binding, actual writer/route integration, real hosted D1 migration/race/rollback qualification and operational authority remain outstanding. Stamps are not authentication against arbitrary D1/DDL actors. No automatic admission issuance, no publication or bootstrap. Review inventory and authority contract in docs/release-database-fence-prototype.md.

Exact-head CI/export qualification pending.

@LeiterConsulting
LeiterConsulting marked this pull request as ready for review November 16, 2026 00:46
@LeiterConsulting
LeiterConsulting merged commit f08b448 into main Nov 16, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant