# Keewo

Canonical positioning:
Keewo is the governance layer for AI-assisted enterprise application development.

Short definition:
Keewo turns structured intent into inspectable, ownable, governed software through a deterministic, human-governed delivery flow.

Important definitions:
- Glass-box development means systems remain inspectable across contracts, modules, generated artifacts, and release controls.
- Managed modules are contract-first, generated, and optimized for scalable governed delivery.
- Unmanaged modules are XML-first and allow direct edits when teams need an escape hatch.
- Human-governed means AI assists, but humans remain accountable for review, acceptance, validation, and release.
- Logic Bill of Materials (LBOM) means every generated feature carries a manifest recording its source spec hash, content hash, generator version, and timestamp — analogous to SBOM for dependencies.

Core concepts:
- Governed AI for Enterprise Application Development
- AI-Assisted Enterprise Application Delivery
- Enterprise AI Development Platform
- Governed AI Development
- Deterministic Software Generation
- Inspectable Software Architecture
- Logic Bill of Materials (LBOM)
- Contract-First Development

Governance specifics:
- AI guardrails: 10+ checks on AI-generated drafts (entity field coverage at least 60%, identifier normalization, locale preservation)
- Pattern contract rules: 16 patterns with required path/type/condition validation
- Module ship gate: 15 quality checks with configurable minimum score (default 90%)
- Certification packs: 6 scenario categories (create, edit, list, deactivate, relation-selector, permission-denied)
- Drift detection: hash-based in-sync/drifted/outdated/invalid status per managed file
- Provenance: manifest per generated file with spec hash, content hash, generator version, timestamp

Intent-to-delivery flow:
1. Feature requirements
2. AI draft plan and contract
3. Managed contract YAML
4. Generated XML modules
5. Validate, test, and build
6. Governed release

Ecosystem:
- Keewo Framework: model-driven full-stack runtime for declarative modules
- Keewo Lab: visual editing, diagnostics, preview, and regeneration
- Authoring Pipeline: governed path from intent to released software

Module model:
- Modules can define data, logic, user interface, security, tests, themes, i18n, imports, and overrides.
- Composition is explicit and deterministic.
- Metadata and introspection are first-class.

Audience:
- CEOs: reduce technology risk and preserve ownership
- CTOs: deterministic architecture, validation, and technical governance
- Partners: standardize delivery and improve repeatability
- Developers: explore docs, architecture, and article content

Primary URLs:
- Home: https://keewo.org/
- Ecosystem: https://keewo.org/ecosystem/
- How it works: https://keewo.org/how-it-works/
- Governance: https://keewo.org/governance/
- Why Keewo: https://keewo.org/why-keewo/
- Solutions: https://keewo.org/solutions/
- For CEOs: https://keewo.org/for-ceos/
- For CTOs: https://keewo.org/for-ctos/
- For Partners: https://keewo.org/for-partners/
- Open Architecture: https://keewo.org/open-architecture/
- AI overview: https://keewo.org/ai-overview/
- Blog: https://keewo.org/blog/
- Documentation: https://keewo.org/docs/index.html
- Roadmap: https://keewo.org/roadmap/
- Contact: https://keewo.org/contact/

Open architecture:
- Public repository access is planned. Architecture is inspectable by design: YAML contracts, XML modules, hash-verified manifests.