Canonical position
Keewo is a governed enterprise application platform that uses Managed Authoring to turn requirements, bug reports, and change requests into inspectable full-stack applications: Vue 3 frontend and Express backend, both TypeScript.
What Keewo is
- Governed enterprise application platform: managed specifications materialize into Vue 3 (frontend) + Express (backend) TypeScript applications
- Model-driven framework with XML parser, expression engine, scope manager, function registry, and module resolver
- 9 module types per feature: data, logic, UI, security, tests, themes, i18n, imports, overrides
- 16 canonical managed-project patterns, with core and extended demo bundles for the mature path
- AI assists in one bounded draft step; Managed Authoring, review, checks, approval, and promotion govern the result
What Keewo is NOT
- Keewo is not an AI coding agent
- Keewo is not an AI workflow orchestrator
- Keewo is not a low-code platform with a proprietary runtime
- AI plays one bounded role: drafting structured source material. Review, materialization, testing, approval, and release remain governed steps
Output stack
- Frontend: Vue 3 with TypeScript, vue-router, Vite build
- Backend: Express with TypeScript, Prisma ORM
- Module format: declarative XML (not code, not templates)
- Managed source format: reviewable structured specifications
- Provenance: hash-verifiable records that connect generated output to governed source material
- Generated code is standard TypeScript on standard frameworks — no proprietary runtime, no lock-in
Core architecture
- XML parser and validators process declarative module definitions.
- Pratt expression parser and expression evaluator handle runtime logic.
- Hierarchical scope manager resolves variables across $screen, $input, $output, $local, $auth, $tenant, and more.
- Function registry supports built-in and module-defined functions.
- Module resolver with import graph, topological sort, and override application.
- Managed Authoring provides a governed source of truth for generated delivery paths.
- Features produce inspectable modules plus hash-verifiable provenance.
- The framework compiles these modules into Vue 3 + Express TypeScript applications.
Intent-to-delivery flow
- Feature requirements
- AI-assisted draft where useful
- Managed registry review
- Materialized modules and runtime output
- Quality evidence and readiness review
- Human approval, promotion, and release
Governance specifics
- AI-assisted drafts are checked for required model coverage, valid identifiers, and preserved localization intent
- Pattern rules validate structure before materialization
- Quality evidence covers validation, tests, business rules, workflow checks, migration safety, and authoring gates
- Drift detection compares governed output with the promoted source model
- Provenance connects generated output to governed source material and approval state
Important definitions
- Glass-box development means the system is inspectable across managed specifications, modules, generated artifacts, and release controls.
- Managed Authoring is the governed source-of-truth path for scalable generated delivery.
- Unmanaged modules are XML-first and allow direct edits when teams need an escape hatch.
- Human-governed means AI can assist, but humans remain accountable for review, acceptance, and release.
- Logic Bill of Materials (LBOM) means generated features carry provenance that connects output to governed source material.