01 · Discover & capture
Find the documented source.
Published material, project documentation, and open implementations are captured with their origin and their terms. Nothing enters on reputation alone.
How it works
Five moves, and
an honest record.
Every step is designed to produce something a later reader can check: where it came from, what was verified, and what was still unknown.
02 · Analyse & propose
Describe the capability.
The material is read and a capability is proposed: what it demonstrably does, at which version, with what scope. A proposal is a candidate, not an admission.
03 · Verify independently
Check the claim, state the scope.
A reviewer independent of the proposal checks what can be checked and records what could not be. Evidence names the version it covers and stops there.
04 · Resolve & package
Assemble against a requirement.
A requirement is resolved into exact assets and versions, with the conditions of use attached and the reasons for exclusion recorded. The package is a snapshot, not a pointer.
05 · Learn & revalidate
Re-check as the world moves.
Sources change, versions ship, reviews age. Records are revalidated on a cycle; anything that no longer holds is marked degraded and blocked from new packaging.
Supersession & retirement
Records move on; history stays.
When a newer version supersedes an older one, the older record is not deleted — it is marked superseded and kept readable, along with the evidence that covered it. A capability can also be retired outright when its terms change or its source withdraws it. Packages already assembled keep exactly what they recorded; what changes is whether they remain eligible for new work.
Verification is never automatic.
Nothing is promoted to trusted because it looks similar to something trusted, or because it has been in the repository a long time. A review has a scope and a version, and it expires when either moves.
Evidence & trust