pllm
Research

Contribute a clean-room reimplementation

Add an independent PLLM implementation with clear provenance, tests, evidence, and review.

PLLM documentationView Markdown ↗
  1. Add a source record with a stable ID and URL, exact version or digest, authors, citation, access method, and license review.
  2. When lawful, preserve the original artifact under a pinned ArtifactLock. Keep restricted code external-process/oracle-only; the registry never downloads, imports, or executes it. Never vendor or import it as a PLLM dependency.
  3. Define the PLLM method and explain how it differs from the source.
  4. Write an inspectable reference from the paper, public specification, and approved test vectors. Do not translate the original implementation.
  5. Record matching results, mismatches, unavailable cases, and scope.
  6. Implement reusable behavior in the component that owns the relevant protocol, kernel, preparation step, or compiler phase.
  7. Apply the method through shared plan interfaces and reject unsupported coverage.
  8. Run the relevant assurance checks and strongest comparable benchmark. Include limitations and negative results.
  9. Record all lifecycle gates in MethodRecord, pass ResearchRegistry.promotion(), and complete the publication review before promoting a claim.

Use canonical paper records, schemas, the component standard, and the documentation standard.

Loading documentation index…

Search runs locally in this browser.