Contributions should stay within file-system path form semantics:
- parsing, classification, and decomposition under selectable Unix or Windows rule sets;
- compare and equate definitions;
- comparative notes and shared test fixtures.
Do not add URL/URI locators, I/O APIs, or language-runtime implementation code to this repository.
Prescribed terms in docs/glossary.md and related documents are provisional until the operator ingests stored web material and explicitly seals naming. When proposing new terms:
- label them provisional / proposed;
- prefer alignment with existing libpath family vocabulary;
- do not rename sealed concepts without operator agreement.
Follow Synesis freelibs markdown conventions: * body lists, double blank lines before ##/###, <!-- omit in toc --> titles on top-level project files, and the standard end-of-file marker.
When fixture files arrive:
- prefer JSON or YAML with lexicographic keys;
- document schema in fixtures/schema.md before bulk cases;
- keep fixtures as data, not embedded port test harnesses.
Open pull requests at https://github.com/synesissoftware/libpath-concepts. For large semantic changes, discuss in an issue first so nomenclature stays coherent across ports.