Finite Property Sources 56e EN - teamswyg/laya-tools GitHub Wiki
Next: expand through real public sources
Repeated use of56e's finite quoted family does not create diversity. This investigation prepares implementation of contracts from other sources. Read fixed-revision root trees, licenses and implementation files through the GitHub API. New acquired development requests, independent truth and model outcomes remain0. Do not turn the historical120-item inventory into a claim that240 are complete.
| Public source read | Fixed revision | Files inspected | Priority behavior |
|---|---|---|---|
| Masterminds/semver v3.4.0 | 61fc460d28283a91c53be65c2e0f20b494ac8ad9 |
version.go, root tree, LICENSE.txt |
Strict parsing, version precedence, ignoring metadata |
| bmatcuk/doublestar v4.9.1 | 8b690afa33319b0a1869367f594e53977e38bc99 |
match.go, root tree, LICENSE |
Directory glob, escaping, malformed-pattern errors |
Both pinned license files contain MIT terms and copyright notices. Any later copied/distributed source must retain the corresponding complete notice/license. No source is vendored or used in weights in this investigation. This does not complete rights review for all dependencies/training assets. Add exact file-byte hashes, closed helper/dependency/compile provenance and NOTICE review in the executable source manifest.
Proposed observable contracts
- Strict semver parsing: finite requests requiring three valid numeric components and rejecting a
vprefix, missing components and leading zeros. Check nil/error identity and value fields with independent literal expectations. Do not mix permissiveNewVersionor mutableCoerceNewVersionwith the strict contract. - Ignore build metadata: different metadata with identical numeric/prerelease components must compare as0. Distinguish textual equality from semantic precedence.
- Prerelease order: finite inputs covering numeric identifier comparison, prerelease below release and numeric versus textual identifiers. Connect
Compare,LessThanandEqualaliases through their helper instead of counting them as independent families. - Directory glob: distinguish
a/*.gofroma/**/*.go, including zero and nested directories, using the original/separator contract. Do not confuse platform-specificPathMatchwithMatch. - Glob escaping: separate an escaped wildcard's literal behavior from single-character wildcard exclusion of separators. Freeze bounded ASCII inputs first and claim truth only for those inputs.
- Malformed-pattern errors: require exact
ErrBadPattern.MatchUnvalidateddeliberately drops errors into a boolean result; false alone does not satisfy an error contract.
These upstream behaviors already exist. They are initially code-semantics sources for unverified hints, not unimplemented coding tasks. Coding-completion/model-routing requests need a separate baseline gap and independent acceptance conditions.
Make them executable
Freeze source bytes/rights → closed source/helper/alias Go compilation → write/review request/candidate captions and independent expectations before observations → mutations and unknown handling → relationship groups → separate official truth freeze/observation → model-free utility preserving every candidate. A narrow literal check cannot certify a general function. Three semver and three glob behaviors do not automatically become six independent families.
Then verify actual acquired counts toward120→240 and repository/language/authorship/behavior coverage. Empty rows and rephrasing do not fill the target. Keep minimum15 groups,5% necessary utility and at least2400 distinct protected-final requests per domain. New paid/model calls, fits, weights and final reads0. Qualified immutable weights belong on HF, never Git.