DITTO · ditto
D23 ledger ruling, canonical. "RESOLVED: Current usage (C) is canonical. DITTO = Verify→Validate→Augment→Disponibilize. Data fetch gateway, API aggregator, capability translator. The original Noology Dictionary etymology 'Device Impersonating Telemetry Transmitter Object' (A/B) was a hardware bridge concept that has evolved — the modern DITTO subsumes it (a hardware bridge IS a kind of capability translation)." [src: HOS-Webdoc/web/src/data/hos-specification.ts:445]
Content
The DITTO is the fetch/translation gateway of sapiens3: "Fetch/translation gateway. Flow: Verify -> Validate -> Augment -> Disponibilize. Also discovers and translates capabilities." [src: wiki/GLOSSARY.md:991] It is level 2 of the 8-level mobilizer-level ladder (BOT < DITTO < DOOIT < …, D1) [src: HOS-Webdoc/web/src/lib/sapiens3/types.ts:27] and one of the 6 datan archetypes.
Runtime stage sequence: Verify → Validate → Augment → Disponibilize [src: HOS-Webdoc/web/src/lib/sapiens3/ditto-gateway.ts:8] — the same 4-step pipeline the pad Gateway runs [src: HOS-Webdoc/web/src/lib/cland/pad-engine.ts:22], which is why the DITTO is the natural server of PAD Gateways. Petra rule K002 (petra): any fetch goes through DITTO. [src: wiki/development/HANDOFF.md:68]
OWNER-2026-07-10 additions (canonical):
- Serves pads: "…DITTOS (API Gateway for the PADs)". [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:550]
- Knowledge role: "Knowledge Analyst - DITTO". [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:553]
- Functional-declarative usage: "RAG, GatewayAPI, Cache - DITTO" — retrieval-augmented generation, API gateways and caches are all read as DITTO work. [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:561]
In the squad approval chain, DITTO holds the success-manager position (DOOIT→ASSISTANT→DITTO→MAESTRO→ADVISOR). [src: wiki/GLOSSARY.md:205] In the Master-Doc 6-level view of the entity-hierarchy, BOT/DITTO are replaced by construct (D26) — the 8-level ladder remains the canonical union.
Variants
| # | Definition (verbatim) | Source | Ruling | Status |
|---|---|---|---|---|
| A/B | "Device Impersonating Telemetry Transmitter Object" — "a hardware bridge concept" | Noology Dictionary, quoted in [src: HOS-Webdoc/web/src/data/hos-specification.ts:445] | D23 → historical only; subsumed by C ("a hardware bridge IS a kind of capability translation") | deprecated |
| C | "DITTO = Verify→Validate→Augment→Disponibilize. Data fetch gateway, API aggregator, capability translator." | [src: HOS-Webdoc/web/src/data/hos-specification.ts:445] [src: HOS-Webdoc/web/src/lib/sapiens3/ditto-gateway.ts:8] | D23 → canonical (current usage; ditto-gateway.ts is source of truth) | canonical |
Composition
- uses: Redis cache in the augment stage [src: wiki/GLOSSARY.md:2483], loop (Datan Loop escalation DOOIT/DITTO/Assistant + DSync, D18)
- used-by: pad (its API Gateway), squad (success-manager in the approval chain), dooit (fetches what DOOITs execute on), cognitive-loop
See also
- dooit · assistant · bot · construct · mobilizer-level · entity-hierarchy
- [Cognis & Kernels](../../../wiki/engines/cognis-and-kernels.md)