Add references v3 specs and notes to the repo - #255
Merged
Merged
Conversation
Brings references_notes/ (previously untracked, gitignored-by-omission working docs) into version control under specs/references_v3/, split into notes/ (informal working notes, drafts, historical record) and spec/ (the authoritative, current specs: references_v3_compendium.md, references_expressions.md, requirements_for_functions.md, and the two normative examples files). Gives these docs real review/diff visibility and history going forward, instead of living entirely outside git. No content changes -- this is a pure add of the current files at their current (renamed/ moved) paths. A follow-up branch will bring the now-stale sections (references_v3_compendium.md predates most of the star-traversal work and ReferenceExpression3 itself) up to date.
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
Brings the references v3 design docs into version control for the first time. Previously these lived at
references_notes/outside git entirely (untracked, no history, no diff review). David reorganized them intospecs/references_v3/, split into:notes/-- informal working notes, drafts, historical record (creating references v3.txt,manifest_field_functions_proposal.md,manifest_keys_reference_v1/v2.md,function_coverage_matrix*.md,ai_csvpath_framework_management_draft.md,more_reference_queries.txt,autocomplete_prototype.py)spec/-- the authoritative, current specs (references_v3_compendium.md-- the main references spec;references_expressions.md-- the reference-expressions spec;requirements_for_functions.md; the twonormative_reference*.txtexample files)No content changes -- pure add of the current files at their current paths.
.DS_Storefiles are already covered by the existing top-level.gitignoreentry (confirmed viagit check-ignore, none included here).Follow-up (separate branch, not this one)
references_v3_compendium.mdis meaningfully stale -- it predates most of the recent star-traversal work (:having()/:flatten()/:all()'s meaning-collision/path-narrowing/name_three/pointer-optionality across all three datatypes),ReferenceExpression3itself, and Rule 1b (the ordinal-indexed global-ledger case, currently documented only in code comments, not inmanifest_field_functions_proposal.mdalongside Rule 1/1a). A dedicated pass to catch it up is planned next.