Repository navigation
docs: reconcile architecture and Workers proposals - #13
Merged
Merged
Conversation
This was referenced Sep 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PRs #11 and #12 describe an atomic edit engine and a Workers transition, but several revised promises still disagree with one another or current service contracts. This documentation successor records the useful shared-writer direction, the current implementation, and the decisions needed before any rewrite or migration. It adds a README pointer and a source-pinned reconciliation; it changes no application code or infrastructure.
The review covers the import log-key collision, batch events and retry/undo semantics, complete data preservation and post-resume rollback, current Doorway and Admission identity contracts, app versus person Gateway accounting, D1/DO/R2 ownership, and staging configuration/access. It uses the current shared Doorway/Admission source at
f149a53d3d9570ebb8d20c57f13a6d848fc09eba: the institutional origin and issuer are current, resolver success includesaccessRoleandbudgetScope, and Admission has no bootstrap allowlist. The document treats Slide Maker's administrator inheritance as a product-policy decision rather than a missing Admission transport.The PR recommends using this document as the successor baseline for #11 and #12 while retaining both original proposals as design history. It does not close either PR or authorize implementation, merging, migration, or deployment. Those decisions remain with the repository maintainers.
Validation: all 19 relative Markdown links resolve;
git diff --checkpassed; all eightbash tests/run_all.shsuites passed; normal PR CI passed at52a33a69579dcf18308b9bad6195f0e5fc5273d4. Independent review confirmed the corrected current-service claims and the file-access, version-authority, and release-path decisions. CI cannot validate the proposed architecture, account migration, or live CUNY/Worker paths.Base reviewed:
4cc0bf4b5b4d4a5d0372c7c1c525ab14ed54755c. Reviewed originals: #11 at75190496c1dacdfd258e4e65563bbebd032cb5d6, #12 at89af32f3c634eea6467e4ff048dd09d65ef61e4a.