Skip to content

t1k:unity:tof:platform-layer-adapters

FieldValue
Moduletof
Version3.46.8
Effortmedium
Tools—

Keywords: already exists, analytics, ATT, audio focus, authentication, cloud save, deep links, define gate, FTUE, GDPR consent, greenfield check, haptics, IAP, localization, notifications, OSA, platform layer, purchase restore, receipt validation, recycling scrollview, runtime permissions, save system

/t1k:unity:tof:platform-layer-adapters

Platform Layer Adapters — Interface Index

Section titled “Platform Layer Adapters — Interface Index”

Purpose: stop plans/contracts from specifying “build a save system” / “build IAP” / “build a tutorial framework” when the interface, implementation, and DI seam already ship in the project’s platform submodules.

The structural fact this skill exists for: in a The1Studio Unity project the gameplay library (e.g. Packages/unity-dots-library/) is only half the codebase. Everything else — persistence, cloud sync, IAP, auth, analytics/consent, localization, audio focus, recycling scroll views, FTUE, notifications — lives in Assets/TheOneFeature/, Assets/UITemplate/, Assets/TheOne.FTUE/ and Packages/com.gdk.*. A search scoped to the gameplay library alone therefore reads as greenfield by construction, no matter how carefully it is run.

Sibling caveat — this skill is the cross-source complement to the per-folder tof-* skills. Each t1k-unity-tof-* skill indexes one source folder and, per The1Studio/theonekit-unity#350, is a candidate index rather than an inventory. This skill is the map across the five sources. Neither is authoritative alone — verify against source over a stated scope before concluding absence.

Measured in the originating project (DOTS-AI, 2026-08-06), that layer compiles to 295 TheOne.Features.* DLLs, 26 UITemplate.*, 6 TheOne.FTUE.*, plus OSA.Core.dll in Library/ScriptAssemblies/. Treat the counts as an order-of-magnitude signal, not a constant.

Activate BEFORE writing a plan/contract/wave task that touches ANY of: save/load, cloud sync, IAP/purchase/restore/receipt validation, auth/account linking, analytics, GDPR/ATT consent, localization, audio mute-on-background, a recycling/virtualized scroll view or grid, FTUE/ tutorial masking-gating-tooltips, push notifications, rate-us, no-internet handling, haptics, deep links, or runtime permissions.

The rule this enforces: docs/library-feature-discovery-protocol.md — before declaring any of the above absent, consult references/platform-layer-interface-index.md first. It is the cheapest accurate map of that layer; a bare grep of Packages/unity-dots-library/ will falsely read as greenfield (see History below).

Monetization surfaces (IAP, ads, shop, piggy bank, battle pass) wire through the interfaces already shipping in the project, never a mock, and the user is never asked mock-vs-SDK — SSOT: t1k:unity:tof:iap § “Decision defaults — do not ask”.

  1. references/platform-layer-interface-index.md — concern → interface (seam) → concrete impl → file path table. Every path is grep-verified against source in the originating project (not inherited from a prior summary). Two rows are marked unverified — treat them as open questions, not as “exists” or “absent.”
  2. references/platform-module-inventory.md — the full module inventory across all five platform sources (com.gdk.3rd 51 asmdefs, com.gdk.core 9, TheOneFeature ~90, UITemplate 34, TheOne.FTUE 6), compiled 2026-08-06 from three parallel source passes. Carries the define-gate table — ~20 asmdefs are gated and ~13 were dead in the originating project, so ads, IAP, analytics, remote-config and cloud-save all bound to dummies there. Re-check the define set per project — the gating is what varies between projects, not the code. No tof-* skill mentions a single define symbol, which makes this table the only place that distinction is written down. Read it before concluding a feature “exists.”
  3. references/vcontainer-wiring-precedent.md — the one working example of wiring this platform layer into a DOTS demo (BackpackCrawler), and the pattern to copy for any new demo (TinyTerraces or otherwise).

