{ "schemaVersion": 1, "baseline": "config/scale/feature-shape-growth.json", "ceilings": { "contextMaxFeatures": 200, "appMaxContexts": 20 }, "summary": "The ceilings bound the count; they are not a verified capacity. The practical limit of one app is the initial JavaScript budget, then typecheck memory. 400 features were not measured (D-18 makes it optional).", "axes": [ { "axis": "Typecheck of one app", "verified": "Linear, about 117k instantiations and 36 MB of tsc memory per feature, up to 100 features", "condition": "Reference-shaped features, tsconfig.app.json, the host recorded in the baseline", "notVerified": "200 features (one full context) and beyond; 4,000 (20 x 200) would need on the order of 150 GB by the same slope" }, { "axis": "Production build", "verified": "Completes at 100 features in seconds", "condition": "Same", "notVerified": "Beyond 100" }, { "axis": "Initial JavaScript", "verified": "15-01: only each feature's declaration (route table, messages, invalidation identities) loads at boot; its runtime half loads with its routes. Baseline: 203,816 B with no copy, about 610-630 B and no extra file per copy (219,508 B at 25, 264,841 B at 100; before 15-01: +3,922 B per copy). tests/unit/feature-shape-growth.test.ts keeps one copy at or under 1 KiB", "condition": "Same; the feature-declarations and feature-platform chunk groups in vite.config.ts", "notVerified": "The initial budget (204,800 B, config/performance/budgets.json) leaves 2,291 B over the baseline's 202,509 B, so about three more reference-shaped features fit at about 610 B each: the platform itself is 98.9% of it" }, { "axis": "Lazy JavaScript", "verified": "About 8.5 KB gzip and eight files per feature, every file far below the 120 KiB lazy-chunk budget", "condition": "Same", "notVerified": "Download cost of many lazy files" }, { "axis": "Routes", "verified": "4 per feature, composed without conflict", "condition": "Same", "notVerified": "Router matching cost at runtime" } ] }