Layered managed settings

How Patterson projects an org chart onto agent configuration, given that the platforms underneath were not designed to carry one.

Source shorthand

Every claim below carries a citation of the form SHORTHAND § section. Anything that no source answers is marked [TBD: not specified in <source>] rather than inferred.

Shorthand	Document
`CC-settings`	`.tmp/staging/docs/claude-code/settings.md`
`CC-marketplaces`	`.tmp/staging/docs/claude-code/plugin-marketplaces.md`
`CC-admin`	`.tmp/staging/docs/claude-code/admin-setup.md`
`CC-server`	`.tmp/staging/docs/claude-code/server-managed-settings.md`
`VSC-enterprise`	`.tmp/staging/docs/vscode/enterprise-ai-settings.md`
`VSC-plugins-norm`	`patterson-platform-docs/references/platforms/vscode/_NORMATIVE-agent-plugins.md`
`VSC-harness-norm`	`patterson-platform-docs/references/platforms/vscode/_NORMATIVE-agent-harnesses.md`
`GHC-precedence`	`.tmp/staging/docs/copilot/response-customization-precedence.md`
`GHC-support`	`.tmp/staging/docs/copilot/custom-instructions-support-matrix.md`
`GHC-cascade`	`.tmp/staging/docs/copilot/policies-concepts-cascade.md`
`GHC-org-instructions`	`.tmp/staging/docs/copilot/org-custom-instructions.md`

Full paths are in Citations. The staged snapshots under .tmp/staging/docs/ and the copies under patterson-platform-docs/references/platforms/ were byte-identical when this document was written; either path resolves the same text.

Source of truth: docs/architecture/layered-settings.md in the patterson-corp repository.