A foundation for software you own.

01 / The problem

The problem

Content applications need a model, clear permissions and a publishing process that fits their work. I am building Waaseyaa so those foundations can be reused in software people own and host themselves.

02 / Constraints

Constraints

Package boundaries must be explicit. Applications need predictable persistence, access control and extension contracts, with support claims tied to evidence.

03 / My contribution

My contribution

I develop the framework architecture, package contracts and application integrations, including the foundations used by GoFormX. I also build and operate waaseyaa.org as a working Framework application.

04 / Decisions & tradeoffs

Decisions & tradeoffs

Framework is the reusable engine, delivered through Composer packages. Studio is a separate open-source builder distribution that composes it. Applications can use Framework independently, with explicit access rules and publishing contracts. The S1 profile targets one application node with an authoritative local SQLite database.

05 / What is demonstrated

What is demonstrated

Waaseyaa.org runs alpha.305 and publishes Git-authored content through HTML, Markdown and read-only MCP. Its developer-first site connects a four-part build guide, a tested Todo walkthrough and curated framework documentation. The October 4, 2026 deployment passed all 27 public smoke checks.

06 / Limitations & current work

Limitations & current work

Waaseyaa remains alpha. The website deployment demonstrates one application, not universal production support or a completed Studio builder journey. The homepage Fieldnotes interaction is a browser-only simulation; the Todo walkthrough is the maintained starting point.

Explore the project

Framework/Studio product boundaries and waaseyaa.org deployment verified October 4, 2026.