Repository navigation
Close Issue 015 consequence learning and release 0.8.5 - #52
Merged
Merged
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
topographo0.8.5Result
COMPLETE/ R1: exact triad symmetry plus designated-query CE fits TRAIN in 8/8 but reaches sustained ROLE95 in 0/8.COMPLETE/ C3: exact baseline replication passes with zero shared deviations; TRAIN-only 243-corruption relational competition reaches exact relation and ROLE in 8/8.The positive conclusion is limited to sufficiency relative to designated-query CE on the 48 observed triads and their already-identifiable ROLE consequences. It does not establish necessity, NOVEL/global completion, a unique learning law, or language-scale/physical semantics.
Release
topographofrom 0.8.4 to 0.8.5 with synchronizedpyproject.tomland editableuv.lockmetadataValidation
Provenance
4309ff3,8f55174,8201e04,992b67f27612778252e0858328b4325154d07f068eafe6cc961dfe36c0861cbf79b5bf44768ae4cd3ffccf4f1d983e3154e4fec25e19b342b0d9de2484da8837929ea0045f62ae4a246ffbbd7747f0c18c21ee1a72c66a31aad2b7e598837ec00d773219cb58b90c299807b88a475eabb2af37ae1126a5e64a0bfe7e7207b9384f31a38Accepted result artifacts remain byte-identical; no frozen experiment-code refactor was performed.