Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/adr/0126-packaged-metadata-customization-model.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
# ADR-0126: The platform customization model for packaged metadata — three regimes, one activation ledger

**Status**: Proposed (2026-08-25) — awaiting the maintainer's hand-merge, which is itself the
**Status**: **Superseded** (2026-09-04) — maintainer ruling, verbatim and untranslated: 「ADR-0126 可以先作废」「相关开发撤回」. The regimes below (overlay, disable + clone) are replaced by the package **install mode** decided in the total-organization-ownership record proposed in PR #14976: *managed* = sealed, upgradeable, the only mode a shared-DB multi-tenant deployment accepts; *template* = copied once into the environment ledger, fully editable, no upgrade channel. The activation ledger and the packaged-flow / packaged-action disable and clone machinery (#12185, #12190, #12296, #12348, #12419, the framework half of #12491) landed after the 17.2.0 tag and are **reverted before 17.3** — never released. Regime E (extend) stands because an extension is itself a package. Kept as the record of the survey; §1.7 of that record summarizes its findings. Original status line follows.
**Original status**: Proposed (2026-08-25) — awaiting the maintainer's hand-merge, which is itself the
acceptance act for a governed surface (Prime Directive #14) **and the ruling that settles the
tentative flow-instance directions in §7** (chartered on
[#12049](https://github.com/objectstack-ai/objectstack/issues/12049); ⛔ none of §7 is settled
Expand Down
Loading