The two genuine gaps (do not re-litigate these as “found”)

Section titled “The two genuine gaps (do not re-litigate these as “found”)”
  1. No server-side receipt/entitlement authority. Client-side Google Play validation exists (UnityIapServices.IsPurchaseValid()); Apple validation is a deliberate logged no-op ("Receipt validation skipped (Apple validation deprecated in IAP v5)"); nothing verifies entitlement off-device. Building this would sit on top of ICloudFunctionsService / PlayFabCloudScriptHandler — both of which already exist as the plumbing.
  2. None of this is wired into any DOTS demo except BackpackCrawler. Every interface in the index is available, not already running in a given demo. Treat integration as real, budgeted work — see the wiring-precedent doc — never as “already done because the seam exists.”
  • Writing a plan task “build a save/serialization system” — the seam is UserDataManager + builder.RegisterUserData<T>(); the task is authoring IWritableData types, not building storage.
  • Writing a plan task “build/acquire a recycling ScrollView” — OSA 7.2.1 is already resolved (transitively, via com.gdk.core) and has three ready-made adapter base classes. The task is subclassing one adapter per list, not building or acquiring anything.
  • Treating an absent #if X_CLOUDSAVE / #if X_LOCALIZATION scripting define as “the system doesn’t exist” — it means disabled, not unbuilt.
  • Citing a t1k-unity-tof-* skill’s silence as proof of absence. Those skills are auto-generated per-folder type listings of Assets/TheOneFeature/Core/* only — they do not cover Packages/com.gdk.3rd, Packages/com.gdk.core, Assets/UITemplate/, Assets/TheOne.FTUE/, or Library/PackageCache/. A tof-* skill’s silence on a topic is not evidence that the topic is unimplemented (originating evidence: DOTS-AI’s own plans/reports/audit-260803-existing-platform-systems.md § “Why the first audit missed this” — a DOTS-AI-project artifact, not shipped with this kit and not resolvable from a theonekit-unity checkout; see also theonekit-unity#350).
  • Read-only submodules. Assets/TheOneFeature/, Assets/UITemplate/, Assets/TheOne.FTUE/, Packages/com.gdk.core/, Packages/com.gdk.3rd/ are third-party-org submodules per CLAUDE.md § “Submodule Editability” — consume them, never patch them. This is a constraint on editing, not on discovery; “I can’t change it” is not a reason to rebuild it.
  • Transitive packages are invisible to a manifest-and-Assets/ search. OSA 7.2.1 is pulled in transitively by com.gdk.core’s own dependencies and never appears in Packages/manifest.json. Always include Library/PackageCache/ in a platform-layer search.
  • com.the1studio.dots-economy ships Wallet + Energy only — NO IAP. WalletTransactionSource.IAP is an enum value, not an implementation; IAP itself lives in Assets/TheOneFeature/ + Packages/com.gdk.3rd/IAP/.
  • FTUE is Assets/TheOne.FTUE/ (~67 files, masking/gating/tooltips/branching/remote-config), NOT com.the1studio.dots-tutorial (a ~270-line ECS step sequencer — keep it as the ECS-side state holder, bridge it to TheOne.FTUE for presentation).

Written 2026-08-03 in DOTS-AI after a plans/reports/audit-260803-existing-platform-systems.md (a DOTS-AI-project artifact — the path does not exist in this kit) found a prior wave-contract-authoring pass had scoped its search to Packages/unity-dots-library/ only, concluded IAP validation / restore / cloud storage / consent / a recycling scroll-view were all absent, and specified ~1,700 lines of contract (including a whole invented “store-readiness” wave) on that false premise. Owner directive: “for everything besides gameplay we already have a codebase that handles it all — find the right interface to use so we don’t have to keep re-checking.” See also core’s negative-result-scope.md rule (shipped by theonekit-core, not this kit) — a negative result is a claim about your search, not the codebase.