Ecosystem report · September 2026
September 2026: how the DETai ecosystem changed
1 September marked the beginning of DETai’s Public Epoch. The first month of the new era was less about the launch itself and more about learning to sustain a public presence: publishing materials, developing channels, understanding audience response, and connecting all of this to the ecosystem’s architecture.
Read the full reportExplore the report
01 / Signals
Change in numbers
02 / Timeline
Seven milestones
DETai’s Public Epoch began
Public Presence
The public era received a clear starting point, while Sites v1.0 established the ecosystem’s primary web surface.
Public presence became a strategic focus
Management
Audience growth, Storytelling, and Telegram were brought together around one operational goal: a sustainable public presence.
Telegram became a managed working layer
Telegram
Account Manager brought account state, roles, and network profiles into one managed system.
Storytelling 2.0 passed its first real E2E
Storytelling
The new mosaic architecture was validated by a real multilingual Rich publication.
Publications gained a link to Knowledge Substrate
Knowledge
Full Publication gained a stable machine-readable relationship between published materials and relevant knowledge-base documents.
The first Full Publication completed the public cycle
Storytelling
The first material in the new contour reached the site and multilingual Telegram representations.
Territory Ψ Edge became a working edge contour
Infrastructure
Local and World were accepted on real clients, while protected transport gained adaptive path selection.
03 / Sections
What changed
Sites — from launch to the primary public surface
The site became the ecosystem’s primary web surface and the place where public materials acquire a stable form.
- Sites v1.0 was established as the public baseline.
- SEO/GEO, structured data, localization, and media handling were strengthened.
- Representations for other platforms are built from materials published on the site.
Storytelling — publication became a repeatable process
Storytelling evolved from a set of separate publication scenarios into a coherent Publication Core.
- Publication process, destinations, delivery, media, and the operator interface received clearer boundaries.
- The first real multilingual Rich E2E was completed.
- A lifecycle from text and metadata to translations, site publication, and external representations was assembled.
Telegram — from a set of bots to an audience system
Telegram became a separately managed communication contour for DETai.
- Account Manager centralized working accounts, roles, and network profiles.
- Comment Plans and Media Library appeared.
- Storytelling now uses the shared Telegram authorization contour.
Archivarius — audience activity separated from our own
Analytics became better at distinguishing ecosystem-managed activity from external audience response.
- Comments and Audience became separate analytical views.
- Actions by managed DETai accounts can be separated from audience activity.
- A repeatable UX pattern was established for future metrics.
Knowledge Substrate — documentation reflects the architecture more precisely
The knowledge base captures the stable meaning of DETai systems and their relationships, not just files and repositories.
- Dedicated documents were added for Account Manager and publication-to-knowledge relations.
- Infrastructure capabilities, the document model, and the Storytelling description were refined.
- The month-end state was fixed in a separate monthly snapshot.
Territory Ψ Edge — digital architecture entered the physical network
Territory Ψ Edge became a separate physical edge contour inside Home Ψ Lab.
- Dell Wyse was accepted as the permanent edge host.
- Local became an independent user internet contour with dual LTE.
- World received redundant protected paths and fail-closed transport selection.
Responsibility boundaryTerritory Ψ Edge is a personal countryside network within Home Ψ Lab. It is technically connected to the city infrastructure, but is separate from DETai team work.
The main result
September’s main result: DETai moved from “we have entered the public space” to a system capable of sustaining that presence. Sites, Storytelling, Telegram, analytics, the knowledge base, and infrastructure began to work much more clearly as parts of one contour.Read the full report