conceptcanonicalC-02D4OWNER-2026-07-104 variants

POD · pod

Owner directive (2026-07-10), canonical for the device sense. "The PAD with the Platform Augmenting Data to be used by Procedural Operational Devices (Components, transitions, Interaction)." — the newest dated owner prompt fixes the device-sense expansion as Procedural Operational Device. [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:457]

Content

A POD is the content surface inside a pad, served by a WebService: "processing/output surface inside a PAD — served by a WebService" [src: wiki/engines/cognis-and-kernels.md:55]. "PODs hold logic/views" — forms, tables, charts, timelines, kanban — while pads hold data. [src: wiki/development/HANDOFF.md:51] [src: wiki/development/REQUIREMENTS.md:44]

The acronym has two canonical senses on two axes (mirroring the IS/DOES pattern of dooit/ditto):

  1. UI-card sense — "Processing Output Display" (C-02): the content card living inside a PAD. [src: wiki/development/HANDOFF.md:134]
  2. Device/execution sense — "Procedural Operational Device (Components, transitions, Interaction)" per OWNER-2026-07-10, superseding the older spellings "Procedural Operating Device" (code/D4) and "Procedural Operator Device" (legacy knowledge-base). Newest dated owner prompt wins the expansion per authority precedence.

Canonical FUNCTIONAL definition (code). A PODDefinition = platform (card + morph), an ordered operatingSequence of OperatingSteps (each carrying "the official optimal method"), and a device config of type app | site | docs | social. [src: HOS-Webdoc/web/src/lib/cland/types.ts:27] [src: HOS-Webdoc/web/src/lib/cland/types.ts:47] Constructors createAppPOD / createSitePOD / createDocsPOD / createSocialPOD bind the device stacks. [src: HOS-Webdoc/web/src/lib/cland/pod-engine.ts:40]

Per D4: "A POD contains algorithm/logic but NO data — it is a lens. Inside the POD lives the dooit. PODs slide OVER PADs to create execution (the Overlay Mechanic)." [src: HOS-Webdoc/web/src/data/hos-specification.ts:525] The members serving PODs are dooits: "The meembers are DOOITS (Agentic Execution, webservicing, triggers) for the PODS and DITTOS (API Gateway for the PADs)". [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:550]

Variants

#Definition (verbatim)SourceRulingStatus
A"POD acronym (C-02) | Processing Output Display — the content card inside a PAD. ('Procedural Operating Device' only in the execution-sandbox sense.)"[src: wiki/development/HANDOFF.md:134] [src: wiki/development/REQUIREMENTS.md:226]C-02 → canonical for the UI-card sensecanonical
B"PODs (Procedural Operating Device)" / D4: "POD = Procedural Operating Device (also known as 'Functional Card' or 'Tool Card')"[src: HOS-Webdoc/web/src/app/page.tsx:83] [src: HOS-Webdoc/web/src/data/hos-specification.ts:525]execution-sandbox sense per C-02; expansion wording superseded by D (OWNER-2026-07-10 "Operational"), substance (lens, no data, Overlay Mechanic) retainedvariant
C"POD (Procedural Operator Device)"[src: knowledge-base/INDEX.md:18]legacy knowledge-base spelling; superseded by A/Ddeprecated
D"Procedural Operational Devices (Components, transitions, Interaction)"[src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:457]OWNER-2026-07-10 → newest dated owner prompt wins the device-sense expansioncanonical

Composition

  • uses: dooit (lives inside the POD; agentic execution, webservicing, triggers), WebService runtime (cogni of CodeLand), morph/glass card (petra K003)
  • used-by: pad (PODs compose inside / slide over PADs, REQ-CLAND-08/12), districts (environments hold pods[] [src: HOS-Webdoc/web/src/lib/cland/types.ts:101]), spatial-site ("maybe now convertions from PADs PODs with more PADs over and even efficient PODs, such as html5 or whatever is lighter" [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:459])

See also

Linked from — 23 cards