Milestones

DASD was established and registered in Georgia in 2012, beginning as a small LLC.

GlobSynk did not exist at this point, and would not for well over ten years. This entry records DASD's own history, which the milestones that follow trace forward from.

After the Founder later moved to Silicon Valley, California for business, DASD was registered with the California Secretary of State in 2016 and began operating from Silicon Valley.

This was a later chapter of DASD's history, not its founding — DASD had already been established in Georgia in 2012. DASD remains active, with continuing operations and connections associated with both Georgia and California.

In 2024 discussions and preparation began around transitioning the earlier DASD direction toward what would become GlobSynk.

Nothing had been formed yet. What existed was a direction under consideration, which moved into active formation the following year.

In early 2025 the earlier technical direction associated with DASD began evolving toward something broader than what came before.

This was not yet a company, and not yet the platform. It is recorded here because the work that followed does not make sense without it.

Through 2025 the formation work continued, and the direction widened from its earlier engineering focus toward the needs the platform now addresses: individuals, organizations, and work shared between people and AI-enabled digital workers.

No company had been registered at this point. What existed was a settled direction and the groundwork for it.

GlobSynk was formally established as a company in 2026. The distinction matters for anyone reading this record: the idea and the formation work began in 2025, and the company dates from 2026. Neither statement should be read as the other.

The earlier DASD work informed the direction that became GlobSynk. This history should not be read as making a claim of legal continuity, succession, merger or acquisition between them.

On 22 August 2026 GlobSynk adopted a written governance rule covering how existing platform capability may be changed. The short version: capability is preserved by default, and the fact that something looks unused is not a reason to remove it.

It sounds like a small administrative matter. In practice it is the rule that decides whether a platform stays coherent as it grows. Software teams remove things constantly — a field with no obvious caller, a route nobody seems to hit, an older path that a newer one appears to replace. Most of the time that is tidy and correct. Occasionally it removes something a customer, an integration or a future product depended on, and the cost only becomes visible much later, when the reasoning behind the original decision is gone.

The rule requires that a removal be explained before it happens: what the thing does today, what depends on it, what stops working, whether the change can be undone, and what the alternatives to removing it are. If that case cannot be made, the capability stays. Where two instructions conflict and the conflict is unresolved, the default is to preserve and escalate rather than to pick the more convenient reading.

We are recording it publicly because it is a commitment about how we treat things other people may be relying on, and a commitment that is only made internally is easy to quietly drop.

In September 2026 GlobSynk published its canonical institutional record — the story behind the platform, the development journal, the acknowledgments and these milestones — maintained as a public record rather than as a campaign.

It is a modest thing to mark. It is here because the alternative, a company whose history exists only in private, is the thing this site was built to avoid.