-
Notifications
You must be signed in to change notification settings - Fork 1
docs(boundary): define domain-empty core #516
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
125 changes: 125 additions & 0 deletions
125
docs/design/0014-domain-empty-core-boundary/domain-empty-core-boundary.md
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,125 @@ | ||
| --- | ||
| title: Domain-Empty Core Boundary | ||
| legend: SOURCE | ||
| packet: 0014-domain-empty-core-boundary | ||
| status: active | ||
| release: v0.0.6 | ||
| --- | ||
|
|
||
| # Domain-Empty Core Boundary | ||
|
|
||
| ## Sponsors | ||
|
|
||
| - Human: I can add compiler truth without accidentally turning Wesley back into | ||
| a product, database, scheduler, or runtime policy repository. | ||
| - Agent: I can decide whether a proposed change belongs in generic Wesley, | ||
| an external module, `wesley-postgres`, or a product repo before editing code. | ||
|
|
||
| ## Hill | ||
|
|
||
| Wesley has one enforced core boundary: it owns generic GraphQL semantic | ||
| compilation, generic module contracts, and evidence plumbing. The `whatever` | ||
| side of `GraphQL -> whatever` is module-owned. | ||
|
|
||
| Product, runtime, database, scheduler, replication, transport, deployment, and | ||
| substrate truth semantics are not Wesley core features. | ||
|
|
||
| ## Why This Cycle Exists | ||
|
|
||
| v0.0.5 cleaned up historical product gravity. v0.0.6 is now deepening Rust IR | ||
| truth and compatibility evidence. That work only stays coherent if the repo | ||
| also blocks new product and database semantics from entering the base platform. | ||
|
|
||
| The first Rust IR parity sentinel already gives Wesley a real compatibility | ||
| check. The next risk is not missing another product feature. The risk is | ||
| growing the compiler around old product assumptions while the Rust kernel and | ||
| module surfaces are still settling. | ||
|
|
||
| ## Boundary Contract | ||
|
|
||
| ### Wesley Owns | ||
|
|
||
| - GraphQL SDL parsing and semantic normalization. | ||
| - Domain-empty L1 IR bytes, hashes, fixture truth, and diagnostics. | ||
| - Generic schema diff, operation selection, directive argument extraction, and | ||
| emitter primitives. | ||
| - Module discovery, module capability contracts, and module-owned target | ||
| dispatch. | ||
| - Evidence plumbing for artifacts, realization shells, witness reports, and | ||
| release checks. | ||
| - Hermetic fixtures that prove compiler behavior without making the fixture's | ||
| product domain a Wesley responsibility. | ||
|
|
||
| ### External Owners Own | ||
|
|
||
| - Echo law, handles, footprints, runtime admission, and observation semantics. | ||
| - jedit editing behavior and product workflows. | ||
| - Continuum product protocol families and release policy. | ||
| - WARPspace, `warp-ttd`, and `git-warp` runtime or substrate behavior. | ||
| - PostgreSQL and Supabase generation, execution, safety primitives, migrations, | ||
| row-level security, and pgTAP behavior in `wesley-postgres`. | ||
| - Application deployment, scheduler, transport, replication, and storage | ||
| semantics. | ||
|
|
||
| ### Module Seam | ||
|
|
||
| External behavior enters Wesley through explicit module capability surfaces. | ||
| The generic compile command must discover targets from registered | ||
| `wesley.targets`; it must not carry built-in product or database target names. | ||
|
|
||
| That keeps the base platform auditable: | ||
|
|
||
| - no module loaded means no target-specific compile semantics are available | ||
| - a target name means a module registered it | ||
| - target collisions are module capability errors | ||
| - historical package residue does not define current Wesley ownership | ||
|
|
||
| ## First Slice | ||
|
|
||
| This first slice is a boundary-definition and front-door enforcement slice. | ||
|
|
||
| It: | ||
|
|
||
| - pulls the domain-empty boundary card out of `docs/method/backlog/asap/` | ||
| - creates this packet as the active v0.0.6 boundary doctrine | ||
| - updates front-door docs to point at the packet | ||
| - reframes README extension examples as externally owned module families | ||
| - adds a repo-level Bats check for the packet link, backlog move, and | ||
| module-owned compile target dispatch | ||
|
|
||
| It does not move behavior into `wesley-postgres`, Echo, jedit, Continuum, or | ||
| other sibling repos. Those moves need their own repo-local cycles. | ||
|
|
||
| ## Playback Questions | ||
|
|
||
| 1. Does the active design map define what Wesley core owns and what external | ||
| owners own? | ||
| 2. Does the front door link to the boundary packet instead of relying on | ||
| scattered doctrine? | ||
| 3. Does the ASAP queue stop carrying the pulled boundary card? | ||
| 4. Does `compile` still discover targets from module capabilities rather than | ||
| built-in product or database names? | ||
| 5. Does PostgreSQL/Supabase behavior point at `wesley-postgres` as the owning | ||
| home? | ||
| 6. Does this slice avoid changing sibling repositories? | ||
|
|
||
| ## Next Enforcement Slices | ||
|
|
||
| - Turn product/database front-door wording into a stronger docs or metadata | ||
| audit if new residue appears. | ||
| - Add module capability fixture coverage for target dispatch, alias conflicts, | ||
| and no-module diagnostics. | ||
| - Decide which historical Node package command surfaces are legacy support | ||
| only, extraction debt, or still generic Wesley toolchain behavior. | ||
| - Keep `wesley-postgres` visible as the database extraction home while leaving | ||
| its implementation work in that repository. | ||
|
|
||
| ## Non-Goals | ||
|
|
||
| - Do not delete historical design packets that remain useful extraction | ||
| context. | ||
| - Do not add product, database, runtime, or scheduler semantics while defining | ||
| the boundary. | ||
| - Do not edit `~/git/wesley-postgres`, Echo, jedit, Continuum, `warp-ttd`, or | ||
| `git-warp` from this Wesley branch. | ||
| - Do not retire legacy Node lowering in this packet. |
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
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,43 @@ | ||
| #!/usr/bin/env bats | ||
|
|
||
| load 'bats-plugins/bats-support/load' | ||
| load 'bats-plugins/bats-assert/load' | ||
|
|
||
| @test "front-door docs point to the domain-empty boundary packet" { | ||
| run grep -F "[Domain-Empty Core Boundary](./docs/design/0014-domain-empty-core-boundary/domain-empty-core-boundary.md)" README.md | ||
| assert_success | ||
|
|
||
| run grep -F "[design/0014-domain-empty-core-boundary](./design/0014-domain-empty-core-boundary/domain-empty-core-boundary.md)" docs/GUIDE.md | ||
| assert_success | ||
|
|
||
| run grep -F "[Domain-Empty Core Boundary](./design/0014-domain-empty-core-boundary/domain-empty-core-boundary.md)" docs/ARCHITECTURE.md | ||
| assert_success | ||
| } | ||
|
|
||
| @test "domain-empty boundary card is pulled from asap into design" { | ||
| run test -e docs/method/backlog/asap/SOURCE_domain-empty-wesley-core-boundary.md | ||
| assert_failure | ||
|
|
||
| run test -e docs/design/0014-domain-empty-core-boundary/SOURCE_domain-empty-wesley-core-boundary.md | ||
| assert_success | ||
|
|
||
| run grep -F "0014-domain-empty-core-boundary" docs/design/README.md | ||
| assert_success | ||
| } | ||
|
|
||
| @test "compile targets remain module-owned instead of built-in product targets" { | ||
| run grep -F "listModuleCapabilities(" packages/wesley-cli/src/commands/compile.mjs | ||
| assert_success | ||
|
|
||
| run grep -F "'wesley'," packages/wesley-cli/src/commands/compile.mjs | ||
| assert_success | ||
|
|
||
| run grep -F "'targets'" packages/wesley-cli/src/commands/compile.mjs | ||
| assert_success | ||
|
|
||
| run grep -F "No compile targets are available. Load a Wesley module that registers wesley.targets." packages/wesley-cli/src/commands/compile.mjs | ||
| assert_success | ||
|
|
||
| run grep -E "['\"](postgres|supabase|echo|continuum|jedit|warp-ttd|ttd)['\"]" packages/wesley-cli/src/commands/compile.mjs | ||
| assert_failure | ||
| } | ||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The boundary smoke test hard-codes single-quoted fragments (
'wesley',and'targets') instead of checking for the semantic condition, so a harmless refactor (e.g., switching to double quotes or formatter-driven quote changes incompile.mjs) will fail pre-push/CI even though module-owned dispatch still works. This creates a brittle gate that can block unrelated work and should be replaced with a quote-agnostic pattern or a behavior-level assertion.Useful? React with 👍 / 👎.