Settings
Company, appearance and platform configuration.
Conflicting contributions
Two extensions claim the same id. The first in activation order keeps it; the other does not load.
acme-pipeline.forecast(widgets) — claimed by acme-pipeline, rival-forecast
| Extension | Kind | State | Status | |
|---|---|---|---|---|
| Acme Pipeline | HQ App | active | Running. | |
| Rival Forecast | HQ App | active | Running. | |
| Overreach Analytics | HQ App | active | Running. | |
| Future Suite | HQ App | incompatible | Requires Foundation >=2.0; this platform runs 1.0.0. | |
| Flaky Reports | Add-on | degraded | Its interface did not respond in time. | |
| Paused Connector | Integration | company disabled | Switched off for this company. | |
| Quarantined Tools | HQ App | ottili disabled | Disabled pending a security review. | |
| Ottili Insights | First-party | active | Running. |
Last activation pass
3 of 8 extensions mounted their contributions.
paused-connector— Not in a state where it can run.future-suite— Not in a state where it can run.overreach-analytics— “admin.impersonate” is not a permission an extension may request.quarantined-tools— Disabled by Ottili.rival-forecast— Contributed ids must start with “rival-forecast.”.
Install review
Run by the shipped validator over each manifest. A manifest that fails here is never installed.
| Extension | Manifest | Compatibility | Findings |
|---|---|---|---|
| Acme Pipeline | valid | compatible | — |
| Rival Forecast | rejected | compatible |
|
| Overreach Analytics | rejected | compatible |
|
| Future Suite | valid | incompatible |
|
| Flaky Reports | valid | compatible | — |
| Paused Connector | valid | compatible | — |
| Quarantined Tools | valid | compatible | — |
| Ottili Insights | valid | compatible | — |
Live contribution registry
What actually mounted after the activation pass above. An extension missing from this table is not contributing.
| Kind | Id | Owner |
|---|---|---|
| Widget | ottili-insights.health | ottili-insights |
| Widget | flaky-reports.summary | flaky-reports |
| Widget | acme-pipeline.forecast | acme-pipeline |
| Command | acme-pipeline.sync | acme-pipeline |
| Route | acme-pipeline.home | acme-pipeline |
| Navigation | acme-pipeline.nav | acme-pipeline |
| Settings section | ottili-insights.section | ottili-insights |
Where these come from
In a product, GET /api/v1/foundation/extensions serves this from platform.foundation_extension_installations.
- The backend now has a real installation table, company-scoped, with an append-only audit log alongside it — so “who disabled this, and when” has an answer.
registry_availablereports whether the registry could be read, not whether anything is installed. An empty company and a registry outage are different things and must not look the same.- The kill switch is a column rather than a state value, because SoT §33.4 makes it an override: it has to survive a company re-enabling the extension, an update, and a restore from backup.
- The Lab reads its eight demonstration extensions from a local fixture rather than that table, so this page works without a database. The runtime driving it is identical.
How to read this
Each demonstration extension lands on a different outcome of the real runtime.
- Acme Pipeline — activates cleanly and registers four contributions.
- Rival Forecast — claims a widget id Acme Pipeline already holds, so it is refused and rolled back entirely.
- Overreach Analytics — its manifest requests a permission the platform will not grant.
- Future Suite — built against Foundation 2; this platform runs 1.
- Flaky Reports — mounted but degraded; still contributes, with the reason stated.
- Paused Connector — switched off by this company, and re-enablable.
- Quarantined Tools — stopped by Ottili. A company administrator cannot re-enable it.
- Ottili Insights — first-party and bundled, so it activates ahead of every third-party extension.