Initial Foundational Semantics Spec #246
Open
willpugh wants to merge 3 commits into
Open
Conversation
willpugh
changed the title
willpugh
force-pushed
the
willpugh/foundational_semantics_spec
branch
from
July 23, 2026 06:26
4fba0e0 to
4ebfd2c
Compare
willpugh
added a commit
that referenced
this pull request
Jul 23, 2026
…e fixes Documentation: - Add compliance/ARCHITECTURE.md (spec<->impl<->suite contract, harness runtime + adapter flow diagrams, test anatomy, conformance model). - Rewrite compliance/README.md as the install/run entry point; refresh the harness and foundation READMEs. Tooling: - Make compliance/ a single uv workspace (pyproject.toml + uv.lock, members harness + foundation, dev group for pytest) so `uv sync` installs everything and `uv run` works from anywhere. Ignore *.egg-info/. Spec alignment (point at core-spec/foundational_semantics.md, per #246): - Repoint every proposals/foundation/Proposed_OSI_Semantics.md and foundation-v0.1 reference to core-spec/foundational_semantics.md and core-spec/expression_language.md across SPEC.md, decisions.yaml, proposals.yaml, conformance.yaml, DATA_TESTS.md, metadata.yaml, proposals_check.py, and test_registry_yaml.py. - Remap anchors to #246's structure: deferred features -> section 3, determinism (D-014) -> sections 5.1/6.10.2; error codes -> Appendix A (decisions are inline, no Appendix B/C). - Fix DATA_TESTS format drift (gold_rows.json -> gold.sql). Harness: - Implement decisions_coverage.md report (write_decisions_coverage in reporter.py, wired into run_suite) so every run surfaces D-NNN coverage gaps. Add test_reporter_coverage.py. Note conformance.yaml levels are declarative for now. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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
Related Issues
This is MD version of the foundational semantics spec. It started in Google Docs: Proposed Foundational Semantics.
This follows from the discussions in the expression language slack group, and mail
NOTE: There were two comments in the original doc around join direction behaviour (to not lose fact table rows) and null safe joins. These have been addressed in this version, by being explicit about when null safe joins are required and being explicit about joining from the fact tables out.
Checklist
Specification
core-spec/and follow the existing structureOntology
ontology/are consistent with spec changesConverters
converters/is updated to reflect spec or ontology changesValidation
validation/are updated if the spec changedDocumentation
docs/is updated to reflect any user-facing changesCONTRIBUTING.mdis updated if the contribution process changedExamples
examples/are added or updated for any new spec constructs or converter supportTests
pytest/ CI green)Compliance