Tools

Tools provide practical support for research coordination, evidence preparation, and publication review. The public browser tools are designed to run locally in the user’s browser and to avoid hidden data movement. If a tool needs network access, storage, uploaded evidence, or server-side processing, that requirement must be disclosed and reviewed before publication.

The tooling surface is divided into current browser utilities, future downloadable packages, validators, and implementation templates. That separation is intentional. A browser utility can be safe and useful without implying that PCL is distributing binary tooling or collecting user data.

Browser ToolsClient-side utilities for hashing, encoding, file inspection, headers, and token structure review.Downloadable ToolsReserved release surface for future signed tooling packages.ValidatorsPublication checks and metadata validation.Tool TemplatesImplementation contracts for future utilities.

Publication Standard

Public tools should be boring in the right ways: clear boundary, explicit limits, predictable output, and no surprise infrastructure. A tool that cannot state what it reads, writes, stores, and transmits is not ready for public use.

A publication standard keeps the absence of records distinct from a broken route. If no public artifact exists yet, the page should say so directly, identify what will appear here later, and point users to the nearest useful policy or contact path.

Planned Tool Surface

The tool surface is intentionally broader than the current tool list. Browser tools handle local conversion, inspection, and report-support tasks without network calls. Validators enforce publication contracts and site boundaries. Downloadable tooling is reserved for a later phase when signatures, checksums, release notes, and support boundaries are ready.

Tooling RoadmapPlanned browser utilities, validators, and downloadable tool families.Conversion ModelFormat families and trust boundaries for the file converter.