The Physlib community
Native namespace leanprover-community/physlib:API-map
Native API map
Browse 232 source-attributed requirements from the exact native revision. Implemented and planned are publisher labels, never Vela Standing.
Source-native objects
api requirement · reference only
source: implementedapi requirement · reference only
source: plannedapi requirement · reference only
source: plannedapi requirement · reference only
source: plannedapi requirement · reference only
source: plannedapi requirement · reference only
source: plannedapi requirement · reference only
source: plannedapi requirement · reference only
source: implementedapi requirement · reference only
source: implementedapi requirement · reference only
source: implementedapi requirement · reference only
source: implementedapi requirement · reference only
source: implementedapi requirement · reference only
source: implementedapi requirement · reference only
source: implementedapi requirement · reference only
source: plannedapi requirement · reference only
source: implementedapi requirement · reference only
source: implementedapi requirement · reference only
source: implementedapi requirement · reference only
source: implementedRepository bindings
A source observation does not create a local scientific record.
Exact observation
observation:physlib:071ce76f0a8083cb
git: e882411d1b6bcbdfdd336d4c509c6cc72e96842d
content root only · none retention
Source-native objects and Repository bindings
232 exact source-native objects
232 rows · complete coverage
0 exact links to local Repository records
Coverage and omissions
Every requirement in all 20 Physlib/API-map.yaml files at the exact pinned commit and tree.
GitHub issue, pull-request, reviewer-allocation, and merge state remain outside this exact-Git API-map observation.
The broader TODO index and generated physlib.io API tracker are not projected; the adapter covers only native tracked API-map files.
The observed revision contains no PhyslibAlpha API-map files, so this bundle projects stable Physlib API maps only.
A source-declared done flag reports native API-map state; it is not a Vela Claim, Verification, Decision, or Standing result.
The adapter confirms referenced Lean files exist but does not run Lean, the Physlib API-map linter, axiom checks, or declaration-name resolution.
Binding exact AI and review policy bytes does not establish compliance, human understanding, scientific fidelity, or maintainer acceptance.
Physlib requirements have no native stable IDs; record identities use the exact API-map path and one-based source ordinal at this revision.
The adapter preserves planned requirements that name partial or empty locations even when the API-map guide prescribes N/A; it does not normalize or infer completion from those fields.
Source declarations, observations, source-native object rows, and Repository bindings record provenance. None creates scientific Standing; only an admitted local Claim can enter the attributed Decision path.
- Release root
- sha256:c9d14c459c518937e758918b5897dc3b22f1a55f07739afe99502f5b046c907a
- Declaration root
- sha256:e8320022f1b34eea75349e0896ae42cd9b78f0191e2f9ea8805743be0accce9c
- Adapter root
- sha256:3a63c4df376d9f6c8e8e04dc8e9b930805897a0dbb4287193001affbae276854
- Source row root
- sha256:e8320022f1b34eea75349e0896ae42cd9b78f0191e2f9ea8805743be0accce9c
- Acquisition root
- sha256:071ce76f0a8083cb5e0e8baf259fe670fede96885e1918942cd8537ff1c92916
- Observation root
- sha256:fce692e559477ec2cbcab6a5931c35bb0a903ff861f4100872eb141f3ed3e6f9
- Projected source-native rows root
- sha256:c538042432169640f3732b1b3d066111616d27c21633a3f097b9d75f89ad8ba4
- Snapshot root
- not retained