proposals: unrepresentable covenants DSL + durable scrivener plan - #71
Open
goldenwitch wants to merge 2 commits into
Open
proposals: unrepresentable covenants DSL + durable scrivener plan#71goldenwitch wants to merge 2 commits into
goldenwitch wants to merge 2 commits into
Conversation
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.
Summary
Two linked proposals from the post-#64 abstraction audit, shaped for the next build phase (a journal-first machine with heavy fan-out and durability requirements).
1.
proposals/unrepresentable-covenants.md— typed covenant tree + DSLApplies a strict prevention ladder (type system → source generator/analyzer → runtime remainder) to the ten bad states that are representable today (multi-provider journal collisions, overlapping-predicate fan-out, dead routes, DI shape traps, tools/streaming gating, manifest lies, dispose-without-start).
Key mechanisms:
Connected<TManifest>evidence tokens — routes to unconnected journals or never-produced types stop compilingDone()— deletes validation Rule 4 instead of tightening itToolCapability<T>tokens — streaming/tools misconfigurations become inexpressibleOn/Teedispatch: one dispatcher per source journal;On= ordered first-match alternatives,Tee= declared always-fire fan-out. Multi-match stays first-class — the fix targets undeclared overlap, not fan-out itselfIProduce<>/IConsume<>markers;Coven.Analyzers(COVEN001–006) for what generics can't express2.
proposals/durable-scrivener.vine— journal contract → durable → distributed (VINE plan)Contract-first DAG, 10 nodes. The
IScrivenerguarantees everything currently relies on are implicit and only true ofInMemoryScrivener; this formalizes them, ships a cross-implementation contract test suite, then a single-node segmented durable log (hydration, torn-write recovery, durable per-consumer cursors, idempotent pumps), then distributed semantics (single position authority w/ lease+fencing; replication with an explicit adopt-vs-build gate refereed by the contract suite).Retires
FileScrivener/FlusherDaemon(in-memory delegator, silent shutdown drop) per delete-unused-code guidelines.Review focus — the opinionated calls
On/Teearbitration split (§2 of the DSL proposal) — first-match alternatives vs declared fan-out replacing today's all-filtered-routes-fireNote: the .vine plan carries two
@guidancelinks to local design docs outside this repo (file:///D:/git/geasarcana/...) — decide during review whether to inline those specs, keep the local-only links, or drop them.Testing
Docs/plan only — no code changes.
.vinevalidates against VINE 1.2.0 (magic line, root-first, DAG dependencies all resolve).