Ordinary web apps: pages, data and simulations that run on your isle's Polari.
13 app(s) match in Polari Apps.
cntfet polari-app
Aligned-CNT FET S1: decomposed one-tube device, clean-room VS-CNFET-derived compact model (first open CNFET compact model) + ToB F2 reference + Verilog-A/OSDI twin. Compute (OpenVAF/ngspice/OpenSTA/kwant) delegates to the cnt-engines worker (dist-1): CNTFET_ENGINES_URL knob, else topology provider cntfet.engines, else local ~/tools.
computelod polari-app
ONE conceptual ladder from C to materials (eleven rungs; die/package hang off microarchitecture through the microchip ladder by design_level_ref), kinds as rows, downward ComputeMappings and upward CharacterizationMappings as evidence-bearing rows, and the compute-lod tech tree of what to learn (plan tt-0).
electrodevice polari-app
Material-derived electronic devices, SPICE cards, circuits/breadboards as rows.
hwdigital polari-app
Logic diagrams as rows -> generated artifacts (iCE40 bitstreams).
hwfpga polari-app
FPGA register maps as data; Verilog/C/testbench artifacts from rows.
magnetics polari-app
Magnetic materials Section A: option catalog with realization ladder, functional role taxonomy (derived viability), theoretical powder designer (MAGNETIC_MATERIALS_PLAN.md).
materials_science library
Legacy registry module (optional, toggleable).
microchip polari-app
Microchip design-level ladder (device -> cell -> block -> core -> chip) + traversal interface. Separable from the device modules: reads cntfet/electrodevice rows softly, imports no device code; absent modules degrade honestly.
motors polari-app
Electric motors Section C: the M0-M3 ladder of buildable samples (Lavet clock stepper -> reluctance -> ferrite-PM -> dual-stator axial flux), clock control-case sim, torque curves, torque_parity (MAGNETIC_MATERIALS_PLAN.md).
pspp polari-app
PSPP foundation: evidence methods, claims-not-values, digitized book datasets + interpolation (PSPP_MATERIALS_PLAN.md).
sifet library
Silicon MOSFETs (planar / FinFET) on thermal and SOL-GEL dielectrics sharing the cntfet VS device contract (states, regimes, scoring, validity, cross-technology ranking), complementary pairs, and silicon refinement routes (MG -> UMG -> SoG -> EG; PV open, EG novel).
tensormath polari-app
Arbitrary-rank tensors as rows with values by reference (a rank-N MatrixDefinition, a DigitizedDataset, an engine state or a PropertyClaim), named dimensions, tensor expressions delegating rank<=2 to the matrix module, operators, and the compute implementations an operator has (plan COMPUTE_LOD_TENSOR_PLAN.md, tt-0).
tensortree polari-app
Rooted, navigable views over tensor state: nodes valid by LOCAL visual coherence (a sim-space binding), typed unresolved spaces anywhere, mappings that may cross branches with two statuses and evidence, selections as mathematical objects, and discovery = hard filters then a configured score (plan tt-0).
The standard installer format on Ubuntu and other Debian-family Linux — the equivalent of a setup file on other systems. Your computer's own Software Install app reads it, shows what will be installed, and asks for your password through the system dialog. Nothing runs until you approve it.
Online is small: it carries the app itself, and the libraries it needs are fetched from the internet when the app is set up — each card lists those libraries and their measured sizes, so nothing downloads invisibly. Offline carries the pip libraries INSIDE the deb (bigger, slower to generate — wheels are fetched at build time), for machines that will have no internet. System engines (e.g. a SPICE simulator) can never ride inside an app deb — they come from the distro's packages or the offline install media, and each card names them.
These debs are not kept on the server — each one is packaged fresh at the moment you ask (analyze shared payload → package module files → write manifest → assemble deb → stream to you), then kept at least three slow-connection downloads long, then only evicted when room is needed, and freed after a day untouched. The wait shown on each card is the median of that app's recorded generation times — measured, never invented.
Pre-prepped files are built ahead of time and sit ready on this server, so the download starts instantly. Generated on demand files are packaged fresh at the moment you ask for them — you wait briefly while the server builds your copy, and the server deletes its copy after delivery instead of keeping a duplicate on disk. Each item on these pages says which kind it is.
When two apps contain identical files, those files are factored into one shared deb both apps depend on, so the content installs exactly once — the installer enforces it. Install the shared deb first; each app card links it when it applies.
Installing an app deb stages its code and data under /var/lib/polari/apps/. The running instance admits staged apps through the dynamic-modules machinery, which is still in review — until it lands, an administrator has to admit the module on the instance manually. This page will say so until that changes; nothing happens invisibly.
Programs install into the system software areas (/usr, /opt) and app data lives under /var/lib/polari. The .deb file you downloaded is only the delivery vehicle — once the install finishes it is safe to delete from your Downloads folder.
← Install Polari itself: the platform installers, online and offline, and the USB stick.