Documentation covers the public product boundary: .algd artifacts, API usage, validation, CLI and deployment.
This is the technical area for engineers and evaluators. It explains what can be called and verified without exposing implementation details.
Artifact: .algd Supported public workflows: file compression folder compression ZIP / RAR / TAR.GZ intake chunked large-object sessions restore verification benchmark report export Verification: SHA-256(original) == SHA-256(restored)
API route families: /api/products /api/algoland/status /api/algoland/validate /api/algoland/quote /api/algoland/chunks/* /api/algoland/verify /api/algoland/deployment/policy Compatibility routes may exist. The public product name remains Algoland Compressor.
Results publish counted artifact sizes and restore proof. Internal research targets stay unpublished until they are verified.
Enterprise pilots run through a controlled runtime boundary rather than implementation disclosure.
Benchmarks are kept on a single page with filetype rows, speed rows, and current open target counts.