POSIX Relative Path Workbench

How to use POSIX Relative Path Workbench

Calculate normalized absolute targets, relative routes and common ancestors from an explicit POSIX-style base path. Review a small path batch with component witnesses. Everything is lexical source text; no current directory, file, symlink or network location is consulted.

1. Provide optional path-model json file, absolute base and target path batch as json.
2. Choose the supported mode and run the tool. Review its assumptions and any reported errors.
3. Copy the result or download a separate output; reset to clear the current form.

Good to know

• One UTF-8 JSON object {base,targets}, at most 100,000 bytes. Supply one explicit absolute base and 1–200 nonempty target strings; each path at most 2,048 UTF-8 bytes and 128 source components. Duplicate/prototype-sensitive object keys, malformed Unicode and controls are refused.
• Selected slash-path profile: repeated interior separators collapse, dot components disappear, parent components pop one component and remain at root if already there. Absolute targets replace the base; relative targets start from the whole explicit base. The base is treated as a directory path, not an inferred file path.
• Trailing separators are removed except root. Identical resolved locations have the exact empty relative string plus a separate display dot. Matching is case-sensitive and Unicode is retained without normalization or locale folding. No source suffix is treated as a file extension rule.
• Backslashes, scheme/drive-looking prefixes and double leading slashes are refused instead of guessing Windows, URL or implementation-specific POSIX behavior. This is not a complete portable-filesystem pathname validator.
• No current process working directory is read. Symlinks, actual existence, permissions, directory types, mount boundaries, percent decoding and URL resolution are outside the lexical calculation. Two lexical paths can name a different real resource after symlink resolution.
• Structured text output is limited to 500,000 characters. Reduce the supplied source when that separate output budget is exceeded.
• Inputs are processed on this device and are not automatically saved or uploaded.