maintainerlinegel
Repository owner and current public maintainer. Review the GitHub profile, signed-in activity, and commit history directly.
Open source · Evidence gated · Publicly versioned
How this skill pack earns trust.
The Three.js WebGPU Skill Pack is a public technical reference for AI coding agents and graphics engineers. This page identifies who maintains it, how claims are classified, what counts as evidence, and how published guidance stays synchronized with source.
People and project identity
The pack is maintained in the open. Authorship is attached to inspectable commits and contributor history rather than an anonymous content pipeline.
contributorsRepository contributors
Every accepted change remains attributable through the public contributors graph and per-file Git history.
licenseISC licensed
The source and generated presentation are distributed under the repository’s ISC License. Third-party dependencies retain their own licenses.
Evidence before acceptance
A source file, a loading page, and an attractive screenshot prove different things. The pack keeps those claims separate so presentation quality cannot silently become runtime evidence.
authoredDeclare the contract
Each skill names its domain, APIs, invariants, ownership boundaries, and explicit non-goals.
derivedBuild deterministic routes
Canonical demos publish fixed scenario, mechanism, and quality-tier routes from versioned source.
measuredCapture runtime facts
GPU timing, resource inventory, readback, lifecycle, visual diagnostics, and error ledgers are measured rather than inferred.
gatedIssue a falsifiable verdict
PASS, FAIL, INSUFFICIENT_EVIDENCE, and NOT_CLAIMED remain distinct. Missing proof cannot collapse into success.
- Implementation
- The canonical source exists and its published route is loadable.
- Presentation preview
- A screenshot or generated asset explains the surface but is not automatically runtime evidence.
- Accepted evidence
- The declared mechanism, timing, lifecycle, and visual contracts passed against the named Three.js revision and adapter context.
Update and correction policy
Published pages are generated from repository source. Search metadata, source hashes, dates, demo classifications, and discovery files are validated together before deployment.
versioningGit is the ledger
Skill publication and modification dates come from repository history. Every page links back to its current source and latest relevant commit.
correctionsFix source, then rebuild
Technical corrections land in the owning skill or demo first. Generated HTML, sitemap metadata, and machine-readable indexes are rebuilt from that source.
reviewClaims remain reversible
Acceptance can be withdrawn when APIs, evidence, or hardware behavior change. The registry preserves the current status instead of promising permanent validity.