@@ -379,16 +379,18 @@ The `single` anchor's own disposition is #11979's (Choice 4B), which this record
379379
380380** Spelling note (2026-10-11, #22831 ).** The second install mode is spelled ` unmanaged ` : the maintainer's
381381ruling ** B** on [ #15213 ] ( https://github.com/objectstack-ai/objectstack/issues/15213 ) (record ` 6108509158 ` ,
382- 「同意」, 2026-10-11). This record was accepted spelling it ` template ` ; the value now reads ` unmanaged ` in
383- this paragraph, in D2's install-mode sentence, in §6's record of the accepted install-mode question and in
384- §8's C12 row. Why: it is the industry's name for this mode — Salesforce's unmanaged packages and Power
385- Platform's unmanaged solutions, both already in [ ADR-0086] ( ./0086-authz-metadata-config-boundary-and-cross-package-composition.md ) 's
386- comparison; ` managed ` and ` unmanaged ` are the two states of one property, whether the package stays the
387- authority; and ` template ` already names other things in the code — the scaffold manifest
382+ 「同意」, 2026-10-11) and, for the bullet label below, the maintainer's decision ** B** on #22831 (record
383+ ` 6109891008 ` , 2026-10-11). This record was accepted spelling it ` template ` ; the value now reads ` unmanaged `
384+ in this paragraph, in the ** Unmanaged** bullet label below, in D2's install-mode sentence, in §6's record of
385+ the accepted install-mode question and in §8's C12 row. Why: it is the industry's name for this mode —
386+ Salesforce's unmanaged packages and Power Platform's unmanaged solutions, both already in
387+ [ ADR-0086] ( ./0086-authz-metadata-config-boundary-and-cross-package-composition.md ) 's comparison;
388+ ` managed ` and ` unmanaged ` are the two states of one property, whether the package stays the authority; and
389+ ` template ` already names other things in the code — the scaffold manifest
388390(` TemplateManifestSchema ` ), the ` email_template ` metadata type and the ` os init ` templates. ⛔ Only the
389391spelling moves: the copy-once import, full editability, no upgrade channel and the refusal on ` group ` /
390- ` isolated ` stand as decided. The rest of this record's prose — the ** Template ** bullet below , "template
391- package", "template import", "template install mode" — is kept as written and names this same mode.
392+ ` isolated ` stand as decided. The rest of this record's prose — "template package" , "template import",
393+ "template install mode" — is kept as written and names this same mode.
392394
393395- ** Managed** (default). The package is registered into the registry as code. ** No door edits a managed
394396 definition** — not Setup, not Studio, not the data or metadata API; to change one, the vendor publishes a
@@ -409,7 +411,7 @@ package", "template import", "template install mode" — is kept as written and
409411 - ** E — extend** (` object ` , ` app ` ): fields, validations, navigation arrive as a package.
410412 Managed is the ** only** mode a shared-DB multi-tenant deployment (` group ` / ` isolated ` ) accepts, and every
411413 regime there is environment-wide and operator-gated — a plant admin neither overlays, switches nor clones.
412- - ** Template .** The package's metadata is copied ** once** into the environment definition ledger as
414+ - ** Unmanaged .** The package's metadata is copied ** once** into the environment definition ledger as
413415 environment-provenance items — from then on it is the environment's own metadata, editable in Studio like
414416 anything authored there, with no upgrade channel (a later version is a new import, refused where names
415417 collide; provenance recorded for information only). ⛔ ** Refused on ` group ` / ` isolated ` ** with a message
0 commit comments