Record platform scope
Each lane states the packaging target, local inputs, and the phrases that must not be used yet.
Local Package Shape and Platform Gates
Latticra has package-shape records for Linux ecosystems and no-effect macOS writer dry-runs. It does not have official distribution packages, published release artifacts, production installer readiness, or daily-driver install eligibility.
Packaging Rule
The current packaging work is useful because it names platform expectations early. Static validation, fixture archives, notice reviews, and dry-run writers stay separate from build artifacts, app bundles, package publication, host mutation, and endorsement claims.
Each lane states the packaging target, local inputs, and the phrases that must not be used yet.
Spec, deb, changes, and ports metadata checks run before any package build or host install claim.
License, notice, trademark, and generated-artifact review records remain blockers until reviewed evidence exists.
Install and removal validation requires disposable targets, clean snapshots, recovery paths, and operator consent.
Official package, PPA, OBS, notarization, app-store, endorsement, and production installer claims stay false.
Workbench Tie-In
The strongest current path is still local evidence: Panel and CLI surfaces can be inspected, status reports can be generated, and package metadata can be checked without pretending a release artifact exists.
Current Snapshot
These fields summarize the public packaging posture across the current Fedora, Ubuntu, openSUSE, and macOS records.
Platform Lanes
The page groups platform work by the strongest evidence currently present and the claim that still remains blocked.
Static RPM validation and source archive fixtures exist. Install and removal evidence requires a disposable Fedora VM with snapshot, recovery, and consent gates.
Fedora readinessThe local deb draft checks the no-effect CLI payload while release-artifact notices, package notice review, lint/build transcripts, and archive readiness remain blocked.
Ubuntu deb laneopenSUSE records cover local RPM shape, a changes file, rpmlint and osc availability, findings classification, source archive reproducibility, temporary RPM topdir handoff, build-gate blockers, disposable build-environment requirements, payload inspection, install/remove transcript requirements, OBS non-claims, validation promotion blockers, build-evidence intake denial, denial review, denial disposition, denial disposition closeout, denial disposition closeout archive gate, archive gate review, archive gate review disposition, archive gate review disposition closeout, archive gate review disposition closeout archive gate, archive gate review disposition closeout archive gate review, archive gate review disposition closeout archive gate review disposition, archive gate review disposition closeout archive gate review disposition closeout, archive gate review disposition closeout archive gate review disposition closeout archive gate, and archive gate review disposition closeout archive gate review disposition closeout archive gate review before any publication claim.
openSUSE readinessDebian deb, FreeBSD port, and OpenBSD port records remain local-only metadata checks with archive, ports-tree, and package redistribution claims blocked.
Debian static laneThe macOS lane can render writer phases, inspect candidate assets, and block unsafe paths while app bundle writes, signing, notarization, and verification stay disabled.
macOS writer alignmentNo official package, Ubuntu archive package, PPA, Fedora approval, Open Build Service publication, SUSE endorsement, notarized app, or production installer is claimed.
Non-claimsGate Matrix
A package lane can advance only by naming which action is allowed, which target it may touch, and which broader claims remain false.
Read plans, run static checks, inspect source archive fixtures, run notice blockers, and execute no-effect macOS dry-run reports.
Fedora archive fixture checks may create and inspect disposable temporary archives without source RPMs, binary RPMs, installs, or publication.
Fedora RPM install/removal validation requires explicit disposable VM evidence, clean snapshot, recovery path, and operator consent.
Distribution approval, package publication, production installer readiness, root installer readiness, daily-driver readiness, notarization, signing, and platform endorsement.
Local Commands
These commands inspect static package shape, fixture boundaries, and no-effect writer readiness. They do not publish packages or grant install authority.
sh scripts/test-fedora-local-rpm-static-validation.sh
sh scripts/test-ubuntu-local-deb-static-validation.sh
sh scripts/test-opensuse-local-rpm-static-validation.sh
sh scripts/test-fedora-source-archive-fixture-lane.sh
sh scripts/test-opensuse-rpmlint-findings-classification.sh
sh scripts/test-ubuntu-release-artifact-notice-requirements-contract.sh
sh scripts/test-macos-app-bundle-writer-alignment.sh
sh scripts/test-macos-local-candidate-asset-probe.sh
sh scripts/test-macos-dry-run-writer-candidate-integration.sh
Source Records