Documentation
¶
Overview ¶
Command portmapcheck derives the PORT_MAP ✅ ticks instead of trusting them. A row is proven only when the interface ledger and the Go tree agree with it:
- Every exported member of the Pi file (the interface inventory rows whose published declaration file is that file) is ported or designed out in the ledger, and the Go symbol each ported member maps to is defined in a Go file the row cites. A cited Go file that holds no mapped symbol fails.
- A Pi file with no exported member (a side-effect module, script or CLI entry point) needs a Go test whose source carries `// pi: <Pi file path>`. The marker is necessary, not sufficient: until the marked test's coverage of a cited file and its mutation red-proof are derived, a marked row stays unproven.
- A renamed implementation is allowed only through a reviewed entry (portmap-reviewed.json) that names the Go symbol for each Pi member; the check verifies that the symbol is defined in a cited file.
A ✅ row that is not proven fails unless the committed baseline lists it. The baseline only shrinks: a new unproven tick fails, and so does a baseline entry for a row that is now proven or no longer ✅. `-generate` rewrites the status column from the derivation.
Click to show internal directories.
Click to hide internal directories.